{
"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 18.1
Code:
#include <std_disclaimer.h>
/*
* 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! 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM is for testing purposes only and may contain unexpected bugs
2. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
3. This ROM will never work with any versions of Google Camera (GCam)!
4. You need to flash Stock Android 10 before flashing this ROM.
5. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
6. If you came from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
Downloads Links
AFH
Google Applications (optional):
NikGApps: https://nikgapps.com/
Information: Flash the GApps before first boot. If not, a clean flash is recommended
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Flash the recovery.img in the zip file
Flash and boot into Recovery then choose Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
Shion Sjll
The LineageOS Team
The CyanogenMod Team
Source Code:
hellobbn/android_device_sony_pdx203
Contribute to hellobbn/android_device_sony_pdx203 development by creating an account on GitHub.
github.com
hellobbn/android_vendor_sony_pdx203
Contribute to hellobbn/android_vendor_sony_pdx203 development by creating an account on GitHub.
github.com
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-01-20
Last Updated 2020-01-20
Important note
1. This Lineage build is based on official Android 10, not Android 11 (since AT72 hasn't been updated yet)
2. This build is highly experimental and for testing purpose only
3. This ROM may not be able to pass SafetyNet check
What works:
- Boot
- Bluetooth (LDAC might have problems, I am not sure)
- WiFi
- WiFi Hotspot
- RIL - Phone - Data
- GPS
- Camera
- Lights
- Touchscreen
- Fingerprint
- Microphone
- Audio & music
- Bluetooth audio
- NFC
- Clock
- USB
- SEPolicies: Enforcing
What does not work:
Always On Display does not seem to work properly
Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.
james194zt said:
Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.
Click to expand...
Click to collapse
Are you on stock android 10 before flashing? Have you erased the userdata?
I tried to flash it again and it boots successfully.
Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).
james194zt said:
Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).
Click to expand...
Click to collapse
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?
I was on the built in fastbootd not Lineage OS, I used Lineageos recovery after to see what was going on, will try the above though
clfbbn said:
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?
Click to expand...
Click to collapse
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.
james194zt said:
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.
Click to expand...
Click to collapse
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....
clfbbn said:
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....
Click to expand...
Click to collapse
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change
james194zt said:
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change
Click to expand...
Click to collapse
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?
clfbbn said:
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?
Click to expand...
Click to collapse
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!
james194zt said:
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!
Click to expand...
Click to collapse
Interesting, did you booted at least once when you downgraded to Android 10 because that might be the problem too?
I am also assuming this problem to be related to the vendor partition. If that is the case, I need to pull the blobs from AT51 and rebuild the ROM.
Edit: Would you mind we talking using telegram? I have PMed you my username.
I have an AT51 if I can help somehow. I'm having a different issue, but maybe its related. https://forum.xda-developers.com/t/...os-17-1-for-xperia-1-ii.4199059/post-84512259
Hi! this is awsome!
I just tried it out and everything seems to be working!
I am wondering it it is possible to get the camera pro and cinema pro working like for xperia 5 II
[EXTRA] Stock Camera && Cinema Pro && Photo Pro For AOSP
You MUST satisfy following condition: * My Device Tree Based ROM (Not SODP) * A PDX206 (Xperia 5 II ) User Download Link: Stock Camera if (ANDROID_VERSION == 10 && STOCK_VENDOR == 10) Using 52_RHE Cinema Pro [52_RHE] Photo Pro [52_RHE] if...
forum.xda-developers.com
Does anyone know how to do it?
@clfbbn, any reason for not making this build official? I'm willing to support.
ShionKagurazaka said:
Not easy to do, I think Bbn and me both are students, we don't have many times.
And then, if we need something like Sony Camera, Sony Photo Pro and so on in ROMs, we can't be offical
So why not Unoffical ?
Click to expand...
Click to collapse
I would like to make it Official because I would like to be able to get OTA updates. But I think you're right about the camera. The alternative is to not provide them and just share them separately as you share them.
I just build mine but I am thinking that not everyone has the patience to do it.
I noticed that extFAT does work on this build. Do you know how to fix it? I formatted the sd card to fat32 but the file size is limited to 4GB...
XQ-AT52 device said cannot find "system" partition" when trying "fastboot flash system system.img" . Please advise.
ShionKagurazaka said:
fastboot reboot fastboot at first
Click to expand...
Click to collapse
tried but "fastboot: usage: unknown reboot target fastboot" message appears
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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Back camera
Front camera
Audio
Sensors
Flash
GPS
VoLTE
Known issues :
Selinux permissive
Report with logcat if found any
Instructions :
Download the latest build
Reboot to recovery
Make sure you're using stock unmodified vendor.
Wipe data, cache, system ( Don't wipe vendor )
Flash the latest build and GApps
Reboot
Downloads :
Unofficial Builds : Click Here
Source :
Device tree
Kernel tree
Credits :
@SagarMakhar for his work on Realme X
Thanks to all testers who helped in testing
XDA:DevDB Information
[ROM][RMX1971][9.0.0][UNOFFICIAL] LineageOS 16.0, ROM for the Realme 5 Pro
Contributors
thesprintster, SagarMakhar
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Based On: Lineage OS
Version Information
Status: Stable
Created 2019-10-18
Last Updated 2019-10-18
Screenshots:
Changelog:
20191018: Initial build
20191109: Here
20191116: Here
Amazing job brother
using as daily driver from last 2 weeks ^_^
Everything Works perfect , Stable ROM :fingers-crossed::laugh:
note :
Keep ambiance display (Always-on display) off ( because our touch drivers are outdated ;p touch doesn't work after booting device, need to press power button on and off to get touch working and with ambiance display on screen doesn't sleep so touch won't work ;p so simple keep it off ;p )
this should get fixed in upcoming builds so relax
yog12 said:
Amazing job brother
Click to expand...
Click to collapse
have you tried it?
---------- Post added at 05:43 AM ---------- Previous post was at 05:34 AM ----------
thesprintster said:
Screenshots:
View attachment 4847829 View attachment 4847831 View attachment 4847833 View attachment 4847835 View attachment 4847837
Changelog:
20191018: Initial build
Click to expand...
Click to collapse
how about the camera quality? is it similar?
:silly: Yeaaaay... gonna try soon..
will try today..
Good job bro
iam flashing bug failed to mount '/system_root'
my devices realme Q
what is the purpose of vbmeta.img?
star.vest2 said:
what is the purpose of vbmeta.img?
Click to expand...
Click to collapse
Do you need to flash this vbmeta.img as well or just the rom?
Touch is not working
thesprintster said:
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Back camera
Front camera
Audio
Sensors
Flash
GPS
VoLTE
Fingerprint
Known issues :
Selinux permissive
Report with logcat if found any
Instructions :
Download the latest build
Reboot to recovery
Make sure you're using stock unmodified vendor.
Wipe data, cache, system ( Don't wipe vendor )
Flash the latest build and GApps
Reboot
Downloads :
Unofficial Builds : Click Here
Source :
Device tree
Kernel tree
Credits :
@SagarMakhar for his work on Realme X
Thanks to all testers who helped in testing
XDA:DevDB Information
[ROM][RMX1971][9.0.0][UNOFFICIAL] LineageOS 16.0, ROM for the Realme 5 Pro
Contributors
thesprintster, SagarMakhar
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Based On: Lineage OS
Version Information
Status: Stable
Created 2019-10-18
Last Updated 2019-10-18
Click to expand...
Click to collapse
touch is not working.
it was working initially then screen became irresponsive on reboot
Karan Yuvraj Singh said:
touch is not working.
it was working initially then screen became irresponsive on reboot
Click to expand...
Click to collapse
U have to flash it again.. Turn of ambient diaply immediately after booting.. There is some.problem with that..
How is it, is there any serious bug in this rom?
How is the camera quality? Can i still use the wide angle lens as well? How if i wanna go back to Color Os? Vooc still working?
mfauzanalg said:
How is it, is there any serious bug in this rom?
How is the camera quality? Can i still use the wide angle lens as well? How if i wanna go back to Color Os? Vooc still working?
Click to expand...
Click to collapse
Can't even flash lineage os with the twrp recovery provided by the same guy. I'm stuck in recovery now and can't flash a single thing for system_root cannot be mounted invalid anrgument. Don't try this.
greenys' said:
Can't even flash lineage os with the twrp recovery provided by the same guy. I'm stuck in recovery now and can't flash a single thing for system_root cannot be mounted invalid anrgument. Don't try this.
Click to expand...
Click to collapse
Hmmm, so what can you do noww to repair it? I rlly want aosp rom on my device (( i dont like color os (
Karan Yuvraj Singh said:
touch is not working.
it was working initially then screen became irresponsive on reboot
Click to expand...
Click to collapse
jijoejoe123 said:
U have to flash it again.. Turn of ambient diaply immediately after booting.. There is some.problem with that..
Click to expand...
Click to collapse
WIll address it in next build
greenys' said:
Can't even flash lineage os with the twrp recovery provided by the same guy. I'm stuck in recovery now and can't flash a single thing for system_root cannot be mounted invalid anrgument. Don't try this.
Click to expand...
Click to collapse
Some Non indian firmware devices are facing trouble while flashing. I have to inspect it
JominatorX said:
Do you need to flash this vbmeta.img as well or just the rom?
Click to expand...
Click to collapse
i don't know the author included it in the download page, so i'm asking
star.vest2 said:
i don't know the author included it in the download page, so i'm asking
Click to expand...
Click to collapse
-----------------------------
TWRP flashing and LenageOS installation REALME 5 pro/Q
1)make sure that your bootloader is unlocked.
you can vist this link https://c.realme.com/in/post-details/1184734239149522944 OR
this youtube video
for referance
2)after you have a unlocked bootloader, download the neccessory files required in your PC
===>platform tools (fastboot files) link: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
===>TWRP recovery img . link: https://drive.google.com/drive/folders/1_pRUK4bj74N6xErkpFLr--2GoKyGxUtl
===> vbmeta img . link: https://drive.google.com/file/d/1kq9rV3eF8rYAUwmUvXo-8vttYIhVcQCb/view
===>Leneage OS for realme 5 pro . link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
3) once you have all the files
flash the vbmeta.img with fastboot..
COMMAND : fastboot flash vbmeta vbmeta.img
4) after that flash the recovery
COMMAND: fastboot flash recovery twrp-RMX1971-20191018.img
5) after that reboot into recovery by pressing the volume button on your phone and see " reboot recovery" in a red font
and press power button when u see that.
--.OPTIANAL AND RISKY step {IF YOU WANT TO BOOT INTO COLOROS AFTER INSTALLING TWRP, FLASH THE TWRP RECOVERY IMG AS BOOT ,i dont know this work in new twrp.but worked for me(fastboot flash boot twrp-RMX1971-20191018.img )}
6)after u successfully get the twrp menu make a backup of your whole system(all partitions) in case something goes wrong and move the backup into a lap or memory card
7)install the LenageOS and gapps . and reboot into fastboot mode and do step 3 again but this time flash vbmeta.img from this link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
8) wipe the whole data partition
9) reboot normally.
IN CASE YOU ARE STUCK IN THE RECOVERY MODE OR FASTBOOT MODE FEEL FREE TO CONTACT ME @azharsalim135
thanks man i managed to boot after i flashed the vbmeta, but any lockscreen method doesn't work. And i forgot to backup the color os so i can't get back to it. Any ideas how to flash magisk? @jijoejoe123
jijoejoe123 said:
-----------------------------
TWRP flashing and LenageOS installation REALME 5 pro/Q
1)make sure that your bootloader is unlocked.
you can vist this link https://c.realme.com/in/post-details/1184734239149522944 OR
this youtube video
for referance
2)after you have a unlocked bootloader, download the neccessory files required in your PC
===>platform tools (fastboot files) link: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
===>TWRP recovery img . link: https://drive.google.com/drive/folders/1_pRUK4bj74N6xErkpFLr--2GoKyGxUtl
===> vbmeta img . link: https://drive.google.com/file/d/1kq9rV3eF8rYAUwmUvXo-8vttYIhVcQCb/view
===>Leneage OS for realme 5 pro . link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
3) once you have all the files
flash the vbmeta.img with fastboot..
COMMAND : fastboot flash vbmeta vbmeta.img
4) after that flash the recovery
COMMAND: fastboot flash recovery twrp-RMX1971-20191018.img
5) after that reboot into recovery by pressing the volume button on your phone and see " reboot recovery" in a red font
and press power button when u see that.
--.OPTIANAL AND RISKY step {IF YOU WANT TO BOOT INTO COLOROS AFTER INSTALLING TWRP, FLASH THE TWRP RECOVERY IMG AS BOOT ,i dont know this work in new twrp.but worked for me(fastboot flash boot twrp-RMX1971-20191018.img )}
6)after u successfully get the twrp menu make a backup of your whole system(all partitions) in case something goes wrong and move the backup into a lap or memory card
7)install the LenageOS and gapps . and reboot into fastboot mode and do step 3 again but this time flash vbmeta.img from this link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
8) wipe the whole data partition
9) reboot normally.
IN CASE YOU ARE STUCK IN THE RECOVERY MODE OR FASTBOOT MODE FEEL FREE TO CONTACT ME @azharsalim135
Click to expand...
Click to collapse
Nothing changes. Still can't flash a thing from twrp. Error: 7, failed to mount /system_root (invalid argument)
{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), 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.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera
Audio
FM radio
WLAN and USB tethering
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8504, https://github.com/lenovo-devs/android_device_lenovo_tb-common/tree/lineage-16.0-msm8937
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo/tree/lineage-16.0-msm8937
2020-03-19
Fixed USB flash mounting when using OTG
mailru: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
Previous versions:
2020-03-13
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
mailru: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
2020-03-04
first release
mailru: lineage-16.0-20200304-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200304-UNOFFICIAL-TB8504.zip
How to install
You have to had TWRP installed from this thread TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F or one from link below
In TWRP clean Data if you coming from stock ROM and do Install of this ROM. If you have android 8 stock rom installed you have to format Data with data loss, because used encryption is incompatible with android 7.1
TWRP
Built from omnirom android 9.0 source (twrp 3.3.1), includes same kernel as Lineage build, with support for pstore (kernel logs after crash), exfat, ntfs, reboot to EDL mode.
mailru: twrp-3.3.1-1-TB8504.img
gdrive: twrp-3.3.1-1-TB8504.img
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8504f/x] LineageOS 16.0 for Lenovo TAB4 8, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2020-03-04
Last Updated 2020-03-19
hero - thank you
Can this be installed on my 8704v?
jcthrower said:
Can this be installed on my 8704v?
Click to expand...
Click to collapse
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
highwaystar_ru said:
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
Click to expand...
Click to collapse
ok thanks for the response. Are you still planning on updating Lineage 16.1 for the 8704v?
Thank you so much for that rom, I'll be trying to flash it next week!
I have question - is there any possibility to get working stock Dolby atmos which is different from that one we can find in other threads
Or
You prefer Viper4android?
Edit: does Netflix work fluently?
Thanks a lot!
Installation went smooth, so far everything seems to be working.
Still need to set up the tab, but I'm glad I finally got rid of the Lenovo bloatware (like kidoz).
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
Update:
2020-03-19
Fixed USB flash drives mounting connected by OTG
Lucinde said:
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
Click to expand...
Click to collapse
If anyone else would have the same question: I found a workaround. You can create a new user via adb with the command "adb shell pm create-user --restricted <username>".
I didn't find a way to create the restricted profile from the settings menu, but once created, it can be managed via the menu.
In the meantime I installed some apps and so far, so good. From the limited time I worked with it, it seems to run smoother than with the stock ROM :good:
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
Managed to install Lineage on my TB-8504F, but it doesnt get past the Lineage boot animation, no matter how long I leave it.
Pushed TWRP to Recovery, formatted as required. Had to amend the Lineage image to remove the device checks, as although I definately have TB-8504F, it didnt like that TWRP reported it as TB_8504f - ?
Installed and installed GAPPS, cant get past load screen.
I do have a backup, so not concerned, but frustrated!
Any help appreciated
BigBrother84 said:
Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
Click to expand...
Click to collapse
Sorry it took me so long to see this, but I had similar problems as you initially. It turns out you actually have to install TWRP to the tablet for it to mount /system properly, booting into it from fastboot doesn't work for some reason - that was what fixed it for me at least. It may be different for your device but I had to run the flash recovery command twice for it to stick..
Also want to say thanks to highwaystar_ru, the past few builds have been running great
Slack3r said:
It turns out you actually have to install TWRP to the tablet for it to mount /system properly
Click to expand...
Click to collapse
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!
BigBrother84 said:
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!
Click to expand...
Click to collapse
Yep, you'd need to flash TWRP via that fastboot command and boot to recovery by holding vol up/power. I put the ROM and gapps files on a MicroSD card which was picked up by TWRP.
I had similar problems with the ROM not being compatible after the first failed flash, you should be able to modify the updater-script file located at META-INF\com\google\android to include "tb_8504" as a compatible device. I didn't test this method however, as I reflashed the stock image which combined with installing TWRP on the device solved my issues.
If you need to, the full stock image can be flashed using QFIL and the instructions from here, but I'd recommend trying to restore the backup posted by Plant as the QFIL method can take some time to get figured out. I'm not sure how this compares to MiFlash but that would likely produce the same results.
Hope this helps!
screen rotation
Does anybody have problem with auto rotation for screen? In mine TB-8504F it doesn't work. Installed some apps which are testing sensors and none sensor responsible for screen rotation is vsible after flashing this system.
---------- Post added at 04:43 AM ---------- Previous post was at 04:24 AM ----------
If you will brick your device as me you can always use Qualcomm Flash Image Loader (QFIL) with proper files for your device. Note for mine works QFIL v2.0.0.1. Newer versions won't work with my device. It will load stock android 7 then under TWRP you can wipe and flash Lineageos. Firstly was bricked while was going from And 8.0 and not flashed but only booted TWRP. As mentioned above need to flash TWRP
I tried restoring the backup, but after I tried booting into system I got a black screen I can't fix. Power buttons don't work, I can't boot into recovery / anything else. No logos or text. It's like the battery is dead, but I can't power it on. Tried charging it, because the battery was around 10% when I tried restoring the backup, but I don't think that will help. Any other ideas? I think I lost this device for good.
Hi,
After coming from stock 8.0, I’ve got everything up and running which appears to run great.
However, I am struggling to get my PS4 controller working.
It will connect fine via Bluetooth, but no input is detected.
Any ideas?
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* 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! 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Read Guidance carefully, Or you will fail at flashing.
The LineageOS 18.1 is based on stock Android 10 this time, Make sure you are running stock Android 10 before flashing this ROM !!!!!!
Important Information
1 You need to flash Stock Android 10 before flashing this ROM.
2. For VoLTE, you might need to boot into stock firmware and enable it before flashing this ROM!
Downloads Links
LineageOS 18.1:
Unofficial-build: Link
Google Applications (optional):
OpenGapps: http://opengapps.org/ (ARM64->Android 11.0->Pico, Nano or Micro)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Moto
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Download Lineage Recovery: AFH
3. Put your device into fastboot mode
4. Type the following command to flash the recovery:
Code:
fastboot flash recovery recovery.img
5. Enter fastbootd:
Code:
fastboot reboot fastboot
6. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash:raw boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
7. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
Gapps:
After flashed images in fastbootd, choose Enter recovery - Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-18.1 for Moto G8/G Fast, ROM for the Moto G8/G Fast
Contributors
Sjll
Source Code:
GitHub - sjllls/android_kernel_motorola_sm6125
Contribute to sjllls/android_kernel_motorola_sm6125 development by creating an account on GitHub.
github.com
GitHub - sjllls/android_device_motorola_rav
Contribute to sjllls/android_device_motorola_rav development by creating an account on GitHub.
github.com
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
Version Information
Status: Stable
Created 2021-01-26
Last Updated 2021-01-27
FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce
Sjll said:
- FM Radio: NA
Click to expand...
Click to collapse
Is it not possible to use the FM radio on custom ROMs?
Tried flashing this tonight but got stuck on:
fastboot flash system system.img
Getting this error " (bootloader) Invalid partition name system" Apparently the system partition doesn't exist on my phone (XT2045-3)
Similar error occurs with product partition.
The Super partition does and I tried to flash to that but the phone immediately booted into fastboot.
Anyone have an idea?
I just finished flashing and everything is working good, i had lost my wifi connection on a custom rom about two moths ago, it only worked with stock rom. this fixed it, anyways, the screen might be broken? notifications show under notch, also when i was trying to flash gapps, it kept giving error for wrong android version, i booted up again, checked the device info and apparently im running on android 11, so had tho get gapps 11 from cynanogen. magisk installed correctly also gapps, im gonna test it tonight see how it goes.
mbrewski said:
Tried flashing this tonight but got stuck on:
fastboot flash system system.img
Getting this error " (bootloader) Invalid partition name system" Apparently the system partition doesn't exist on my phone (XT2045-3)
Similar error occurs with product partition.
The Super partition does and I tried to flash to that but the phone immediately booted into fastboot.
Anyone have an idea?
Click to expand...
Click to collapse
so something like this happened to me, but it my error said: not enough space to resize partition... something like it, while trying to flash the system img, here is what i did, got the error, skipped system, flashed product, went back and flash system img. continued with the command list, and booted right up.
Thanks for the tip! It worked like a charm.
Csrtek said:
so something like this happened to me, but it my error said: not enough space to resize partition... something like it, while trying to flash the system img, here is what i did, got the error, skipped system, flashed product, went back and flash system img. continued with the command list, and booted right up.
Click to expand...
Click to collapse
Csrtek said:
also when i was trying to flash gapps, it kept giving error for wrong android version, i booted up again, checked the device info and apparently im running on android 11, so had tho get gapps 11 from cynanogen. magisk installed correctly also gapps, im gonna test it tonight see how it goes.
Click to expand...
Click to collapse
NikGapps-core-arm64-11-20210124-signed.zip
ffff2 said:
Is it not possible to use the FM radio on custom ROMs?
Click to expand...
Click to collapse
Do we have it on stock?
mbrewski said:
Tried flashing this tonight but got stuck on:
fastboot flash system system.img
Getting this error " (bootloader) Invalid partition name system" Apparently the system partition doesn't exist on my phone (XT2045-3)
Anyone have an idea?
Click to expand...
Click to collapse
Read OPs carefully, FastbootD mode.
Sjll said:
Do we have it on stock?
Click to expand...
Click to collapse
Yeah I had it on stock eu version, but I haven't seen it on any custom ROMs
Is there a command to fix the screen overlay? Notifications and carrier label show under the notch/front camera, I tried the command listed on other threads but doesn't work. Its the only problem I've encountered so far.
Csrtek said:
Is there a command to fix the screen overlay? Notifications and carrier label show under the notch/front camera, I tried the command listed on other threads but doesn't work. Its the only problem I've encountered so far.
Click to expand...
Click to collapse
Because I didn't build the overlay. I will consider about it.
ffff2 said:
Yeah I had it on stock eu version, but I haven't seen it on any custom ROMs
Click to expand...
Click to collapse
I will check it.
Will this work on the moto g stylus - us version.?
MaxyPanther said:
Will this work on the moto g stylus - us version.?
Click to expand...
Click to collapse
It should.
What about Moto g8 Power?
TheOnlyRealChosenOne said:
What about Moto g8 Power?
Click to expand...
Click to collapse
The odds of it working are fairly high because we both have the same gpu and chipset. I would expect a bootloop at worst. Give it a go and let us know!
MaxyPanther said:
Will this work on the moto g stylus - us version.?
Click to expand...
Click to collapse
TheOnlyRealChosenOne said:
What about Moto g8 Power?
Click to expand...
Click to collapse
Some kernel modules of other Moto sm6125 devices are not included, so some hardware doesn't work.
Csrtek said:
Is there a command to fix the screen overlay? Notifications and carrier label show under the notch/front camera, I tried the command listed on other threads but doesn't work. Its the only problem I've encountered so far.
Click to expand...
Click to collapse
Look for the Display Cutout option in Developer Options. I have that on my G7, and my G6 which doesn't even have a cutout, so I assume it's in all models.
MaxyPanther said:
Will this work on the moto g stylus - us version.?
Click to expand...
Click to collapse
Sjll said:
Some kernel modules of other Moto sm6125 devices are not included, so some hardware doesn't work.
Click to expand...
Click to collapse
Can you provide any more detail on what would be missing on the Stylus, and if support will be added for those things in this LOS rom, or if it'll take someone creating a Stylus based LOS rom for better support?
Okay, now I'm a little confused. I just flashed my stock moto g with the 20210127 build. Didn't run into any trouble except the resize error Csrtek described above, and solved it the same way (flash product partition first). Didn't try to load the gapps at the time (they were too big to download over LTE).
Now I'd like to install the gapps, but there is no Android 11 version on the opengapps.org site linked above, although the instructions say to use them. I tried the Android 10 version, but the installer chokes when I try to sideload them.
So, are version 11 gapps available yet? Or am I missing something? Do I need to downgrade back to stock version 10, then reflash Lineage, then sideload the version 10 gapps before booting? I would have tried it, but none of the stock images are available right now.
Thanks for doing this port, Sjll! And the overlay would be nice if you can do it! ;-)
Guru Meditation No. 42 said:
Okay, now I'm a little confused. I just flashed my stock moto g with the 20210127 build. Didn't run into any trouble except the resize error Csrtek described above, and solved it the same way (flash product partition first). Didn't try to load the gapps at the time (they were too big to download over LTE).
Now I'd like to install the gapps, but there is no Android 11 version on the opengapps.org site linked above, although the instructions say to use them. I tried the Android 10 version, but the installer chokes when I try to sideload them.
So, are version 11 gapps available yet? Or am I missing something? Do I need to downgrade back to stock version 10, then reflash Lineage, then sideload the version 10 gapps before booting? I would have tried it, but none of the stock images are available right now.
Thanks for doing this port, Sjll! And the overlay would be nice if you can do it! ;-)
Click to expand...
Click to collapse
I think you want Nik 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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH(for first install) :1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
CherishOS for OnePlus 8T
Device: kebab
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Reserved
Amsal1 said:
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Click to expand...
Click to collapse
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Zekedw said:
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Click to expand...
Click to collapse
The main thing you need to know for this device regarding A/B is that you need to have the latest firmware from Oneplus on both slots.
Run all your updates and then find the Lineage Wiki for kebab. There is a script there that will copy firmware to both slots so you can start flashing ROMs.
Zekedw said:
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Click to expand...
Click to collapse
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
kjslabber said:
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
Click to expand...
Click to collapse
I have actually repaired it from a boot loop many times. I've been modding and flashing for many years. It's just that this is my first a/b device and despite all the tutorials and research I've done it still hasn't worked. I'm not giving up tho, just wondering what I'm missing. I actually did get a couple roms to work. But I don't know why I'm not getting them to work now. More research I guess...
double tap to wake works while aod is on?
I have many problems trying to install these roms on my phone using sideload or twrp no matter what recovery I use. End up dumping files from payload bin and flashing individual files using fastbootd. Only handful of files to flash, not like oos rom. Almost foolproof. Just make sure you reboot to recovery and format data before booting to system.
GbnrVR said:
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Click to expand...
Click to collapse
No. I mistakenly wrote face unlock in a hurry which is removed from OP now
kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Yes. That is because A12 latest standards uses a different assert verification process (which is used to detect the device before loading packages into the recovery). TWRP and old recoveries are still using old asserts from A11 standards. I don't like to implement the old assert thus you can either flash using any fastboot installer script or fastboot enhanced. One tester confirmed me that lineage recovery also worked fine for him but I still recommend fastboot installer mode.
Muntasir Mahmud Saif said:
double tap to wake works while aod is on?
Click to expand...
Click to collapse
Yes.
Ivanherrero said:
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Click to expand...
Click to collapse
Have you tried changing monet colour through Cherish Settings->Themes->Custom Color?
Can you give more details, since I can't reproduce the issue and many of my testers have tested it for days and have no issues with changing monet colours.
Amsal1 said:
Yes.
Click to expand...
Click to collapse
can not find any payload.bin in the folders after extracting
All you need to do is change wallpaper. Color is controlled by wallpaper theme in a12.
Muntasir Mahmud Saif said:
can not find any payload.bin in the folders after extracting
Click to expand...
Click to collapse
Did you download the zip file or md5?
i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
this is the GSI img file that nned to flashed am i correct?
{
"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"
}
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse
GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.
up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn
viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net
iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps
downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)
wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?
This guide worked, thank you so much!
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.
TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix