CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, dead cats,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will break it! :P
* Act accordingly
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
{
"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"
}
Important information:
This thread is for CyanogenMod 13.0 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi (but I'm not sure this company really exist). The following will not be supported in this thread:
- Custom Kernels
- Mods
- Modified system files
- Xposed
Instructions:
Comprehensive installation instructions for CM on Wingtech WT88047 can be found on the CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Install_CM_for_rendang
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/sys/fs/pstore/console-ramoops".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official build: https://download.cyanogenmod.org/?device=wt88047
Google Drive: https://goo.gl/zhGZjQ
EmfoxZhou's build: https://goo.gl/iQNZjC
Recomended Recovery:
Stock CM or TWRP recovery: https://goo.gl/cDJQXI
TWRP source: https://github.com/kumajaya/android_bootable_recovery
Recomended GApps:
Open GApps ARM - 6.0 - Micro: http://opengapps.org/
I would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Known Issues:
Both back and front still picture camera not working
Sound out from both speaker and headset if headset already connected on a reboot
Before get locked, hardware GPS disturbing network location service
Use VOL UP + VOL DOWN + POWER button to enter recovery mode
If you experiencing a random freeze, tell me your MMC type. You can check it using "dmesg | grep mmcblk0" command as root or use SD Insight app by HumanLogic. Known chip in Redmi 2 variant:
Redmi 2 8 GB:
H8G2d 7.28 GiB - Hynix - inside my Redmi 2, no freeze
QN1SMB 7.28 GiB - Samsung
P1J95K 7.29 GiB - Numonyx Micron - reported random freeze
Redmi 2 16 GB:
HAG2e 14.6 GiB - Hynix
R1J96N 14.6 GiB - Numonyx Micron
Experienced low benchmark result? Check https://github.com/kumajaya/android...mmit/ebed706cb93a924d9c0f068b8a155928069b64fe For benchmark oriented user, you can edit /system/build.prop, boot to recovery to clear dalvik-cache, and reboot.
This ROM not compatible to the new Lollipop bootloader. Please check post #3 how to restore back KitKat bootloader (at your own risk!). Build 20160624 and newer compatible to both KitKat and Lollipop bootloader.
Don't set preferred network type to LTE only, some network service not working on LTE carrier and switching to GSM carrier needed
Contributors:
ketut.kumajaya (rebased someone else kernel to Cyanogen's MSM8916 kernel in 5 days continues hacking, rendang device tree changes, rendang vendor blobs changes, fix, fix, fix, etc), someone else (initial open source kernel for stock KitKat ROM), @zwliew (initial device tree reference, kernel fix contribution)
Source Code:
Device tree: https://github.com/CyanogenMod/android_device_wingtech_wt88047
Kernel source: https://github.com/CyanogenMod/android_kernel_wingtech_msm8916
Vendor blobs: https://github.com/TheMuppets/proprietary_vendor_wingtech
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
If you want to donate a few bucks for the work we're doing in our freetime:
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-11-07
Last Updated 2016-01-25
Current manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="kumajaya/android_device_wingtech_wt88047" path="device/wingtech/wt88047" remote="github" revision="cm-13.0" />
<project name="kumajaya/android_kernel_cyanogen_msm8916" path="kernel/cyanogen/msm8916" remote="github" revision="cm-13.0-amss-2.1-wt88047" />
<project name="kumajaya/proprietary_vendor_wingtech" path="vendor/wingtech" remote="github" revision="cm-13.0" />
<project name="kumajaya/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<!-- Optional busybox -->
<project name="CyanogenMod/android_external_busybox" path="external/busybox" remote="github" />
</manifest>
Current cherry-pick:
- Ignore null USSD dialing number: http://review.cyanogenmod.org/133154 New M blobs from rendang fix USSD issue
- Property for GPU compositing: http://review.cyanogenmod.org/132998
Flash I'm not sure this complete instruction still needed for the current build:
Download the ROM, download OpenGApps for ARM 6.0 micro from http://opengapps.org/
Turn off your phone, pull out the SIM card
With my latest TWRP build installed, boot to your TWRP recovery
Backup your ROM, format your /system, /data, /cache
Flash the ROM, don't flash GApps!
Normal boot your phone. If you are lucky, after the optimization process done, Google and Cyanogen Setup Wizard will appear
[*]Playing your brand new OS for a while and then power off your phone. Insert back the SIM card
[*]Boot to recovery, flash GApps and then directly delete /system/priv-app/SetupWizard using TWRP file manager!
[*]Normal boot your phone, Google apps will be repeatedly force close
[*]Open Settings - Apps. From the menu, tap "Show system" and then give all permissions needed by every Google apps installed (GMail, Google Account Manager, Google App, Google Backup Transport, Google Contacts Sync, Google Play Services, Google Play Store, Google Services Framework)
If you experiencing any unusual app behaviour, just drag it from app drawer to upper screen "App Info" and check the permissions (i.e. stock browser force close when download, it need Storage permission). This is Marshmallow
Just flash ROM update as usual but always remove GApps SetupWizard every time you update GApps.
How to Flash Firmware and Modem
Don't mix between firmware version (i.e KitKat sbl1 with Lollipop aboot)!
Flash a complete firmware partitions:
Code:
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
Flash a complete firmware backup partitions:
Code:
fastboot flash tzbak tz.mbn
fastboot flash hypbak hyp.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash abootbak emmc_appsboot.mbn
Much easy if you always backup your firmware in TWRP.
Flash modem partitions:
Code:
fastboot flash modem NON-HLOS.bin
Enable data connection in dual SIM mode a bit tricky:
Install your primary SIM for data connection in SIM slot 1 and your secondary SIM in slot 2
Boot to TWRP and delete /data/data/com.android.providers.telephony
Open Settings - Apps - Menu - Show system, open Phone apps and give all needed permission
Open Settings - Cellular networks and set CARD 2 to "GSM only" and CARD 1 to "GSM/WCDMA/LTE", maybe you need to choose network operator manually
Open Settings - SIM cards and set Cellular data to "CARD 1"
Reboot, dual SIM mode need longer time to register to network
Sometime cellular data get switched to SIM that registered first
If somehow you get locked at "GSM only" connection, search and select proper network operator service manually
Awesome
nick37332001 said:
LOL... Camera is still not fixed... edit your bugs list XD
Click to expand...
Click to collapse
This thread still under construction edit your comment
Yay, finally on XDA !
LOL. Finally you come to XDA.
I hope there is some other develop will help to make this rom better...
Btw, thank you bli Kumajaya..
@ketut.kumajaya Can you merge with upstream cyanogenmod branch for msm8916 device common? There's a needed commit to compile.
nick37332001 said:
@ketut.kumajaya Can you merge with upstream cyanogenmod branch for msm8916 device common? There's a needed commit to compile.
Click to expand...
Click to collapse
Yes, my repo still not get updated since my local source still too dirty. I promise to update it in this weekend.
Hi, uncle Kumajaya. I try to build the ROM by myself. But it stucked here. I don not know what is the reason. Could you help me to solve it? Thx.
Autines said:
Hi, uncle Kumajaya. I try to build the ROM by myself. But it stucked here. I don not know what is the reason. Could you help me to solve it? Thx.
Click to expand...
Click to collapse
Pick http://review.cyanogenmod.org/123510, I'll update my source later.
Build 20151210 available for download.
ketut.kumajaya said:
Build 20151210 available for download.
Click to expand...
Click to collapse
This is a really good build IMHO. Things I noticed immediately:
- Android 6.0.1
- Network location now works out of the box.
- Proximity and light sensor seem now more sensitive and react more quickly at the beginning. Proximity sensor range is now 0-30 (was 0-35), but in the end the issue is stille there: after a while they go bananas just like they did with last build and become laggy.
- Camera issue is still there (you already knew it, but better to be safe than sorry, huh?)
- If you enable the Phone Number Lookup (Forward Lookup) in the Dialer options, the device asks for location permission every time you try to search for a number. No option to make the device remember the setting (location permission is already granted to phone in app manager)
Did not test if wifi channels > 11 are now ok (i need to reconfigure the router to test), but throughput is really high (90 mb/s on my network, just like 20121202 build)
Did not test if Dual SIM environment is now safe for my SIM yet: I will test it during the day (now my phone is charging)
TY very much for this new toy...
moving here?
02 des build using sim2 only, i can't set 3G,
lets try new build.. downloading now
Glad you made a thread here too.
Anyway.. I am not having sim or data problem at all. Both Sims working fine. Internet working as expected too.
xteroit said:
moving here?
02 des build using sim2 only, i can't set 3G,
lets try new build.. downloading now
Click to expand...
Click to collapse
try to dial *#*#4636#*# > phone setting > set preferred network to 3g only
also, it's been a while since my last time visitting xda, thankyou uncle kuma for giving me a reason to visit xda again
iCung said:
try to dial *#*#4636#*# > phone setting > set preferred network to 3g only
also, it's been a while since my last time visitting xda, thankyou uncle kuma for giving me a reason to visit xda again
Click to expand...
Click to collapse
no it's didn't work, maybe because i'm using dual sim before and i set 3G only in sim1, and then i remove sim1 and forget to change sim preferred sim1 to auto before remove it,
xteroit said:
moving here?
02 des build using sim2 only, i can't set 3G,
lets try new build.. downloading now
Click to expand...
Click to collapse
I'm not sure SIM 2 have data support beyond 2G.
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 is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your (probably expired) 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! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
TWRP 2.8+ is recommended.
Flashing Instructions (if coming from another rom):
Make a nandroid Backup (seriously)
Wipe System, Data, and Cache
Flash ROM
Flash GApps
[Optional] Flash SuperSU or Lineage Root addon
Update Instructions:
Make a nandroid Backup (seriously)
Flash ROM
Wipe cache/dalvik
Profit!
What works:
Booting
Wifi
Wifi Hotspot
Bluetooth
MTP
Screen
RIL
Buttons
Sound (speaker, headphone jack, bluetooth audio, and microphone)
Sensors
FM Radio (tested on Spirit Light)
GPS
Camera
Offline Charging
HWComposer
MicroG
Issues:
Screen recording (as usual)
Possibly more
Supported Devices:
GT-I8190/N/L
GT-I9070 (Galaxy S Advance)
Planning to support soon:
SGH-T599/N/V (Very similar hardware)
Unsupported Devices:
GT-I8200 (Different hardware)
Download Links:
ROM
Gapps (use arm 7.1)
TWRP 3.0.2
Based on Andi's sources. Blank screen fix patch added and kernel replaced to fix reboot loop issue.
Screenshots are broken (recovery crashes/reboots when you attempt to take a screenshot)
Download Link Updated Link (2021-10-01)
Performance Tips:
Set all animations to 0.5x
The included Camera app is laggy. Use Open Camera instead (quality is also better).
Sources:
.repo/local_manifests/local_manifests.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_external_stlport" remote="github" path="external/stlport" revision="cm-14.1" />
<project name="3liteking148/android_device_samsung_golden" path="device/samsung/golden" remote="github" revision="cm-14.1"/>
<project name="3liteking148/android_kernel_samsung_golden" path="kernel/samsung/golden" remote="github" revision="cm-14.1-alpha"/>
<project name="3liteking148/android_vendor_samsung_golden" path="vendor/samsung/golden" remote="github" revision="cm-14.1"/>
<project name="3liteking148/android_hardware_u8500" path="hardware/u8500" remote="github" revision="cm-14.1"/>
</manifest>
For building unified builds (janice support):
Code:
<project name="3liteking148/android_device_samsung_janice" path="device/samsung/janice" remote="github" revision="cm-14.1"/>
<project name="Epirex/Samsung_STE_Kernel" path="kernel/u8500" remote="github" revision="marshmallow"/>
<project name="3liteking148/android_vendor_samsung_janice" path="vendor/samsung/golden" remote="github" revision="cm-14.1"/>
Before building, don't forget to apply patches (cd patches; . patch.sh).
Credits list:
@Meticulus - for original cm13 device tree
@ChronoMonochrome and SergeyL - cm14 bringup in u8500 platform and Patches
@golden-guy - Kernel
Reserved
Thanx for this development
Sent from my GT-I8190 using XDA-Developers mobile app
It's new release?
kindadifferent said:
It's new release?
Click to expand...
Click to collapse
Yeah. It's now 7.1.1 and wifi is now fixed but not wifi autoconnection. RIL is still the same as last release (buggy).
It starts shutting down system process and does not run aop keyboard, I can not enter the key for wifi and complete the start.
ENRIQUEMM said:
It starts shutting down system process and does not run aop keyboard, I can not enter the key for wifi and complete the start.
Click to expand...
Click to collapse
If AOSP keyboard is the problem and you installed gapps, flash the keyboard fix on my cm13 thread.
thank you for bringing cm14.1 for us ?
Finally, ty elitking
After installing i found this bug
1. Laggy
2. Notif about Mtp host fc.
3. Can't open ext.memory trough cm manager need root
Wifi work fine with auto connect
Sorry for my bad englis..
Thank you for keeping 4 years old phone alive. Awesome work really.
muito bom, tomara que sejas possível reparar os bugs existentes na versão eu gosto muito desse aparelho.
Hey guys i tried installing it on my I8190 but it dosen´t boot, it keeps in the cm logo.
I hope you can fix it
Merry Christmas
adrianmich said:
Hey guys i tried installing it on my I8190 but it dosen´t boot, it keeps in the cm logo.
I hope you can fix it
Merry Christmas
Click to expand...
Click to collapse
The first boot is super slow. (5min) or more
Mkkt Bkkt said:
The first boot is super slow. (5min) or more
Click to expand...
Click to collapse
I let it boot all night long and it dosen´t turned on
I installed ROM , my Sim-card has been recognized and call and sms is fully work [ until now ]
But The camera app couldn't connect to hardware and doesn't work (Pls Solve It)
The Battery drain is a bit high.
The Speed is good ( for my device is as fast as the cm12.1 )
The AOSP Keyboard Forces Stop every 10 seconds So I installed the GBoard(Google inc).
The SD Card some times doesn't recognize ( You should go to setting -> Develop... Mode -> Change Root Access to ON to work with the stock file manager - ( My SD DOESN'T Recognized by The ES Explorer App )
It has been a few lag
In totally as a Alpha Version it gets a GREAT MARK in my opinion.
Thanks For The Developer
Try To Solve The PROBLEMS PLEASE(That Would BE SO GREAT ).
adrianmich said:
I let it boot all night long and it dosen´t turned on
Click to expand...
Click to collapse
Did you do a a clean flash?
When I saw this topic here, I told myself "I'm going to wait for the stable version..." But then I realized that if i'll download and flash this ROM it can help to developers. So I flashed it a few moments ago... The first thing- super ultra slow boot time. It took maybe about 8 mins. When the system finished the booting there was a problem... "System is not responding" But after small time it disappeared again. Next thing I noticed was strange blinking near the arrows while the phone was turning WiFi and verifying Google Account. When the system was ready there were the same problems that are described in this topic. File Manager couldn't open ext. SD Card... The camera didn't work and there also was a quite big battery drain. System was almost smooth, but there also were sometimes lags... And at the end I have to say: Design of this Android is really beautiful!
Hope you'll be succsesfull in solving problems with this ALPHA!
Big Thumb up from me!
New Release
This is the last release of CyanogenMod 14.1 I'm going to do. The reason for it is if you haven't heard about it, CM already shut down . The good thing is LineageOS is being developed as the successor of CM. So the next releases will be LineageOS instead of CM14.1.
Changelog:
Updated CM Sources
Fixed Camera (Unstable, Video recording fc happens)
Now a userdebug build (faster boot time)
Download Link: https://www.androidfilehost.com/?fid=673368273298919392
So it means that this ALPHA is the last relase? Or will there be available stable version of CM14.1?
KopecekCZ said:
So it means that this ALPHA is the last relase? Or will there be available stable version of CM14.1?
Click to expand...
Click to collapse
Just read what he said.
CyanogenMod no longer exists, LineageOS took its place.
So no, there won't be a stable release of CM14.1, maybe you'll have one of LineageOS instead.
{
"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 is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Important information:
This thread is for LineageOS 14.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi (but I'm not sure this company really exist). The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Video Playback
Audio
Sensors
Flash
LED
GPS
voLTE
What's not working :
Use VOL UP + VOL DOWN + POWER button to enter recovery mode
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Official Weekly Builds:
https://download.lineageos.org/wt88047
TWRP:
http://forum.xda-developers.com/showthread.php?t=3611503
Open GApps ARM - 7.1.2 - Nano:
http://opengapps.org/
I would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Credits :
@banmeifyouwant: For his initial kernel source
@ketut.kumajaya: For his major contributions to Wingtech (OSS Xiaomi)
@zwliew: Initial device tree reference, contributions for OSS kernel
@premaca: "Me: HAALP!" He answered me
LineageOS Team
CyanogenMod Team
Xiaomi: For MAYBE providing the not so useful Kernel Source Code after 1 whole year of waiting
Donations :
Bitcoin addresses:
LineageOS Team address:
*From: https://wiki.lineageos.org/costs.html
12aDckQC6YHEn75zReQWxXFCivBBNXfRjM
My address:
1HaYFagqvGqwTQX7xYBviXZcAqmThwsywR
Paypal:
LineageOS Team paypal:
*From: https://wiki.lineageos.org/costs.html
https://www.paypal.me/LineageOS
Source Code :
Device tree: https://github.com/LineageOS/android_device_wingtech_wt88047
Kernel source: https://github.com/LineageOS/android_kernel_wingtech_msm8916
Vendor blobs: https://github.com/TheMuppets/proprietary_vendor_wingtech
XDA:DevDB Information
[ROM][7.1.2][WT88047] LineageOS 14.1, ROM for the Xiaomi Redmi 2
Contributors
nicknitewolf, premaca, ketut.kumajaya
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: LP Bootloader
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-12-31
Last Updated 2017-09-23
My local manifest for those who want to build. (May subject to sudden changes. Don't come here crying if it suddenly does not want to compile)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_wingtech_wt88047" path="device/wingtech/wt88047" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_kernel_wingtech_msm8916" path="kernel/wingtech/msm8916" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_wingtech" path="vendor/wingtech" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
</manifest>
Supported Firmware:
Downloads:
wt88047: https://goo.gl/FNbbMP
wt86047: https://goo.gl/YHufVo
Note:
It is the firmware LineageOS supports and all users are expected to be on this very firmware. So it's mandatory that you flash this firmware via TWRP if you're newly installing Lineage.
You don't need to reflash this everytime you update you LineageOS build.
To add on:
There seems to be some confusion with this post in general. If you are coming from a stock MIUI Lollipop build, it is highly unlikely that you would need to update your firmware with the one above since Xiaomi hardly updates its firmware on older devices. Otherwise, if you are not sure what firmware you currently have, I urge you to flash the firmware linked above.
Why should I even flash this firmware?
The simple answer is that this firmware is known working with LineageOS builds and I am currently running it. Running other versions of the firmware (Like the Kitkat firmware) may warrant unheard of bugs and / or bugs that have been squashed long ago.
When should I flash this firmware?
This firmware should only be flashed once, anytime before the first boot into LineageOS.
Change-log:
Official NIGHTLY changelog:
https://download.lineageos.org/wt88047/changes
Third Party NIGHTLY changelog:
https://www.cmxlog.com/14.1/wt88047
Older change-logs:
20170114
- Enable adaptive LMK
- Adjust vm heapsize by total system ram
- Random fixes
- Upstream
20170111
- Enable SDCARDFS by default
- Tune ART JIT
- Update audio HAL again (small change)
20170109
- Various fixes
- Upstream
- Android 7.1.1_r9
20160108
- Update Sound drivers
- Update Sound HAL
- Disable VM_BMS (Because xiaomi is weird and don't support this)
- Update SDCARDFS drivers (Might be enabling by default in next build)
20170106
- Fixed unified LED HAL
- enable vm_bus
- Updated IMS blobs from potter
20170104
- Updated Unified LED functionality
Initial Build (20161230)
- SDCardfs is disabled by default
- libhealthd replaced with LineageOS OSS charger
Other Links / Info
How to Report Bugs?
State your:
Device Model
Build Number and Version (Eg. 20170201 NIGHTLY or 20170205 UNOFFICIAL)
Bootloader [Lollipop]
Logcat
Dmesg
SU Addon:
https://download.lineageos.org/extras
LineageOS no longer comes pre-rooted
* Note: Using any other methods to root your device other than the above method will result in me ignoring your bug report and / or pleas for help.
TWRP Thread: https://forum.xda-developers.com/redmi-2/development/recovery-twrp-touch-recovery-t3611503
Hell yeah....
YAY!!!!
bookmark first
Whoa!! Great job to the Dev!
Haaaaalp, you build it! Yay....
Made my day! Thanks @nicknitewolf
Just hoping that it gets official status when time comes!
Is possible flash this ROM as update from CM14.1 20161225 ?
does camera work on WT86047?
wohooo!! thanks mate
What is main difference between lineage OS and cynogen OS?
Just the name different or anything specific?
Just curious to flash
Duddits said:
Is possible flash this ROM as update from CM14.1 20161225 ?
Click to expand...
Click to collapse
Clean flash is always recommended.
nicknitewolf said:
Supported Firmware:
Downloads:
wt88047:https://goo.gl/FNbbMP
wt86047:https://goo.gl/YHufVo
Note: It is the firmware CyanogenMod supports and all users are expected to be on this very firmware. So it's mandatory that you flash this firmware via TWRP if you're newly installing CM.
You don't need to reflash this everytime you update you CyanogenMod build.
Click to expand...
Click to collapse
Nick, thanks for update. Please change cyanogenmod word here.
yay cool sir, thanx for hard work
vishnumenon1701 said:
What is main difference between lineage OS and cynogen OS?
Just the name different or anything specific?
Just curious to flash
Click to expand...
Click to collapse
Search in google. Dont spam here.
[17.1 cve 202301] download : https://androidfilehost.com/?w=files&flid=306432All-in-one: "Regular" #derf elot Los17.1 build with microG patches, extended 2x permissions, #ale5000 implementation and multiple foss apps:
microG: GmsCore(mapbox) GoogleServicesFramework DroidGuard
addons: NominatimGeocoderBackend DejaVuBackend IchnaeaNlpBackend LocalWifiNlpBackend openbmapRadiocellsOrg LocalGsmNlpBackend wlanBackend
hot-built: photoEditor aospBrowser2
prebuilt: Fdroid F-DroidPrivilegedExtension NeoLinker jQuarks
others: LineageOS_webView ; system/bin* aapt32
Also included are these non-foss 3 Google : Playstore, Calendar/Contact_Sync; like Sony embedded artfilter soundphoto moviecreator apk, they are disabled by default (due to Internet permission with known trackers), and can be activated via Settings/Apps.
Click to expand...
Click to collapse
not included: Latest compatible Google Maps 9.84.2 optional https://androidfilehost.com/?fid=11410963190603886579
Extra(s): Nfc and AudioFX tiles, basic photoEditor*, experimental WakelockBlocker via Settings/{}DevOptions <USE WITH CAUTION>.
Nota: : android Webview v106 is signed & upgradable from LineageOS_webView, Terminal is activated via Settings/System/Advanced/DeveloperOptions and Playstore has to be ForceStop-ed once after registration/wizard, and relaunch. F-Droid V.102.3 auto-update needs FDroid/Settings/ExpertMode/Privileged disabled.
After first rom flash and MicroG prim-initialization, for immediate working location, toggle /Settings /Security&Location /Location off&on.
All other included prebuilts are fdroid signed editions.
donations: Consider prim-origin @derf elot @MaR-V-iN @csagan5(Bromite)
others : @Setialpha #ThibG(DroidGuard)
+info for microG implementation https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
If you need more, please let me know about it, but for more "Google": just switch to derf_elot 's and flash Gapps...
{
"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"
}
WIP Installation, Features, Patches, ...
Installation : be sure to [FormatData]/yes with latest derfelot/Los17.1 xz1's TWRP
before flashing all-in-one rom' zip.
Features:
Sony xz2 stock Camera/Panorama/SoundPhoto/CreativeEffect
Playstore + GoogleSync calendar/contacts
...
microG with BackgroundLocation granted & latest ForegroundService
Q un-throttled wifi backends
LineageOS stats removed
Cafeine long-press to PermissionsManager
LineageOS live updatable WebView
Bromite webView compatible
F-Droid photoEditor
AudioFX tile
jQuarksBrowser : Jelly with AdBlock
aosp HTMLViewer (Browser2) for webrtc permissions (missing in Jelly)
WakelockBlocker
(EasterEgg is up and have no idea what IconQuiz is about ??)
XML:
<manifest>
<remote name="gitlab" fetch="https://gitlab.com/"/>
<remote name="aos" fetch="https://android.googlesource.com/"/>
<remove-project name="LineageOS/android_packages_apps_Updater"/>
<!-- fdroid signed jQuarks instead of Jelly: -->
<remove-project name="LineageOS/android_packages_apps_Jelly"/>
<project path="packages/apps/Browser2" name="platform/packages/apps/Browser2" remote="aos" revision="master"/>
<!-- SONY -->
<project name="whatawurst/android_kernel_sony_msm8998" path="kernel/sony/msm8998" remote="github" revision="lineage-17.1" />
<project name="whatawurst/android_device_sony_yoshino-common" path="device/sony/yoshino-common" remote="github" revision="lineage-17.1" />
<project name="whatawurst/android_device_sony_poplar" path="device/sony/poplar" remote="github" revision="lineage-17.1" />
<!-- Pinned blobs for poplar -->
<project name="whatawurst/android_vendor_sony_poplar" path="vendor/sony/poplar" remote="github" revision="lineage-17.1" />
</manifest>
Magisk 20.4 compatible useful apps: https://forum.xda-developers.com/an...etter-v1-0-t3637705/post81954189#post81954189
EDIT: to enable Gesture Typing (glide) in keyboard, use Magisk module https://forum.xda-developers.com/t/module-google-glide-typing-library.4223595/
Attached patches.zip if for rom devs only
Thats exactly what i was looking for before upgrading. Thanks a lot!
Just only one version for g8341 ? . DSDS can't use it ?
Sent from my Sony G8342 using XDA Labs
Hi, thanks for the amazing ROM! I've used your treble based ROM, but then switched to derf elot's los for more stability, now this is perfection!
If I may have a feature request: would it be possible to add an option to have the old Oreo style (vertical) recents menu?
Also I feel like nowadays most apps unfortunately need interNet (why capitalise the N btw) so can we have a switch for default state of the internet permission. It was a bit inconvenient to always go into settings and allow permission for every single app.
Sorry if I sound a bit greedy, your patches are already awesome!
Quick question... How stable is this LOS? Is it more stable than derf's rom?
Well it's stable enough for me, but if you rely heavily on gapps, then I don't recommend it. So for example Google classroom didn't work, had one app that couldn't enable push notifications and some firebase related crashes - stuff you'd expect from using microg. I had a few crashes at first but I think that's just because I didn't allow certain permissions. Since it's based on derf elot's build, I think it's mostly the same as if you'd have his build with microg and signature spoofing patches.
Found a bug with the boot animation being scaled wrongly, luckily bootup time is super fast.
Real quick question does love caption work on here? Also can I dirty flash it over my LOS17.1?
May cve release
Latest May 2020 is uploaded : https://androidfilehost.com/?fid=4349826312261816983
Changelog:
- Lineage & derfelot/kernel latest upstream
- Swappiness 25
- Calendar is now working with edit feature ok (be sure to grant all secured tweaked InterNEt apps permission)
- photoEditor updated
Gmail crashing when version > 2020.03.15: download https://androidfilehost.com/?fid=4349826312261817054
boa05 said:
scaled wrongly, luckily bootup time is super fast.
Click to expand...
Click to collapse
This is all the good about microG, isn't it ...
haiha2001 said:
Just only one version for g8341 ? . DSDS can't use it ?
Click to expand...
Click to collapse
I'm now testing unified build method from Carbon, but can't get all FingerprintedPartitions_system equal ( @Myself5 https://github.com/derfelot/android_device_sony_poplar/blob/lineage-17.1/lineage_poplar.mk#L28 missing in CarbonRom process ?); also I'm not sure if it is crucial for microG integration, since safetyNet is still broken (?). @haiha I'll pm you when I'll upload a unified test-build.
oF2pks said:
I'm now testing unified build method from Carbon, but can't get all FingerprintedPartitions_system equal ( @Myself5https://github.com/derfelot/android_device_sony_poplar/blob/lineage-17.1/lineage_poplar.mk#L28 missing in CarbonRom process ?); also I'm not sure if it is crucial for microG integration, since safetyNet is still broken (?). @haiha I'll pm you when I'll upload a unified test-build.
Click to expand...
Click to collapse
The fingerprint is stored on /odm. As I dont touch the stock odm, the vaues are loaded and set via init_yoshino from there. Therefore theres no need to set them inside the device sources
Woohoo. Just dirty flash over top?
Dirty flash and she's running like a dream ?
Few days now, and all is good. She seems smoother than before. I used to get the occasional lock up, in the launcher. But none recently.
Great work dude. Thank you for keeping my phone relevant ?
i tried to install this ROM after wiping everything (previous was Carbon rom - Android 10) with twrp 3.3.1-0, the twrp says UNABLE TO DECRYPT FBE DEVICE but it shows it installs the ROM. But when I restart the phone after flashing with TWRP I get continuos boot loop, I see the SONY LOGO but the device restarts to TWRP, I enter twrp again, wipe everything again and install lineage beta 17.1 but the same things happen, the same message UNABLE TO DECRYPT FBE DEVICE and boot loop.
Then I go and wipe everything and install Carbon ROM again, everything seems fine. Why I cannot install Lineage?
Update: it seems that twrp remembers the security options to unlock the screen from the previous ROM, even after wipping everything, including internal SD, I have a 4 points pattern. After I installed Carbon ROM again, I entered twrp again and wiped everything and the error mesage is no more (UNABLE TO DECRYPT FBE DEVICE). Then I tried to instal this ROM again but still no succes, I see SONY LOGO, the device cannot boot and enters TWRP again (and with the same error mesage before flashing UNABLE TO DECRYPT FBE DEVICE). Something is not quite wright.
Make sure to format data, and wipe everything except SD when you install. Not just flat over the top
7hr08ik said:
Make sure to format data, and wipe everything except SD when you install. Not just flat over the top
Click to expand...
Click to collapse
That's what I did, multiple times. But with no result
No idea then. Trying to think back.
So, for me the process was
TWRP - format data (type yes)
Reboot into recovery
Full wipe (slide across for data, cache etc)
Another reboot into recovery
Then install
But at end of install don't reboot phone.
Go back to TWRP main menu.
Shutdown
Power back on
pleniceanu cristian said:
That's what I did, multiple times. But with no result
Click to expand...
Click to collapse
Are you using derfelot latest twrp ?: https://androidfilehost.com/?w=files&flid=295816
Myself5 said:
The fingerprint is stored on /odm. As I dont touch the stock odm, the vaues are loaded and set via init_yoshino from there. Therefore theres no need to set them inside the device sources
Click to expand...
Click to collapse
@Myself5 , on Lineage, I also have system_fingerprint different and same as odm (checked via Build.getFingerprintedPartitions()) : any hint about possible downside effects with init_poplar.cpp modified, such as:
Code:
void target_load_properties()
{
std::string model = GetProperty("ro.product.vendor.name", "");
[B]+ std::string fp = GetProperty("ro.bootimage.build.fingerprint", "");
+ property_override("ro.odm.build.fingerprint", fp.c_str());
+ property_override("ro.system.build.fingerprint", fp.c_str());[/B]
if (model == "G8342") {
... ...
(btw, didn't follow 100 extreme value for swappiness value on both Lineage & Carbon : 25 instead ?)
oF2pks said:
Are you using derfelot latest twrp ?
Click to expand...
Click to collapse
Yes
[11.0_r40/v312] download : https://androidfilehost.com/?a=show&w=files&flid=286761
All-in-one: "Regular" #phhusson Roar AOSP 11.0 build with microG patches, embedded #su /system (+abVndkLite), and multiple foss apps:
official microG: GmsCore(mapbox) GoogleServicesFramework DroidGuard
addons: NominatimGeocoderBackend DejaVuBackend IchnaeaNlpBackend LocalWifiNlpBackend openbmapRadiocellsOrg LocalGsmNlpBackend
hot-built: musicEleven calendarEtar Terminal testDevCamera Calculator
prebuilt: Fdroid F-DroidPrivilegedExtension browserQuarks axetAudioRecorder kDI Superuser BromiteWebview NeoLinker
system/bin* : aapt32 grep64(pcre2grep version 10.22 2016-07-29)
Also included are these non-foss 3 Google : Playstore, Calendar/Contact_Sync; like phh-Superuser apk, they are disabled by default, and can be activated via Settings/Apps.
Click to expand...
Click to collapse
not included: Latest compatible Google Maps 9.84.2 optional https://androidfilehost.com/?fid=11410963190603886579
Extra(s): Nfc and Cafeine tiles, basic photoEditor*, experimental WakelockBlocker via Settings/{}DevOptions <USE WITH CAUTION>.
Nota: android Webview v92 is signed & upgradable from Bromite, Terminal is activated via Settings/System/Advanced/DeveloperOptions and Playstore has to be ForceStop-ed once after registration/wizard, and relaunch. F-Droid V.102.3 auto-update needs FDroid/Settings/ExpertMode/Privileged disabled.
After first rom flash and MicroG prim-initialization, for immediate working location, toggle /Settings /Security&Location /Location off&on.
All included prebuilds are fdroid signed editions.
donations: Consider prim-origin @phhusson @MaR-V-iN @csagan5 (Bromite)
others : @ale5000 @Setialpha #ThibG(DroidGuard)
+info for microG implementation https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
If you need more, please let me know about it, but for more "Google": just switch to phhusson "gapps" flavour...
{
"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"
}
Bugs reporting
ufOfficial rom includes static & passive app kDI (KalturaDeviceInfo) to list all your device specs (treble, widevine...) in a json, and can help you with GSFid or others info(s). This app doesn't connect to internet, and the json (~Android/data/com.oF2pks.kalturadeviceinfo/files/) should not include any private data or ids; it's up to you to share or not.
If you encounter major AOSP "hardware (not software)" related bugs, please switch to #phhusson vanilla v___ edition and help him with proper focused hardware logs. For Camera2 missing features, take time to check OpenCamera first, aosp DevCamera "sample stub" is included for testing purpose : autofocus... ; full cam specs are also in KalturaDeviceInfo (per each "physical" cam).
Click to expand...
Click to collapse
(Specific Redmi Note 9 Pro overlay_joyeuse & props_ curtana/joyeuse are optimized)
(Huawei/msm8937 Moto/G7Play Razer/cheryl Sony/XZ3 Realme/X2Pro overlays are switched to aosp FusedLocation)
swappiness =28 & dirty_writeback_centisecs =1500: check #suSmartPack-KernelManager for other tweaks.
For Treble with root #su (+abVndkLite), you can do some tests modifying specifically,
/system/bin/rw-system.sh to change some features on post-fs:https://github.com/phhusson/device_phh_treble/blob/android-11.0/vndk.rc#L1
check also phh-on-boot.sh & phh-on-data.sh
hot-built links :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="los" fetch="https://github.com/LineageOS/" />
<remote name="of2" fetch="https://gitlab.com/oF2pks/" />
<remote name="qcom" fetch="https://source.codeaurora.org/" />
<remote name="aos" fetch="https://android.googlesource.com/" />
<project path="packages/apps/ExactCalculator" name="android_packages_apps_ExactCalculator" remote="los" revision="lineage-18.1" />
<project path="packages/apps/Eleven" name="snapmusic" remote="of2" revision="test2" />
<remove-project name="platform/packages/apps/Calendar" />
<project path="packages/apps/Etar" name="android_packages_apps_Etar" remote="los" revision="lineage-18.1" />
<remove-project name="platform/packages/apps/Terminal" />
<project path="packages/apps/Terminal" name="android_packages_apps_Terminal" remote="los" revision="lineage-18.1" />
</manifest>
- Bromite latest webView v92, upgradable via F-Droid repo https://fdroid.bromite.org/fdroid/repo
- Optimized browser Quarks ( adBlocker, offline reading mht , print/pdf , share/clipboard target ...) https://gitlab.com/oF2pks/jelly/commits/fdroid. Conversely to embedded WebViewShell, Quarks don't allow permissions for Camera & Microphone capture (WebRTC)
Attached State_Changes___.zip if for rom devs only
V307system11-arm64-aONLY-ufOxTERM_mapbox.img
Build does not boot on ZTE Axon 7 (ARM64 A Only) device. Using the same vendor and kernel as phh v307, which boots normally.
I could not get a log as the device would keep boot-looping to the bootloader and did not make it to the boot animation. I've attached a .json file of the device running phh's roar v307 build using your kDI app if it's of any use. Let me know if further logs are needed.
Is gesture navigation enabled by default? Because on some GSI with 3 button navigation, the screen keeps glitching. I can't even unlock the screen due to that.
runninghamster said:
V307system11-arm64-aONLY-ufOxTERM_mapbox.img
Build does not boot on ZTE Axon 7 (ARM64 A Only) device. Using the same vendor and kernel as phh v307, which boots normally.
Click to expand...
Click to collapse
Did you flash it on working Axon 7 ZTE's oem original rom, or on top of phh previously flashed gsi ?
oF2pks said:
Did you flash it on working Axon 7 ZTE's oem original rom, or on top of phh previously flashed gsi ?
Click to expand...
Click to collapse
The stock OEM rom for the Axon 7 is outdated and doesn't support Project Treble. We have our own unofficial vendor and kernel for Treble. I did a clean flash (wiped all partitions, flashed treble zip, flashed system image, boot).
Phh's roar v307 boots with the same procedure, as well as the other v307 based GSI.
Thanks a lot for this great package. I have been running v302 a32b64 for a while and it's quite functional.
One question: does V307system11-arm32_binder64-ab-ufOxTERM_vndklite include mapbox and will there also be a non-vendklite version?
Hello,
I can't figure it out.
I have flashed r307 vndklite on the top of previous r302.
I have ensured I have no magisk patched boot image.
I can get root access within adb shell and I seemingly can remount the root partition read write by saying
mount -o remount,rw /
I can then change just anything e.g. inside /system/app folder.
However as soon as I call
mount -o remount,ro /
or reboot the device, everything is back to the previous state as if I have done no modifications to the system partition.
I am afraid phh-securise.sh won't work too.
My goal is to eventually replace phh-su with magisk so I can use magisk hide.
What are my choices?
oF2pks Is there a chance you will update this to more recent phhusson GSI base please?
pvdeejay said:
oF2pks Is there a chance you will update this to more recent phhusson GSI base please?
Click to expand...
Click to collapse
Indeed, will sync latest phhusson's github repo by next weekend; probably last android 11 before a possible aosp 12 September start (?)
New build AOSP 11.0_r40 (v312) is up: https://androidfilehost.com/?a=show&w=files&flid=286761
August cve
GmsCore v0.2.22.212658
Bromite v92.0.4515.134
Eleven (optimized): https://gitlab.com/oF2pks/snapmusic/-/commits/test2
GSi devices' specifics & commits: https://github.com/phhusson/device_phh_treble/commits/d0355b6dd57b4cba3d01a39866ad3552eba173e0
@pvdeejay this is including Make phh-securize.sh work with current Magisk recent commit. @landsome since safetyNet fails with microG, vndkLite brings more possibilities.
Don't forget to thanks @phhusson on his github's: https://github.com/sponsors/phhusson
R40 runs nicely on Zenfone 8, no bugs found
@oF2pks: If you will ever be updating this one or making a new one based off of Android 12, can you consider adding f-droid prebuilt edition of axet call recorder as a system app? I see you are already including axet audio recorder. Adding call recorder as a system app would allow the call recorder app to request CAPTURE_AUDIO_OUTPUT permission what is needed for the call recording to actually work these days. Since root hide is no longer a thing even with magisk, I haven't managed to get modifying system partition to work, this is the only bit I am currently missing.
Hello,
Have you got Android 12 update of this? Or in other words is there a rom I might be able to flash over this so I will not have to reinstall the whole system from scratch including aps and their data?
pvdeejay said:
Hello,
Have you got Android 12 update of this? Or in other words is there a rom I might be able to flash over this so I will not have to reinstall the whole system from scratch including aps and their data?
Click to expand...
Click to collapse
Will upload 12.1 March arm64_AB-seamless soon with a new thread for April release: works out of the box over android 11, with axet callRecorder as system app.
Be aware that like all @phhusson 12.1 editions, flashing 12.1 gsi on dynamic partition will throw a Invalid sparse file format at header magic that can lead to bootloops: if flashing latest vndkLite android 11 was fine then 12.1 will update & boot fine.
oF2pks said:
Will upload 12.1 March arm64_AB-seamless soon with a new thread for April release: works out of the box over android 11, with axet callRecorder as system app.
Be aware that like all @phhusson 12.1 editions, flashing 12.1 gsi on dynamic partition will throw a Invalid sparse file format at header magic that can lead to bootloops: if flashing latest vndkLite android 11 was fine then 12.1 will update & boot fine.
Click to expand...
Click to collapse
That's not an error. Maybe a warning, but realistically just a debug information. And no, it doesn't lead to bootloops.
phhusson said:
That's not an error. Maybe a warning, but realistically just a debug information. And no, it doesn't lead to bootloops.
Click to expand...
Click to collapse
I used to update Redmi note 9 pro [vendors/boot/bin ...]partitions, with latest MIUI ROM package file from Xiaomi, via fastboot flash_all_except_data_storage.sh which includes fastboot flash super super.img,
...followed straight (no reboot), by a fastbootd (dynamic) flash of gsi system.img : on vndk android 11, I got bootloops, but work fine with normal aosp gsi build.
So I thought sas-creator re-build was missing the headerMagic (?).
I was able to recover device bootloop and my (gsi)/data, by first reflashing (fastbootd) normal aosp gsi build: reboot fine with /data safe, then reflash (fastbootd) vndklite with no more bootloops (but still the headerMagic warning), and all my /data safe back (... plus updated Xiaomi proprietory partitions).
Now with android 12.1, even normal aosp build has this headerMagic warning (?).
btw, on android 12.1, aosp native command development/tools/privapp_permissions/privapp_permissions.py
throws multiple warnings on missing private permissions for apex modules like
XML:
################################################################################
#
# apex/com.android.permission XML:
#
################################################################################
<?xml version="1.0" encoding="utf-8"?>
<!-- for the partition: /apex/com.android.permission -->
<permissions>
<privapp-permissions package="com.android.permissioncontroller">
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
<permission name="android.permission.GET_APP_OPS_STATS"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.MODIFY_AUDIO_ROUTING"/>
<permission name="android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS"/>
<permission name="android.permission.PACKAGE_USAGE_STATS"/>
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.REQUEST_INCIDENT_REPORT_APPROVAL"/>
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
</privapp-permissions>
</permissions>
@phhusson , is this related to android 12.1 change for "ro.apex.updatable": "false", (true in android 11)?
Anyway, overall, your gsi 12.1 is fully functional for my microG mods (congrats).
@phhusson , aosp android 12 now provides out/host/linux-x86/bin/img2simg tool to create ext2->sparse,
...so I re-iterated new Xiaomi proprietary ROM update followed straight by gsi fastbootD dynamic re-flash, and have both my vndkLite builds bootlooping: ext2 + sparse.
And, as you indeed clarified this headerMagic warning , I could recover with natural ext2 android12 despite Invalid sparse file format at header magic
So the bootloop comes from fresh proprietary + super.img, above previous gsi/data partition, finalized by vndkLite flavor only (?). Hope you find the faulty origin...
Finally I can flash vndk gsi back, above my working natural gsi, with my /data safe back.
@phhusson fyi, for vndkLite flavor, I end your lite-adapter.sh with resize2fs s.img [{resize2fs -P s.img}+60000] to manage few extra space for AdAway or others #root tools: https://github.com/phhusson/sas-creator/issues/12
(previous post cleaned, sorry again for headerMagic warning misunderstood)
Android 12.1 pre-release v411 for arm64_abSeamless only:
V411system12_1-arm64-ab-ufOxTERM_fallback.img.xz | by oF2pks for GSI AEX
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
- March 2022 cve
- non-vndk flavor: use it to avoid bootloops in case of device specifics proprietary upgrade needs, prior to upcoming vndkLite edition
- switch to LineageOS webview v99, (Bromite can still be installed aside as a normal app like Google webview(s)): up-datable straight from https://github.com/LineageOS/android_external_chromium-webview/tree/master/prebuilt
- callRecorder added as pre-installed /system and disabled by default
- calendarEtar removed from /system: use Fdroid version if needed.
(not yet as stable as android11 and no wakelockBlocker option)
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="los" fetch="https://github.com/LineageOS/" />
<remote name="aos" fetch="https://android.googlesource.com/" />
<project path="packages/apps/ExactCalculator" name="android_packages_apps_ExactCalculator" remote="los" revision="lineage-19.1" />
<project path="packages/apps/Eleven" name="android_packages_apps_Eleven" remote="los" revision="lineage-19.1" />
<project path="packages/apps/Terminal" name="android_packages_apps_Terminal" remote="los" revision="lineage-18.1" />
<project path="external/libvterm" name="platform/external/libvterm" remote="aos" revision="2caab416f758b648c4034e9f22cb7b76c37203f0" />
<remove-project name="platform/external/chromium-webview" />
<project path="external/chromium-webview" name="android_external_chromium-webview" remote="los" revision="master" />
<remove-project name="platform/packages/inputmethods/LatinIME" />
<project path="packages/inputmethods/LatinIME" name="android_packages_inputmethods_LatinIME" remote="los" revision="lineage-19.1" />
</manifest>
Android 12.1 vndkLite v413 for arm64_abSeamless only:
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
- May 2022 cve
- vndkLite flavor with extra 150Mo free on /system: to avoid bootloops in case of device specifics proprietary upgrade needs, use previous _fallback v411 edition first.
Let me know your priorities for other device builds: arm32 aOnly...
{
"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"
}
lineage-20.0-20230222-UNOFFICIAL-shamu.zip
lineage-20.0-20221217-UNOFFICIAL-shamu.zip
lineage-20.0-20221014-UNOFFICIAL-shamu.zip
Known issues:
- On some boots the camera may not be working. Simply reboot your phone to fix it.
How to enable encryption on the February build and newer:
- Data must be formatted. If you're using TWRP, click wipe and then format data
- Install the LineageOS zip
- Install the attached SetEncryption.zip
- Reboot and enjoy encryption
How to build from source:
I'm going to assume you've built LineageOS before and just describe the special steps
- Repo init with the LineageOS-UL sources here: https://github.com/LineageOS-UL/android
- Copy the attached roomservice.xml to .repo/local_manifests
- Sync the sources
- From the source root execute:
Code:
sed -i "s/.*TARGET_BUILD_UNBUNDLED.*/ifeq (0,1)/" build/make/core/tasks/platform_availability_check.mk
- If you want your builds to use encryption then run:
Code:
sed -i "s/latemount/latemount,fileencryption=adiantum/" device/moto/shamu/rootdir/etc/fstab.shamu
- cd to frameworks/opt/net/ims and run git apply path_to_attached_Ignore-SubId.patch
- DO NOT use an existing vendor repo . You must run ./extract-files.sh on the latest build I've provided
- Build as normal
Kernel Source: https://github.com/rootfan/android_kernel_moto_shamu
Special thanks to:
- LineageOS team
- Elektroschmock, npjohnson, and anyone else who has worked on shamu in the past
- abhishekt295 and wavedashdoc for getting IMS to work on android 10
- tarkzim and khalvat for their work on the LineageOS-UL project
Standard disclaimer: You're responsible for what you do to your devices, so don't blame anyone else if something goes wrong.
Enjoy android 13 on the Nexus 6
bravo!!!!!!!
any build plan for angler?
Which gapps to use with this build?
Hey, I'm here to do some reports.
My last OS is Mokee based on Oreo 8.1 and I flashed this from with TWRP 3.1.1-0.
When the first time I try to flash it notices that "This package is for shamu, and your device is [empty]." So I removed the asserts check from update-script and I made it this time.
Here are my steps to flash this:
1. Reboot into recovery, wipe data.
2. Wipe data, davlik, system, data, and cache.
3. Flash the rom
4. Format data
5. Reboot
Now it is stuck in the loop of lineage os boot animation. Any suggestions?
I happen to come across this thread and just had to poke my head in here real quick and say "hell yeah! ' " Long live the Nexus!! "I always like it when I see a Nexus still getting current rom love. I had all of the Nexus devices.
Those were the days!!
lepi said:
Which gapps to use with this build?
Click to expand...
Click to collapse
I used BiTGApps-arm-13.0.0-v1.4_signed.zip. I did dirty flash to lineage-19.1-20220919-UNOFFICIAL-shamu. lineage-20.0 booted without any problem.
MindTheGapps-13.0.0-arm-20221007_211145.zip may be used instead.
TatsuMasa said:
I used BiTGApps-arm-13.0.0-v1.4_signed.zip. I did dirty flash to lineage-19.1-20220919-UNOFFICIAL-shamu. lineage-20.0 booted without any problem.
MindTheGapps-13.0.0-arm-20221007_211145.zip may be used instead.
Click to expand...
Click to collapse
Used MindTheGapps 13, thanks
Thanks a lot! Great work!
the camera is not working, please tell me how to fix it
bccrosby said:
the camera is not working, please tell me how to fix it
Click to expand...
Click to collapse
Be patient. Release 20.0 is very early. Take a look at >chengelog<. Work continues, including on the camera.
bccrosby said:
the camera is not working, please tell me how to fix it
Click to expand...
Click to collapse
Just reboot your phone and then the camera should work fine.
rootfan said:
Just reboot your phone and then the camera should work fine.
Click to expand...
Click to collapse
thank you for android 13 on the nexus 6 although the play store cant update apps because it doesnt have a storage permission
for some reason
@rootfan
Thanks for your work !
I was feeling adventurous this morning so I tried to build with your repos
To do so I've gotten to adding the following lines to my roomservice.xml
XML:
<project path="kernel/moto/shamu" remote="github" name="rootfan/android_kernel_moto_shamu" revision="los-20.0" />
<project path="device/moto/shamu" remote="github" name="rootfan/android_device_moto_shamu" revision="los-20.0" />
<project path="vendor/motorola" remote="github" name="TheMuppets/proprietary_vendor_motorola" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" revision="lineage-18.1" />
but build is failing with
Code:
FAILED:
build/make/core/main.mk:1308: warning: device/moto/shamu/lineage_shamu.mk includes non-existent modules in PRODUCT_PACKAGES
Offending entries:
nfc_nci.bcm2079x.default
build/make/core/main.mk:1308: error: Build failed.
12:15:32 ckati failed with: exit status 1
--> What am I missing ?
I noticed you also have a android_frameworks_opt_telephony repo, but I have not used it as your initial post suggests only kernel source and device tree repos are necessary. --> Is it also required ?
Lastly, do you plan on merging the shamu: Kang DRM from angler commit that make NEtflix work again !
Looking forward to testing this on my shamu
dwardo said:
@rootfan
Thanks for your work !
I was feeling adventurous this morning so I tried to build with your repos
To do so I've gotten to adding the following lines to my roomservice.xml
XML:
<project path="kernel/moto/shamu" remote="github" name="rootfan/android_kernel_moto_shamu" revision="los-20.0" />
<project path="device/moto/shamu" remote="github" name="rootfan/android_device_moto_shamu" revision="los-20.0" />
<project path="vendor/motorola" remote="github" name="TheMuppets/proprietary_vendor_motorola" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" revision="lineage-18.1" />
but build is failing with
Code:
FAILED:
build/make/core/main.mk:1308: warning: device/moto/shamu/lineage_shamu.mk includes non-existent modules in PRODUCT_PACKAGES
Offending entries:
nfc_nci.bcm2079x.default
build/make/core/main.mk:1308: error: Build failed.
12:15:32 ckati failed with: exit status 1
--> What am I missing ?
I noticed you also have a android_frameworks_opt_telephony repo, but I have not used it as your initial post suggests only kernel source and device tree repos are necessary. --> Is it also required ?
Lastly, do you plan on merging the shamu: Kang DRM from angler commit that make NEtflix work again !
Looking forward to testing this on my shamu
Click to expand...
Click to collapse
Try to track this in your manifests, maybe it will work.
GitHub - LineageOS/android_hardware_broadcom_nfc
Contribute to LineageOS/android_hardware_broadcom_nfc development by creating an account on GitHub.
github.com
Furthermore,resync @rootfan 's repos for 20.0 branch when he make it up-to-date.
Can someone kindly confirm GPS works on this build? I have LinOS 20 on another phone (admittedly an ancient Sams. Note 2) and the GPS works but very sluggish. All else works fairly well.
On my Nexus 6, I have the well-cared for LinOS 18.1 and GPS is very quick- the whole ROM is rock solid. I can of course make a recovery copy but just want to know what to expect as this is still my daily driver. Some of the rebooting & charging issues also make me a bit uneasy. I know it is still early days and am only grateful for rootfan's efforts.
What have any of you lab rats (just kidding) experienced so far specifically regarding GPS with this 20 ROM on a nav map system e.g. Organic or Google Maps? Thanks
TotalChen said:
Try to track this in your manifests, maybe it will work.
GitHub - LineageOS/android_hardware_broadcom_nfc
Contribute to LineageOS/android_hardware_broadcom_nfc development by creating an account on GitHub.
github.com
Furthermore,resync @rootfan 's repos for 20.0 branch when he make it up-to-date.
Click to expand...
Click to collapse
That got me to the next issues .
tons of warnings turned to errors (found how to bypass that) as -Werror compile option is set
kernel includes not found by other projects
Seems rootfan's modification's are not up to date or all available on his github. Will check from time to time and see if updates become available.
Took the plunge as I can quickly and easily revert back to rock solid LOS18 if nec. with TWRP backup. So..
Unlocked phone and SIM card, dirty flashed ROM, BitGaps 1.6, Magisk 24.3s.....
Whole installation, a few reboots, some App checking, took like 10 Min. Dirty flash saves hours of re-confiuring and reinstalling files and apps. YMMV but as I am fully backed up, it was well worth a try.
All seems just fine. Banking apps, travel, cars etc. all good. My Open Camera app, and the built in Camera all sans problems. Even kept some deep Magisk modules. Will have to watch for a few days re GPS, notifications, battery life. It is slightly less smooth than LOS18 but can easily live with it, and it may improve over time. Have asked trusted wingman to also try and monitor.
@rootfan Nice one; hope you'll keep supporting and updating this great work.
Thank you @rootfan for bringing new up to date life to Shamu . Really amazing to see android 13 on it !
Just a heads-up. Reporting, not complaining.
I followed @esysfound in dirty flashing my N6, and it looked good, but today I've booted from cold and I'm in a bootloop - the LOS circles have been running for a while with occasional reboots. No problem - (a) I knew dirty flashing isn't reliable and (b) I can restore my OrangeFox 19.1 backup.
Just in case anyone is thinking of trying a dirty flash...