Develop Bugs

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

Deodex stock rom for installing Xposed on SM-T805

I'm just taking my first steps with my brandnew SM-T805.
I managed to get root, I installed a custom recovery and everything runs pretty promising.
Now I have still the problem that not every app can be run in the side by side multi window mode. I read that this can be fixed with the xposed framework.
So for Xposed it seems that I need to have a Deodexed ROM.
My stock rom seems to be Odexed.
How can I convert or get a Deodexed one?
I'd prefere to use a stock rom for now, just to get no troubles with LTE and so on... Just stock, with root and deodexed with xposed.
Hope someone can help...

I'd highly recommended sweetrom, it's the one I use.

fpdragon said:
I'm just taking my first steps with my brandnew SM-T805.
I managed to get root, I installed a custom recovery and everything runs pretty promising.
Now I have still the problem that not every app can be run in the side by side multi window mode. I read that this can be fixed with the xposed framework.
So for Xposed it seems that I need to have a Deodexed ROM.
My stock rom seems to be Odexed.
How can I convert or get a Deodexed one?
I'd prefere to use a stock rom for now, just to get no troubles with LTE and so on... Just stock, with root and deodexed with xposed.
Hope someone can help...
Click to expand...
Click to collapse
Did you manage to deodex the stock rom?

Here's a guide on how to deodex stock. http://forum.xda-developers.com/showthread.php?t=3254734
Sent from my SM-T700 using Tapatalk

Stuck in boot loop

I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1

Thuganomics said:
I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1
Click to expand...
Click to collapse
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin to flash custom recovery would be a prerequisite for rooting stock with those zips or custom ROM zip.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk

samep said:
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin would be a prerequisite for rooting stock with those zips or custom ROM zip.
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the TWRP 2.8.1.1 and im able to access the menu in recovery mode however I still get stuck on the boot loop with no kernel even though I had one on the phone before starting the process

Have you flashed the Beastmode kernel and SuperSU zip linked in the post I linked you to above? Are you getting a message indicating no kernel installed? A ROM flash or those zips would get a kernel onboard.
If you're stuck, just try OBAR ROM on a clean install. You can find it in development forum.
Sent from my SM-N910P using Tapatalk

I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.

Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
The link is live in the post above. Scroll down to where SuperSU zip is linked as well. Flash both those in TWRP recovery.
You'll still need to freeze or remove Knox. There's some other notes that apply to stock in that post, like the build.prop edit.
Sent from my SM-N910P using Tapatalk

Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.

jhill110 said:
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.
Click to expand...
Click to collapse
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?

Thuganomics said:
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?
Click to expand...
Click to collapse
Odexed is better for performance, deodexed is a better choice for moding. I always use deodexed as the performance of this device is outstanding.
As for the battery issues, I use GSam battery monitor (there are many others). It helps you see what is using up battery.
Go through the system settings and turn off things that aren't necessary for you. Many of them contribute to battery drain. It's a drip, drip, drip thing... Not any one thing. A process of learning what helps and what doesn't. There's no catch all answer... You've got to work at it.

Does a stock Rooted 6.0.1 Exist?

As the title says, just looking for a stock and rooted Marshmallow, I will go on and remove the stuff I don't want. I have not seen one or my google skills are failing...
Sent from my SM-N910V using Tapatalk

Or a quick way to go from CM 13 to rooted stock...I really don't want to have to go through the whole process....I will if that's the only way though...
Sent from my SM-N910V using Tapatalk

This might be it. Post in this thread and inquire before you do anything. You might need to flash and Unlock, again, but once you Unlock, you might be able to use it Unlocked/Rooted as-is. Again, though, inquire there.
http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727

cdrshm said:
Or a quick way to go from CM 13 to rooted stock...I really don't want to have to go through the whole process....I will if that's the only way though...
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Which CM13 version are you using? Have you upgraded the bootloader to MM yet? If you are using an older version of CM13 that was on the LP bootloader then you'll have to go through the unlocking process once more with the LP-MM hybrid firmware. If you have already done that and you have the MM bootloader then you can flash JasmineROM or PaulPizz as a close-to-stock ROM. Jasmine is probably the closest to stock.

shadeau said:
Which CM13 version are you using? Have you upgraded the bootloader to MM yet? If you are using an older version of CM13 that was on the LP bootloader then you'll have to go through the unlocking process once more with the LP-MM hybrid firmware. If you have already done that and you have the MM bootloader then you can flash JasmineROM or PaulPizz as a close-to-stock ROM. Jasmine is probably the closest to stock.
Click to expand...
Click to collapse
I did end up getting on Jasmine, i did the restore of the jasmine rom from TWRP and then flash the PartialFirmware_PatchedKernel and i am working now...

PF3 Firmware
cdrshm said:
I did end up getting on Jasmine, i did the restore of the jasmine rom from TWRP and then flash the PartialFirmware_PatchedKernel and i am working now...
Click to expand...
Click to collapse
I have a copy of PF3 firmware that's almost stock. It has busybox, deodexed, and zip-align. To root, you could flash su zip for system-less or just install su from playstore. It still has Knox and all bloat.
PF3 Firmware link

Please Help - SM-910P 5.1.1 OK1

I have read, watched many Videos on rooting my Sprint Note 4 5.1.1 on N910PVPS4COK1 , most are from few years past. All I want to do is to Root my Phone, I did flash TWRP 3.1.1-0. I do not want to Upgrade, downgrade or Flash another ROM.
I am confused since some mention that a new Kernel must be flashed and some Just mention to Flash CF Auto Root. Please Help.
Thank you all in Advance.

Most just flash a zip in TWRP recovery to root.
SuperSU is in Google Play but honestly I've not rooted stock from there to day that works but used the recovery zip instead. This link may get you started; read the OP and follow the link to get stable release or read notes. The title will change with latest beta test version but here is a good place to start for SuperSU.
https://forum.xda-developers.com/showpost.php?p=55256620&postcount=1
If you're looking to pass safety net, Google search Magisk. SuperSU doesn't support hiding root from Google's safety net but doing so may be dodgy and require frequent updates.
Older methods you find may mention older methods and kernel requirements. I'm not sure if CF Auto Root gets updated with latest SuperSU but it's intended to be a shortcut to root and for those not looking to not Odin TWRP to use a custom recovery.
You've gone the common route, starting with Odin to flash TWRP. You're next step would likely to root with one of the methods above or flash a custom kernel first. There are a few but stock kernel can also be used. I use Beastmode for permissive mode to flash sound modes that include ViPER4Android; permissive kernel is recommended for that one.
Sent from my SM-N920P using Tapatalk

Thank you for Quick response, Basically I need to flash a custom Kernel before I flash SuperSu Root. Which Stock Kernel can I use that will allow me to do that. Thank you again

AVillart said:
Thank you for Quick response, Basically I need to flash a custom Kernel before I flash SuperSu Root. Which Stock Kernel can I use that will allow me to do that. Thank you again
Click to expand...
Click to collapse
The stock kernel you have would work with SuperSU or Magisk root. Stock kernel is enforcing selinux so it may not fully work as expected with ViPER4Android and maybe some other apps too. The need for permissive kernel impacted lollipop 5.1 and I've used it since then so I'm not having to know which apps are impacted.
If you're interested, Beastmode kernel is in the development forum for Sprint Note 4. Beastmode is very close to stock feel right out of the box without having to tune it; it may improve your battery stats too. The kernels with "r" are Samsung Marshmallow kernels do you'd use the numeric-only ones for Samsung lollipop.
Sent from my SM-N920P using Tapatalk

samep said:
The stock kernel you have would work with SuperSU or Magisk root. Stock kernel is enforcing selinux so it may not fully work as expected with ViPER4Android and maybe some other apps too. The need for permissive kernel impacted lollipop 5.1 and I've used it since then so I'm not having to know which apps are impacted.
If you're interested, Beastmode kernel is in the development forum for Sprint Note 4. Beastmode is very close to stock feel right out of the box without having to tune it; it may improve your battery stats too. The kernels with "r" are Samsung Marshmallow kernels do you'd use the numeric-only ones for Samsung lollipop.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Which One would I flash as I only see BeastMode r56 RAGE for N910P on that page.
Thank you

AVillart said:
Which One would I flash as I only see BeastMode r56 RAGE for N910P on that page.
Thank you
Click to expand...
Click to collapse
I agree it was a bit of a search to find and not where I recalled it being.
https://www.androidfilehost.com/?fid=24052804347789588
Flash kernel then SuperSU zip. That should give you root on stock 5.1
I actually have a newer version but it's only had limited testing with a custom 5.1.1 ROM; original links were removed. Other updates were incorporated in custom ROMs. Since this is the only one readily available, try that one if you like. Recommend flashing over stock kernel only and make a full TWRP backup before flashing in case you prefer stock kernel.
If wishing to root stock with stock kernel, flash latest SuperSU.
Sent from my SM-N920P using Tapatalk

samep said:
I agree it was a bit of a search to find and not where I recalled it being.
https://www.androidfilehost.com/?fid=24052804347789588
Flash kernel then SuperSU zip. That should give you root on stock 5.1
I actually have a newer version but it's only had limited testing with a custom 5.1.1 ROM; original links were removed. Other updates were incorporated in custom ROMs. Since this is the only one readily available, try that one if you like. Recommend flashing over stock kernel only and make a full TWRP backup before flashing in case you prefer stock kernel.
If wishing to root stock with stock kernel, flash latest SuperSU.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you again.