Develop Bugs

[ROM][GSI][9.0] Havoc-OS 2.7 for Lenovo Z5 Pro GT [L78032]

Download: Havoc-OS-v2.7-20190712-phhgsi_arm64_ab-Official.img.xz
Original Post: HERE
Note: you will need some program to extract the .img file from the downloaded .xz file.
How to install
To install use this tutorial HERE
Note: You will need to install the gapps
Known Bugs
Fingerprint not work
Slide functions not work
Automatic brightness not work
Fixing the 4G
1) Call to *#*#4636#*#*
2) Phone information
3) In "Set Preferred Network Type" select "LTE / UMTS auto (PRL)"
4) Finish
Fixing the Faceunlock(Smart Lock): Delete folder: /system/app/FaceLock/lib (Backup before removing)
Fixing the Bluetooth Audio A2DP: HERE
Fixing the NFC: HERE
Note: if you have a password on the device, in order to access TWRP you need to remove your password.
To fix other unknown bugs in the original post

Thanks for the post. This run great but I've upgraded and been running Havoc OS 3 GSI (Android 10) for a week now great results (same caveats as above apply).

miji2 said:
Thanks for the post. This run great but I've upgraded and been running Havoc OS 3 GSI (Android 10) for a week now great results (same caveats as above apply).
Click to expand...
Click to collapse
Hi, thank you if it wasn't for you i would've never been able to install twrp. However, i've got some questions. Do you recommend installing GSI 3.0 ROM? Does it really increases SD855 overall performance? How do i install this rom, Magisk and the gapps all in one, if it wipes all the data and has no micro sd slot, do the flash files get wiped too?

aldolzn066 said:
Hi, thank you if it wasn't for you i would've never been able to install twrp. However, i've got some questions. Do you recommend installing GSI 3.0 ROM? Does it really increases SD855 overall performance? How do i install this rom, Magisk and the gapps all in one, if it wipes all the data and has no micro sd slot, do the flash files get wiped too?
Click to expand...
Click to collapse
Nope, no performance increase if you go GSI ... but you do lose the fingerprint reader
I do it for novelty, consistency (to maintain OS experience across devices), and security rather than performance. In most cases going to newer OS means you slow down. But personally I don't find 340k++ on Antutu to be slow so I am OK with that. As a bonus, gcam 7.x actually works for me on Android 10 but not on default global ROM.
So to get going with that, what I use to salvage all my files is a USB-C to SD OTG adapter and I store all files there.
Important --> do full TWRP back up of all partitions with OTG USB as storage for it. Better safe than sorry.
Then I flash GSI IMG file to system image partition, resize system, flash nano gapps, then format data and finally reboot.
After the first successful boot I go back to TWRP and flash Magisk from there. All set to go.
Going back is simply a matter of restoring the System + Boot backup and formatting data. Note, this will replace recovery so you need to fastboot and reinstall it.
Rinse and repeat for any other.
If you want performance increase you need to do full ZUI 10.5 flash via EDL recovery .. which I am still hesitant to do since it's not clear to me if bootloader will remain unlocked and if I can still do GSI after the fact.

miji2 said:
Nope, no performance increase if you go GSI ... but you do lose the fingerprint reader
I do it for novelty, consistency (to maintain OS experience across devices), and security rather than performance. In most cases going to newer OS means you slow down. But personally I don't find 340k++ on Antutu to be slow so I am OK with that. As a bonus, gcam 7.x actually works for me on Android 10 but not on default global ROM.
So to get going with that, what I use to salvage all my files is a USB-C to SD OTG adapter and I store all files there.
Important --> do full TWRP back up of all partitions with OTG USB as storage for it. Better safe than sorry.
Then I flash GSI IMG file to system image partition, resize system, flash nano gapps, then format data and finally reboot.
After the first successful boot I go back to TWRP and flash Magisk from there. All set to go.
Going back is simply a matter of restoring the System + Boot backup and formatting data. Note, this will replace recovery so you need to fastboot and reinstall it.
Rinse and repeat for any other.
If you want performance increase you need to do full ZUI 10.5 flash via EDL recovery .. which I am still hesitant to do since it's not clear to me if bootloader will remain unlocked and if I can still do GSI after the fact.
Click to expand...
Click to collapse
Ok, thanks for the advice! I would have to think it for a while before doing it. One last thing, the tutorial says that i have to deactivate DMverity or something, since i have the newer version of twrp, i can't find that option, is it still necesary? am i getting a bootloop by installing any unsigned rom? how do i avoid it? Thanks again. :laugh:

Thank's.
I use this ROM.
What do you do about the proximity sensor? In call, if I want to end the call or open the "in call UI", I need to open the slider, and after that press on the power butten

Also, internal storage show only 32gb, how I can access all the memory?

hi! can someone check this link? https://www.pling.com/s/Images/p/1347594/ (direct) https://github.com/Lucchetto/android_kernel_lenovo_sm8150

miji2 said:
Nope, no performance increase if you go GSI ... but you do lose the fingerprint reader
I do it for novelty, consistency (to maintain OS experience across devices), and security rather than performance. In most cases going to newer OS means you slow down. But personally I don't find 340k++ on Antutu to be slow so I am OK with that. As a bonus, gcam 7.x actually works for me on Android 10 but not on default global ROM.
So to get going with that, what I use to salvage all my files is a USB-C to SD OTG adapter and I store all files there.
Important --> do full TWRP back up of all partitions with OTG USB as storage for it. Better safe than sorry.
Then I flash GSI IMG file to system image partition, resize system, flash nano gapps, then format data and finally reboot.
After the first successful boot I go back to TWRP and flash Magisk from there. All set to go.
Going back is simply a matter of restoring the System + Boot backup and formatting data. Note, this will replace recovery so you need to fastboot and reinstall it.
Rinse and repeat for any other.
If you want performance increase you need to do full ZUI 10.5 flash via EDL recovery .. which I am still hesitant to do since it's not clear to me if bootloader will remain unlocked and if I can still do GSI after the fact.
Click to expand...
Click to collapse
The bootloader will remain unlocked. Good rom. Use 10.5 cn as daily driver (with every chinese app debloated)

Btw if you use an app like MoreLocale2 and use the ADB code the app gives you, you can change the kanguage of the phone in Zui. I used this app to change the language (for a big part) to Dutch.

miji2 said:
Thanks for the post. This run great but I've upgraded and been running Havoc OS 3 GSI (Android 10) for a week now great results (same caveats as above apply).
Click to expand...
Click to collapse
Does Havoc 3 still has issues with Bluetooth Audio A2DP? I could not fix this issue with earliers versions of havoc

Sheep888 said:
Does Havoc 3 still has issues with Bluetooth Audio A2DP? I could not fix this issue with earliers versions of havoc
Click to expand...
Click to collapse
What kind of issues did you have? How to reproduce?
EDIT: NVM, I think I see your other post about it. I will test tonight and let you know.

I tried havoc 2.9 but it remains in bootloop .. does this happen to you too?

lucabest2002 said:
I tried havoc 2.9 but it remains in bootloop .. does this happen to you too?
Click to expand...
Click to collapse
I only played with going from shipping ROM to Havoc/GSI and back (ie. no EDL/QPST flashing), so depending where you're coming from YMMV. You have to at least factory reset or maybe even fully wipe the device. Start with factory reset and try, but I think you may have to fully wipe internal storage because of encryption. Make sure you move your backups and any other files off internal storage to OTG USB storage before you wipe/format.
---------- Post added at 11:50 ---------- Previous post was at 11:46 ----------
Sheep888 said:
Does Havoc 3 still has issues with Bluetooth Audio A2DP? I could not fix this issue with earliers versions of havoc
Click to expand...
Click to collapse
So no go with Redmi AirDots or my QCY headphones. They discover OK, pair OK, but after connection the audio does not seem to be routed to bluetooth properly.

miji2 said:
I only played with going from shipping ROM to Havoc/GSI and back (ie. no EDL/QPST flashing), so depending where you're coming from YMMV. You have to at least factory reset or maybe even fully wipe the device. Start with factory reset and try, but I think you may have to fully wipe internal storage because of encryption. Make sure you move your backups and any other files off internal storage to OTG USB storage before you wipe/format.
---------- Post added at 11:50 ---------- Previous post was at 11:46 ----------
So no go with Redmi AirDots or my QCY headphones. They discover OK, pair OK, but after connection the audio does not seem to be routed to bluetooth properly.
Click to expand...
Click to collapse
Thanks for trying!
I tried it as well today, but still the same issues, i could control the playback with my headset (1more and libratone) but i could not hear the music.
Maybe a future update can solve the issue

installed havoc 2.9
nfc fixed with magisk module(didnt work when i tried "([AOSP 10.0] [2019-12-06] Quack Phh-Treble")
no slider detection so when playing whatsapp voice messages need to open slider or proximity sensor will cause screen to turn off.
double tap to wake doesnt work
whatsapp web the camera has issues focusing and solved by zooming the qr code in web browser
tried enabling aux camera (qualcom) in phh treble settings but still no option for 2nd camera on the back of device. have 1 back camera and selfie camera only.
only method i found to turn on screen from sleep is with power button.
cant test bluetooth audio since i dont have bluetooth earphones.
edit:AOD zip keeps display on only if i keep the slider open so proximty sensor is making it turn off when slider is closed.
adaptive brightness zip installed but still not working.
antutu score is almost 370k so pretty decent imo.

Do the problems that are named always occur?
And the problems of which the solution appears, are also problems that may occur?

Havoc 3.4?

GUIDE: Install GSI Treble Roms on Honor 8X Max ARE-AL00

Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working

riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?

hatemelectr said:
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
Click to expand...
Click to collapse
Some images simply do not work, so you will need to check for other images simply.

Just install this one : https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
root&gapps&backlight working
of course you'll need Device+ID.apk and register ID with Google but that's easy and simple

Device: Huawei 8x Max AR00
The Quack version works but sadly it is Android 10. I have found many Android 12L GSI roms that I would like to use but the brightness is an issue on all of them. Anyone know how to copy the Quack backlight vendor display and patch it to the newer GSI roms? Tried buildprop GSI wont boot (Crdroid, Lineage 19) Tried Dirty flashing, obviously didn't work. Can't seem to find the file containing the slider brightness limitations. Phherson gives rom backlight options and tried several combinations, and yes rebooted everytime none of them work. Any ideas?

riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
After trying many different gai variants and versions I found they all have an issue with browsers. Both chrome and edge freeze after scrolling a bit. I'm wondering if this because the GSI uses too much storage space and cannot buffer? Tried to port GSI onto other partitions such as cust, prod didn't work. Even Magisk flashes successfully but does not appear in the rom. The a and b is confusing like EMUI uses both and the TWRP does not decrypt and no Verity commands don't work either. The havoc rom seems to work the best with gapps pico flashed.
~ Android 12 backlight issues had to revert to android 10
~ All GSI have the common browsers freezing. Have to use VIA browser (basic)
~ Magisk won't install have to port to ramdisk, but isn't that the TWRP recovery?

Hello, which one is the Qualcomm driver to be installed for sdm660?

[Tutorial] How to update Android 10 to Cubot Power (Or any treble-endabled device)

This is a guide how I flashed Android 10 to my Cubot Power.
Preparation:
HINT:
Make a Backup! You will definitely loose all your data on the phone due to several factory resets!
First make sure your Device can use treble and also which one you need with this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
(according to this post https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559)
note down:
Architecture: (Cubot Power: arm64)
System as Root: (Cubot Power: A-only)
then you will need fastboot and adb:
Windows:
https://forum.xda-developers.com/showthread.php?t=2588979
Linux:
Code:
sudo apt-get install android-tools-adb
Code:
sudo apt-get install android-tools-fastboot
Then you need twrp Recovery or something similar. Cubot Power is not supported by the official twrp project, but there is this unofficial version:
https://unofficialtwrp.com/twrp-3-2-3-recovery-cubot-power/
And you will probably need gapps:
https://opengapps.org/
For cubot power you will need "arm64" and "anrdoid 10" of course.
For the variant version I went with "nano" but you can probably choose what you like.
If you have a external sd card you want to copy the gapps, supersu and no-verty-opt-encrypt ZIP onto it.
Now download the android 10 treble image from:
https://github.com/phhusson/treble_experimentations/releases?after=v211
For the Cubot Power i went for the system-quack-arm64-aonly-vanilla.img.xz. But you should select the right one according to the treble app.
I went for vanilla because with gapps it did not seem to work.
Optional:
From this site:
https://romprovider.com/cubot-power-root-twrp/
Download SuperSu (https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip)
and no-verty-op-encrypt (https://romprovider.com/download-no-verity-opt-encrypt-version/)
this prevents bootloops.
In case something goes wrong have your stock rom and sp flash tool ready:
Cubot Power: http://forum.cubot.net/viewtopic.php?f=21&t=2419
Flashing
Make sure your phone is charged probably. Booting might take up to an hour. At least 70% is recommended.
Go to developer settings and enable usb -debugging and disable oem.
now type:
Code:
adb reboot bootloader
the device should now restart and boot into fastboot
now disable oem in fastboot and unlock flashing: (WARNING: this will factory reset your phone)
Code:
fastboot oem unlock
Code:
fastboot flashing unlock
now we want to "install" twrp:
Code:
fastboot flash recovery TWRP_cubot_power-030918.img
--(Optional) check if twrp is working:
Code:
fastboot reboot
and restart with the volume up button
in twrp go to mount and check if you can mount data. If not: https://appuals . com/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/.
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Then go to install and install no-verty-op-encrypt.
then got to reboot and select bootloader.
--
continue with flashing android 10:
unzip the xz file
Code:
fastboot flash system system-quack-arm64-aonly-vanilla.img
this might take a while.
Then reboot
Code:
fastboot reboot
now your phone should boot into android 10. This can take very long for me it took about 30 minutes. If it takes longer then one hour you can probably start troubleshooting.
Install google apps(playstore)
once it has booted you either can start the login process and enable usb debugging again and reboot into recovery:
Code:
adb reboot recovery
or turn it off and restart into twrp (power button and volume up).
In twrp again check if you can mount data (see the optional step).
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Install super su and gapps.
Now reboot to system.
Now again the phone will boot a very long time (up to a hour).
Conclusion:
For me it is pretty stable but sometimes the fingerprint sensor does not work or the sim card is not recognized. But a reboot fixes it (sometimes).
But rebooting always takes time. At least 5 minutes sometimes up to 30 minutes. Once the system is booted there are no feel-able performance issues.

Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al

Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Click to expand...
Click to collapse
Probably it will work, but I can give you no guarantee for that.

Thank you!
Hi Johanno,
Thank you for this great tutorial! I think I already downloaded the treble check tool in March and I also found the github page, but I didn't find any experience on the net related to Cubot Power, so I didn't dare to upgrade.
Did you try later releases?
Should I go with latest release v222 or do you know about any change in v211 that prevents us from upgrading to a later version? ( your link in the tutorial shows only older versions: https://github.com/phhusson/treble_experimentations/releases?after=v211 )
Did you use windows or linux?
Did you experiment with V25 ROM?
https://www.cubot.net/platform/Support/detail/id/192/cid/23.html
Br,
taarzaan

I'm trying the latest release v222. I'm after the last reboot. It's not fast, but I would say it's less than 30 minutes. It should boot in 5 or 10 minutes.
Br,
taarzaan

Results of my experiments
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan

Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports legacy Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
regards
Al
Click to expand...
Click to collapse
hi
i just want to understand what is legacy version? and vndk27 ? i googled but few info
my phone say same info here
i ll post the results but if one could explain those 2 things
thank u in advance

taarzaan said:
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Click to expand...
Click to collapse
notes for the next experiment (we should open a proper ticket for phhusson):
"What does "can't be used" mean? Does the pone vibrate? Does screen lights on? If you go in Fingerprint settings, do you see the enrolled fingerprint? Can you enroll a second one? If you press your fingerprint sensor when you're on that screen, what happens?"

I've tried with both v211 and v222 - but I don't seem to get past boot screen.
After using fastboot flash (and I've also tried SP flash tool flash) the phone shows cubot boot screen (with a warning about "orange mode" not being trusted) and can boot into TWRP but when booting system it shows a black screen with white slowly flashing "android" for a long time. More than one hour. I lose faith and re-install stock each time.
Any ideas how to debug and see what's happening?

Any improvements to this? I am having a P20/cubot and had same problems. AOSP v222 does not boot but I tried lineage-17.1-20201215-UNOFFICIAL-treble_arm64_avS.img.xz from https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
Surprise. it works but a bit slowly. Due to large battery I am thinking of cubot power?
I have 2 questions:
1. Can you please try the lineage-17.1 rom?
2. BTW, did AOSP8 work OK in cubot power? (i like oreo more than android 10)
Thanks for your replies.

htorsten2020 said:
1. Can you please try the lineage-17.1 rom?
Click to expand...
Click to collapse
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
htorsten2020 said:
2. BTW, did AOSP8 work OK in cubot power?
Click to expand...
Click to collapse
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.

taarzaan said:
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
Click to expand...
Click to collapse
Call/SMS/data stability. A lot of devices that came with oreo (vendor) have lots of issues with signal (mobile SIM) dropping after some hours. Thanks
taarzaan said:
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
Click to expand...
Click to collapse
Cubot Power ships with Android 8.1 (oreo). So I asked if you tried the old AOSP from phhusson (v32 - this is AOSP8 equivalent treble ROM). I found the AOSP from the same version (oreo as the device) is faster than installing newer ROM.

Hi guys, as you may have noticed I am not very active here ;-)
I actually went back to stock firmware after a few weeks because I couldn't get the phone working again. And since I want to use my smart phone and not tinker on it every few days I gave up. But now I am thinking about using Lineage os.
But first I need to back up everything and that's probably the thing that will hinder me the most.

Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").

kezyr said:
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
Click to expand...
Click to collapse
hi, how exactly did you install the lineageos 18.1 with the twrp 3.2.3? thank you in advance for your help

i just get boot loop on every rom i try on cubot power

I had the same problem and gave up

[ROM][A51] HAVOC OS for Samsung Galaxy A51 [GSI]

Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI
Havoc-OS - Browse /arm64-ab at SourceForge.net
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in
otherwise it is Vanilla Android.
GSI Flasher
(It is used for converting your img file into flashable Zip)
https://drive.google.com/file/d/1J8OlI2CCXpvAJ5FhFlR2b_y58eHQERGs/view?usp=sharing
Extract it you’ll find three folders gsi, META-INF, scripts, keep all of them inside the GSI
Flasher extracted folder.
Twerp Recovery
twrp-a51-3.5.0_10-1_ianmacd.tar | by androidhowto for Utilities (androidfilehost.com)
Do not use any other in this case you might get mounting errors.
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer.
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx
Now click on the AP button and select the twerp you downloaded.
Press start and twerp will be installed in your device. Your device will reboot don’t let it boot to one ui, press all three buttons together and hold, as soon as the screen goes black release only the volume down button. Keep holding the Volume UP and power buttons for 3 seconds and then release, you find yourself in twerp. If you miss it repeat the process again but don’t let it boot to One Ui.
In twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
Now in your computer extract the Havoc os image and rename it as “system.img”.
Extract the GSI flasher, copy system.img and paste it in the gsi folder of the GSI Flasher.
Select gsi, Meta-inf, scripts and compress them into a zip and transfer into the phone.
Now in twerp Press install, select the zip file and swipe to install. Also install Gapps or Magisk if you want (though normal magisk will have problem try install phh_magisk, discussed later).
Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/

I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.

Yillié said:
I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.
Click to expand...
Click to collapse
Oh, my bad.. changed it.

GrandmaGotGuns said:
Oh, my bad.. changed it.
Click to expand...
Click to collapse
Thanks a lot

Is stable? Does the fingerprint on the screen work?

LichtEstarossx said:
Is stable? Does the fingerprint on the screen work?
Click to expand...
Click to collapse
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.

GrandmaGotGuns said:
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.
Click to expand...
Click to collapse
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?

LichtEstarossx said:
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?
Click to expand...
Click to collapse
You need to flash disable dm verity before flashing the gsi.. one ui encrypts the data.

I'll soon update this for Android 11 (R)

I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?

LichtEstarossx said:
I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?
Click to expand...
Click to collapse
What android version are you at?

GrandmaGotGuns said:
What android version are you at?
Click to expand...
Click to collapse
I had android 10
one ui 2.5
although it is rare that the gsi does not work

LichtEstarossx said:
I had android 10
one ui 2.5
although it is rare that the gsi does not work
Click to expand...
Click to collapse
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?

GrandmaGotGuns said:
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?
Click to expand...
Click to collapse
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work

LichtEstarossx said:
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work
Click to expand...
Click to collapse
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].

GrandmaGotGuns said:
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].
Click to expand...
Click to collapse
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so

LichtEstarossx said:
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so
Click to expand...
Click to collapse
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here

GrandmaGotGuns said:
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here
Click to expand...
Click to collapse
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi

LichtEstarossx said:
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi
Click to expand...
Click to collapse
I attach my telegram username in case you need something more specific.
(nicopizza) Add the @

Can someone plz assist........I got the rom installed on issues
Root chkr says I'm rooted but substratum says I'm not Magisk I don't think I have the patch img. for it..... plz can someone hlp

Flashing GSI ROMs onto Your Nord N10 5G

DISCLAIMER!!!
Any lost data, bricked device or issues caused by attempting everything below is not my fault. You assume responsibility of your own actions. This has ONLY BEEN TESTED ON A BE2026!! You have been warned!
What You'll Need
Full Fastboot/ADB installed, system wide helps
-- My method is use the ADB Quick Installer (here: ADB Reborn), then also download the platform-tools and put everything in the ADB Folder (here: Select for your OS)
A GSI ROM
-- So far, only tested /e/OS DeGoogled GSI ROM, which is Android 10 based. ZERO issues thus far (here, arm64 ab: CLICKY) this rom does have issues with Wifi if you patch the boot.img with Magisk. Recommend testing 11 Based GSI's instead like LeOS which is based off of eOS
GAPPS if you so choose
Stock vbMeta.img
-- found here from OnePlus: OnePlus Software ... just select the Nord N10 and click download. or find it on a post here
Video instructions
text instructions
Instructions
1.) Download your selected GSI ROM, GAPPS (if needed), Magisk Manager, stock firmware and make sure ADB is system wide installed
2.) Unlock your bootloader
-- 2a.) Go to Settings, then About phone, tap Build number a bunch to enable developer settings
-- 2b.) Go back and select System, then Developer Settings, enable USB Debugging and OEM Unlock
-- 2c.) Plug in device, give PC developer control, and reboot to bootloader with "adb reboot bootloader"
-- 2d.) Once in bootloader mode, use "fastboot flashing unlock" to unlock the bootloader. Device will wipe and reboot to system
3.) Plug your Device into your computer, open Command prompt and type the following command. It may ask for Debugging permission on device, select yes
Code:
adb reboot bootloader
4.) Now that you're back on the Bootloader, you can use fastboot commands to get started flashing your GSI, first command to enter is
Code:
fastboot reboot fastboot
5.) You're now in Fastbootd, this allows for easier flashing. You now need your vbmeta.img. Use the command below
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6.) Reboot fastbootd with the command from step 4, then use the commands below once rebooted
Code:
fastboot erase system
fastboot delete-logical-partition product
fastboot flash system GSI.img
fastboot -w
fastboot reboot
7.) You should now have your GSI flashed onto your device! That simple
Do NOT patch the boot.img with Magisk Manager and flash it. It breaks Wifi and Bluetooth on every single GSI Right now. If I find a work around, I will post it here.
How to Root your GSI Based ROM and keep Wifi Working!!
1.) Go to the PixelExperience ROM page and download just the Custom Recovery (here: PixelExperience Post)
2.) Once you have the recovery, reboot to bootloader
Code:
adb reboot bootloader
3.) Flash the recovery
Code:
fastboot flash recovery recovery.img
4.) Reboot to recovery, then download MagiskManager APK from Github (just follow along, I promise, here: Magisk)
5.) Select Apply Update by USB in the Recovery, and sideload with the Magisk APK (it works, trust me)
Code:
adb sideload MagiskManager.apk
6.) Reboot device, select the Magisk Icon and you're Rooted and ROM'd with working Wifi!

Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.

Generic123. said:
Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.
Click to expand...
Click to collapse
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone

KaptinBoxxi said:
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone
Click to expand...
Click to collapse
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).

Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
I disable auto-brightness entirely, but its still exceptionally bright. Its so weird. I still have it, haven't sent it in yet, so I'll give it a shot soon
Actually just realized its the GSI I'm using, the sim card doesn't work. Gonna try a different gsi and see what happens

I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.

bbabel said:
I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.
Click to expand...
Click to collapse
I suggest this method instead

MetaruSonikkuX said:
I suggest this method instead
Click to expand...
Click to collapse
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.

bbabel said:
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.
Click to expand...
Click to collapse
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.

MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
You have to use GSIs with GAPPS in them to get gapps for now. no way around it

MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
As KaptinBoxxi says, look for a GSI rom with GAPPS included, otherwise you'll have a lot of problems. I'd start for Pixel Experience but you can look for other roms here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
Is there a tutorial on making these that you followed? The one I found on phh wiki didn't go so well