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

Odin (fail! auth) Note 4 SM-N910P

A month ago I needed to get an extra Note 4 I had back to 5.0.1, it was on 5.1.1. I flashed it in Odin everything worked perfectly, rooted it, phone works great. A bout 2 weeks ago, I helped someone out that needed a phone temporarily, so I let them borrow it being the phone is unlocked. The person reset the phone and updated it before giving it back to me, they thought they were being nice because I let them borrow the phone. I wasn't mad but the unlock went away, no big deal, but now I can't get it off 5.1.1, and back to 5.0.1. I tried 4.4.4 and 5.0.1 a few times now Odin keeps giving me a fail. Here is what I have done:
-Tried both Odin 10.6 & 10.7 (use as admin)
-Tried 4.4.4 and 5.0.1
-There is no Google account on the phone
-Reactivation lock is off
I had flashed this phone and 2 other same model without any issues. Like I stated I have done this a few times on the SM-N910P, not to mention I'm not an expert but have been rooting and using Odin for a few years. Any help would be greatly appreciated, and I will answer any questions as far as what I did. I'm not looking for the fix to be spoon fed to me, but maybe some other options I should look at.
"long time listener, first time caller"

If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7 shouldn't be attempted.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk

Thanks for the quick reply
samep said:
If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened

Alex215 said:
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened
Click to expand...
Click to collapse
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk

samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I left the phone at the shop and will be picking it up tomorrow to try to figure it out. I have a feeling it was updated beyond the OB7, I will use PhoneInfo to verify the current bootloader.

Bootloader version...
samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.

Alex215 said:
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.
Click to expand...
Click to collapse
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk

Thanks
samep said:
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...

Alex215 said:
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...
Click to expand...
Click to collapse
I just can't understand why it won't at least allow me to return to the stock firmware.

Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you trying to get your MSL? Or UICC unlock?

Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk

samep said:
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.

ianmb said:
Are you trying to get your MSL? Or UICC unlock?
Click to expand...
Click to collapse
MSL

Alex215 said:
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.
Click to expand...
Click to collapse
Presently, the only tars that will restore are OJ6 OK1. OK1 is on Sammobile now.
Sent from my SM-N910P using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
Alex215 said:
MSL
Click to expand...
Click to collapse
MSL doesn't change. If you had it before, it still works. If not, there is a galaxy tools version that still works. If your phone is paid in full, Sprint will release it in chat session.
Sent from my SM-N910P using Tapatalk

[ROM] [N910PVPS4COK1] [100% Stock, Root, Odexed&Deodexed, No KNOX/Itson] [12/15/2015]

[ROM] [N910PVPS4COK1] [100% Stock, Root, Odexed&Deodexed, No KNOX/Itson] [12/15/2015]
Once again I bring to you two completely stock builds of Android TW-Lollipop 5.1.1 (N910PVPS4COK1) for the Sprint Samsung Galaxy Note 4.. Both ROMs are built from the official Samsung tar ball. The ROM will self root upon flash and it has init.d/busybox support. Knox and Sprint Itson has been removed. Both ROMs are completely stock with all of the original factory installed apps. Available in odexed and deodexed. Both ROMs are identical other than one being odexed and the other deodexed. Also included in both ROMs in this thread is the stock OK1 modem and APN patch to ensure you have the latest modem & APN's from the latest OK1 software.
Other than the removal of Knox and Sprint Itson, these roms are 100% stock in every other way. They are stock and will stay that way. Please don't ask for mods, changes, etc in this thread. These roms are intended for those people who want the stock roms in their original form with the addition of root and removal of Knox & itson, as well as other members who need a good solid base for their rom projects. I give permission for other dev's to use this rom as your base ONLY if you contact me prior to using it. If I find users using my work without proper credits I will report you and make you look like a fool I promise. Do the right thing and give credits to people for their time and work. It's a curtesy and respect thing nothing more. With that said, I highly recommend other rom chef's/dev's to use this base rom because it is bug-free and built from the official Samsung tar ball. Last but not least, if you appreciate my work please press that Thanks button, rate this thread and consider a kind donation! Enjoy!
Mods and fixes will be in post #2 below.
Important Notes: Before flashing ANY Lollipop 5.1.1 TW-based ROM, including this one, you MUST first do one of the following:
1. Take the Lollipop OK1 ota update on your phone. (Start by being on the stock unrooted OJ6 rom then take the OK1 ota update)
2. Odin flash the stock OK1 rom tar using odin on your PC. Thanks @samep
http://forum.xda-developers.com/showpost.php?p=64337077&postcount=115
Once you have correctly updated your Note 4 to Lollipop 5.1.1, software version N910PVPS4COK1 DO NOT... I repeat, DO NOT attempt to root your phone with CF-auto root or other methods. It will soft brick your phone. Instead, you ONLY need to flash the latest TWRP recovery using odin on your pc. Nothing else. The ROM zip will automatically root your phone.
If you are still on any KK or Lollipop 5.0 TW-based ROM such as NIE, NK2, OB7, OE1 , OF5, OB7 or OJ6 (including any KK AOSP/CM-based roms) then you MUST first update to Lollipop 5.1.1 OK1 by one of the two methods I mentioned above BEFORE flashing this ROM. Failure to properly update your device partitions to 5.1.1 OK1 firmware absolutely WILL cause problems. You have been warned. Please don't ask for help if you did not follow my simple instructions and warnings.
Flashing instructions: ***Before beginning the flash/setup process MAKE SURE your battery has at least 50% charge and/or connected to the charger!!!***
1. Backup anything you don't want to lose off your internal and external storage to another location just to be safe.
2. Download the rom using your pc. (downloading with your phone has a much higher risk of file corruption. Not recommended with large files).
3. VERIFY the MD5!!! Once the download has finished, compare the androidfilehost MD5 using a MD5 tool on your pc. (Google "md5 checksum windows") for a good MD5 tool for your pc.
4. Put the downloaded rom onto your internal storage or external micro sd card.
5. With phone powered off, reboot into recovery by pressing and holding volume up, power and the home button until you see the Samsung logo then release all buttons.
6. Once in recovery choose the wipe button and do a factory reset three times. Optional but recommended is to wipe "Data". This will wipe all of your user data such as google accounts so MAKE SURE you backed up first like I said in step #1 above! Next go to "advanced wipe" and select all of the partitions EXCEPT micro-sd card and internal storage. Internal storage is optional but recommended when first updating to a major software revision such as 4.3 to 4.4 or 5.0.1 to 5.1.1. The reason is to remove left-over data from previous version of Android and start with a clean slate.
7. Choose the "Install" option and select the rom "Sprint_Stock_N910PVPS4COK1_XXX" from either your internal or external micro-sd card. It will flash the rom and give a confirmation once completed.
8. Press "Reboot" then "reboot system". You will get a prompt warning about not having root. Please IGNORE IT and DO NOT allow TWRP to apply root! If you do then you MUST wipe everything and start over at step 5 above and reflash the rom in order to get rid of the traditional root system binaries. ***Please pay attention and DO NOT let TWRP install root. Ignore the "No Root" warning.***
9. Initial rom "optimization" will take several minutes for the deodexed rom while ART builds its cache (the odexed rom takes much less time for first boot). The phone will remain on the yellow Sprint Spark screen for about 10 -13 minutes during this time. Let the phone optimize for at least 13 minutes (for the deodexed rom) and the screen will eventually turn off or show the setup wizard once it finishes. When the screen turns off, simply turn it on and proceed to setup your phone.
10. Once finished with the setup wizard, wait a few moments and the phone will automatically install the Sprint apps. You must either "accept" or "disagree" with each and every google prompt for these apps or else the installs pause until you do so.. Also you will be prompted for the "connections optimizer". Quickly set it to what you want and close it. That's it! You're done!
One last bit of important information... If you allow any system update or Samsung security update to install it WILL break root. I advise everybody to disable automatic updates which is located in Settings/System update.
You can allow an update to install but you will then need to flash the beta systemless SuperSU packages located in HERE in order to regain systemless root.
Credits:​@Chainfire for root and SuperSU. Without him we would not have root. Thank you!​@TeamWin for TWRP recovery. http://teamw.in/project/twrp2 and here​
General disclaimer:​flashing anything on your device is done at your own risk. There is no way myself or any other developer can guarantee that flashing this ROM or any other file will not brick your device or otherwise cause some other type of damage. This is just a standard warning. I am not responsible for anything that you do to your device. However, all of my roms, mods, etc are pre tested by myself and other testers prior to public release.
Sprint_Stock_N910PVPS4COK1_Odexed​Sprint_Stock_N910PVPS4COK1_Deodexed​
XDA:DevDB Information
Stock-Rooted-N910PVPS4COK1, ROM for the Sprint Samsung Galaxy Note 4
Contributors
tx_dbs_tx
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N910PVPS4COK1
Based On: SPR-N910PVPS4COK1-20151209172046
Version Information
Status: Stable
Stable Release Date: 2015-12-15
Created 2015-12-16
Last Updated 2015-12-16

Mods & Fixes​---------------------------------------------------------------------​Odexed-Deodexed-N910PVPS4COK1-Hotspot-Mod (This can be flashed on odexed or deodexed OK1 roms)
N910PVPS4COK1-PrivateMode-Fix (This can be flashed on odexed or deodexed OK1 roms)

Reserved

Thanks tx. I'll take the update in the morning, and flash this. We appreciate all that you do.
Sent from my SM-N910P using Tapatalk

Nice work! Just in time!

So far so good as usual.
Interesting thing, Software OK1, Baseband OJ6, Bootloader OB7.
Thanks for this Tx. It will help the anxiety while we wait for Marshmallow. :thumbup:
Yep, didn't flash the stock tar.
Now to see about wanam xposed.

jhill110 said:
So far so good as usual.
Interesting thing, Software OK1, Baseband OJ6, Bootloader OB7.
Thanks for this Tx. It will help the anxiety while we wait for Marshmallow. :thumbup:
Yep, didn't flash the stock tar.
Now to see about wanam xposed.
Click to expand...
Click to collapse
That's interesting. You should still have the OK1 modem after flashing either of these roms because I included it in the rom zips.

tx_dbs_tx said:
That's interesting. You should still have the OK1 modem after flashing either of these roms because I included it in the rom zips.
Click to expand...
Click to collapse
I'll play with it tonight, backup and flash the stock tar. Go from there and see.

Well if you flash the OJ6 tar then take the OK1 ota update then you will definetely get the OK1 modem. No worries do as you want. I was just suprised to hear that the OK1 modem didn't stick when flashing this rom. You really should update your entire firmware, bootloader etc to latest OK1. Unles you want to run older KK and Lollipop 5.0 software.

tx_dbs_tx said:
Well if you flash the OJ6 tar then take the OK1 ota update then you will definetely get the OK1 modem. No worries do as you want. I was just suprised to hear that the OK1 modem didn't stick when flashing this rom. You really should update your entire firmware, bootloader etc to latest OK1. Unles you want to run older KK and Lollipop 5.0 software.
Click to expand...
Click to collapse
First thing in the morning. I'm all blurry eyed. ?
Thanks again Tx.
EDIT:
Flashed OK1 Tar, wiped everything, flashed this rom, restored all my apps and I picked up 9gb of internal storage. Lotta leftover junk.
Wanam xposed is working perfectly.

I rooted my daughters phone back in March and left it stock. Didn't even put TWRP. She wanted some updating... Ao I flashed back the stock tar from ANIE (which is what she had on the phone)
It downloaded 1 update. The cok1. 1.7 gb.
So that phone should be good to go...?

JohnnyEpic said:
I rooted my daughters phone back in March and left it stock. Didn't even put TWRP. She wanted some updating... Ao I flashed back the stock tar from ANIE (which is what she had on the phone)
It downloaded 1 update. The cok1. 1.7 gb.
So that phone should be good to go...?
Click to expand...
Click to collapse
Yes sir you will be good to go with this rom or any OK1 base Touchwiz rom.
I will try to start on a new custom OK1 rom soon. I gotta juggle my free time so not sure how much time i'll have to spend on it. I will have to manually redo all of the mods, etc.

Thank you, tx_dbs_tx!

I was on OJ6 when I flashed this rom and it still says that I'm on OJ6.

dbug2008 said:
I was on OJ6 when I flashed this rom and it still says that I'm on OJ6.
Click to expand...
Click to collapse
You didnt odin to the latest COK1 tar file.

Anyone else notice they patched the ability of iapps to get msl and unlock again
Sent from my 0x1 Note 4...... I love tep

I'm on your oj6 rom, my phone and pc doesn't detect sdcard but root explorer does. Is their anyway I can update to this rom without a working sdcard?
Sent from my SM-N910P using Tapatalk

allcity187 said:
I'm on your oj6 rom, my phone and pc doesn't detect sdcard but root explorer does. Is their anyway I can update to this rom without a working sdcard?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
If by detect you mean can't write to it use sdfix from the play store.
As this rom is stock without knox & itson it has the same issue with same fix.
Tx may (or not) update his rom (hybrid series) to OK1 in which case it would not be an issue.
I would suggest you Odin the stock OK1 Tar after backing up EVERYTHING including internal storage and wipe everything including internal storage. Then flash this rom.
But thats just me...
Edit.
Just reread your post...hmm pc and phone don't detect the card... Get to OK1 just the same. ..

jhill110 said:
If by detect you mean can't write to it use sdfix from the play store.
As this rom is stock without knox & itson it has the same issue with same fix.
Tx may (or not) update his rom (hybrid series) to OK1 in which case it would not be an issue.
I would suggest you Odin the stock OK1 Tar after backing up EVERYTHING including internal storage and wipe everything including internal storage. Then flash this rom.
But thats just me...
Edit.
Just reread your post...hmm pc and phone don't detect the card... Get to OK1 just the same. ..
Click to expand...
Click to collapse
I have the ok1 tar, so when I Odin to ok1, how can I install this rom without a working sdcard? Thanks for the help.
Sent from my SM-N910P using Tapatalk

kaos420 said:
Anyone else notice they patched the ability of iapps to get msl and unlock again
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
You mean Galaxy tools? I had a hell of a time getting it to install. Ended up doing a complete wipe , flashing this rom and installing gt then restoring my apps. Took me a couple hours to figure it out. :sly:
Luv that app for easy access to hidden menu.

Currently Alliance ROM want to go back to Stock

Title sums it up. Currently on AllianceROM 5.0.1 OB7. Want to go to stock (rooted probably) so I can get MM when it (if it ever) drops. Do I need to do anything special or can I just wipe everything in TWRP, then Odin the stock zip? I get a little weary reading about bootloaders locking above OB7. What does that mean for flashing ROMs if I upgrade the bootloader? Also, does the hotspot fix work on the most recent stock ROM?
Thanks for any help. I have three little kids and no time to research this fully, otherwise I would.

If you're looking to stay OTA capable without going through Odin again to update to MM (weeks to go possibly, IDK?), you most likely wouldn't be able to add hotspot mod without losing OTA capability.
- Use the updated Chainfire Auto Root for Note 4 mostly stock with OTA capability.
*You'd use the full un-root option in SuperSU to update. It's supposed to work if no system mods or system mounting occurs but no guarantee or confirmation I'm aware of on that. You could test that with OJ6, full un-root and take OK1 OTA update if so inclined to test it.
==================================
If upgrading to the reactivation locked bootloaders, alternate ROMs really have little limitation if done without Odin downgrading (only where the ROM you seek or return to is on an older update- that applies to alliance whether you're restoring a backup or flashing a ROM zip). But that also requires Odin again at some point unless you wait and do it only when necessary. You must flash ROM zip or restore a backup and flash a 5.1 kernel like Beastmode rather using Odin to downgrade. The kernel had to be flashed in order to get it to boot. Only limitation that I'm aware of is that your screen may not auto-dim on handset call when you put phone to ear. I had that issue with OB7 ROM with 5.1 kernel; I used the power button to dim the screen but you can't have power button set as an option to dismiss call or that happens when you don't want it to.
=================================
Moar 2.1 ROM is coming soon. That may help with the anticipation of waiting long for MM. But again, that means Odin for OK1 update, then Odin for MM. There's a chance that OTA to MM could be achieved even if dm-verity gets detected in stock recovery while trying to OTA. I think you'd have to clear and download the MM OTA again but first root with Chainfire Auto Root, full un-root in SuperSU app then try the OTA again. Odin OK1 by itself may not clear the modified status but systemless root and un-root may clear it. Just thinking ahead though; no guarantees. May have to wait for MM stock tar.
If not interested in current or future Lollipop rooms, you could just wait, Odin OK1 and OTA to MM when the update is available. Easy?
To answer the Odin question, you're correct on the update though. I tried to answer any questions you might have but may confuse you. I'd need more information on direction you're considering to answer more thoroughly if that leaves more questions.
Sent from my SM-N920P using Tapatalk

I'll have to find a time when I have time and can be without a working phone for a few hours and try to play around with some of this stuff. I'm sure I'll be back on here with questions at some point. Thanks for the initial guidance.
Sent from my SM-N910P using Tapatalk

Okay. I think today is the day. I've downloaded MOAR 2.1 and am going to try this for now. I also have the OJ6 stock (I know it's not the absolute most current) downloaded and ready for standby if I so choose. Here is my plan.
1) Wipe Factory Reset in TWRP 3x's (actually include internal storage as well, correct?)
2) Install TWRP 3.0 via Odin (currently 2.8.5)
2a) Per MOAR install instructions, install stock OJ6 via Odin and activate, etc, etc. Ensure everything works, maybe take the OTA to OK1.
3) install MOAR via TWRP from micro SD card
4) Profit!
If I want to install stock, all I need to do is install the stock ROM via Odin and I will be able to update OTA since I will by default be unrooted, correct?
Thanks for the help. I plan to attempt this later today.

I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk

samep said:
I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?

pilotmills said:
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?
Click to expand...
Click to collapse
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk

samep said:
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I think I need to slow down my postings . I looked around and found out basically what you just told me. Flashing the stock OK1 now, then I'll redo TWRP. Thanks for the timely replies. I'll try to keep it to only issues I run into that I can't resolve after some Google research. I really do appreciate the help.

Progress, but now I can't get the GPS to lock. Tried GPS status app, GPS Status and toolbox. Occasionally I get one or two satellites that show a signal being received, but never locking onto them. Eventually they will drop completely to zero signal. On the other hand, somewhere between OB7 and OK1, Samsung actually addressed the barometer issue that had plagued the N4 since launch where above about 3,000', it would not register anything but a sea-level pressure. Baby steps. . .

Is GPS failing to lock on stock OK1 tar update or the port? The port has GPS a release with fixes pending. But most were only reporting GPS navigation in Google Maps lagging or losing sync during navigation.
Sent from my SM-N910P using Tapatalk

Sorry, should have specified. I'm on stock OK1 now.

pilotmills said:
Sorry, should have specified. I'm on stock OK1 now.
Click to expand...
Click to collapse
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk

samep said:
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
The GPS chip in this phone is horrible. I had the phone up against the window as a last resort and still nothing from the GPS. Went outside and it grabbed a lock within 30 seconds. I didn't opt for the anti-NSA snooping coating on the windows when we had them installed either. . . Backing up OK1 in TWRP now, then attempting to flash MOAR.
Thanks again. Stay tuned. . .

Got MOAR up and running. I had an activation issue the first time which was strange since I was able to send and receive texts and calls, but I kept getting an activation not complete message popping up and persisting. I did exactly as posted in the OP as well. Anyway, went back to OK1 stock and waited even longer after the data established before reflashing MOAR. Works like a charm now. Thanks for the patience and assistance!

Downgrade N910p from MM to LP or KK?

My N910p arrives with MM on PC1 and I flashed it to PD1, but it seems it reboot by itself a lot. I'm not sure it's the MM or the hardware. I used to have a N910T on KK which is very stable. I wonder if there is a way to downgrade from MM to KK or LP. TIA.

You can Odin stock tars that are Android 5.1 but no less. I believe that's no lower than OG5, so OG5 and up are good.
If you were running a custom kernel or stock ROM in marshmallow and factory reset, you may have had ItsOn in /carrier/ItsOn try to initiate the ItsOn bootstrapper setup. If you have an arm file as first entry in /data/dalvik that refers back to /carrier/ItsOn/...apk, that's likely the issue. Note: freeza's ROM won't do this because there's a script to prevent that now.
You could ensure ItsOn is removed (delete the arm file in dalvik-cache and ItsOn folder in /carrier) or go back to Lollipop 5.1
If you go beck to Lollipop, I'd suggest one of tx_dbs_tx Note 5 ports. Wipe everything but extSdCard, factory reset, Odin OK1 stock tar and follow the OP closely.
Sent from my SM-N910P using Tapatalk

samep said:
You can Odin stock tars that are Android 5.1 but no less. I believe that's no lower than OG5, so OG5 and up are good.
If you were running a custom kernel or stock ROM in marshmallow and factory reset, you may have had ItsOn in /carrier/ItsOn try to initiate the ItsOn bootstrapper setup. If you have an arm file as first entry in /data/dalvik that refers back to /carrier/ItsOn/...apk, that's likely the issue. Note: freeza's ROM won't do this because there's a script to prevent that now.
You could ensure ItsOn is removed (delete the arm file in dalvik-cache and ItsOn folder in /carrier) or go back to Lollipop 5.1
If you go beck to Lollipop, I'd suggest one of tx_dbs_tx Note 5 ports. Wipe everything but extSdCard, factory reset, Odin OK1 stock tar and follow the OP closely.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I believe you can go back to any version. I went back to KitKat a couple of times. The problem is every time you upgrade again you lose ram. I only have 2.7 available now. I want to know if there is a way to clear it?
You can change versions forward with OTA but to go back you have to Odin stock firmware. You can get any version here.
Note 4
SM-N910P
http://www.sammobile.com/firmwares/database/SM-N910P/

planb234 said:
I believe you can go back to any version. I went back to KitKat a couple of times. The problem is every time you upgrade again you lose ram. I only have 2.7 available now. I want to know if there is a way to clear it?
You can change versions forward with OTA but to go back you have to Odin stock firmware. You can get any version here.
Note 4
SM-N910P
http://www.sammobile.com/firmwares/database/SM-N910P/
Click to expand...
Click to collapse
Thanks for sharing. Mind telling the lastest version that you have been on before you go back to kk? I heard that once it pass a certain version then it can't go back.

planb234 said:
I believe you can go back to any version. I went back to KitKat a couple of times. The problem is every time you upgrade again you lose ram. I only have 2.7 available now. I want to know if there is a way to clear it?
You can change versions forward with OTA but to go back you have to Odin stock firmware. You can get any version here.
Note 4
SM-N910P
http://www.sammobile.com/firmwares/database/SM-N910P/
Click to expand...
Click to collapse
My RAM is the same. Haven't noticed if reserved RAM varies or if developers tweak this but I believe you're seeing reserved RAM deducted from total as shown here:
{
"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"
}
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar. But, if you're one of the ones that retained OB7 bootloader without flashing full tar updates, then it's also possible to Odin back to KitKat.
But once you update the bootloader via OTA, you'll see it in the update notes that downgrade of bootloader is no longer possible due to the increased security of newer bootloader. Odin would be the same but you wouldn't see the update notes.
Sent from my SM-N910P using Tapatalk

samep said:
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Can you show the way?

shadowcliffs said:
Thanks for sharing. Mind telling the lastest version that you have been on before you go back to kk? I heard that once it pass a certain version then it can't go back.
Click to expand...
Click to collapse
The last time I went back was from bob7. I have not tried it from 6.0. If someone can tell me how to clear out the RAM I will test it out. I think the KitKat is by far the best version for the note excepting for how vulnerable it leaves you to the molesters.
---------- Post added at 09:25 AM ---------- Previous post was at 09:16 AM ----------
shadowcliffs said:
Thanks for sharing. Mind telling the lastest version that you have been on before you go back to kk? I heard that once it pass a certain version then it can't go back.
Click to expand...
Click to collapse
planb234 said:
The last time I went back was from bob7. I have not tried it from 6.0. If someone can tell me how to clear out the RAM I will test it out. I think the KitKat is by far the best version for the note excepting for how vulnerable it leaves you to the molesters.
Click to expand...
Click to collapse
Actually thinking about it, I took my S4 back from 5.1 to 4.1 last week. So I know for sure that you can do it if your still on 5. I asked Samsung support about it a while ago and he said yes but that was still during lollipop. According to Chainfire you can not take a bootloader back but Odin decides what version you will get anyways. So as long as you go back with a stock boot loader intact it will be fine.
---------- Post added at 09:47 AM ---------- Previous post was at 09:25 AM ----------
planb234 said:
The last time I went back was from bob7. I have not tried it from 6.0. If someone can tell me how to clear out the RAM I will test it out. I think the KitKat is by far the best version for the note excepting for how vulnerable it leaves you to the molesters.
---------- Post added at 09:25 AM ---------- Previous post was at 09:16 AM ----------
Actually thinking about it, I took my S4 back from 5.1 to 4.1 last week. So I know for sure that you can do it if your still on 5. I asked Samsung support about it a while ago and he said yes but that was still during lollipop. According to Chainfire you can not take a bootloader back but Odin decides what version you will get anyways. So as long as you go back with a stock boot loader intact it will be fine.
Click to expand...
Click to collapse
I also found out for sure you don"t want to change versions with any thing but stock firmware and odin. I accidentally (stupidly) had Kitkat and lollipop backed up in the same folder and tried restoring from 5 to 4 and cried for a couple of months trying to get it working again. After a lot of trying I was able to use my phone off one back up I had and using the Plasma kernel. I didn't enjoy my phone much until Samsung put out the COJ6. I'm guessing the issue I caused was in the bootloader and until there was a whole new version out there was nothing I could do. I noticed on my S4 and my Note 4 if you want to keep KitKat you have to get it off official status quickly. When they start up on KitKat Samsung pushes the update before you even get through set up and they will install the update with out your permission.
---------- Post added at 10:28 AM ---------- Previous post was at 09:47 AM ----------
samep said:
My RAM is the same. Haven't noticed if reserved RAM varies or if developers tweak this but I believe you're seeing reserved RAM deducted from total as shown here:
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar. But, if you're one of the ones that retained OB7 bootloader without flashing full tar updates, then it's also possible to Odin back to KitKat.
But once you update the bootloader via OTA, you'll see it in the update notes that downgrade of bootloader is no longer possible due to the increased security of newer bootloader. Odin would be the same but you wouldn't see the update notes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you. That Ram thing helps. My Phone says 273 reserved also. I thought I was losin it each time. I took my phone back to KitKat using Odin twice. Both times from Lollipop. I got the update OTA once. Chainfire explains it well, as always. He said that you can not ever go back a version of boot-loader and there is no way to choose your bootloader. Odin decides what firmware it will run.

samep said:
My RAM is the same. Haven't noticed if reserved RAM varies or if developers tweak this but I believe you're seeing reserved RAM deducted from total as shown here:
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar. But, if you're one of the ones that retained OB7 bootloader without flashing full tar updates, then it's also possible to Odin back to KitKat.
But once you update the bootloader via OTA, you'll see it in the update notes that downgrade of bootloader is no longer possible due to the increased security of newer bootloader. Odin would be the same but you wouldn't see the update notes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
My mistake, I was right bot the loss of RAM. You can see that each time you upgrade from KitKat it locks op 20mb. I guess it doesn't cost to jump from 5 to 6. Does anyone know how to free it back up? I want to down grade for awhile but it seems to costly.

shadowcliffs said:
Can you show the way?
Click to expand...
Click to collapse
I posted a known method in the general forum's tar thread
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Another thread you may find helpful is below. Refer to post 22 for recommended links.
http://forum.xda-developers.com/showthread.php?p=63882755
When reading that thread, take into account the OP started on KitKat but wanted to go back after updating to Marshmallow.
Sent from my SM-N910P using Tapatalk

samep said:
I posted a known method in the general forum's tar thread
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Another thread you may find helpful is below. Refer to post 22 for recommended links.
http://forum.xda-developers.com/showthread.php?p=63882755
When reading that thread, take into account the OP started on KitKat but wanted to go back after updating to Marshmallow.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So with OK1 bootlosder/baseband + customer LP kernel + pre-rooted KK rom itb can work on a phone currently on PD1? I want to give it a try but I'm kinda afraid of bricking it.

shadowcliffs said:
So with OK1 bootlosder/baseband + customer LP kernel + pre-rooted KK rom itb can work on a phone currently on PD1? I want to give it a try but I'm kinda afraid of bricking it.
Click to expand...
Click to collapse
I know this worked on Lollipop and I know you can go beck to Lollipop from Marshmallow.
If you really want to try it, I'd suggest TWRP backup, wipe everything but extSdCard, power down and Odin back to OK1 full stock tar. Let that auto boot and complete the setup wizard.
Odin TWRP. Backup. Factory reset, wipe everything but extSdCard. Flash the ROM and kernel before booting. TWRP backup if you like the result or before you modify anything, just in case (it may save some hassle down the road).
I can't guarantee you won't have any issues. If you do, restore the OK1 backup or restore your PD1 baseband and bootloader and restore PD1.
Save backups to extSdCard and verify all your md5 sums. Download twice and compete where no md5 is given. Keep flashables on extSdCard too. I'd also recommend setting up as new device to avoid issues. You could also delete the Android folder on your extSdCard as part of your wipes.
Sent from my SM-N910P using Tapatalk

samep said:
I know this worked on Lollipop and I know you can go beck to Lollipop from Marshmallow.
If you really want to try it, I'd suggest TWRP backup, wipe everything but extSdCard, power down and Odin back to OK1 full stock tar. Let that auto boot and complete the setup wizard.
Odin TWRP. Backup. Factory reset, wipe everything but extSdCard. Flash the ROM and kernel before booting. TWRP backup if you like the result or before you modify anything, just in case (it may save some hassle down the road).
I can't guarantee you won't have any issues. If you do, restore the OK1 backup or restore your PD1 baseband and bootloader and restore PD1.
Save backups to extSdCard and verify all your md5 sums. Download twice and compete where no md5 is given. Keep flashables on extSdCard too. I'd also recommend setting up as new device to avoid issues. You could also delete the Android folder on your extSdCard as part of your wipes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I just had time to give it a try today. Unfortunately, it kept bootlooping after flashing the pre-rooted KK rom and BeastModeKernel. It booted up OK with OK1 tar though.

shadowcliffs said:
I just had time to give it a try today. Unfortunately, it kept bootlooping after flashing the pre-rooted KK rom and BeastModeKernel. It booted up OK with OK1 tar though.
Click to expand...
Click to collapse
Sorry that didn't work.
Did you factory reset and wipe everything but extSdCard?
It has worked before with the original OG5 Beastmode kernel but I didn't think a newer Android 5.1 would make any difference.
Sent from my SM-N910P using Tapatalk

samep said:
Sorry that didn't work.
Did you factory reset and wipe everything but extSdCard?
It has worked before with the original OG5 Beastmode kernel but I didn't think a newer Android 5.1 would make any difference.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yes, wiped everything except for extsdcard x3. The kk rom used is N910PVPU1ANK2_Bonsai_Deodex_v0.0.3. Should I try other rom/kernel combination?

shadowcliffs said:
Yes, wiped everything except for extsdcard x3. The kk rom used is N910PVPU1ANK2_Bonsai_Deodex_v0.0.3. Should I try other rom/kernel combination?
Click to expand...
Click to collapse
Did you start with an Android 5.1 stock tar? Which one? What bootloader and baseband are you running? That would suggest OG5 stock tar. One post even called for OB7 baseband (but understand that you cannot Odin the full stock tar). But his phone was stuck with no means to restore stock due to absence of updates when bootloader initially got the reactivation lock that blocked downgrade.
Looking back through some history, success may be dependent on earlier updates. There is an OB7 baseband Odin flash available but I'd try OG5 stock tar first.
The kernel is here.
https://www.androidfilehost.com/?fid=24052804347789588
The ROM is OK but personally I'd prefer an Odexed ROM if you can find one. You're not limited to deodexed ROM for Xposed and Xposed uses the official Xposed framework for KitKat.
Did you have a question about Moar ROM? I'd totally understand if you went with that and didn't attempt any further with this KitKat method.
Edit: despite the lack of doze on Lollipop, battery was about the same between Moar and latest PG1 Marshmallow. I prefer the Smart Manager we had from Note 5 on Moar ROM to the Note 4 one we have on PG1. Smarter.
Sent from my SM-N910P using Tapatalk

samep said:
Did you start with an Android 5.1 stock tar? Which one? What bootloader and baseband are you running? That would suggest OG5 stock tar. One post even called for OB7 baseband (but understand that you cannot Odin the full stock tar). But his phone was stuck with no means to restore stock due to absence of updates when bootloader initially got the reactivation lock that blocked downgrade.
Looking back through some history, success may be dependent on earlier updates. There is an OB7 baseband Odin flash available but I'd try OG5 stock tar first.
The kernel is here.
https://www.androidfilehost.com/?fid=24052804347789588
The ROM is OK but personally I'd prefer an Odexed ROM if you can find one. You're not limited to deodexed ROM for Xposed and Xposed uses the official Xposed framework for KitKat.
Did you have a question about Moar ROM? I'd totally understand if you went with that and didn't attempt any further with this KitKat method.
Edit: despite the lack of doze on Lollipop, battery was about the same between Moar and latest PG1 Marshmallow. I prefer the Smart Manager we had from Note 5 on Moar ROM to the Note 4 one we have on PG1. Smarter.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
As mentioned in the first post, this Note 4 arrived with PC1, then I ondined it to PD1 beofre this. Then ondined OK1, wiped all, then kk rom and beastmode kernel. It's currently on MOAR. Still testing to see if it's stable for me.