[ROM][COMPLETED][9.0.0_r44] AospExtended ROM V6.6 [OFFICIAL][PL2]

[theimpulson]

Hey I'm new to this stuff of custom romming and stuff can you tell me what all downloads I must do and all the trustable sites which can provide me with necessary tools.
Also please tell me the instructions I know it's long but I never did this and I need some professional help for this.

And I'm choosing your rom because it is original and I can believe on it I did not go for lineage is unofficial because I'm just 17 and I don't to brick my phone ..

As summer vacations are going on I have planned to learn the above stuff:victory:

Instructions are posted in 1st post. Read it.

 

[kunal Basumatari]

Instructions are posted in 1st post. Read it.

Yeah I remember to first unlocking bootloader but do you have any free website where I can unlock it. Official Nokia web bootloader is not working as it is not supported by them officially. I tried to Google for free unlocking bootloader but all are paid

---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------

Instructions are posted in 1st post. Read it.

Ah yeah I collected all basic info. But do you have any idea where I can find free bootloader unlock site. The official by Nokia does not work anymore and alternatives are paid...
Any site where I can find it for free??

 

[AshleyNG2]

The official by Nokia does not work anymore and alternatives are paid...
Any site where I can find it for free??

Currently there is no free method to unlock the bootloader, it will cost you around $5 to get it unlocked.

There is probably another thread better suited for discussing this rather than here.

 

[PicaMaru]

Can someone install netflix? It tells me it's not compatible with the device

Solved, now works

 

[AshleyNG2]

That's an selinux denial. It is easy to fix. I will do it tonight and will check again.

Will 'Setenforce 0' provide a temporary fix for this until you push the build out?

 

[theimpulson]

Will 'Setenforce 0' provide a temporary fix for this until you push the build out?

New update will be pushed in next 24 hours. I suggest to wait. New builds has improvements for AUX as well.

 

[Solannae]

Hi,

My internal storage is encrypted when I flash this rom, coming from pure stock. Any way to fix this ?

 

[AshleyNG2]

Hi,

My internal storage is encrypted when I flash this rom, coming from pure stock. Any way to fix this ?

Format your data partition in TWRP.

 

[theimpulson]

AospExtended v6.6 Changelog

- Merge June security patch (9.0.0_r40)
- Update all translations
- Update all pre-built apks
- Update all of our packages
- Update APN configs
- Update Weather client
- Update Boostframework
- Update our launcher with Quick Space
- Add Pocket Lock feature
- Add Sysserv support for Substratum theme engine
- Add Pixel Navigation bar animation
- Add Live Display
- Add Font QS tile
- Add Aggressive battery saving feature
- Add Android Q's seek bar to media notification
- Add Android Q's lock screen clock style
- Add Android Q's status bar battery icon
- Add Less boring heads up feature
- Add Battery animation in settings
- Add a new Elegant UI theme
- Improve UI for certain applications
- Improve three finger swipe screenshot feature
- Improve some UI/UX aspects
- Improve auxiliary camera support
- Improve Bluetooth SBC
- Improve Location QS tile
- Fix battery icon shortcut
- Fix some theme issues
- Fix AOSP WFD (Miracast) support
- Fix audio server crashes again
- Under the hood improvements
- Bug fixes and performance improvements

- Merge Latest CAF Tag
- Update Vendor to Stock May Build
- Fix VoLTE
- Enable Wireguard support in Kernel
- Enable OTG by default
- Build required display libs
- Allow appdomain to get vendor_camera_prop

OTA is broken as of now. Fix is in testes. Kindly use TWRP to flash this and next possible update. NFC and CTS Tests issue is still unotuched so might be having issues. Other than that, it should be fine. Thanks.

Edit:- OTA is now fixed. Grab the new apk and push it into system/priv-app/Updates using TWRP and it will start working again. Thanks.

 

[AshleyNG2]

AospExtended v6.6

OTA is now fixed. Grab the new apk and push it into system/priv-app/Updates using TWRP and it will start working again. Thanks.

Updated via OTA, took a while but booted up successful, thanks for keeping my device alive :good:

 

[PicaMaru]

before update tried to do twrp backup, but failed.

 

[AshleyNG2]

@TheImpulson Camera issue still persists after update, first few shots worked now none will save.

Here is the full log.

Seen some errors about autofocus calibration and the same vendor.camera.aux.packagelist error from before.

 

[theimpulson]

@TheImpulson Camera issue still persists after update, first few shots worked now none will save.

Here is the full log.

Seen some errors about autofocus calibration and the same vendor.camera.aux.packagelist error from before.

Try changing selinux to permissive and try it again. I see more selinux denials for vendor_camera_prop.

 

[AshleyNG2]

Try changing selinux to permissive and try it again. I see more selinux denials for vendor_camera_prop.

@TheImpulson In terminal I entered su / setenforce 0 and the issue still persists. I have attached the log.

Hopefully these extracts help identify the issue:

06-12 13:32:43.120 E/CamComm1.0-MD(721): Mismatched tag type when updating entry enable (-2146762752) of type byte; got type int32 data instead

06-12 13:32:44.724 E/CamComm1.0-MD(721): Mismatched tag type when updating entry is_main (-2146762751) of type byte; got type int32 data instead

06-12 13:32:41.891 E/soundtrigger(719): audio_extn_sound_trigger_update_stream_status: invalid input device 0x0, for event 3

06-12 13:32:43.572 E/OisListener(8404): Null pointer for OIS data. OIS API version: 2

 

[Greywander87]

Greetings, first time poster to this forum. I just recently got a Nokia 6.1 (TA-1045) and am happy to have found this thread. I see TheImplosion was also working on a Lineage OS ROM, but has stopped maintaining it. I'm curious what the difference is between Lineage OS and AOSP Extended, but I'll go with AOSP Extended for now.

I just messaged hikari_calyx to ask for an unlock code for the bootloader. I'm very new to all of this, but I think I can figure things out eventually.

I read somewhere that your phone needs to be unencrypted before you try to unlock it or install a ROM on it, otherwise you get locked out as it can't read the encrypted phone. I can find under Security and Location where it says my phone is encrypted, but there doesn't seem to be any option to disable encryption. The OP doesn't seem to mention encryption, though. Do I need to unencrypt my phone, and if so, how do I do so?

Edit:- OTA is now fixed. Grab the new apk and push it into system/priv-app/Updates using TWRP and it will start working again. Thanks.

Does this need to be installed on top of the base AOSP Extended ROM flash, or is it now included in the latest release?

Alright, I think that's all for now. I'll be back if I have more questions, but hopefully I'll be able to figure it out. Thanks for all the hard work on this project.

 

[AshleyNG2]

@TheImpulson logs previously attached were from GCAM, the log attached to this post is from the stock camera with setenforce 0.

 

[Greywander87]

While I'm waiting to hear back about getting an unlock code, I did have another question. Is it possible to relock the bootloader after installing AOSP Extended? My understanding is that you can't, and that having the bootloader unlocked makes it trivial to access the device if someone has physical access to the phone. Obviously I'd hope this would never happen, but in the event that it did I'd prefer the person not be able to access the phone.

After searching for the answer, it seems that it is possible to relock the bootloader, but that you should only do so with stock Android installed. Is there any way to secure my phone after installing AOSP Extended so it can't be accessed through the bootloader?

 

[theimpulson]

@TheImpulson logs previously attached were from GCAM, the log attached to this post is from the stock camera with setenforce 0.

Alright, I will check what's wrong. Thanks.

 

[theimpulson]

Greetings, first time poster to this forum. I just recently got a Nokia 6.1 (TA-1045) and am happy to have found this thread. I see TheImplosion was also working on a Lineage OS ROM, but has stopped maintaining it. I'm curious what the difference is between Lineage OS and AOSP Extended, but I'll go with AOSP Extended for now.

I am in AospExtended Team. That allows me to push OTA updates like stock. Moreover, I can add features and stuff required in ROM side as AEX is somewhat more restrictions free than LineageOS.

I just messaged hikari_calyx to ask for an unlock code for the bootloader. I'm very new to all of this, but I think I can figure things out eventually.

I read somewhere that your phone needs to be unencrypted before you try to unlock it or install a ROM on it, otherwise you get locked out as it can't read the encrypted phone. I can find under Security and Location where it says my phone is encrypted, but there doesn't seem to be any option to disable encryption. The OP doesn't seem to mention encryption, though. Do I need to unencrypt my phone, and if so, how do I do so?

I suggest to do a clean flash that includes wiping storage to avoid any issues.

Does this need to be installed on top of the base AOSP Extended ROM flash, or is it now included in the latest release?

Alright, I think that's all for now. I'll be back if I have more questions, but hopefully I'll be able to figure it out. Thanks for all the hard work on this project.

You need to install it on top of latest release for now. I will include it in next release probably after 26th when guests leave. (I got some guests, so not gonna do anything meanwhile)

While I'm waiting to hear back about getting an unlock code, I did have another question. Is it possible to relock the bootloader after installing AOSP Extended? My understanding is that you can't, and that having the bootloader unlocked makes it trivial to access the device if someone has physical access to the phone. Obviously I'd hope this would never happen, but in the event that it did I'd prefer the person not be able to access the phone.

After searching for the answer, it seems that it is possible to relock the bootloader, but that you should only do so with stock Android installed. Is there any way to secure my phone after installing AOSP Extended so it can't be accessed through the bootloader?

Possible I assume, but not suggested. I can give multiple reasons but lets not do that.

 

[theimpulson]

Meanwhile, as I didn't checked before, I didn't included this in changelog, but CTS Tests are now getting passed. In case someone wants, you can use Google Pay. I tried using it yesterday and it works fine.