[ROM][05/20][11.0] Yet another AOSP project [OP7P][STABLE]

[ClassickWORLD]

@ClassickWORLD You can try my method:
1. Flash LOS latest
2. Flash the boot.img of YAAP in fastboot
3. Reboot recovery, format data to f2fs
4. Sideload YAAP rom .zip

What is LOS?

 

[Zhuang zhuang]

What is LOS?

LineageOS

 

[OmkarTheAndroid]

New update is up with fixed WiFi, new launcher stuff and support for ntfs on otg

 

[HippoMan]

@ClassickWORLD You can try my method:
1. Flash LOS latest
2. Flash the boot.img of YAAP in fastboot
3. Reboot recovery, format data to f2fs
4. Sideload YAAP rom .zip

These steps worked for me! ... after other flashing methods failed.
Thank you!

Now, however, it seems like I can no longer take nandroid backups, because the LOS recovery has been installed, and "fastboot boot twrp.img" does not work.

How can we take usable backups with the LOS recovery?

 

[Zhuang zhuang]

These steps worked for me! ... after other flashing methods failed.
Thank you!

Now, however, it seems like I can no longer take nandroid backups, because the LOS recovery has been installed, and "fastboot boot twrp.img" does not work.

How can we take usable backups with the LOS recovery?

Actually, I didn't even use the nandroid backup since A10, so I know nothing about it

 

[HippoMan]

Actually, I didn't even use the nandroid backup since A10, so I know nothing about it

Do you utilize some other backup method now?

 

[HippoMan]

Do you utilize some other backup method now?

And a related question: back in the days of TWRP, if a Magisk module caused some kind of freeze or bootloop, I could boot into TWRP and use its file manager in order to delete the offending module.

But now, if I install a Magisk module which prevents my device from booting, how can I get onto any of my filesystems in Recovery mode in order to delete that module? The LOS Recovery that is installed with the latest YAAP ROM doesn't seem to allow anything like this.

 

[Zhuang zhuang]

Do you utilize some other backup method now?

I use Swift Backup

And a related question: back in the days of TWRP, if a Magisk module caused some kind of freeze or bootloop, I could boot into TWRP and use its file manager in order to delete the offending module.

But now, if I install a Magisk module which prevents my device from booting, how can I get onto any of my filesystems in Recovery mode in order to delete that module? The LOS Recovery that is installed with the latest YAAP ROM doesn't seem to allow anything like this.

I didn't think about this issue, maybe you can ask someone in LOS thread

 

[HippoMan]

I use Swift Backup

I didn't think about this issue, maybe you can ask someone in LOS thread

Thank you very much.

I checked in the YAAP Telegram thread, and it turns out that I can fix bootloops that are caused by Magisk module errors as follows:

(1) Try to boot and get into the bootloop ... wait for the boot animation to start
(2) Connect the device to a computer via USB
(3) On the computer, run this: adb wait-for-device shell magisk --remove-modules

This worked for me, and it should work as long as the "adbd" service is started on the device, which is almost always the case unless the device is seriously bricked.

This removes all Magisk modules, so after rebooting, any desired Magisk modules will have to be reinstalled.

 

[melinder]

I flashed this rom on oos 11.0.2 stable and wifi is disconnected too often.
should i flash this rom wih oos ob4 to get wifi fixed?

 

[Zhuang zhuang]

I flashed this rom on oos 11.0.2 stable and wifi is disconnected too often.
should i flash this rom wih oos ob4 to get wifi fixed?

I flashed on 11.0.2 too but see no issue here. Did you flash through LOS recovery & format datat to f2fs or not?

 

[melinder]

I flashed on 11.0.2 too but see no issue here. Did you flash through LOS recovery & format datat to f2fs or not?

Yes I flashed rom though that method.
But it seems like my personal problem... thank you for your answer.

 

[Zhuang zhuang]

The rom cannot charge with non-Oneplus charging brick, but it works after reboot. I think this is kernel relating issue (I had same issue with arter kernel on A10)

 

[UpperCenter]

@OmkarTheAndroid Does this ROM work for OnePlus 7 Pro 5G edition?

 

[jaggillararla]

Did anyone make a .bat file to flash this ROM?

 

[famewolf]

These steps worked for me! ... after other flashing methods failed.
Thank you!

Now, however, it seems like I can no longer take nandroid backups, because the LOS recovery has been installed, and "fastboot boot twrp.img" does not work.

How can we take usable backups with the LOS recovery?

You'll need the "fbev2" version of TWRP by nebrassy for fastboot boot to work.

https://androidfilehost.com/?fid=14943124697586351426 or seach "nebrassy fbev2 oneplus 7 pro" on xda.

 

[HippoMan]

You'll need the "fbev2" version of TWRP by nebrassy for fastboot boot to work.

https://androidfilehost.com/?fid=14943124697586351426 or seach "nebrassy fbev2 oneplus 7 pro" on xda.

Thank you very much. I'm familar with the Nebrassy TWRP and the "fbev2" version. I didn't know if this would also work with YAAP, and now I'm glad to know that it indeed does.

 

[dankovac1999]

Thank you very much. I'm familar with the Nebrassy TWRP and the "fbev2" version. I didn't know if this would also work with YAAP, and now I'm glad to know that it indeed does.

Could you please explain me what are the differences between normal and fbev2 recovery. Or just send me link to thread. I was unable to find information on google.

 

[famewolf]

Could you please explain me what are the differences between normal and fbev2 recovery. Or just send me link to thread. I was unable to find information on google.

Try duckduckgo next time. It was in the paragraph shown for the 2nd result. It's a new type of encryption.

 

[Toutatis_]

Vanilla variant user here.

After updating from latest 13 build to 14 via OTA (20231123 build), it seems that location no longer works at all. Neither Organic Maps nor OsmAnd~ can find my position. In microG settings > Self-Check, all location related permissions are still granted. Tried to manually update microG to v0.3.0.233515, to no avail. The issue persists after a clean flash.

Anyone else?

Edit: GPStest cannot retrieve any data either.

Edit 2: It fixed itself automagically after even more attempts.