Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 19.1
Android 12
lineage-19.1-20230111-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Camera is not working yet.
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- As it looks like Widevine L1 has been revoked by end of August 2020.
- Maybe more issues ..
Installation:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions !
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (25.2)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Enjoy 12
Android 11
lineage-18.1-20220216-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (21.x)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-18.x builds:
1. Boot into TWRP
2. Install ROM.zip
3. Re-Install Magisk 21.x
4. Wipe CACHE and DAVLIK
5. Reboot into system
Enjoy 11
Android 10
lineage-17.1-20201211-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
system-as-root (SAR)
For gapps installation issues and more information ..
Pls read first .. https://forum.xda-developers.com/showpost.php?p=80693701&postcount=1350
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (20.x+)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-17.1 builds:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe CACHE and DAVLIK
4. Reboot into system
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
Enjoy TEN
Android Pie
lineage-16.0-20191017-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Encryption seems not to work - and has not been tested. -> Pls do not encrypt your data partition yet !
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install lineage-16.0-201Yxxyy-UNOFFICIAL-dragon.zip
4. Install Opengapps
5. install Magisk.zip (tested with 18.x)
6. Reboot into system ..
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
And big thanks to @NYCHitman1 (Dirty Unicorn) !
Without his work the Android Pie project would not have been possible !
I have uploaded the last official Lineage Oreo build to androidfilehost.com ..
lineage-15.1-20200221-nightly-dragon-signed.zip - -> DISCONTINUED
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-lineage-18.1
DOWNLOADS:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
https://androidfilehost.com/?w=files&flid=289293
Enjoy LineageOS on your Pixel C .. [/B]
RESERVED
Here you are ..
TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today
minieod said:
TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today
Click to expand...
Click to collapse
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy
followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse
followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..
Click to expand...
Click to collapse
Hey follow
Yep did all of that. Formatted system, flashed boot.img, and no issues with mtp prior to the boot loops.
I went ahead and did a complete userdata reset and am sampling the O DP1 now ..I'm sure it'll work fine when (if) I come back to 7.x
Officialness
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.
gaufres said:
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.
Click to expand...
Click to collapse
You are not the first asking me this question ..
Here some more information ..
https://wiki.lineageos.org/submitting_device.html
Who is the maintainer ? .. me
- Changing vendor stuff .. monthly
- Applying kernel patches .. monthly
- Applying possible device tree patches and changes .. monthly
- Etc.
Here is the manifest for LOS ..
https://github.com/followmsi/manifests/tree/dragon-lineageos-cm-14.1
Also for the people who like to build their own verison
- As you may see we are removing 2 LOS repos today, due to build errors.
- This needs to be fixed on code level first - commited on LOS github.
- The stock google vendor.img needs to be integrated into the LOS Installer
Still not clear how this is done for "official" lineageos .. also from legal point of view.
Actually I need to get information here ... How is this done for other ROMs having a dedicated vendor.img ?
- The missing integrated kernel building was impemented a few minutes before
https://github.com/followmsi/androi...mmit/316a7e0e87b191bcf11b8de55778ddec83fac2f8
https://github.com/followmsi/android_kernel_tegra/commit/3e3e24c41db74693efc2fc74efaf6286b1c06013
You see there a few issues left ..
The ROM works perfectly but its not ready to be official yet.
Don't want to force and push a go live now .. No need to rush !
Hope you have a better understanding now ..
Cheers
Reuben_skelz92 said:
followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse
No !
The OMS version is the same like lineageOS but including OMS - to be ready to install substratum .. etc.
Made a version for Nexus 10 as well .. it seems to work fine.
Just have installed the ROM .. works fine - but did no special customizations or anything else.
Hope this helps ..
Click to expand...
Click to collapse
Debugging bootloop
followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
Click to expand...
Click to collapse
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?
gaufres said:
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?
Click to expand...
Click to collapse
You did flash boot.img via fastboot ?
The ROM installation had no errors ?
What version of bootloader are you using .. .50 for 7.1.2 ?
Do you see the LOS logo (boot animation) when you boot-loop ?
Are you able to make a md5 hash ..Or similar to compare ?
File corrupt ?
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
I am testing several ROMs and kernels in the last days .. no problems at all.
EDIT:
Which version of TWRP ?
EDIT2:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)
Re: Debugging bootloop
followmsi said:
You did flash boot.img via fastboot ?
Click to expand...
Click to collapse
Yes. No errors.
followmsi said:
The ROM installation had no errors ?
Click to expand...
Click to collapse
None.
followmsi said:
What version of bootloader are you using .. .50 for 7.1.2 ?
Click to expand...
Click to collapse
I think so. Version 7900.50.0 from n2g47d.
followmsi said:
Do you see the LOS logo (boot animation) when you boot-loop ?
Click to expand...
Click to collapse
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
followmsi said:
Are you able to make a md5 hash ..Or similar to compare ?
Click to expand...
Click to collapse
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
followmsi said:
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
Click to expand...
Click to collapse
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
followmsi said:
I am testing several ROMs and kernels in the last days .. no problems at all.
Click to expand...
Click to collapse
Good. Weird.
followmsi said:
Which version of TWRP ?
Click to expand...
Click to collapse
Your build of 3.1.0-0.
followmsi said:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)
Click to expand...
Click to collapse
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?
I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.
gaufres said:
Yes. No errors.
None.
I think so. Version 7900.50.0 from n2g47d.
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
Good. Weird.
Your build of 3.1.0-0.
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?
Click to expand...
Click to collapse
[HashChecker]
[File]/storage/emulated/0/download/lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip
[MD5]C79F1066186FF36C55643E264B3647E2
[SHA1]4DDD0A811FE22359D745335AA563023E95E808D3
[SHA256]D124B4048F096317F593FA5DBF313CEAEBBDDD4352F0422276A86FD5F6707902
At least the sha256 matches
Good bootloader
Good TWRP version ..
Do you install supersu at last step of your installation procedure ?
After you did install the ROM in TWRP, pls install supersu.zip (2.79 -sr3) as last step.
It will boot twice for the first time .. but then it should boot normally.
badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.
Click to expand...
Click to collapse
The SetupWizard is related to gapps .. the beans version seems to run perfectly.
Opengapps seems still to have issues on certain devices.
Will check supersu topic ..
Thanks for the feedback !
badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU.
Click to expand...
Click to collapse
followmsi said:
Do you install supersu at last step of your installation procedure ?
Click to expand...
Click to collapse
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK
gaufres said:
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK
Click to expand...
Click to collapse
Cool !
Found the issues as well ..
It's related to DM-verity .. even some config is missing.
Or the overwrite of build_fingerprint is related.
Need to investigate ..
Both supersu and magisk are removing the DM-verity checks in ramdisk.(boot.img)
As I always install supersu, I never realized.
Just compiling a new version .. changed the sources.
https://github.com/followmsi/androi...mmit/aae5804e75f4133ec82253cf6b2afbe39e46a56a
Removing DM-verity from fstab .. should solve this issue, also without supersu.
At later stage we can enable again, if it's working fine.
Thanks for your help testing ..
Cheers
New release ..
lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
Changes:
- Integrated kernel compiling - using DU branch
- disabled DM-verity -> should fix proper booting even without supersu/magisk.
- General LineageOS changes -> fresh repo sync from today .. https://download.lineageos.org/
Installation:
1. Boot into TWRP
3. Install lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
4. install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system ..
- The ROM installer will keep your existing gapps installation.
- If you had SuperSu installed before you need to install it again - as we overwrite the boot.img completely.
A new OMS version will come later ..
Enjoy ..
SUPPORTS ALL TYPES OF USERDATA DECRYPTION FOR BOTH OREO AND PIE ROMS - PASSWORD, DEFAULT_PASSWORD, PATTERN, PIN!!!
SUPPORTS BOTH FULL AND INCREMENTAL OTA UPDATE PACKAGES AUTOMATIC INSTALL!!!
Sharing my unofficial TWRP recovery mod for nitrogen which I have started about 2 years ago for hydrogen/helium. For more details visit https://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-2-hydrogen-helium-t3512981...
This is and will be work in progress with fixes and reasonable features to be added.
Download:
(02-01-2019)twrp_v323-4_nitrogen_nijel8-MOD.img
To install:
- USB connect device to PC
- reboot to fastboot
- open Command prompt/Terminal in the folder with the recovery image and run these commands line by line:
Code:
fastboot flash recovery (XX-XX-XXXX)twrp_v323-X_nitrogen_nijel8-MOD.img
fastboot boot (XX-XX-XXXX)twrp_v323-X_nitrogen_nijel8-MOD.img
or just flash the image with TWRP selecting recovery partition
- reboot from the fresh recovery - it'll take few seconds... let it do its magic to survive MIUI stock recovery replace at system boot. This will happen whenever you install any new ROM.
Done... This TWRP will not go anywhere, /system is untouched so you can get MIUI OTAs, no need to root if you don't want to, no need to flash anything else, MIUI boots just fine having no idea about the recovery, everybody's happy...
NOTES:
ROM install:
- skip wiping Data even if switching different ROMs. Do dirty install, see how it runs, if no problems, great... you saved yourself from doing the initial
setup. If having issues then wipe Data and see how it goes...
- You do not need to wipe/format/factory reset anything before install(see above), especially System and Vendor.
- Do not install any patches like lazyflasher, sound or whatever mods, root-on-system etc that are altering System or Vendor partitions on stock MIUI without installing Magisk first or system will not boot!!!
MIUI OTA Install:
- Let MIUI download update and press "Reboot" when prompted
- Device will reboot to TWRP and start installing it.
- If device reboots to system automatically - all good, update successful
- If device does not reboot you should see some error in red
- Just flash the zip package in Internal storage -> downloaded_rom folder and reboot to system
- Done - you just got your OTA
Decryption:
If MIUI asks for decription password after reboot from TWRP don't panic!
You will most likely never see this but as anything in this live sh*t happens. I for example have seen this only once in hundreds of TWRP and MIUI flashings and reboots to system and it happen after reboot from MIUI OTA testing. Did I mentioned I never do clean installs? Why bother wiping if no post-install issues, right...
Anyway... here is how to get back to normal without loosing any data:
- Reboot back to recovery by pressing and holding POWER + VOLUME UP buttons
- Run Data backup in TWRP
- USB connect device to computer and copy all personal data you don't wanna loose from Internal storage to computer
- DO NOT FORGET TO COPY THE DATA BACKUP YOU JUST MADE FROM TWRP/BACKUPS/XXXXXX TO COMPUTER TOO!!!
- Click Wipe -> Format data -> type yes -> [ENTER]
- Reboot to MIUI and let it encrypt the device. You will see Setup new device wizard when its done
- Reboot back to recovery by pressing and holding POWER + VOLUME UP buttons
- Copy back all your personal data including the recent Data backup from computer to Internal storage -> TWRP/BACKUPS/XXXXXX
- Reboot recovery so TWRP can detect the Data backup you copied
- Restore Data backup and reboot to MIUI
- Done - MIUI should boot without complaining and all your data is intact... even your old lockscreen password and fingerprints should work
Backup/restore:
- normal backup includes Data only, you can always flash what you are running currently to restore boot, system and vendor
- if you have modified boot,system or vendor post install you can back them up to keep your changes
- You do not need to wipe/format/factory reset anything before restore... restore does that for you
Some observations during my extended decryption testing with China and Global MIUIs 8.1 and 9.0, EU MIUIs, MIUIPro, etc:
- Downgrading to ROM with lower security patch level brakes encryption in Android but not in TWRP so just boot back to recovery, backup your data to safe location, format data, restore data back and you are good to go...
- Some times switching back and forth passwords types(pin, pattern etc...) brakes encryption and you loose your data, no way back!!! This is ROM fault and not TWRP. Crypto footer just gets corrupted from Android... I have taken good measures for this not to happen in my TWRP so don't blame recovery if that happens to you...
Changelog:
[02-01-2019
- hide navbar during running operarions
- more userdata decryption reliability improvements
- Mi bunny is terrified loosing recovery control
- sync with latest Omnirom android-9.0 sources
[01-28-2019
- fix decryption with good user password on next retry if wrong password was entered before that
- improve TWRP persist
- sync with latest Omnirom android-9.0 sources
[01-09-2019
- fix system boot after restoring regular file-for-file backup on ext4 file systems(System and Vendor) - now any backup type works for any partition of any ROM
- sync with latest Omnirom android-9.0 sources
[01-07-2019
- fix installing incremental OTA patching boot - this will start working properly after your first full ROM install with new recovery(boot.img flash)
- fix loading settings from /persist if decryption fails
- made sure we always keep current settings copy on /persist
- remove excessive save settings calls
- some minor improvements
- sync with latest Omnirom android-9.0 sources
[01-05-2019
- fix incremental OTA update automatic install
- sync with latest Omnirom android-9.0 sources
[01-04-2019
- new much smaller Pie kernel built from source with LineageOS 16.0
- much smaller recovery image(see above)
- sync with latest Omnirom android-9.0 sources
[12-29-2018
- improved decrypt routine
- some minor fixes and improvements
- sync with latest Omnirom android-9.0 sources
12-28-2018
- much improved and reliable decryption routine for preventing crypto footer corruption and loosing all your data - this update is highly recomended
- fix Android 9.0 userdata decryption with custom user set password, pin or pattern
- more reliable format data routine for crypto footer support
- disable useless and sometime buggy reboot check for system size(No OS installed msg)
- sync with latest Omnirom android-9.0 sources
12-27-2018
- migrate to Android-9.0 for android tree and TWRP sources
- switch to MIUI Pie prebuilt kernel
- speed up userdata decryption
- fix userdata decryption for Android-9.0 with default password only. At this time userdata decryption wit user set password is not supported! Working on it...
- sync with latest Omnirom android-9.0 sources
11-25-2018
- fix survival routine hang/bootloop after openrecoveryscript execution(OTA)
- improved decryption handling
11-23-2018
- fix userdata decryption - no more inaccessible userdata in TWRP
- fix vendor missing from partitions to restore list in some cases
- fix TWRP bootloop trying to apply survive magic in some cases
- finaly fix crypto footer for F2FS partition formating(tested and working!!! - you can format userdata in TWRP without any system boot issues now)
- skip survive magic for good ROMs to speed up reboot
- translatable and more user friendly survive system boot screen - If you want to help translate and PM me these strings:"
Code:
<!-- Survive system boot strings -->
<string name="survive_line1">Checking if TWRP will survive system boot!</string>
<string name="survive_line2">Please, wait...</string>
- sync with latest Omnirom android-8.1 TWRP sources
11-12-2018
- fix TWRP system boot survive - no need to flash anything to prevent stock recovery reflash at MIUI boot
- fix crypto footer for F2FS partition format - need no more fastboot format userdata for system boot with forced encription enabled(needs testing)
- fix error when creating ext2, ext3, or ext4 filesystem in some cases(needs testing)
- some minor fixes and optimizations
- kernel compiled from source at build time
- build with latest Lineage OS 15.1 sources
- sync with latest Omnirom android-8.1 TWRP sources
Github sources:
NITROGEN TWRP device tree
TWRP Mod repo
Kernel source
Thank you:
TeamWin for the initial device tree!
Omnirom/TeamWin for the TWRP source code!
@topjohnwu for the magiskboot source code!
Yes, You finally stepped in.
you save my life thankyou sir. unlocked bootloader today as i waited for 720 hrs. as i known i can skip by 9001 mode i just wait the official unlock to play safe. missed you so much since max1 thankyou sir
Just noticed on 4PDA forum there is a bug when you try restore vendor is missing from the list of available partitions at first... Well, it's not a bug... It's something I had to add for hydrogen...
Yeah, I know exactly what you guys are talking about... Back in the days when I was trying to bring treble to Max1 I added some code to detect in the fly if vendor partition is available on the running device so I can hide it in UI if ROM was Nougat or show it if was treblelized. I forgot about it and now it causes inconvenience on Max3. Will get it fixed in the next release.
Thaks for the reminder 4PDA guys...
nijel8 said:
Just noticed on 4PDA forum there is a bug when you try restore vendor is missing from the list of available partitions at first... Well, it's not a bug... It's something I had to add for hydrogen...
Yeah, I know exactly what you guys are talking about... Back in the days when I was trying to bring treble to Max1 I added some code to detect in the fly if vendor partition is available on the running device so I can hide it in UI if ROM was Nougat or show it if was treblelized. I forgot about it and now it causes inconvenience on Max3. Will get it fixed in the next release.
Thaks for the reminder 4PDA guys...
Click to expand...
Click to collapse
I hope that you are able to create an un-official build of LineageOS for Mi Max 3
I thank you for your time for creating this un-offical twrp build as its faster than the official one
have a great week!
Going to keep an eye on this.
300 hours left for my Mi Max 3, will flash this when I unlock.
What's different between this and official TWRP may I ask?
omer919 said:
I hope that you are able to create an un-official build of LineageOS for Mi Max 3
I thank you for your time for creating this un-offical twrp build as its faster than the official one
have a great week!
Click to expand...
Click to collapse
Don't know if it's faster but should be more bugs free...
AsadP2013 said:
...
What's different between this and official TWRP may I ask?
Click to expand...
Click to collapse
Read first post and changelog, then click the link for more info and read the looong changelog there as well.
But if I have to summarize the dev is listening and every bug terminated right away...
Oh... and the most important thing... Dev has the device and runs on it only what he builds himself... You get what the dev gets and he hates it when something's not working as intended.
Hope this helps...
nijel8 said:
Don't know if it's faster but should be more bugs free...
Read first post and changelog, then click the link for more info and read the looong changelog there as well.
But if I have to summarize the dev is listening and every bug terminated right away...
Click to expand...
Click to collapse
Thanks, no I have had a look but in short, what would you say?
Do you reckon that it has more features and is capable of doing slightly more?
Basically, should I use this TWRP over official as I'm a modder/tweaker?
Or should I flash it for the sake of it providing more than official?
Ohh Sir @nijel8 I've tried, but incremental OTA updates does not installable with this rec.
(Or I am making a mistake.)
JulianJenner said:
Ohh Sir @nijel8 I've tried, but incremental OTA updates does not installable with this rec.
(Or I am making a mistake.)
Click to expand...
Click to collapse
More specifics, please, recovery.log. What not installable means?
The only reason OTA would not install is if the updater-script checks boot partition checksum. Can you post its content?
I would test it myself but I am away from home right now...
Thx. I am back to miui with chinese PC suite (full clean install)
I will try again. When I have time again.
I've found on baidu a new TWRP a lot of settings and partition backup
http://www.mediafire.com/file/04xqp...-1030-XIAOMI_MAX3-CN-wzsx150-fastboot.7z/file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13
JulianJenner said:
Thx. I am back to miui with chinese PC suite (full clean install)
I will try again. When I have time again.
I've found on baidu a new TWRP a lot of settings and partition backup
http://www.mediafire.com/file/04xqp...-1030-XIAOMI_MAX3-CN-wzsx150-fastboot.7z/file
View attachment 4642012
View attachment 4642013
View attachment 4642014
View attachment 4642015
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13
Click to expand...
Click to collapse
One thing I should've mentioned... Since recovery hardware decryption is not fixed yet after OTA update.zip is downloaded you have to move it to nonencrypted accessable location like external SD Card or OTG reboot to recovery and flash it manually.
Another thing I should mention is although decryption with default passwords is not working decryption with user password should work. Don't ask me how to switch from default to user password encryption... I am not familiar with MIUI.
I just testing. No problem.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13
nijel8 said:
One thing I should've mentioned... Since recovery hardware decryption is not fixed yet after OTA update.zip is downloaded you have to move it to nonencrypted accessable location like external SD Card or OTG reboot to recovery and flash it manually.
Another thing I should mention is although decryption with default passwords is not working decryption with user password should work. Don't ask me how to switch from default to user password encryption... I am not familiar with MIUI.
Click to expand...
Click to collapse
I think, there is not the encryption/decryption is the bigger problem.
Max3 MIUI ROMs contains a scrip, that it rewrite MiRecovery, but this action occurs across boot. Earlier rewriting supervened after system installing/flashing. So far, we could have avoided this with Lazyflasher or something. At the moment, we install TWRP versions in vain, because after successfully TWRP install, MIUI system immediately restore MiRecovery at rebooting.
In Mi Max 1 I solved the problem of recovering stock recovery by deleting the file "Recovery from boot.p" in the system directory. You must do this before the first start of the system.
Guys, you have system verify in the kernel on Oreo so LazyFlasher doesn't work on Oreo and deleting files in system causes bootloop. The new approach for disabling recovery replace is to patch rc scripts in boot image. That's how this recovery does it.
Edit: BTW vendor is verified as well so modifying anything in that partition causes bootloop as well...
nijel8 said:
Guys, you have system verify in the kernel on Oreo so LazyFlasher doesn't work on Oreo and deleting files in system causes bootloop. The new approach for disabling recovery replace is to patch rc scripts in boot image. That's how this recovery does it.
Edit: BTW vendor is verified as well so modifying anything in that partition causes bootloop as well...
Click to expand...
Click to collapse
"nice" new security items...
Installed the recovery today. It went well. When I tried to boot to the system afterward it started running OpenRecoveryScript 'checking if TWRP will survive system boot!'. It has been over 2 hours. Is this normal? If Any way to stop it? Rebooting doesn't stop it.
EDIT: Figured it out. Didn't have writer permissions for /data. Had to reformat it. After that it went ok.
lowfat said:
Installed the recovery today. It went well. When I tried to boot to the system afterward it started running OpenRecoveryScript 'checking if TWRP will survive system boot!'. It has been over 2 hours. Is this normal? If Any way to stop it? Rebooting doesn't stop it.
EDIT: Figured it out. Didn't have writer permissions for /data. Had to reformat it. After that it went ok.
Click to expand...
Click to collapse
Doesn't sound right. /data should not affect that. Post any recovery related log you find in /cache, please...
Thanks for the recovery mod. I think that a translation into Russian will eventually be added. I am also grateful to nijel8 for his work!
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
Hi everyone, I tried to get LineageOS 18.1/Android 11 again onto my A8 and this time it worked. I have written down all the steps I followed.
You can take these steps and do whatever you want but don't blame me if it breaks anything. You are responsible for what you do to your phone. You will loose your warranty. You will loose all data on your phone including internal storage. I don't think you will pass Safetynet afterwards so say bye to banking apps.
Some steps are copied out of other posts so big thank you to them. I always linked them. Actually this is more or less a summary of different guides I read put together in one.
I don't use Google Services so I don't know if they'll work.
CHAPTER 0 - Prerequisites
- Make a backup of all your important data
- Make a backup of data in your internal storage
- Have the bootloader unlocked (Go to settings/Developer options and enable OEM unlock)
- Be RMM unlocked (no RMM State prenormal). You can check this in download mode (Power + Vol. Up + Vol. Down) by reading the small text
- Read everything before you start
- You can also download all the things before starting
CHAPTER 1 - Reset
I don't think that this is necessary but things like calls were broke for me before so I decided to reset everything by flashing stock firmware. Please decide for yourself if you need this.
- Download Odin
- Download official firmware (e.g. from here: https://galaxyfirmware.com/model/SM-A530F)
- Extract zip file
- Enter download mode (turn off, then Power + Vol. Up + Vol. Down)
- Connect phone to computer
- Open Odin
- Select all the files you extraced from the firmware zip in Odin (BL/AP/CP...)
- Untick Autoreboot under options
- Hit start
- When finished, disconnect phone
- Press "Power" and "Vol. Down" until screen goes black
- In this moment, press all buttons (Power + Vol. Up + Vol. Down) again to reenter download mode!
CHAPTER 2 - Install custom recovery
see https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3760975/
- Download TWRP tar file from here: https://twrp.me/samsung/samsunggalaxya82018.html
- After chapter 1, your phone is in download mode. If you skipped it, turn off and press Power + Vol. Up + Vol. Down to enter download mode
- Connect phone to computer
- Open Odin, go into options and untick Auto-reboot and put the TWRP tar file in AP tab of odin, hit Start and wait
- When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
- At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
- ***Don't boot into rom because it will lock your device again!!!!
CHAPTER 3 - Wipe
- Swipe "Allow modifications"
- Go into Wipe menu and select "Format data" - note that this will erase all your data including internal storage
CHAPTER 4 - Trebelize
see https://forum.xda-developers.com/t/...-guide-for-galaxy-a8-2018-18-04-2019.3894881/
- Download Treble creator and treble TWRP
- Wipe system/cache/data
- Copy the TrebleCreator.zip(of your variant) and TWRP-jackpotlte-Treble.img to your Internal/SDcard
- Flash the TrebleCreator.zip through TWRP recovery
- After completing your device will reboot to RECOVERY
- Now touch INSTALL > Select Image > Locate TWRP-jackpotlte-Treble.img
- Flash TWRP-jackpotlte-Treble.img to recovery
- Reboot your device to recovery
- Wipe system, cache, vendor, dalvik cache and data.
CHAPTER 5 - Android 11
- Download Vendor, GSI (if you used the linked vendor, you'll need: arm64, A/B, vndklite)
- Vendor download: https://forum.xda-developers.com/t/...dor-quack-v2-5-for-galaxy-a8-a8-2018.4157533/
- GSI download (recommendation): https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4205461/
- Extract the system image .xz file
- Reboot to recovery
- Copy files onto the phone
- Install vendor zip
- Flash gsi image as system image
- Reboot to system
CHAPTER 6 - Enjoy
Don't turn on "Workaround for broken fingerprint".
WHAT WORKS
The system seems to be pretty stable for a GSI. I haven't experienced any random freezes yet.
- Phone, Mobile data
- Wifi
- Bluetooth
- NFC
- Hotspot (I opened one but didn't try to connect to it)
- Camera (also 3rd party apps, YES!)
- Fingerprint
If you downloaded the LineageOS version I linked above, you will automatically have root because it's based on the phh treble GSI. You can install the Superuser app from F-Droid: https://f-droid.org/de/packages/me.phh.superuser/ just as a normal APK file.
NOT WORKING
- probably everything that doesn't work in any GSI like voLTE and Bluetooth calls but havent tested any of them
- of course the second front cam
- USB accessories? (they are broke with this vendor)
What is your experience with this gsi so far?
JohnnyxS said:
What is your experience with this gsi so far?
Click to expand...
Click to collapse
It's about as good as the Android 10 gsi I used earlier. The camera app takes some seconds to start but I had no other problems with it (except for the things mentioned in the post under "not working")
Have you used other GSIs before?
jannis3 said:
It's about as good as the Android 10 gsi I used earlier. The camera app takes some seconds to start but I had no other problems with it (except for the things mentioned in the post under "not working")
Have you used other GSIs before?
Click to expand...
Click to collapse
I haven't, i managed to install it but not with google services, lost an entire day trying: (
I am a complete n00b, I'm going trough this.
Thanks a lot @jannis3 for these clear instructions!
Here are my observations, in case someone needs them:
Chapter 0:
- Have the bootloader unlocked (Go to settings/Developer options and enable OEM unlock)
To access the Develloper Menu, you need to tap 7 time the Build number in about page:
How do I turn on the Developer Options menu on my Samsung Galaxy device?
Find out how to turn on the Developer options menu on your Samsung Galaxy device.
www.samsung.com
- Be RMM unlocked (no RMM State prenormal). You can check this in download mode (Power + Vol. Up + Vol. Down) by reading the small text
This did not show on my device (no mentions of RMM).
However, there was:
FRP LOCK: ON
OEM LOCK: ON
First one needs to be disabled by remove ALL accounts before starting to flash
Second one is removed trough the Bootloader option in the developer menu.
Chapter 5:
Choose the "treble_arm64_avS.img" version
JohnnyxS said:
I haven't, i managed to install it but not with google services, lost an entire day trying: (
Click to expand...
Click to collapse
Hello Johny,
I just lost my day trying too.
No GApps with this GSI, because it keeps shrinking the system partition to 1MB Left.
Do you have a suggestion of another GSI that works nice on our A8?
I'm on it again!
I just found out about Phhusson and its incredible work.
Since LineageOS clearly does not work if you want GApps, here are the releases for Phh-Treble:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Specific page for A8 (2018):
Samsung Galaxy A8 (Exynos)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Make sure you use: system-roar-arm64-ab-vndklite-gapps.img.xz for the A8.
Upon bootup, Google framework goes bezerk about not being Play Protect Certified.
Follow the instructions to register your device to google here:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
After a reboot, I then had everything working but the Play Store would still throw me a Google Play Protect error.
Clearing data and cache on Google Play Services worked for me.
Google Play Store Not Working? Fixes and Solutions | nextpit
Google Play Store problems can usually be fixed simply by clearing the cache, but if not, we have even more solutions in this article!
www.nextpit.com
jaylimo84 said:
I'm on it again!
I just found out about Phhusson and its incredible work.
Since LineageOS clearly does not work if you want GApps, here are the releases for Phh-Treble:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Specific page for A8 (2018):
Samsung Galaxy A8 (Exynos)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Make sure you use: system-roar-arm64-ab-vndklite-gapps.img.xz for the A8.
Upon bootup, Google framework goes bezerk about not being Play Protect Certified.
Follow the instructions to register your device to google here:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
After a reboot, I then had everything working but the Play Store would still throw me a Google Play Protect error.
Clearing data and cache on Google Play Services worked for me.
Google Play Store Not Working? Fixes and Solutions | nextpit
Google Play Store problems can usually be fixed simply by clearing the cache, but if not, we have even more solutions in this article!
www.nextpit.com
Click to expand...
Click to collapse
Meh i gave up for now, i might return at some point to trying it again.
jaylimo84 said:
I'm on it again!
I just found out about Phhusson and its incredible work.
Since LineageOS clearly does not work if you want GApps, here are the releases for Phh-Treble:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Specific page for A8 (2018):
Samsung Galaxy A8 (Exynos)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Make sure you use: system-roar-arm64-ab-vndklite-gapps.img.xz for the A8.
Upon bootup, Google framework goes bezerk about not being Play Protect Certified.
Follow the instructions to register your device to google here:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
After a reboot, I then had everything working but the Play Store would still throw me a Google Play Protect error.
Clearing data and cache on Google Play Services worked for me.
Google Play Store Not Working? Fixes and Solutions | nextpit
Google Play Store problems can usually be fixed simply by clearing the cache, but if not, we have even more solutions in this article!
www.nextpit.com
Click to expand...
Click to collapse
Have you tried Android 12L?
g000n said:
Have you tried Android 12L?
Click to expand...
Click to collapse
Nope... 12L did not exist at the time.
Also, I gave up.
Phh-Treble was less stable than my mother in law.
My first goal was to "save" the A8 to use it for one or two year more, but the difficulty to get something simple and stable was getting harder by the minute.
I got a pretty good deal on a S20 FE 5G, so I moved on.
Great work !
Hi, I followed the guide, I don't flashed the stock ROM because I'm doing with heimdall (linux odin) and it can boot after flash. But I follow the other chapter and steps and works. The only issue I have is that after the LineageOS without GApps is installed and I reboot the phone enters in a boot loop and it can't boot. If I try to enter in the recovery boot freezes at TWRP logo splash screen.
The question is: Why enters in the boot loop ? What can I do ?
Hi, today I tried flashing the phh Android 12 GSI and it actually booted. It's a bit laggy and apparently you cannot set a screen lock for whatever reason (I read something about too old keys?). Also some random things did not work so I wanted to get back to the Android 11 LineageOS GSI. I restarted into the recovery mode but only the TWRP splash screen showed up, just as @ferriol mentioned earlier. What I did to recover my phone was:
Go to download mode
Flash original OS
It then automatically rebooted to the original recovery
I selected something like "wipe data" or "reset phone"
rebooted to original OS (It wouldn't start for me, idk why)
force reboot (power + vol. down) into download mode (power + vol. down + vol. up)
Follow my own instructions from Chapter 2 on and flashed Android 11 again
I did this three times. I don't know what actually did the job in the end but I think it was wiping the system using the original recovery and rebooting (or trying at least) into the original OS
Sooo weird... My next phone is probably not a samsung one xD
ferriol said:
Hi, I followed the guide, I don't flashed the stock ROM because I'm doing with heimdall (linux odin) and it can boot after flash. But I follow the other chapter and steps and works. The only issue I have is that after the LineageOS without GApps is installed and I reboot the phone enters in a boot loop and it can't boot. If I try to enter in the recovery boot freezes at TWRP logo splash screen.
The question is: Why enters in the boot loop ? What can I do ?
Click to expand...
Click to collapse
I resolved flashing the RMM_Bypass_v3_corsicanu.zip and no-verity-opt-encrypt-6.1.zip after flashed lineage-19.1-20220510-UNOFFICIAL-arm64_bvS-vndklite.img
Thanks for your work !
Hi!
Thanks for your tutorial. It is of great help!
I can install the os find on my A8 and run it but i noticed a few issues:
- camera app is missing
- updater app is misssing
- I cannot install GAPPS (opengaps nano or pico) because of missing space (32mb left on system) and I tried to resize system but TWRP gives an error: /sbin/e2fsck -fp /dev/plock/platform/13500000.dwmmc0/by-name/SYSTEM process ended with ERROR: 8
Unable to repair System.
I tried upgrading TWRP to 3.9.2_9-0 but still have the same issue.
Do you have any idea on how to fix the resize error?
For those looking to make lineageos work on galaxy A8 SM-A530W here is what I did:
follow the guide and then:
instead of LOS 18.1 install lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS.img.xz
install opengapps 10 nano
If stuck on loading screen, reinstall os and opengapps without wiping the disk
I still have the camera not working though. Everything else seems fine.
lejeanf said:
For those looking to make lineageos work on galaxy A8 SM-A530W here is what I did:
follow the guide and then:
instead of LOS 18.1 install lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS.img.xz
install opengapps 10 nano
If stuck on loading screen, reinstall os and opengapps without wiping the disk
I still have the camera not working though. Everything else seems fine.
Click to expand...
Click to collapse
Here is a lead: https://forum.xda-developers.com/t/everything-you-need-to-know-to-fix-camera-on-custom-rom.4218165/ " No easy route it seems.
Hi man, thanks for the ROM. However, a couple of hours ago, I tried to install it, and I'm not sure if it's because the project has been discontinued or because I didn't fully understand the instructions in English, but I couldn't install the ROM. Is it still functional, or should I look for other alternatives?
AOSP for OnePlus 5/5T - Android 12
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/
Most of the information from here can be applied for this ROM.
Introduction
This projects aims to create an upgradable AOSP build system for the Oneplus 5 (Cheeseburger).
No repository from AOSP is changed: no commit over AOSP is at the moment present on the sources for this ROM.
All the changes are provided in separate repositories (HALs, kernel): this allows to upgrade Android with minimal effort, potentially also for future major versions.
Most of the added repositories is provided by LineageOS or CAF, so thanks to them for those repos.
Screenshots are attached.
This ROM is based on the work on Android 11 from here: https://forum.xda-developers.com/t/...-19-september-2021-locked-bootloader.4183691/
As usual, only builds with enforcing SELinux, no root access and 'user Android build flavor' will be posted here.
Known issues
- None that I'm aware of.
Changelog
See second post.
Download
Releases can be found on AndroidFileHost.
OnePlus 5 (Cheeseburger): https://androidfilehost.com/?w=files&flid=328726
OnePlus 5T (Dumpling): https://androidfilehost.com/?w=files&flid=328820
Installation
Backup everything.
The provided zip can be installed using the TWRP recovery: clear data while doing that.
The ROM expects the firmware from OOS 10.0.1: different firmwares are not tested.
The provided recovery allows only flashing signed images: use TWRP if you need to flash GApps or different packages.
Sources
Kernel on github: https://github.com/robertoglandroid/kernel_oneplus_msm8998
ROM sources: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
Telegram discussion group here!
XDA:DevDB Information
AOSP for OnePlus 5/5T, ROM for the OnePlus 5/5T
Contributors
robertogl
Thank you to @T1mb3 and @Maitreya29!
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-10-05
Last Updated 2022-07-07
Changelog
[07/07/2022] aosp12_cheeseburger/dumpling-ota-user-20220707.zip
July2022 Security patches (synced with AOSP android-12.1.0_r10)
[08/06/2022] aosp12_cheeseburger/dumpling-ota-user-20220608.zip
June 2022 Security patches (synced with AOSP android-12.1.0_r8)
[21/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220521.zip
Support f2fs formatted /cache partition
Synced with Lineage 19.1 sources
Minor fixes
Code cleanup
[15/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220515.zip
Add option to apply OTA updates from SettingsExtra
4 files can be installed:
the ROM OTA - put the zip in /sdcard/update.zip
magisk - put the zip in /sdcard/magisk.zip
gapps - put the zip in /sdcard/gapps.zip
decryption zip - put the zip in /sdcard/decrypt.zip
The device will reboot automatically in recovery and apply the updates. Only TWRP can install magisk, gapps or the decryption zip.
Fix crash of the Settings app while configuring fingerprint or PIN lock (during the first setup, or from the Settings page)
Add possibility to enable location indicator in the Development Options
Location indicator is disabled for the Phone Services
[03/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220503.zip
May 2022 Security patches (synced with AOSP android-12.1.0_r5)
Fix issue with Led Manager (SettingsExtra)
[04/04/2022] aosp12_cheeseburger/dumpling-ota-user-20220404.zip
April 2022 Security patches (synced with AOSP android-12.1.0_r4)
Fix slow unlock when fingerprint is used
[13/03/2022] aosp12_dumpling-ota-user-20220313.zip
Fix Settings app crash when opening fingerprint settings
[08/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220308.zip
Android 12L
March 2022 Security patches (synced with AOSP android-12.1.0_r1)
Fix time and date not persisted after a reboot/factory reset
Fix vibration level setting on SettingsExtra
[01/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220301.zip
Sync with Lineage 19 source
Fix issue with sim2 (data works also on sim2 now)
Fix Pocket Mode
Fix 'issue' that was causing some apps to detect root without Magisk
[08/02/2022] aosp12_cheeseburger/dumpling-ota-user-20220208.zip
February 2022 Security patches (synced with AOSP android-12.0.0_r29)
Fix Jio issues with VoLTE calls
[04/01/2022] aosp12_cheeseburger/dumpling-ota-user-20220104.zip
January 2022 Security patches (synced with AOSP android-12.0.0_r26)
Fix alarms not working with default Clock app
[07/12/2021] aosp12_cheeseburger/dumpling-ota-user-20211207-beta.zip
December Security patches (synced with AOSP android-12.0.0_r16)
[02/11/2021] aosp12_cheeseburger/dumpling-ota-user-20211102-beta.zip
November Security patches (synced with AOSP android-12.0.0_r13)
Add separate wifi and cellular data quick settings tiles (as Android 11)
Unified Android 12 tile is still present
[25/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211025-beta.zip
Add f2fs support on /data partition
[20/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211020-experimental.zip
Add support for OnePlus 5T (Dumpling)
Fix data on SIM1 (SIM2 is not working for data in this release)
Enable switch for default mobile data between SIM1 and SIM2 directly in the Android Settings (removed tile: less code to mantain)
Grant permissions to Play Store (and some Google apps) automatically - allow to setup the device and restore a backup at first boot
Fix TWRP not booting after flashing Android 12
Now recovery is not updated/overwritten anymore (no need for the persist_twrp mod or anything - installed recovery is persisted)
Vibration and alarm icons are back in the status bar
[09/10/2021] aosp12_cheeseburger-ota-user-20211009.zip
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
[06/10/2021] aosp12_cheeseburger-ota-user-20211006-alpha.zip
First release: October 2021 Security Patch (synced with AOSP android-12.0.0_2)
Only known issue is encryption not working
Booting with locked bootloader
This ROM can be booted with locked bootloader.
Not supported at the moment.
For more info, refer to the A11 thread (the information are the same):
[ROM][11.0][OnePlus 5] AOSP for OnePlus 5 [06 OCTOBER 2021][Locked bootloader]
New build in the first post: aosp_cheeseburger-ota-user-20201205.zip Changelog: Add option to enable Call Recording - available in the Settings Extra app Add battery level on the bluetooth icon on status bar (when a bluetooth device reports a...
forum.xda-developers.com
Reserved3
Gapps android 12 here
Added to the OnePlus 5 Index Thread here.
Sources are now available here: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
New release: aosp12_cheeseburger-ota-user-20211009.zip
Changelog:
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
So, this release fixes encryption: I only plan to support builds with encryption enabled, so if you flashed the first A12 release (without encryption), you'll need to format /data or disable encryption somehow (I don't provide support for this, sorry, but there should be some flashable zips).
This is the last time that formatting /data will be require, I promise!
This also means that if you have my A11 ROM (linked in the first post) you can actually update to A12 without losing any data (app included). But this is still a beta release, so at your risk!
Roms works fine for the most part. I'm not sure if i'm even supposed to test different browsers but chrome and kiwi browser end up crashing when downloading heavy files (> 100Mb)
work on device decrypted and twrp?
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
kitamurt said:
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
Click to expand...
Click to collapse
What logo? Android animation, oneplus logo, or Android recovery logo?
morfances said:
work on device decrypted and twrp?
Click to expand...
Click to collapse
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
robertogl said:
What logo? Android animation, oneplus logo, or Android recovery logo?
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
Click to expand...
Click to collapse
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
kitamurt said:
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
Click to expand...
Click to collapse
What TWRP are you using? TWRP should boot as it should not depend on the OS.
robertogl said:
What TWRP are you using? TWRP should boot as it should not depend on the OS.
Click to expand...
Click to collapse
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
kitamurt said:
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
Click to expand...
Click to collapse
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
robertogl said:
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
Click to expand...
Click to collapse
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
kitamurt said:
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
Click to expand...
Click to collapse
For sure current TWRP cannot decrypt data as they need to be updated to support A12.
But at least you can flash/format things now.
I'm not sure why your TWRP didn't work, the signature should not be important (I shared that because it was already uploaded).
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
kitamurt said:
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
Click to expand...
Click to collapse
- The networking is a bit broken apparently, I already had different report of this. We are working on fixing this.
- This happens when you open the settings button from the Quick Settings view, right? It is broken also on A11, it should work only if you have a PIN/fingerprint configured (for some reason).
- TWRP will need to be updated to support A12 encrypted, yes
Of course, thanks for reporting these issues! Always appreciated, as I cannot test everything by myself