Related
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
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?
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.
My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?
The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/
Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?
If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.
TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.
chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.
chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Fatmonk8 said:
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Click to expand...
Click to collapse
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
TheKnux said:
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
Click to expand...
Click to collapse
To de-bloat.
But if that's the only positive this go around then it's probably not worth me doing since I have been de-bloating more with ADB lately. But if others have any input on other benefits then I may do it again.
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
TheKnux said:
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
Click to expand...
Click to collapse
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Fatmonk8 said:
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Click to expand...
Click to collapse
So I spent a week figuring this out. I realized a few days ago that I mistakenly flashed the Indian firmware for the OnePlus 9 PRO. I have the regular 9. I tried to flash every other msm I could find and download. Nothing seems to work except the Indian OnePlus 9 PRO msm... Problem is, the camera, flash and fingerprint scanner didn't work. I was able to toggle the unlock oem button by running an adb command line then I did oem unlock in fastboot. After that, I followed the instructions for installing StagOs 12.1, which involves installing lineage recovery then flashed the rom. Everything works flawlessly! Love this rom.