Develop Bugs

Unlock bootloader and root new device

I am going to purchase a Nexus 7 2013 and will be wanting to unlock the bootloader and root the device straightaway. I would be grateful if someone could tell me the best way to go about this. Should I carry out these tasks with no ROM updates applied, i.e. on 4.3 or should I update to Lollipop first? Thanks in advance.

With the nexus 7 its as simple as typing fast boot OEM unlock, but here is a more comprehensive guide on the matter. http://forum.xda-developers.com/showthread.php?t=2381698
Sent from my Nexus 7 using Tapatalk

Unlock the bootloader before doing anything else, as it will wipe your data in the process.
If you plan on staying with the stock rom, don't bother rooting or installing a custom recovery until you've updated all the way to lollipop, as it can cause the ota updates to fail and you'll just lose root with each update anyways. Beware of taking this route though, the are lots of posts around saying that the latest ota update bricked devices. Might be safer to fastboot flash the latest factory image directly.
If you plan on using custom ROMs, go ahead and root it and install custom recovery then flash away to your heart's content. You may need to update the bootloader to latest version first to successfully flash lollipop ROMs though. I think its version 4.04, and there are flashable zips for doing this somewhere around here that worked great for me.

crazymonkey05 said:
With the nexus 7 its as simple as typing fast boot OEM unlock, but here is a more comprehensive guide on the matter. http://forum.xda-developers.com/showthread.php?t=2381698
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Many thanks. I used the excellent Nexus Root Toolkit.

PrizmaticSmoke said:
Unlock the bootloader before doing anything else, as it will wipe your data in the process.
If you plan on staying with the stock rom, don't bother rooting or installing a custom recovery until you've updated all the way to lollipop, as it can cause the ota updates to fail and you'll just lose root with each update anyways. Beware of taking this route though, the are lots of posts around saying that the latest ota update bricked devices. Might be safer to fastboot flash the latest factory image directly.
If you plan on using custom ROMs, go ahead and root it and install custom recovery then flash away to your heart's content. You may need to update the bootloader to latest version first to successfully flash lollipop ROMs though. I think its version 4.04, and there are flashable zips for doing this somewhere around here that worked great for me.
Click to expand...
Click to collapse
I unlocked the bootloader, updated to Lollipop 5.0.2 by flashing the latest factory image, then rooted and flashed TWRP. I would now like to flash custom ROMS. You mentioned I may need to update the bootloader in order to successfully flash custom Lollipop ROMS? Am I correct in thinking I will have the latest bootloader, now that I have updated to Lollipop 5.0.2? Thanks.

pretty pixel said:
I unlocked the bootloader, updated to Lollipop 5.0.2 by flashing the latest factory image, then rooted and flashed TWRP. I would now like to flash custom ROMS. You mentioned I may need to update the bootloader in order to successfully flash custom Lollipop ROMS? Am I correct in thinking I will have the latest bootloader, now that I have updated to Lollipop 5.0.2? Thanks.
Click to expand...
Click to collapse
Yep, you're correct. If you flashed the factory image, you should already be on the latest bootloader. :good:
By the way, 5.1 factory image finally was released today for this device.

PrizmaticSmoke said:
Yep, you're correct. If you flashed the factory image, you should already be on the latest bootloader. :good:
By the way, 5.1 factory image finally was released today for this device.
Click to expand...
Click to collapse
Great, thanks for letting me know. Do you recommend I update to the 5.1 factory image before I flash any custom ROMS, or doesn't it matter?

pretty pixel said:
Great, thanks for letting me know. Do you recommend I update to the 5.1 factory image before I flash any custom ROMS, or doesn't it matter?
Click to expand...
Click to collapse
Doesn't matter, though you may wait for the custom ROMs to update to 5.1 so they will have the latest binaries.

PrizmaticSmoke said:
Doesn't matter, though you may wait for the custom ROMs to update to 5.1 so they will have the latest binaries.
Click to expand...
Click to collapse
Thanks. Do you know if CM12 has moved to 5.1 yet?

Not sure, don't really follow cm, but u can just check their website.

pretty pixel said:
Thanks. Do you know if CM12 has moved to 5.1 yet?
Click to expand...
Click to collapse
as i know only few devices are on 5.1 yet

Bootloader question, Android Pay related

I am currently running an OG5 based ROM, with the OB7 bootloader.
I had been keeping the OB7 bootloader, instead of upgrading to OE1/OF5, because it allowed me to go back to Kit Kat NK2, after evaluating the initial lollipop release.
Now that OG5 is out, I am pretty happy and can't imagine going back to KK.
So I've been trying to get Android Pay to allow me store a credit card and no fix has worked. I am thinking that it might be because my rom and bootloader don't match up (OB7 & OG5)?
I was going to give it a shot, but now wondering if there is any reason to keep OB7 bootloader, other than having the option to downgrade?
If I decide to go all OG5 (ROM and bootloader) is there any easier way than starting with the OTA?
Thanks,

Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card

Also... any chance its possible to set up a card on Android Pay from another unrooted device then use as normal from your rooted phone once a card is added to your account? I don't have a secondary device to try
Sent from my SM-N910P using XDA Free mobile app

ch3ck3rs said:
Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card
Click to expand...
Click to collapse
Do you also have the OB7/OG5 combo?
I wonder if anyone with OG5/OG5 has had any luck. from what I've read plenty of people with unlocked bootloaders have been successful.
FYI there is an app called Keyring that does a decent job with loyalty cards.

Yep. I have the same combo. Running Saintz OBAR

A lot of variables are at play here. Most root users of any device are hitting roadblocks when it comes to getting AP to load their cards. In my instance I am on OG5/OG5 running HybridX 3. I've explored nearly all of the 'fixes' out there short of flashing the stock build.prop. Some reports are saying it is checking against known good OS (ie: CM12 stable vs. CM12 nightly). Others are saying it is checking directory level instances of root (ex: system/bin/su or system/xbin/su). Still more are just unlucky and are hitting the wall for no explained reason (there is a reason I'm sure, the info provided isn't helping). What it is going to boil down to is some smart cookie is going to unlock the secret, and we're going to say 'you've got to be kidding, that was too easy'.

With Android Pay, it will block root users and I haven't found a way that gets around it on the Note 4, even with Root Cloak and No Device Check to mask root and custom ROM's to get it to work.
From what I saw, Android Pay does have SafetyNet built in to it to check if your device and your firmware match up. I ran into the same issue with running the OB7 bootloader and CM12.1 ROM which doesn't work. I'm assuming you are having a similar as me issue with using the 0B7 bootloader and a 0G5 ROM. Unfortunately, you will probably have to unroot and go back to stock to get it to work since none of the workarounds I've tried hasn't worked.
Sent from my SM-N910P using Tapatalk

ThatGuy94 said:
FYI there is an app called Keyring that does a decent job with loyalty cards.
Click to expand...
Click to collapse
I use beep and go, works with older infrared barcode scanners

I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!

Quick answer is OB7 allows you to go back to KK OG5 will not

dh350nwo said:
Quick answer is OB7 allows you to go back to KK OG5 will not
Click to expand...
Click to collapse
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?

duongdn said:
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?
Click to expand...
Click to collapse
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk

duongdn said:
I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!
Click to expand...
Click to collapse
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl

cherylbaker said:
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl
Click to expand...
Click to collapse
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk

SafetyNet is just 1 part of the puzzle. If it was the only thing then the Xposed module 'No Device Check' would be enough to bypass. There are multiple checks taking place.

OG5 and non OG5 roms
samep said:
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.

Iceburn1 said:
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.
Click to expand...
Click to collapse
I recall reading that but couldn't recall the steps. Makes sense. Thanks.
Edit: I wouldn't recommend Odin any tar. I believe you still cannot go backwards regarding Odin. The OG5 bootloader won't allow downgrade flash.
Sent from my SM-N910P using Tapatalk

nacron said:
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So your saying unless you are running stock rom and no root there is no way to get android pay to work
cheryl

In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.

dh350nwo said:
In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.
Click to expand...
Click to collapse
What if you went stock set it up avd than flashed back custom rom... does it do the same ssfety checks even after it is setup?
cheryl

Just got note 4 still on KITKAT

I got the note 4 I am on kit kat N2K. I want to root but wanted to know the best way to go about it. Root on kitkat, then flash a rom to get on lollipop? Or accept the lollipop update, and then root and flash? Please advise thank you !

You'd have to decide what you want the most.
With Lollipop you get improved Sprint Wi-Fi Calling and latest security and bug fixes. The battery usage is notoriously higher in Lollipop and the fabled material theme is ugly to many.
KitKat has better battery and theme. Until the recent Android 5.1.1 updates, Lollipop bugs had many utilizing fixes to make Lollipop more like KitKat. The thing most important to consider is that if you upgrade to Android 5.1.1, the bootloader will inhibit you from Odin'g back to KitKat unless you use a specific Odin tar for OB7 to OG5 but it doesn't support the most recent OJ6 update. It's said you could just update the modem to OJ6 but I'd think you have to at least Odin the OB7 lollipop tar before doing that.
I wouldn't recommend rooting and then flashing a ROM outside of the base you're running. Use Odin to update to the equivalent base. OJ6 would be the latest but bootloader inhibits downgrade to KitKat.
I'd suggest rooting KitKat and trying it or a custom NK2 ROM. Next you could try OB7 to see if Lollipop is to your liking. Then you could decide if the latest is what you prefer.
Developer support is currently at OG5 and OJ6; Android 5.1.1 Keep in mind that Android 5.1.1 stock requires kernel with root exploit and SuperSU zip flashed in custom recovery to root. The updates prior can be rooted with CF Auto Root or just Odin custom recovery and flashing custom ROM or SuperSU zip to root stock.
What to flash? You'd have to ask a specific question once you have a better idea of what you prefer or direction you're starting at.
Sent from my SM-N910P using Tapatalk

Thank you for taking the time to type all that up for me! I am going to stay stock until the 14 days incase the phone has some problems before rooting but my brother and dad have note 4 also and both on 5.1.1 and phones are way smoother than mine on kit kat so I would want to be on the latest and have root. I also saw there is a note 5 rom which looks great as well. So is it cool if I PM you in a week or so to help me? I know there are threads but I dunno where to begin . Appreciate it!
Thank you,
Indels

Yes, you could PM. Are the other Note 4 phones rooted or plain stock?
Currently, the Note 5 port is one update behind latest. Maybe it will update.
You don't have to stay with KitKat. Updating won't void your return exchange. But I would recommend a factory reset before making the jump to Lollipop. You can take incremental updates over the air; KIES or Odin stock tar OJ6 from general forum would get you updated to latest in one session.
Just don't Odin custom recovery if you're concerned about Knox trip during your return period.
To get started you'll need the Samsung driver for your PC to use with KIES or Odin. You'll find that here:
http://www.samsung.com/us/support/owners/product/SM-N910PZWESPR# Run the .exe file on PC to install.
Here's a link to TWRP for Note 4:
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
Download Odin (below) and make a folder for it and put the TWRP file and stock tar in it. Find the latest tar in general forum and check the md5.
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
You can also download the zip for ROM you wish to install. Typically, you'd flash the tar that corresponds to the ROM you wish to run for maximum compatibility so you could wait on the tar and zip. Any of these could change but preparation wouldn't hurt.
Sent from my SM-N910P using Tapatalk

Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !

Ind3lible said:
Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !
Click to expand...
Click to collapse
Battery life for initial Lollipop was not so good until Beastmode kernel came out starting in OG5. I've heard OJ6 is even better but I haven't tried it.
Like I said, KitKat has better battery but worse Wi-Fi Calling feature.
Touchwiz 5.1.1 is rooted with custom kernel and SuperSU zip or any custom ROM is pre-rooted. Just don't use Chainfire auto root for Note 4 on that.
Sent from my SM-N910P using Tapatalk

"But I would recommend a factory reset before making the jump to Lollipop."
So I should factory reset on kit kat and then go to lollipop if I understand this part correctly? I have to notification to go to 5.0 right now. I can odin twrp once I go to lollipop too right? Sorry for so many questions just confused. I have not rooted a phone in quiet some time :fingers-crossed:

Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk

samep said:
Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!

Ind3lible said:
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!
Click to expand...
Click to collapse
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk

JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx

samep said:
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.

Ind3lible said:
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.
Click to expand...
Click to collapse
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk

samep said:
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir! You've been of most help!!

alwright1980 said:
JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx
Click to expand...
Click to collapse
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !

I havent keard of a firmware ending ok1 for the SM-N910P
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
Ind3lible said:
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !
Click to expand...
Click to collapse
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root Restrictions​All of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents

alwright1980 said:
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root Restrictions​All of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents
Click to expand...
Click to collapse
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:

Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
I don't think it would have been possible to have gon from KK - LP - MM while preserving a KK Bootloader, and if I am correct in that you won't bee able to Odin back to KK unles you can get reliable instructions on how to seperately flash bootloader, which might be a risky venture, I simply don't know there. You also may be able to get a custom rom which is KK based but I would discuss trying to use it on a phone that has been updated to MM with the DEV if they still offer support. Whatever you do be cautious and well informed before proceeding and know your risks, otherwise it can get expensive.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
I would have thought that it would have been impossible to flash 2 a lollipop and then a marshmallow ROM from a KitKat ROM while preserving the KitKat bootloader. If I'm correct in this then you will not be able to Odin Flash from your marshmallow ROM back to stock KitKat firmware. That is unless you know of a way to separately and reliably Flash your bootloader. You may be able to use a custom rom that incorporates KitKat, but I would be careful about deploying around like that after having updated to marshmallow firmware, and I would discuss it with the developer if they're still offering support for it. Whatever you do be cautious and well informed before moving forward otherwise it can get expensive!

Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
It can be done but not as you would think. The KK bootloader wouldn't flash but read the instructions in this post.
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Edit: if you still have that KK backup, you could restore that instead of the KK ROM but still need the Lollipop custom kernel and Lollipop bootloader.
Sent from my SM-N910P using Tapatalk

Like I said I don't know anything about bootloader switching betweem KK -LP -MM. So I cannot comment effectively on whether or not it would besafe or what you might lose or gain by these methods. Just don't know.

Questions on how to go from VZW N4 LP to MM

Hope the title isn't confusing but I wanted to ask some questions and get some answers without blowing up hsbadr's thread on how to go from LP to MM. So here it goes.
When flashing the full firmware update coming from an already unlocked and rooted Verizon on LP to MM what happens?
Are you back to stock MM rom from Samsung or are you on a modified version of the MM firmware? In other words can I flash the full update and just stay on that base rom?
I believe that is the case and if so hsbadr says we can root and go through the process of unlocking again. What root works best and is it permanent or is it temporary? Is it really temperamental like on LP or will it stick easy enough to unlock?
My purpose in asking is I would like to do all this in phases and help others understand. If I flash the full firmware then I would like to stay on the base rom MM for awhile and when I have time I will unlock the phone.... Again. However if I can't have perm root then flashing the firmware would need to be done in one go with the whole unlocking process.
Any answers are very much appreciated! Thanks ??
Sent from my SM-N910V using Tapatalk

SlothlyDX said:
Hope the title isn't confusing but I wanted to ask some questions and get some answers without blowing up hsbadr's thread on how to go from LP to MM. So here it goes.
When flashing the full firmware update coming from an already unlocked and rooted Verizon on LP to MM what happens?
Are you back to stock MM rom from Samsung or are you on a modified version of the MM firmware? In other words can I flash the full update and just stay on that base rom?
When flashing the full firmware update coming from an already unlocked and rooted Verizon on LP to MM what happens?
My purpose in asking is I would like to do all this in phases and help others understand. If I flash the full firmware then I would like to stay on the base rom MM for awhile and when I have time I will unlock the phone.... Again. However if I can't have perm root then flashing the firmware would need to be done in one go with the whole unlocking process.
Any answers are very much appreciated! Thanks
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
When flashing the full firmware update coming from an already unlocked and rooted Verizon on LP to MM what happens?
Click to expand...
Click to collapse
Which full firmware? hsbadr's* is a hybrid Lollipop/Marshmallow version which I don't think would be a suitable daily driver. The full firmware from sammobile will give you Marshmallow as Verizon intended. Either way, your bootloader is locked. Using hsbadr's means your bootloader can be unlocked. The official version, not so much.
With the full official firmware being available, I would not advise using the update.zip method in other threads. Either flash the official firmware in ODIN or take the OTA update. Either way, you'll have a locked bootloader. Rumor has it that you can flash a Lollipop firmware and re-root, but I wasn't about to try. I could bide my time and let the developers work their magic.
* Also extending credit and thanks to ryanbg and beaups who together worked to get us an unlocked Marshmallow bootloader.
My purpose in asking is I would like to do all this in phases and help others understand. If I flash the full firmware then I would like to stay on the base rom MM for awhile and when I have time I will unlock the phone.... Again. However if I can't have perm root then flashing the firmware would need to be done in one go with the whole unlocking process.
Click to expand...
Click to collapse
If you want root... if you think you'll want root... just bite the bullet and do it. Jasmine ROM has all of the benefits of the Verizon version of Marshmallow. If that's good enough, stay there. If you want to explore, that option will be available as well.

Yea I'm talking about hsbadr hybrid. I'm unlocked and rooted on LP using one of his roms right now. Just want sure what the hybrid version of MM meant. Thanks for the help and understanding. Makes sense now.
Sent from my SM-N910V using Tapatalk

I need the kitkat files (basebands, bootloaders)

Install a rom kitkat of note 4 sprint, when trying to boot the phone is left rebooting and does nothing else

robtudares said:
Install a rom kitkat of note 4 sprint, when trying to boot the phone is left rebooting and does nothing else
Click to expand...
Click to collapse
For SM-N910P model? I sent you a PM but verify the model matches before considering.
And also, is there a specific reason for wanting KitKat?
If you've already flashed ROM (I wasn't aware when I sent PM), try the kernel I linked first. But remember, that depends on your current bootloader.
You can PM also; there's unknown answers to my questions. I'll reply when possible.
Sent from my SM-N920P using Tapatalk

samep said:
For SM-N910P model? I sent you a PM but verify the model matches before considering.
And also, is there a specific reason for wanting KitKat?
If you've already flashed ROM (I wasn't aware when I sent PM), try the kernel I linked first. But remember, that depends on your current bootloader.
You can PM also; there's unknown answers to my questions. I'll reply when possible.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
If I use a note 4 sprint, I want to return to kitkat for the rendering it has with that version of android

If you're on anything newer then 5.0.1(OB7) then you can NOT go back. Only the original bootloader from KK and the OB7 bootloader from 5.0.1 are able to go backwards..the 5.1.1 bootloader write protects itself because 5.1.1 brought a new partition scheme to android.
**Unsure about this but...maybe a NANDroid backup of a KK install would overwrite the more current bootloader**

lazy_dingo said:
If you're on anything newer then 5.0.1(OB7) then you can NOT go back. Only the original bootloader from KK and the OB7 bootloader from 5.0.1 are able to go backwards..the 5.1.1 bootloader write protects itself because 5.1.1 brought a new partition scheme to android.
**Unsure about this but...maybe a NANDroid backup of a KK install would overwrite the more current bootloader**
Click to expand...
Click to collapse
Restoring a KitKat nandroid is possible if flashing a Samsung 5.1 kernel prior to boot.
I'd suggest Beastmode 1.0 kernel followed by SuperSU zip.
On a more recent note, MM update QH1 also also prevents bootloader downgrade. I'm not sure how this effects the longstanding statement about all TouchWiz ROMs are possible with the Beastmode 1.0 kernel and SuperSU zip flash combination?
It's a possibility that the newest bootloader introduces new challenge for booting any TouchWiz ROM. Maybe it would require the MM custom or stock kernel along with latest SuperSU zip? I think that's an unknown a far as KitKat and Lollipop are concerned but already confirmed to work for MM older ROMs.
It's best not to try in any way to downgrade bootloader. Which also means not attempting to Odin older stock tars with older bootloader than your current bootloader's version.
Sent from my PH-1 using Tapatalk