[ROM][OFFICIAL][instantnoodlep][12] LineageOS 19

Search This thread

[email protected]_

Senior Member
Oct 18, 2012
79
3
Oh, that's bad. I'm trying to figuring out how to make google wallet works again and i will be glad if i can make a full system backup before try something.
Problem with google wallet is:
I can't add my debit card.
Google wallet says: your phone doesn't meet security standards to make contactless payments. It may be rooted or running uncertified software.....
Does anybody working solution for this?
 

d3viou5

Senior Member
Jun 4, 2007
236
58
Oh, that's bad. I'm trying to figuring out how to make google wallet works again and i will be glad if i can make a full system backup before try something.
Problem with google wallet is:
I can't add my debit card.
Google wallet says: your phone doesn't meet security standards to make contactless payments. It may be rooted or running uncertified software.....
Does anybody working solution for this?

I don't use wallet, but you could try the regular stuff:

Root with magisk
Hide the magisk app
Install safety net fix
Enforce deny list for gpay
Spoof the fingerprint to a pixel with magisk hide props config.

Presumably it passes safety net?
 

d3viou5

Senior Member
Jun 4, 2007
236
58
Upgraded from 18.1, went great but broke my Magisk root. I tried to patch and flash a new boot img, now it only starts into recovery. I'm hoping someone can tell me what boot.img file to use to get it working again. I tried "OxygenOS 11.0.7.7.IN21AA" from https://www.thecustomdroid.com/oneplus-8-pro-stock-boot-image-collection/ also, but no dice (is there a LineageOS specific one I need to use?)
Download lineage for op8p from their website and run the payload.bin through payload dumper to extract the boot image.

You should be able to flash it through fastboot to get working again.

To root:
put the boot image from the dumped payload on your device
patch with magisk
copy the patched file from downloads off the device
boot with it from fastboot
direct install in magisk

Don't mix images from stock ROMs with custom ones.
 

[email protected]_

Senior Member
Oct 18, 2012
79
3
I don't use wallet, but you could try the regular stuff:

Root with magisk
Hide the magisk app
Install safety net fix
Enforce deny list for gpay
Spoof the fingerprint to a pixel with magisk hide props config.

Presumably it passes safety net?
I know about this. I will try. But if i change the fingerprint can i change it back to original? If something goes wrong? Thx
 

edutchie

Member
Mar 10, 2021
14
1
Download lineage for op8p from their website and run the payload.bin through payload dumper to extract the boot image.

You should be able to flash it through fastboot to get working again.

To root:
put the boot image from the dumped payload on your device
patch with magisk
copy the patched file from downloads off the device
boot with it from fastboot
direct install in magisk

Don't mix images from stock ROMs with custom ones.
Perfect! Thanks so much for taking the time to reply. I'm way out of my league with this, but I am learning what I can. @LuK1337 thanks for your efforts keeping the OP8P up to date.
 

edutchie

Member
Mar 10, 2021
14
1
Alright, new problem. My modem seems to be off. My device cannot call, text, or recieve mobile data. I have tried apn settings, restarting, resetting, wiping everything and following LineageOS instructions from start to finish, and still:
  • The network icon shows and exclamation point, no bars.
  • Settings > Network and Internet > Calls and SMS says "Red Pocket (Temporarily unavaliable)
  • Settings > About phone > SIM status (sim slot 1) says "Mobile network state: Disconnected" and "Service state: Radio off"
  • *#*#4636#*#* does detect the phone number on the SIM, but the "Mobile Radio Power" toggle is off and doesn't turn on.
I have confirmed the sim works in other devices.
lineage-19.1-20221204-nightly, with accompanying recovery.
Any suggestions?
 
Last edited:

d3viou5

Senior Member
Jun 4, 2007
236
58
Alright, new problem. My modem seems to be off. My device cannot call, text, or recieve mobile data. I have tried apn settings, restarting, resetting, wiping everything and following LineageOS instructions from start to finish, and still:
  • The network icon shows and exclamation point, no bars.
  • Settings > Network and Internet > Calls and SMS says "Red Pocket (Temporarily unavaliable)
  • Settings > About phone > SIM status (sim slot 1) says "Mobile network state: Disconnected" and "Service state: Radio off"
  • *#*#4636#*#* does detect the phone number on the SIM, but the "Mobile Radio Power" toggle is off and doesn't turn on.
I have confirmed the sim works in other devices.
lineage-19.1-20221204-nightly, with accompanying recovery.
Any suggestions?
When you upgraded from 18.1 to 19, did the modem work before everything else we've talked about? Did you just wipe the 19.1 install or msm back to stock?

I'm not sure as I've never experienced this myself, but it could be something to do with the base firmware.

18.1 is based on android 11 so I the issue may be there. You could try a dirty flash of 19.1, but I suspect your only fix will be to msm a oneplus stock ROM and try again to install lineage. (Complete wipe)
 

edutchie

Member
Mar 10, 2021
14
1
When you upgraded from 18.1 to 19, did the modem work before everything else we've talked about? Did you just wipe the 19.1 install or msm back to stock?

I'm not sure as I've never experienced this myself, but it could be something to do with the base firmware.

18.1 is based on android 11 so I the issue may be there. You could try a dirty flash of 19.1, but I suspect your only fix will be to msm a oneplus stock ROM and try again to install lineage. (Complete wipe)
The modem worked on 18.1
By "wipe," I mean I just wiped the install. I must have botched the MSM because she's as bricked as they come now. I followed these instructions to the best of my abilities, but always get "Sahara communication failed." Now it won't even start to recovery. Power button, volume buttons, any combonation thereof, dead. Nothing. The only spark of life is through EDL, it does connect to MSM. Attempting to charge to full now (no lights), I may try resuscitation again tomorrow evening. Should I move this to the MSM thread?

EDIT: I am a complete idiot. The battery was dead. While messing around with it earlier, the battery was slowly draining, and since I was only in the recovery and MSM tool, I just thought it was still almost full and didn't top it off. I don't deserve your help, I'm too dense. Update to follow.
 
Last edited:

d3viou5

Senior Member
Jun 4, 2007
236
58
The modem worked on 18.1
By "wipe," I mean I just wiped the install. I must have botched the MSM because she's as bricked as they come now. I followed these instructions to the best of my abilities, but always get "Sahara communication failed." Now it won't even start to recovery. Power button, volume buttons, any combonation thereof, dead. Nothing. The only spark of life is through EDL, it does connect to MSM. Attempting to charge to full now (no lights), I may try resuscitation again tomorrow evening. Should I move this to the MSM thread?

EDIT: I am a complete idiot. The battery was dead. While messing around with it earlier, the battery was slowly draining, and since I was only in the recovery and MSM tool, I just thought it was still almost full and didn't top it off. I don't deserve your help, I'm too dense. Update to follow.
Ouch! Bummer!

At least if its recognised in MSM even only for a bit you should be fine. Don't forget EDL mode times out if there is no activity pretty quickly, so as soon as it pops up in MSM, start the flash process and you should be good.

Once you are back on stock, keep running through the OTA's restarting each time so you have the latest firmware on both slots. Saves a lot of hasstle further down the line and should make sure you are prepared for installing Lineage 19.1 or any other A12 custom rom.
 

d3viou5

Senior Member
Jun 4, 2007
236
58
Ouch! Bummer!

At least if its recognised in MSM even only for a bit you should be fine. Don't forget EDL mode times out if there is no activity pretty quickly, so as soon as it pops up in MSM, start the flash process and you should be good.

Once you are back on stock, keep running through the OTA's restarting each time so you have the latest firmware on both slots. Saves a lot of hasstle further down the line and should make sure you are prepared for installing Lineage 19.1 or any other A12 custom rom.
Also, make sure you are using the original OP8pro USB cable, or a high quality one when flashing. Those have caused problems in MSM as well.
 

[email protected]_

Senior Member
Oct 18, 2012
79
3
I still can't figure it out what's wrong with wireless charging. Except this everything works really great. Cable charging works fine. Wireless charging is fast but phone can't reach 100%. After all night battery have 73% and percentage going down really fast for the first 10%
I try turn off magisk module - input power control from charge control app which i didn't install but it was there after flashing magisk
 

edutchie

Member
Mar 10, 2021
14
1
Ouch! Bummer!

At least if its recognised in MSM even only for a bit you should be fine. Don't forget EDL mode times out if there is no activity pretty quickly, so as soon as it pops up in MSM, start the flash process and you should be good.

Once you are back on stock, keep running through the OTA's restarting each time so you have the latest firmware on both slots. Saves a lot of hasstle further down the line and should make sure you are prepared for installing Lineage 19.1 or any other A12 custom rom.
MSM worked after a full charge, running the OTA's now. I tested the SIM and it worked, so modem is back! Once the OTA's are done I'll try lineage 19.1 again. What an adventure. For a while I was having some regrets.
 

edutchie

Member
Mar 10, 2021
14
1
When you upgraded from 18.1 to 19, did the modem work before everything else we've talked about? Did you just wipe the 19.1 install or msm back to stock?

I'm not sure as I've never experienced this myself, but it could be something to do with the base firmware.

18.1 is based on android 11 so I the issue may be there. You could try a dirty flash of 19.1, but I suspect your only fix will be to msm a oneplus stock ROM and try again to install lineage. (Complete wipe)
  • The network icon shows and exclamation point, no bars.
  • Settings > Network and Internet > Calls and SMS says "Red Pocket (Temporarily unavaliable)
  • Settings > About phone > SIM status (sim slot 1) says "Mobile network state: Disconnected" and "Service state: Radio off"
  • *#*#4636#*#* does detect the phone number on the SIM, but the "Mobile Radio Power" toggle is off and doesn't turn on.

Modem issue on 19.1
The SIM worked fine on stock after MSM all the way to the latest OTA update. After following the install instructions word for word, re-downloading from official sources, we're back to square one. Is there anything I can provide that would be useful to further document the issue?
 

d3viou5

Senior Member
Jun 4, 2007
236
58
Modem issue on 19.1
The SIM worked fine on stock after MSM all the way to the latest OTA update. After following the install instructions word for word, re-downloading from official sources, we're back to square one. Is there anything I can provide that would be useful to further document the issue?
Did you update all the way to A13 or stop at A12-C33?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    3
    If someone has a workaround to get past the "The current image boot/recovery have been destroyed" after flashing dtbo&recovery images please let us know. I am stuck with oos12 which has become intolerable to use nowadays.
    Any advice or suggestion is welcome :)
    Can you try flashing vbmeta from https://mirror.math.princeton.edu/pub/lineageos/full/instantnoodlep/20220825/?
    2
    Does someone have a cheat on installing gapps? I've tried all of them with installing alongside lineage or installing after a reboot. NikGapps, Opengapps, and MindtheGapps from 12.1 arm64. One of the major problems I see is that the play store is hanging.

    I am using mindthegapps without having any kind of issue so far.
    How to pass SafetyNet and user GPay?

    I used magisk to flash "safetynet fix" and "magiskhide props config" modules. After that you need to run props configuration via terminal (search for termux app in playstore) and change the fingerprint of your device.
    That's it. You can also use yasnac app from play store to see if your device can pass safenet attestation successfully.

    good morning, does 5 g, face unlock and fingerprint work on the oneplus 8 pro (EU)?
    5g and fingerprint are working fine. Never checked face unlock, so i can't tell.
    2
    Same issue here.
    Used msm tool to go back to oos 11.0.4.4 and then updated the device up to c33.
    Flashing the dtbo and then the recovery images damage the boot.

    I have also tried flashing recovery from unofficial los and twrp. Nothing seems to be working
    Msmtool,
    local update to c33,
    reboot,
    local update to c33 again to make sure both slots are C33
    reboot,
    flash dtbo
    flash recovery
    Sideload LOS.