[ROM][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord N10/billie]

[gaww]

nice you got it working in the end!

1. no need to be concerned - this is normal for a not official lineageOS build.
2. Probably from within the rom, but the dev is offline since april...

Tell me about it....

 

[diablo090909]

Can you please post the camera and dialer apps; i want to see if i can install those apps on my N10 5G. Does this dialer app have call recording option?

 

[eriklion]

Can you please post the camera and dialer apps; i want to see if i can install those apps on my N10 5G. Does this dialer app have call recording option?

Not likely unless your country/region allows it. For example, it's built into lineage, but if you're on a US network, call recording is not present.

Posting the Dialer and Camera apps would not help. would also need libraries that you couldnt install without root.

 

[diablo090909]

Not likely unless your country/region allows it. For example, it's built into lineage, but if you're on a US network, call recording is not present.

Posting the Dialer and Camera apps would not help. would also need libraries that you couldnt install without root.

I was able to get it... a little round about way.
1. installed the android 11 one plus apk beta.
2. installed another app that set the call recording property to 1.
3. only thing is i need to manually open the app everytime i rebooted.

 

[texasslim281]

am I the only one who couldnt even get this to install? I have unlocked bootloader and flashed derpfest successfully. wanted to try lineage and it got me bootloader loop. finally found the correct tmobile rom that I had to install from windows pc and decided to try it again straight from factory settings and unlock bootloader again etc, same results.

 

[hidroela]

I was able to get it... a little round about way.
1. installed the android 11 one plus apk beta.
2. installed another app that set the call recording property to 1.
3. only thing is i need to manually open the app everytime i rebooted.

would you mind to share the link of the app to change the property to 1

 

[onlyfanofopensource]

Please forgive my ignorance but I looked up and down this thread and cannot find a link for the TWRP .. I see pinned top link for the rom, thank you...but no TWRP

 

[RTamas91]

Could anyone post here some browser benchmark results? (speedometer for example)
I'm about to flash this ROM but I would like to know first if it is worth it.

I'm currently gettign some really low numbers on speedometer 2.0 (13~)
My 3 year old ASUS zenfone Max Pro M1 gets around 33~

 

[killerbee0077]

ADB sideload

Okay, since EVERYONE seems to be having problems here like I did, I'll make it simple.

DON'T USE TWRP, it's outdated software we really don't need it unless you're making backups.

OP in thread obviously didn't have the same problems we did.

1. Download Recovery.IMG and ROM.zip from OP. Magisk.apk from their site.
2. Get phone into fastboot, at this point you should already have a backup made because beating the dynamic partition will eventually destroy your info anyway.
3. fastboot flash recovery RECOVERY.IMG from OP. Use volume buttons to go to recovery now.
4. From the new Android 11 recovery, factory data reset. Advanced boot into bootloader.
5. NOW fastboot boot RECOVERY.IMG, takes you into recovery directly and nails down the wiggly partition.
6. Update, ADB sideload ROM.ZIP
7. Reboot system. You now have Lineage.
8. From inside Lineage ROM boot into recovery again.
9. Update adb sideload MAGISK.APK, you don't rename it or anything, it'll give you a signature verification error on phone, go ahead anyway, magisk patches from outside ROM, runs code, reboot into system.
10. Install MAGISK.APK, follow directions. Direct install. ENJOY.
11. Now if you want GAPPS use Android 11 magiskgapps module.

DON'T TRY TO PATCH BOOT.IMG FROM OP: BOOTLOOP
DON'T TRY TO INSTALL NICKGAPPS, IT'S A FRUITLESS ENDEAVOR.
AS LONG AS YOU CAN ACCESS BOOTLOADER STILL FOLLOW THESE DIRECTIONS EXACTLY TO FIX YOUR FUDGE UPS, IT'S A SIMPLE SOLUTION TO WHAT YOU MADE INTO A COMPLICATED PROBLEM BY TRYING TO OUTTHINK THE SOFTWARE.

in Step 4, when i go to recovery mode from fastboot using volume key, it takes me to the custom rom recovery, instead of android 11's own recovery, can you please help?

 

[Futtbucker34]

I got MSM to flash it from my Windows work laptop then tried the whole process over after unlocking the bootloader again. After flashing the Lineage zip it started its bootloader bootloops again.. lol There must be something different here.. Again, I noticed the recovery image included in the download section on this forum is for Pixel Experience then it changes to Lineage after flashing the rom. Should I be using a Lineage recovery image?

EDIT: After trying a few more times it finally boot to Lineage and got magisk.

Thanks!

 

[Futtbucker34]

I can't get this to install. Everytime I try to sideload the lineage rom I get this error
"loading: 'lineage.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc"
and adb crashes.

I used msm tool 3 times already and re followed the steps but keep getting stuck here. Anyone know what i'm doing wrong??? Help lol

I've done all the steps and get stuck at 6 "

1. Download Recovery.IMG and ROM.zip from OP. Magisk.apk from their site.
2. Get phone into fastboot, at this point you should already have a backup made because beating the dynamic partition will eventually destroy your info anyway.
3. fastboot flash recovery RECOVERY.IMG from OP. Use volume buttons to go to recovery now.
4. From the new Android 11 recovery, factory data reset. Advanced boot into bootloader.
5. NOW fastboot boot RECOVERY.IMG, takes you into recovery directly and nails down the wiggly partition.
6. Update, ADB sideload ROM.ZIP"


ps. When I go to pixelexperience recovery mode i noticed in the bottom its saying

"E:Failed to bind mount /mnt/staging/emulated/media/0 to storage/emulated: No such file or directory
E:emulated failed to bind mount /mnt/staging/emulated/media/on storage/emulated: No such file or directory"

Im pretty sure its why its not working the partition is still not right even tho I used msm tool from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4245461/

someone said you have to configure the oxygen os first so i went and did that .

Now at pixel recovery it don't show that it "failed to bind mount" error in the bottom anymore, but now it says "E:recvmsg no buffer space available"

any ideas?

 

[eihli]

I scanned this thread and haven't seen mentioned the issue I'm having.

Everything installed fine and the phone appeared to work great for a few days. I was texting and calling a few people.

Then I realized some people had been texting me and they weren't coming through. I realized I couldn't message them either. Messages would say "sending..." for a bit and then fail.

I took my phone to ATT and they said my online account was in a state they hadn't seen before. They tried to reset my passcode and their system was giving them a message that my account had no number attached to it. I had already experienced the same error message while trying to reset my passcode from home.

I wouldn't have imagined an issue in their system would be related to this ROM. But as soon as I put my SIM in a different phone, I was able to reset the passcode.

In brief... on ATT, I can only successfuly SMS/call about half of my contacts. I tried a T-mobile SIM card and I wasn't able to send SMS to anyone (but was able to call at least one person).

I plan on looking into this some more but wanted to leave a note here in the meantime.

 

[JJF2]

I've bricked my Nord N10 trying this and can't get past this screen. It shows up for a few seconds and then shuts my phone back off.

 

[ninjasinabag]

I've bricked my Nord N10 trying this and can't get past this screen. It shows up for a few seconds and then shuts my phone back off.

That screen shows up anyways because your phones bootloader is unlocked, you're probably getting a failed boot though from something else down the line.

 

[JJF2]

That screen shows up anyways because your phones bootloader is unlocked, you're probably getting a failed boot though from something else down the line.

I have not figured out any other buttons to push to get it to start on another screen. I recall several mos ago when I gave up on this project that I was able to push the right buttons and get to the Fastboot screen and could connect to my Win10 but not having any luck now.

EDIT: Scratch that this (QUALCOMM) just popped up when I was connected to my laptop.

EDIT2: Was able to connect to adb device and now have Fastboot screen up.

EDIT3: Now able to send recovery.img and did factory reset, but cannot go further.

 

[TechNerdGolla]

I have not figured out any other buttons to push to get it to start on another screen. I recall several mos ago when I gave up on this project that I was able to push the right buttons and get to the Fastboot screen and could connect to my Win10 but not having any luck now.

EDIT: Scratch that this (QUALCOMM) just popped up when I was connected to my laptop.

EDIT2: Was able to connect to adb device and now have Fastboot screen up.

EDIT3: Now able to send recovery.img and did factory reset, but cannot go further.

Bruh i would say you could try msm tool to restore your phone.

[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...

forum.xda-developers.com

use the link to MSM toolbox once you put your phone is edl mode you should be able to recovery ur phone regardless of any trouble.

 

[boffster99]

Okay, since EVERYONE seems to be having problems here like I did, I'll make it simple.

DON'T USE TWRP, it's outdated software we really don't need it unless you're making backups.

OP in thread obviously didn't have the same problems we did.

1. Download Recovery.IMG and ROM.zip from OP. Magisk.apk from their site.
2. Get phone into fastboot, at this point you should already have a backup made because beating the dynamic partition will eventually destroy your info anyway.
3. fastboot flash recovery RECOVERY.IMG from OP. Use volume buttons to go to recovery now.
4. From the new Android 11 recovery, factory data reset. Advanced boot into bootloader.
5. NOW fastboot boot RECOVERY.IMG, takes you into recovery directly and nails down the wiggly partition.
6. Update, ADB sideload ROM.ZIP
7. Reboot system. You now have Lineage.
8. From inside Lineage ROM boot into recovery again.
9. Update adb sideload MAGISK.APK, you don't rename it or anything, it'll give you a signature verification error on phone, go ahead anyway, magisk patches from outside ROM, runs code, reboot into system.
10. Install MAGISK.APK, follow directions. Direct install. ENJOY.
11. Now if you want GAPPS use Android 11 magiskgapps module.

DON'T TRY TO PATCH BOOT.IMG FROM OP: BOOTLOOP
DON'T TRY TO INSTALL NICKGAPPS, IT'S A FRUITLESS ENDEAVOR.
AS LONG AS YOU CAN ACCESS BOOTLOADER STILL FOLLOW THESE DIRECTIONS EXACTLY TO FIX YOUR FUDGE UPS, IT'S A SIMPLE SOLUTION TO WHAT YOU MADE INTO A COMPLICATED PROBLEM BY TRYING TO OUTTHINK THE SOFTWARE.

 

[ssabchew]

Is there an update?

I've just installed LineageOS - thanks for instructions!

What does not work - Work in Progress:
UI has ridiculous small font
All icons are too small - sams like DPI is not accurate.
UI does not respect back camera - so I have a black spot there.
Wifi - Does not list any network.

 

[ssabchew]

Okay, since EVERYONE seems to be having problems here like I did, I'll make it simple.

DON'T USE TWRP, it's outdated software we really don't need it unless you're making backups.

OP in thread obviously didn't have the same problems we did.

1. Download Recovery.IMG and ROM.zip from OP. Magisk.apk from their site.
2. Get phone into fastboot, at this point you should already have a backup made because beating the dynamic partition will eventually destroy your info anyway.
3. fastboot flash recovery RECOVERY.IMG from OP. Use volume buttons to go to recovery now.
4. From the new Android 11 recovery, factory data reset. Advanced boot into bootloader.
5. NOW fastboot boot RECOVERY.IMG, takes you into recovery directly and nails down the wiggly partition.
6. Update, ADB sideload ROM.ZIP
7. Reboot system. You now have Lineage.
8. From inside Lineage ROM boot into recovery again.
9. Update adb sideload MAGISK.APK, you don't rename it or anything, it'll give you a signature verification error on phone, go ahead anyway, magisk patches from outside ROM, runs code, reboot into system.
10. Install MAGISK.APK, follow directions. Direct install. ENJOY.
11. Now if you want GAPPS use Android 11 magiskgapps module.

DON'T TRY TO PATCH BOOT.IMG FROM OP: BOOTLOOP
DON'T TRY TO INSTALL NICKGAPPS, IT'S A FRUITLESS ENDEAVOR.
AS LONG AS YOU CAN ACCESS BOOTLOADER STILL FOLLOW THESE DIRECTIONS EXACTLY TO FIX YOUR FUDGE UPS, IT'S A SIMPLE SOLUTION TO WHAT YOU MADE INTO A COMPLICATED PROBLEM BY TRYING TO OUTTHINK THE SOFTWARE.

What you mean by:
"""
Download Recovery.IMG and ROM.zip from OP
"""
Could you share a URL?

 

[nomadicdev]

deleted