I've installed the latest build of Lineage OS on my Nextbit and set up Android Pay with my card, however when I go to pay, nothing happens. I've read about this problem on other devices such as the OnePlus 3 but wasn't sure if others were having this issue on their Nextbit. Is there any solution?
Phone passes SafetyNet fine and the bootloader is locked.
comady25 said:
I've installed the latest build of Lineage OS on my Nextbit and set up Android Pay with my card, however when I go to pay, nothing happens. I've read about this problem on other devices such as the OnePlus 3 but wasn't sure if others were having this issue on their Nextbit. Is there any solution?
Phone passes SafetyNet fine and the bootloader is locked.
Click to expand...
Click to collapse
The reason behind this is that lineageos is not a Google approved ROM. You can usually only use Android pay on stock factory ROMs, without root.
xBane_ said:
The reason behind this is that lineageos is not a Google approved ROM. You can usually only use Android pay on stock factory ROMs, without root.
Click to expand...
Click to collapse
This is false. You might be thinking of SafetyNet, which as I said, the phone passes. Otherwise, there is no reason why it shouldn't work, and indeed it has been confirmed that Pay works on Lineage. The app opens fine and I can add cards, it's just that paying doesn't happen.
My theory is that there's something wrong with the NFC drivers, as this is what happened with the OnePlus, but idk.
comady25 said:
This is false. You might be thinking of SafetyNet, which as I said, the phone passes. Otherwise, there is no reason why it shouldn't work, and indeed it has been confirmed that Pay works on Lineage. The app opens fine and I can add cards, it's just that paying doesn't happen.
My theory is that there's something wrong with the NFC drivers, as this is what happened with the OnePlus, but idk.
Click to expand...
Click to collapse
Excuse me then, on my Robin, and on my Nexus 4 (with custom ROM) it fails to work but I can still do NFC.
you need root and magisk to get android pay to work with lineage. No other way presently. Lineage worked with my Oneplus One with an unlocked bootloader but not with the Robin. I ended up restoring stock Nougat and it still wouldn't pass. Had to restore Marsh mellow, then lock the bootloader and do the ota update to Nougat. Android Pay now works. It's a shame because I'd rather have Lineage but Android pay is a deal breaker.
Hope this helps anyone in this situation.
comady25 said:
I've installed the latest build of Lineage OS on my Nextbit and set up Android Pay with my card, however when I go to pay, nothing happens. I've read about this problem on other devices such as the OnePlus 3 but wasn't sure if others were having this issue on their Nextbit. Is there any solution?
Phone passes SafetyNet fine and the bootloader is locked.
Click to expand...
Click to collapse
Since when are u able to have custom recovery and custom ROM and have a locked bootloader. I call false on that as well. Can't have a locked bootloader with at least custom recovery
the_rooter said:
Since when are u able to have custom recovery and custom ROM and have a locked bootloader. I call false on that as well. Can't have a locked bootloader with at least custom recovery
Click to expand...
Click to collapse
Code:
fastboot oem lock
Works now with the new LineageOS update anyway
comady25 said:
Code:
fastboot oem lock
Works now with the new LineageOS update anyway
Click to expand...
Click to collapse
The code will work but that is calling for a full brick of device. Can't have locked bootloader with custom recovery
the_rooter said:
The code will work but that is calling for a full brick of device. Can't have locked bootloader with custom recovery
Click to expand...
Click to collapse
Don't know what to tell you man but my phone is working fine. The bootloader only needs to be unlocked when you flash a new recovery.
If someone can get build.prop from latest stock ROM, I can make Android Pay working
hiimpig1 said:
If someone can get build.prop from latest stock ROM, I can make Android Pay working
Click to expand...
Click to collapse
No need to, Android Pay was fixed in the latest LineageOS build
Related
I am on new Nougat stock os. Phone has been re-locked.
Can't use the phone for paying and two safety net tests I ran fail both at the last test: cts profile match.
Any idea what should I do to make Android pay work? Thanks
I'm waiting to upgrade to 4.0 until they fix Android pay. I read a couple people say android pay wasnt working but when I asked no one would confirm Android pay was broken...
lock Bootloader needed for safetynet pass on nougat. Put recovery to stock reinstall OOs from stock recovery and relock bootloader.this worked
From what the very little information I can gather, this issue appears to only affect previous users having unlocked bootloaders.
Could it be that there's still some tampering or unlock flag that's not cleared after the re-lock and Google is able to see?
Sent from my ONEPLUS A3000 using Tapatalk
safetynet test apps
For those willing to test safetynet (on an unrooted, locked bootloader ofc) here are some links to test apps I tried:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en (rating: 4.6)
https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground&hl=en (rating: 4.3)
https://play.google.com/store/apps/details?id=com.vpals.apps.safetynettestapp&hl=en (rating: 5, out of 8 reviews though)
Magisk works, can't test android pay though cause my card doesn't support it
Yeah, this might be what I'm going to do anyway, it's just a little bit ironic to have to root in order for safetynet to be happy.
Sent from my ONEPLUS A3000 using Tapatalk
I had an unlocked bootloader and Android Pay wasn't working. However, when I locked the bootloader after installing the stock recovery, it is working. I have successfully used it since then.
dindoliya said:
I had an unlocked bootloader and Android Pay wasn't working. However, when I locked the bootloader after installing the stock recovery, it is working. I have successfully used it since then.
Click to expand...
Click to collapse
Was that on marshmallow or the new nougat?
Sent from my ONEPLUS A3000 using Tapatalk
millicent said:
Was that on marshmallow or the new nougat?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
I am on OOS 4.0
So android pay is working with Oos 4.0??? Or not??
I am going to try -- again -- the unlocking/reflashing say marshmallow stock and relocking + updating to oos4 and Will post back. However it'll have to wait until weekend.
Sent from my ONEPLUS A3000 using Tapatalk
d3funct said:
So android pay is working with Oos 4.0??? Or not??
Click to expand...
Click to collapse
It's working. However, some are reporting that it's not. It's working for me. Stock with locked BL.
It's finally working here as well. As suggested, I had to unlock again, reinstall stock recovery shipped with 3.2.8 sideload 3.2.8, lock bootloader, several factory resets. I am back on Nougat and safetynet is good now.
Sent from my ONEPLUS A3000 using Tapatalk
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Banan PL said:
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Click to expand...
Click to collapse
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Click to expand...
Click to collapse
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
There's a temporary workaround if you're a stock rooted user:
Here's a reddit link regarding a workaround:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
However, this isn't helpful if you're a regular custom rom user as you'll notice in the details.
As for DRM, I think so. I have been looking for confirmation about DRM being impacted by this "No RPMB" status. I've only seen one other person outright mention this. It's hard to find users who get this issue and even harder to get them to respond on my inquiry on whether they can use DRM apps. What issue are you seeing with Play Movies? Can you open the app? Or are you given an error message of any kind? I'm interested from the troubleshooting perspective so that I can help ID when others have the same issue. Also, can you confirm this affects other multimedia apps with DRM protection? I was thinking that Hulu, Netflix, HBO would be apps that utilize DRM if you have subscriptions.
Sent from my Nexus 5X using Tapatalk
I don't care much about custom OS, at least for now. I can open Play Movies browse feed and library, but it ain't play any video (Couldn't fetch license (error -1)). Unfortunately I don't have subscriptions in these services, but I used local TV streaming app that uses DRM and it showed error 203 (whatever that means). I tried also watch movies from Google's app on YouTube, no luck.
Sent from my Nexus 5X using XDA Labs
Hi there, same case, no rpmb after replacing motherboard, Netflix won't start (error 500 device failure). Tried with stock but now PureNexus rom.
Sent from my Nexus 5X using Tapatalk
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
tuningsea said:
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
Click to expand...
Click to collapse
Thanks for the advise, however I want to find a way to create this Rpmb at home, for users who warranty has gone, still looking..
Sent from my Nexus 5X using Tapatalk
Netflix norpmb
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
I confirm it's working. Has anybody found a different solution for no rpmb from the one posted on reddit?
Inviato dal mio Nexus 5X utilizzando Tapatalk
kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
Netflix app will crash few times, try to hide with Magisk Btw. Re open few times, like 10 and login. Then you will be redirected to the homepage.
Envoyé de mon Nexus 5X en utilisant Tapatalk
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
androidfreak11 said:
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
Click to expand...
Click to collapse
I'm also looking for a solution all the time
but I haven't found one yet
openyourmind said:
I'm also looking for a solution all the time
but I haven't found one yet
Click to expand...
Click to collapse
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
i was able to flash stock rom via fastbook (had to unlock bootloader 3 times, everytime it rebooted, but it worked tho)
only problem, when i install twrp and press reboot phone, it will only boot to twrp! and i have to type in a decription password or something, because i unlocked the bootloader and android should have deleted everything, but didn't cause i would have to reboot for that, but it will only boot in twrp .. so yeah, that's where i got stuck .. any idea?
otherwise i'll resell this thing and maybe get an htc 10 or a nexus 5x with stock mobo
Hi all,
I currently have stock 8.1 installed on my refurbished Nexus 5X with NO RPMB, and would like to install a custom ROM (Pixel2ROM from argraur).
If possible, I prefer NOT to get root. Maybe it helps passing safetynet.
As I understood, I should do following steps:
- Unlock bootloader
- Flash stock ROM. -> Is this step necessary since I already have stock 8.1 installed?
- Flash TWRP
- Reboot directly into TWRP
- Wipe data and cache
- Flash custom ROM
- Flash Magisk or superSU -> Without this step, would TWRP get replaced with stock recovery? Is Magisk or superSU better?
Can you please check if the steps are right, and answer the 3 questions.
Thanks!
EDIT: I tried without flashing the stock ROM nor root. Everything went fine and TWRP remains installed.
Hello I created a thread trying to help with this cases.. If someone with better knowledge see a better option, please say it there to update it..
NO RPMB (how to install TWRP, a new ROM and using Magisk)
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
ciorci said:
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
Click to expand...
Click to collapse
Without the magisk part its like you are using a normal rom with a normal boot image, just need to dirty flash the new rom..
With the magisk part it would need to make a new patched boot image..
So at least you will need to extract the new boot image of the new rom file, use it on magisk and patch it, after that I dont know... to my method work the first time it was needed a clean installation, but didn't tried it yet because the new update of my rom developer needed to be a clean installation due to many changes on the rom, so i didn't have opportunity to try update normally but when I do I will update my thread with what to do on that case and if it works..
Hello Everyone!
I am sure this has been passed around multiple times, but my searches are getting me no results, and this is driving me crazy.
For the life of me I cannot get SuperSU to install and root! I've included what I've attempted to install via TWRP below..
I also have another question relating to slots...
So when I install Lineage OS on Slot B, Lineage OS installs it's own custom recovery, which forces me to install TWRP on Slot A, I have to boot into bootloader to switch active slot to get back into TWRP, is there a way around that?
Phone: Google Pixel XL from Verizon
ROM: https://forum.xda-developers.com/pixel-xl/development/rom-lineageos-14-1-nightlies-google-t3601893 (Lineage OS 7.1.2)
SuperSU: I've tried v2.79-SR3, and v2.79-SR2, and also the latest beta version available: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TWRP: 3.1.0 RC2
Steps:
Booted into bootloader, fastboot twrp recovery, installed on slot A
switched into slot B via TWRP, formatted data, installed the latest ROM from list above.
Installed SuperSU (versions above)
Any help would be great!
You may need to search for magisk 13.1 and use that instead of SuperSU.
Milly7 said:
You may need to search for magisk 13.1 and use that instead of SuperSU.
Click to expand...
Click to collapse
Has Magisk 13.1 been ported for pixel yet?
i know 13 has, but there have been a lot of reports of people going back to 12 following the switch
y2grae said:
Has Magisk 13.1 been ported for pixel yet?
i know 13 has, but there have been a lot of reports of people going back to 12 following the switch
Click to expand...
Click to collapse
Not sure about that. But I know on other devices supersu doesn't play well with updated Roms
Do you have an un-updated Verizon Pixel? With the latest versions of Android, the bootloader can't be unlocked on the Verizon version
Seeing as the OP is booting into bootloader and switching slots... I'd say it was already unlocked
KeithGS said:
Hello Everyone!
I am sure this has been passed around multiple times, but my searches are getting me no results, and this is driving me crazy.
For the life of me I cannot get SuperSU to install and root! I've included what I've attempted to install via TWRP below..
I also have another question relating to slots...
So when I install Lineage OS on Slot B, Lineage OS installs it's own custom recovery, which forces me to install TWRP on Slot A, I have to boot into bootloader to switch active slot to get back into TWRP, is there a way around that?
Phone: Google Pixel XL from Verizon
ROM:https://forum.xda-developers.com/pixel-xl/development/rom-lineageos-14-1-nightlies-google-t3601893 (Lineage OS 7.1.2)
SuperSU: I've tried v2.79-SR3, and v2.79-SR2, and also the latest beta version available: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TWRP: 3.1.0 RC2
Steps:
Booted into bootloader, fastboot twrp recovery, installed on slot A
Installed SuperSU (versions above)
Any help would be great!
Click to expand...
Click to collapse
You're using the wrong supersu. You need 2.82 SR1
Crap nevermind lol. Just realized the link. Wow I'm cooked.
strra said:
Do you have an un-updated Verizon Pixel? With the latest versions of Android, the bootloader can't be unlocked on the Verizon version
Click to expand...
Click to collapse
Is this really true? I have the bootloader already unlocked but I was gonna file a claim to get it replaced eventually due to scratches and dinks I don't wanna end up with a pixel from Verizon that's perma bootloader locked.
So you guys are saying to use magik instead?
KeithGS said:
Is this really true? I have the bootloader already unlocked but I was gonna file a claim to get it replaced eventually due to scratches and dinks I don't wanna end up with a pixel from Verizon that's perma bootloader locked.
Click to expand...
Click to collapse
yes, as of 7.1.1, there is no bootloader unlock for Verizon Pixel
Thanks... So about magisk where do I get the pixel XL one because the official thread says there is no support for it yet.
strra said:
yes, as of 7.1.1, there is no bootloader unlock for Verizon Pixel
Click to expand...
Click to collapse
I wonder if a refurbished would be updated since Verizon outsourced their replacement team
KeithGS said:
Thanks... So about magisk where do I get the pixel XL one because the official thread says there is no support for it yet.
Click to expand...
Click to collapse
The unofficial version of Magisk is hosted in the Resurrection Remix rom thread. You should also be able to find which version of Magisk Manager is compatible with the unofficial build in that thread.
---------- Post added at 09:07 PM ---------- Previous post was at 08:58 PM ----------
KeithGS said:
I wonder if a refurbished would be updated since Verizon outsourced their replacement team
Click to expand...
Click to collapse
You would be taking a big chance if having an unlocked bootloader is important to you. 7.1.1 is from early this year and getting a refurbished phone that out of date is unlikely. Some Verizon users have reported getting the Google version with the oem unlock option available back instead of the locked Verizon version but that would be like winning the lottery --odds aren't good that would happen if you RMA'd your phone. Also, even if you did get a Google version back you would need to enable OEM unlocking immediately before accepting any system updates from Verizon. The first Verizon system update installed while OEM Unlocking is not enabled will permanently disable the option. Someone reported that they locked their bootloader but didn't disable OEM Unlocking and that a Verizon update disabled the option for them--so at this point you might actually need to have your bootloader unlocked before accepting any Verizon updates.
jhs39 said:
The unofficial version of Magisk is hosted in the Resurrection Remix rom thread. You should also be able to find which version of Magisk Manager is compatible with the unofficial build in that thread.
---------- Post added at 09:07 PM ---------- Previous post was at 08:58 PM ----------
You would be taking a big chance if having an unlocked bootloader is important to you. 7.1.1 is from early this year and getting a refurbished phone that out of date is unlikely. Some Verizon users have reported getting the Google version with the oem unlock option available back instead of the locked Verizon version but that would be like winning the lottery --odds aren't good that would happen if you RMA'd your phone. Also, even if you did get a Google version back you would need to enable OEM unlocking immediately before accepting any system updates from Verizon. The first Verizon system update installed while OEM Unlocking is not enabled will permanently disable the option. Someone reported that they locked their bootloader but didn't disable OEM Unlocking and that a Verizon update disabled the option for them--so at this point you might actually need to have your bootloader unlocked before accepting any Verizon updates.
Click to expand...
Click to collapse
Caused my phone to go into an infinite bootloop.
KeithGS said:
Caused my phone to go into an infinite bootloop.
Click to expand...
Click to collapse
I've never heard of anyone bricking a Pixel XL yet. Completely power down your phone. Let it sit for a minute. Power directly into the bootloader mode by pressing power and volume down at the same time. When the phone vibrates let go of both buttons. Once in bootloader mode you can flash-all.bat the latest factory image from Google's website and you should be fine.
What were you doing exactly that led to the bootloop?
Hey so I got the Nokia 6.1 unlocked from Best buy and noticed that it's a treble device and also has official twrp recovery. I noticed that we don't really have roms for this phone though and was wondering if I could just flash treble roms and if maybe that's the reason why? I really hope someone can help me out here lol.
There isn't any official bootloader unlock, and the paid, unofficial unlock stopped working long ago.
That is the reason that no developers have any interest in this phone.
As to flashing a treble rom: if you somehow get the bootloader unlocked, you can try. But many phones require some additional tweaks - treble isn't perfect. I don't know about this phone.
runekock said:
There isn't any official bootloader unlock, and the paid, unofficial unlock stopped working long ago.
That is the reason that no developers have any interest in this phone.
As to flashing a treble rom: if you somehow get the bootloader unlocked, you can try. But many phones require some additional tweaks - treble isn't perfect. I don't know about this phone.
Click to expand...
Click to collapse
The paid one is still working. I had to order last week, i had to downgrade from pie and unlock the bootloader, works fine. I can't recommend which one to order becuase of the rules of the forum, but at least one still works.
@SVcross
How did you downgrade?
runekock said:
@SVcross
How did you downgrade?
Click to expand...
Click to collapse
With the same service for unlocking the bootloader.
Well yes it's safe... currently i'm running havoc os 2.0....and it is working like charm...i haven't noticed any bugs yet...you can give it a try
But one thing to notice.... sometimes some magisk modules...like quickswitch for example....changes slot (from B to A in my case) when device is rebooted..and causes my device to stuck at bootloader aka download mode...idk why it happens...however it can be resolved by using fastboot....and typing fastboot --set-active=_b when device is in download mode....hope this helps...i encountered this a lot btw
Hi. I've posted this under the liniage thread, but I'm hoping more people will see it here since it's not a liniage specific problem, but rather something to do with my device or me. Any help would be greatly appreciated:
I am on the stock Samsung u3 Q firmware and I cannot get any custom Rom working, except for DR. Ketan which is based on the Samsung stock, but otherwise works great, root and all. My main purpose is to get to u1. I've tried liniage 17, 16, lightrom, crdroid and nemesis, all with the same result: after successfully flashing in TWRP, the phone restarts and does not boot. first it does another restart, then goes into download mode on some roms, and recovery in others. I'm sure I'm missing something, or doing something wrong, but I can swear I've followed all the instructions. Any guess to what that might be, or what I can try?
By u3 and u1 you mean bootloader versions?
winol said:
By u3 and u1 you mean bootloader versions?
Click to expand...
Click to collapse
Yes, the security on the boot-loader. Any since all official firmware check, that's not an option. But as long as I'm able to run a custom rom, I should be good, I think.
There is no roll back with bootloaders, I have never tried something of the sort, but it has been said over and over again that bootloaders can not be downgraded
Would that mean that any device with a higher than u1 bootloader will not work with custom roms? That doesn't sound right to me.. Perhaps I haven't asked my question well enough, so first, I'd like to figure out why custom non-samsung based roms all fail on boot.
mancaalberto said:
Would that mean that any device with a higher than u1 bootloader will not work with custom roms? That doesn't sound right to me.. Perhaps I haven't asked my question well enough, so first, I'd like to figure out why custom non-samsung based roms all fail on boot.
Click to expand...
Click to collapse
You said you were on U3. If so, you cannot load ANY rom with a U1 bootloader. Period.
Sent from my SM-N975U1 using Tapatalk
mancaalberto said:
Would that mean that any device with a higher than u1 bootloader will not work with custom roms? That doesn't sound right to me.. Perhaps I haven't asked my question well enough, so first, I'd like to figure out why custom non-samsung based roms all fail on boot.
Click to expand...
Click to collapse
All firmwares, or ROMS, official or custom, have a bootloader version, newer ones have higher number version, you can not install anything with a lower bootloader number than the currently installed one, no matter if official or custom or whatever, this can not be circumvented in any way, so, if your current firmware has a bootloader 3, (U3) as you posted, you will be able to install roms (custom or official) with bootloader number 3 or higher, that's it, I hope you got it this time
donc113 said:
You said you were on U3. If so, you cannot load ANY rom with a U1 bootloader. Period.
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Not what I was hoping for, but understood. Thank you.