Oh, yeah that's a 5.1 bootloader. There's no way that I'm aware of to update to MM without going through the process again, which will completely wipe the internal storage (I always like to mention this part because I kept forgetting myself and would lose a bunch of stuff).
This post has some pretty good instructions to go from BPA1 to CPD1.
No, it's already tested a few days ago. I just recreated the tar to include MM modem and NON-HLOS so that you don't have to flash extra tars. I'll upload it very soon, but in the meanwhile, you can familiarize yourself with the process and do any preliminary steps (backups, LP unlock, ... etc)
Many rom links in XDA return 404 unfortunately. Only good source of custom roms are in androidfilehost.com. You can search for n910v or trlte to get list of available roms. And you can find N910VVRU2CQL1_PartialFirmware_DevEd.zip on androidfilehost.
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about the tools/files!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you.
You NEED a MicroSD, and it WILL be formatted during this process.
THIS WILL NOT WORK ON GALAXY S3/GALAXY S4/GALAXY S6|e/Galaxy S7|e. It will NOT work on AT&T.
We can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this.
This is a summarized guide with the required files to upgrade and unlock the new bootlloader required for Android 6.0.1 Marshmallow (N910VVRU2CPD1) on Verizon Samsung Galaxy Note 4 (SM-N910V). Extended details about each step (e.g., rooting) can be found in the General Section of this forum.
If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial firmware via Odin to upgrade:
If you own a Developer Edition, you can still use this method unless you want to keep your original CID and signature. If so, make backup of your aboot and CID! You may contact @ryanbg to create a special unlock binary for your own device.
Everyone should unlock his bootloader on Lollipop to save extra steps and prevent complications. The official thread (or any guides based on it) will change your device CID to 150100523231384d4100657e54fc1200 which will match and allow for direct unlocking of the Marshmallow bootloader. Otherwise, the unlock binary will change your decvice CID and reboot, which may end up with a bootloop that requires extra step(s) to fix.
It's recommended to wipe data (factory reset) in stock recovery after Odin flash of full firmware.
Make appropriate backups of everything before trying this.
Unlock your Lollipop bootloader to match CID (start here)
You can ignore this step if you did it already. If not and for Developer Edition owners, I'd recommend to flash N910VVRU2BPA1 Full Firmware via Odin before unlocking.
Root your device (Check General Section for detailed instructions)
Note that WiFi will not work due to the updated bootloader, but you can use Mobile data if needed for rooting.
Unlock the bootloader using the same method:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
Do you understand the implications of these warnings?
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
This is the steps I took to complete this. I am not a dev and I don't take any credit. All the credit is to @hsbadr
Once your unlocked and rooted on 5.1.1
Flash the new bootloader that was posted in the download section of the OP.(I kept the reboot box checked in Odin)
When you phone powers back on, download kingroot and rootchecker (Just like you did when you unlocked your bootloader on 5.1.1)
Enable developer mode and USB debugging in settings
In Windows, Copy samsung_unlock_n4-fix to the "Minimal ADB and Fastboot" install folder location. (Make sure you delete the old samsung_unlock_n4_fix from the last time you did this process)
Plug in with USB cable and make sure Usb settings are MTP and check ok on USB Debugging
Root with kingroot and check root with Rootchecker
open Command window in your ADB folder and type
(1) adb devices
(2) adb push samsung_unlock_n4-fix /data/local/tmp/ (make sure the samsung_unlock_n4-fix is typed in exactly as it is in the adb folder)
(3) adb shell
(4) su ( You have to grant root permission on the phone and continue)
(5) cd /data/local/tmp/
(6) chmod 777 samsung_unlock_n4-fix
Boot into Download Mode
Extract and flash twrp-3.0.2-0-trltevzw.tar.md5 via Odin
Boot into TWRP recovery
Flash JasmineROM v6.0 or any Marshmallow-based ROM
Reboot to system