[RECOVERY]TWRP BETA 1 - Sony Xperia M

Hello There!
I am here with a good news and a bad news!
The good news is that I have sucessfully compiled TWRP recovery for our beloved Xperia M!
The bad news is that It is unstable, and I am not able to make it stable. I need help from some developers in order to make it stable.
Please note that this kernel bringup is only for CM11 FXP310.So, dont try it on other ROMs, as your may get into a serious problem after that.
Please bear with me, as I am a noob and will need a lot of help in making this stable for use!
Sources :
The TWRP sources can be found here : https://github.com/omnirom/android_bootable_recovery
The device tree of rebelos(contains commits for TWRP bringup, thanks to him for letting me use the tree) : https://github.com/rebelos/android_device_sony_nicki
The Kernel sources used : https://github.com/freexperia/android_Kernel_sony_msm8x27
Working /Not working
Working :
Normal Touch
Navigation
And Basic operations
Not - Working
Some glitches (sometimes) [that is, the half screen problem]
Screenshots(again, thanks to Bonoboo)
{
"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"
}
Downloads
New flashable zip(thanks to Bonoboo) : https://www.mediafire.com/?gg84xysk8w64fwc
OLD[not recommended for use] :
boot.img
recovery.img ( I am having problems installing this, via fastboot. Use boot.img)
Changelogs
16-03-2014
Initial Release
17-03-2014
fixed up the bugs in main ROM. i.e, the wifi and RIL bugs.
Credits :
PecanCM - For sources
FXP, for supporting this device officially
rebelos for allowing me to use his updated commits in device tree. His device tree can be found on his github.
Bonoboo for giving the idea of packing the ramdisk(the partition with recovery and the boot.img) and for packing it up for me!
A note : I need help from you all to achieve this task Please help me up.
XDA:DevDB Information
[RECOVERY] TWRP, a Tool/Utility for the Sony Xperia M
Contributors
PixCM
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2014-03-17
Created 2014-03-16
Last Updated 2014-03-18

lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues

rebelos said:
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
Click to expand...
Click to collapse
Thank You soo much Will compile and post in an hour or so! Got to do something else at the moment
Tried.. But they didnt help :/ Same bugs!

Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off

Best Recovery Shown up!
TWRP just the best recovery ever... my fav.
hope this can be fixed soon... thanks for the good job

Good work bro...
Sent from my C1905 using XDA Premium 4 mobile app

Thanks mate for TWRP recovery! Always used this on my GT-I9100
Wating for an update
Sent from my C1905 using Tapatalk

Bonoboo said:
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
About screenshots.
Please hide them under spoiler – thread very lagre with them now.
Here flashable ZIP with original FXP310 kernel and this recovery.
Click to expand...
Click to collapse
Thanks dude! I will give you another build, check if the mount is working in this one!
Check your PM.

SUM ONE SAY TWRPDDDDDD goddamn, i want try it, but after the bug like wifi-RIL etc fixed

PixCM said:
Thanks dude! I will give you another build, check if the mount is working in this one! .
Click to expand...
Click to collapse
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Richardsentosa said:
i want try it, but after the bug like wifi-RIL etc fixed
Click to expand...
Click to collapse
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).

Bonoboo said:
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Click to expand...
Click to collapse
but now i using HellKat .-.

Updated
Updated OP with new build.
Download : https://www.mediafire.com/?gg84xysk8w64fwc
Special thanks to @Bonoboo for this

@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.

Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.

PixCM said:
I will release it in both the forms.
Click to expand...
Click to collapse
Yes, this will be nice and more flexible: someone can manually add recovery in beloved kernel and CM11 users can directly flash it.
PixCM said:
And, will you become my tester?
Click to expand...
Click to collapse
Recovery – yes, but not ROM, sorry.

PixCM said:
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
Click to expand...
Click to collapse
OmniROM with TWRP recovery is brilliant mate! Hope you will release it
Sent from my C1905 using Tapatalk

a new build? i will try it (if i flashed the FXP CM11)

Richardsentosa said:
a new build?
Click to expand...
Click to collapse
Yep, CM11 FXP311 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.

Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
+1 lol... you just wrote what i want to...
now it's being clear...
coz i need to replace the whole cwm from every Roms i've downloaded... yeah... keep it rolling dude :good:

CM11 FXP312 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.

Related

[Kernel][Mokee]CM11 kernel repack for mokee

As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.​
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
{
"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"
}
thnx to the help from
kapil.git
Thanks for the Wake Up!!
saurabhrck said:
As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.​
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
thnx to the help from
kapil.git
Click to expand...
Click to collapse
deadlyindian said:
Thanks for the Wake Up!!
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
SuperDroid-BOND said:
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
saurabhrck said:
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
Click to expand...
Click to collapse
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
SuperDroid-BOND said:
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
Click to expand...
Click to collapse
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
saurabhrck said:
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
Click to expand...
Click to collapse
so is it repack of old ramdisk and new zimage... btw can u please give me link/info about the tool which u have used to repack kernel.. i tried to make kernel unsecure once but cant make it boot... kernel size reduced ~4 mb....
deadlyindian said:
Thanks for the Wake Up!!
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
pgreed said:
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
Nope its automatically set when phone boots...
What are the features of the kernel? This for mokee only? Any version??
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small and after app is launched phone reboot.
Click to expand...
Click to collapse
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
saurabhrck said:
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
Click to expand...
Click to collapse
No it use the 8 May kernel! (is the sychost unofficial)
Shahi00 said:
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
Click to expand...
Click to collapse
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Shahan_mik3 said:
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Click to expand...
Click to collapse
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 don't have ZRAM and V41.1 and above have it...that's the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
Click to expand...
Click to collapse
link for mokee unofficial plz..
RohanAJoshi said:
link for mokee unofficial plz..
Click to expand...
Click to collapse
Because from Mokee site was deleted all unofficial and experimental version (I dunno why) I've upload the file elsewhere:
Shahi00 said:
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 dont have ZRAM and V41.1 and above have it...thats the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
Click to expand...
Click to collapse
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Shahan_mik3 said:
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Click to expand...
Click to collapse
Our developer is good enough for tracking bugs that causes Random Reboots !!
Kra always did that (on previous phone too)
:good:

[ROM][5.1.1][Endeavoru UNOFFICIAL]OMNI ROM[RRO 3.1]

{
"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"
}
Omni is a community-based project for the Android community which is Free: Free to Use, Free to Modify, Free to Share. It's also about options, which is the beauty of Android. Omni 5.1 is based on Android Lollipop.​
Wiki;
=================
http://docs.omnirom.org/Main_Page
Sources:
=================
http://github.com/omnirom
Gerrit:
=================
https://gerrit.omnirom.org/
Bugtracker:
=================
http://jira.omnirom.org
IRC:
=================
irc.freenode.net #omnirom
Be Advised:
=================
- Root access is not included by default as of yet. Please flash SuperSU for root (See below).
- This is a beta build. Bugs are to be expected.
- Feel free to leave your bug reports in this thread or on the bugtracker.
Installation Instructions:
=================
- Copy GApps and the OmniROM zip to your internal SDCard
- Make sure you're running a proper and working custom recovery such as TWRP(New Layout).
- Boot into Recovery
- Flash OmniROM zip from internal SDCard
-Flash the boot.img using "fastboot flash boot boot.img"
- Flash GApps zip from internal SDCard (Optional)
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
Downloads:
Gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps
SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Source code:
=================
OmniROM source: https://github.com/Omni-rro
Device Tree:https://github.com/onexmaster/omni_device_htc_endeavour
A huge thanks as always to @audahadi for the original device trees and support!
XDA:DevDB Information
OmniROM 5.1, ROM for the HTC One X
Contributors @onex master @teemo
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
=================
DOWNLOADS
ROM(first build)
ROM(second build)
ROM(Third build)(Includes RRO Support)
ROM(fourth build)
=================
Extra Information
What is RRO
RRO Projects
thank you very much will give try please keep it up
Yessss. HOX will never die
Thanks for doing this!
teemo said:
Yessss. HOX will never die
Thanks for doing this!
Click to expand...
Click to collapse
hi im using it now it going well but needs some more features cause it very poor thanks
hassoly said:
hi im using it now it going well but needs some more features cause it very poor thanks
Click to expand...
Click to collapse
Yes I know ..there are not many features ...will try to add them in next build
thank you its working smooth
Have used it for 3 days, it is stable, smooth, runs well.keep your good work bro.
Sent from my One X using XDA Free mobile app
New build up
No major changes .. Just fixed some bugs and added some features
Will try to add RRO 2.1 in the next build
hey guys, asking for a bit of advice here; my nexus 6 broke so I'm back to the Htc One x; I haven't flashed anything on it since a long time so I'm unsure about what I need to do..
right now I have cwm touch 5.8.4.0 and I would like to install twrp and this rom
So I think the steps I need to follow are:
1 install twrp from the one x toolkit
2 install the rom
3 flash the boot.img
are there any other things needed? i don't know like the hboot number or anything that may brick the phone?
thanks in advance!
gol-D said:
hey guys, asking for a bit of advice here; my nexus 6 broke so I'm back to the Htc One x; I haven't flashed anything on it since a long time so I'm unsure about what I need to do..
right now I have cwm touch 5.8.4.0 and I would like to install twrp and this rom
So I think the steps I need to follow are:
1 install twrp from the one x toolkit
2 install the rom
3 flash the boot.img
are there any other things needed? i don't know like the hboot number or anything that may brick the phone?
thanks in advance!
Click to expand...
Click to collapse
Yes you are partially right ...here follow this
You need twrp new layout for hox ..all the info about that can be found out here
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
"Read carefully there and follow each and every step there"
then you can follow the steps like flashing the rom and the boot.img
hassoly said:
thank you its working smooth
Click to expand...
Click to collapse
Namautoenx said:
Have used it for 3 days, it is stable, smooth, runs well.keep your good work bro.
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
Thanks dude for your information :good: , really help me to know this rom .
onex master said:
New build up
No major changes .. Just fixed some bugs and added some features
Will try to add RRO 2.1 in the next build
Click to expand...
Click to collapse
Thanks a ton Dev @onex master, I will taste it.
broim kaskus said:
Thanks dude for your information :good: , really help me to know this rom .
Thanks a ton Dev @onex master, I will taste it.
Click to expand...
Click to collapse
If you could wait for a few more hours..you will a get a new build to download ..I am just compiling a new build will upload in a few hours
unfortunately this will also not contain rro support ...coz I am getting broken repos while building with rro repos ..will try a fix soon
onex master said:
If you could wait for a few more hours..you will a get a new build to download ..I am just compiling a new build will upload in a few hours
unfortunately this will also not contain rro support ...coz I am getting broken repos while building with rro repos ..will try a fix soon
Click to expand...
Click to collapse
Oh my GOD, thank you so much Dev. I just downloaded it, but no matter for waiting your final rom. I'll check again tomorrow Dev.
New build up
Added rro layers support
Enjoy
I already flashed this ROM, and it's cool. I hope someday Dev @onex master will add sense 7 into this rom :good:
Okay, I will taste this great ROM for someday, and I'm gonna tell you if I face some troubles.
Thanks a ton Dev.
Last edited by broim kaskus; Today at 01:02 PM.
============================================
NOW My Hox is looking perfectly with full Sense 7 and Blink Feed :good:
Thank you for @Shaumaaa for useful information about link sense 7.
broim kaskus said:
I already flashed this ROM, and it's cool. I hope someday Dev @onex master will add sense 7 into this rom :good:
Okay, I will taste this great ROM for someday, and I'm gonna tell you if I face some troubles.
Thanks a ton Dev.
Click to expand...
Click to collapse
If you want Sense 7, here it is: http://forum.xda-developers.com/android/apps-games/htc-blinkfeed-plugins-devices-08-03-2015-t3049438
Install it like a regular app.
New build up
updated with omni rom's latest sources
will build next build with uber toolchanin and add features like 3 finger swipe to take screenshot
Enjoy
Hi, I've been using the rom for a while now...
I've got some problems tho with playing video's in apps / and sometimes alot of stuttering and delay with the browser.
I must say that everything works but it is pretty slow tho...
Oh and my wifi settings aren't sticking, each time I shut down wifi I'll have to re-enter my wifi pass... Which is rather annoying...
hi i think you build Tesla-endeavoru-5.1.1 i try the 3 roms but its not booting clean flash .... is it new or old layout thanks for all the work you do.
hassoly said:
hi i think you build Tesla-endeavoru-5.1.1 i try the 3 roms but its not booting clean flash .... is it new or old layout thanks for all the work you do.
Click to expand...
Click to collapse
it is for new layout ..and yes its not booting ...I have to figure it out ....

[ROM][UNOFFICIAL][6.0.1][02/28] OmniROM

{
"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"
}
DISCLAIMER
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! 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.
DOWNLOADS
ROM - 02/27/2015
Recovery
OLD (5.1.1)
ROM - 11/18/2015
TWRP (for Updated TA)
boot.img with TWRP
BUGS
Buggy camera
Test and report back
SOURCE CODE
Kernel
Device Tree
Rhine Board Tree
CREDIT
erikcas - Developing and building this ROM
jerpelea
OmniROM Dev team
FXP Dev team
etc
XDA:DevDB Information
OmniROM, ROM for the Sony Xperia Z1
Contributors
zhuoyang, erikcas
Source Code: https://github.com/erikcas?tab=repositories
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2015-11-20
Last Updated 2016-02-28
Reserved
beware, the camera is an (partly) opensource development preview solution.
That is the "bad" news.
The good news is that we never had an opensource solution before this. Except a hacky closed source solution.
It can only get better from here
erikcas said:
beware, the camera is an (partly) opensource development preview solution.
That is the "bad" news.
The good news is that we never had an opensource solution before this. Except a hacky closed source solution.
It can only get better from here
Click to expand...
Click to collapse
Guys. Your TWRP won't have brightness control, which results in overheating. You need to change max brightness from 4095 to 255 in rhine omniboardconfig. This was merged by Slimroms in August...
optimumpro said:
Guys. Your TWRP won't have brightness control, which results in overheating. You need to change max brightness from 4095 to 255 in rhine omniboardconfig. This was merged by Slimroms in August...
Click to expand...
Click to collapse
Thanx for reporting. I have no ability to test on honami, I will make this device specific instead of platform specific.
edit: see here and here
Thanx again
erikcas said:
Thanx for reporting. I have no ability to test on honami, I will make this device specific instead of platform specific.
Click to expand...
Click to collapse
The brightness value is the same for all rhine devices...
By the way: Does Omnirom have Layers?
optimumpro said:
The brightness value is the same for all rhine devices...
By the way: Does Omnirom have Layers?
Click to expand...
Click to collapse
tested 255 earlier on amami a while ago as I read about this issue before. And that was no good. I couldn't see anything on my screen in daylight. Besides from that, I have no heating issues in twrp. I.e. I leave twrp asap always, as I hate to carry around a device in recovery mode all day. It drops too many functionalities for my phone I use it for, like mobile networking.
So, as I am in twrp for not more then 5 minutes I think it is impossible for it to overheat. And I think the auto dimming of the screen after a minute of inactivity also prevents overheating
can you be specific about layers, it can mean multiple things. And I remember you asking this somewhere else before
edit ph***, the brightness remark made me review my notes I have to retest that on amami, it maybe a case of a screwup with yukon M2 here. Anyway, good to bring this to attention
erikcas said:
tested 255 earlier on amami a while ago as I read about this issue before. And that was no good. I couldn't see anything on my screen in daylight. Besides from that, I have no heating issues in twrp. I.e. I leave twrp asap always, as I hate to carry around a device in recovery mode all day. It drops too many functionalities for my phone I use it for, like mobile networking.
So, as I am in twrp for not more then 5 minutes I think it is impossible for it to overheat. And I think the auto dimming of the screen after a minute of inactivity also prevents overheating
can you be specific about layers, it can mean multiple things. And I remember you asking this somewhere else before
Click to expand...
Click to collapse
Layers as a theme engine. If I asked before, I would know the answer.
Could you build a clean aosp as well please?
Sent from my Xperia Z1 using XDA Forums
optimumpro said:
Layers as a theme engine. If I asked before, I would know the answer.
Click to expand...
Click to collapse
http://forum.xda-developers.com/omni/development/planning-theme-t3096423
tadeas482 said:
Could you build a clean aosp as well please?
yes, will be done this weekend
Sent from my Xperia Z1 using XDA Forums
Click to expand...
Click to collapse
Just flashed and started Manual camera compatibility test app from playstore,and it showed that our device now supports all manual settings,even raw support.
Had it flashed, it felt awesomely smooth, fast s hell, booted in a few seconds... Camera was a said in op.. I just lost root and recovery so had to reflash kernel with recovery... Otherwise hell of a job with the ROM... thank you
what are the features included in this ROM?
caki25 said:
Had it flashed, it felt awesomely smooth, fast s hell, booted in a few seconds... Camera was a said in op.. I just lost root and recovery so had to reflash kernel with recovery... Otherwise hell of a job with the ROM... thank you
Click to expand...
Click to collapse
I'm hot booting recovery at the moment. What kernel did you use . I don't want a 3.4 kernel again .
Rashr. Is pushing recovery to fota partition but ROM/kernel does not seem able to use it .
Another 3.10 kernel that doesn't seem to work with my device. I must mention that I have an aftermarket display. It would be great if the ROM had a recovery, so that I could post the last kmesg. @erikcas
LSD DREAMER said:
I'm hot booting recovery at the moment. What kernel did you use . I don't want a 3.4 kernel again .
Rashr. Is pushing recovery to fota partition but ROM/kernel does not seem able to use it .
Click to expand...
Click to collapse
I changed the kernel to get restore a backup... But I will definitely try again later. Agreed with the recovery, I tried optimumpro's fota recovery, but was not able to boot into it.
drakonizer said:
Another 3.10 kernel that doesn't seem to work with my device. I must mention that I have an aftermarket display. It would be great if the ROM had a recovery, so that I could post the last kmesg. @erikcas
Click to expand...
Click to collapse
Can you upload a dmesg from stock?
As early as possible from boot.
If you have an aftermarket display that works on stock, the display has to be defined in the stock kernel to. I need to see how it is inited on stock rom. If it is I will find it and make it work (oops.. no guaranty offcourse, but will do my outmost)
edit: recovery will be up in 20 minutes in this post
edit 2: download honami TWRP here (should be working, but not able to test...)
Verstuurd vanaf mijn E6653 met Tapatalk
LSD DREAMER said:
I'm hot booting recovery at the moment. What kernel did you use . I don't want a 3.4 kernel again .
Rashr. Is pushing recovery to fota partition but ROM/kernel does not seem able to use it .
Click to expand...
Click to collapse
the kernel has not compiled the recovery "incompiled". I use updated TA partition for opendevices which allows a permanent recovery to be flashed to a "real" recovery partition, which you can enter (after updating TA and flash recovery) by powerup device by <voldown> + <power> keys at the same time when device is turned off.
wow really good rom. Just a few things:
- green videos were even on 5.1? I thought that it was caused by 6.0. Never mind, can you use new adreno binaries in next build (maybe there are some for 5.1, but it's worth try https://github.com/alviteri/vendor-sony-blobs/commit/11f24412c2e3b4b5531f2fa061fc2a0576933d2a )? Now I'm trying to push them to my phone and I'll see if it fix that
- some graphics glitches were present after first boot but they're gone, so I don't mind it
- camera is "somehow" working, but as OP mentions it isn't usable and it making weird sound on camera init (I should better not use the camera, I don't want to break it )
- superb freq scaling - my phone heats I think even less then on tweaked stock
edit: Also I used nut's ramdisk recovery and it's working link: http://nut.xperia-files.com/?ql=89140980648c1ad31bad3aa52f38245a2ef3c5a7
edit2: okay, do not flash this, in recovery there is no screen, it just vibrates and I can't restart my phone even with red button. (I have to wait till it die )
OK, @erikcas thank you
erikcas said:
Can you upload a dmesg from stock?
As early as possible from boot.
If you have an aftermarket display that works on stock, the display has to be defined in the stock kernel to. I need to see how it is inited on stock rom. If it is I will find it and make it work (oops.. no guaranty offcourse, but will do my outmost)
edit: recovery will be up in 20 minutes in this post
edit 2: download honami TWRP here (should be working, but not able to test...)
Verstuurd vanaf mijn E6653 met Tapatalk
Click to expand...
Click to collapse
THANK YOU!
I will post the dmesg as soon as possible.
As for the recovery, will it work in this ROM if I flash it to FOTA partition? I have a C6902 so there is no way I can get the updated bootloader for using an actual recovery partition
EDIT: dmesg attached. The adb shell command resulted in 0kb logs so I had to use Syslog, so that might have resulted in a few seconds of delay in capturing the log. Hope it helps!

[rom-port-patch][7.1.1]RR v5.8[N] for a7000

RR v5.8..0 N WITH JAN 7 SECURITY PATCH
{
"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"
}
About Resurrection Remix ROM​Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters​
ABOUT THIS PROJECT​
Rather that the usual ready to flash port rom,today am here with a change.in fact i was forced to do this.so first of all sorry if the title misguided you
this time am up with a patch so that you can flash the RR v5.8.0(N) rom made for k3 note/a7000 plus/p70 directly to out device
NOTE:this method may work out on a few other MM/N(based on mm libs and kernel) you may try and verify it yourself @ your own risk.please let me know if u successfully boot any other roms
UPDATE: source compiled k3 note Nougat roms with system in system.new.dat format wont get flashed on our device directly,you will need to manually extract it(use superr kitchen or some other alternatives) and try​
FLASHING PROCEDURE[MUST READ]​
many of you will be enough and more experienced in flashing roms but to boot this rom,follow the method below or else it wont boot in majority of the cases.flash try this at your own risk,please dont do this in case you are not sure about what you are actually doing
step 1:download a sutiable rom.this time lets try with RR v8.5 Nougat
link:here
[all respect&credits to rom developer and his team,please dont spam his post asking about this patch just download
rom from the link and continue reading this thread]
step 2:reboot to recovery do a advanced wipe as usual[data/dalvic/cache/system]
step 3:go flash the rom directly
step 4:flash kernel for a7000
link:here
step 5:reboot to system
step 6:wait for 5+ minutes with bootanimation[imp]
step 7:do a manual reboot to recovery
step 8:mount system and flash the patch(links below)
step 9:reboot to system and see the rom boots and works flawlessly
step 10: once rom booted successfully change display size through setting or using build.prop editor
set lcd density to 320(default)
step 11:thats it you are good to go
note:do not do a reset cause you will have to do all the above steps once again if data is lost!
BUGS​
Nothing major however be ready to face few which i might havent noticed.i didnt promise a stable rom with this method
[jio works:set 4g lte only+barer=lte it will work]​
A FEW FINAL WORDS​
*dont go and spam the threads made for k3 note asking about this patch.they have made the rom for k3 and hence wont have any idea regarding this patch
*neither me nor the developer of rom will have no responsibilities in case you bricked your device
*its my final port-project for a7000 and hence dont expect any updates.however i *may work on kernels and base that too when i have enough and more free time
*after all thanks to all who supported me and my works till date
HAVE A HAPPY FLASHING GUYS:highfive:
LINK[PATCH]:HERE
DONATIONS​like my work?any donations could be made here(paytm)
barcode
*sadly i havent earn any money from any of my works till date :crying:
*Eventhough you couldnt donate please be kind enough to hit the thanks button to encourage me.thats my only benifit from this :good::good:
REGARDS:
ASWIN PRADEEP
XDA:DevDB Information
[rom-port-patch][7.1.1]RR v5.8[N] for a7000, ROM for the Lenovo A7000
Contributors
aswinp222
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2017-02-03
Last Updated 2017-02-04
Reserved
proof screenshots of booting RR v8.5.0 is given below
reserved
Guys, if you don't want to set screen size manually after booting, here is a zip for you.
https://drive.google.com/file/d/0BxkDSj8MtdPQRmtzTnVfN2t4eDQ/view?usp=sharing
It also changes some values to make it more compatible with A7000, rather than keeping the default values from ME note.
I used this zip myself and I assure you it works as it should.
@aswinp222 Please edit your installation instructions to ask users to download this patch too. If possible, please don't copy paste the link.
Nice ROM bro.:laugh::good:
Edit : @aswinp222 I just discovered a glitch in RR. This build prop fix is compulsory to fix it. Can't be fixed by native nougat DPI feature.
tanish2k09 said:
Guys, if you don't want to set screen size manually after booting, here is a zip for you.
https://drive.google.com/file/d/0BxkDSj8MtdPQRmtzTnVfN2t4eDQ/view?usp=sharing
I used this zip myself and I assure you it works as it should.
@aswinp222 Please edit your installation instructions to ask users to download this patch too. If possible, please don't copy paste the link.
Nice ROM bro.:laugh::good:
Click to expand...
Click to collapse
Users,if u face any difficulty in changing display size you may flash this.
Btw i didnt pre-include it since i made the patch not only for this particular rom and also since this rom and many other N roms have option to change display size by default in settings itself.
@tanish2k09 , any major bugs ?
emil_515 said:
@tanish2k09 , any major bugs ?
Click to expand...
Click to collapse
Hmm. Yes. Since the source is same (k3), LOS bugs are also present in this ROM.
I've also faced issues with titanium backup but that was probably a problem with my backups.
this rom have engineer mode? if not - it's not usable without volume fixing inside engineer mode.
Here is a link to devil kernel for all the users. Latest kernel build as of 3rd Feb 2017.
https://drive.google.com/file/d/0BxkDSj8MtdPQeHF2T0J0bDRVcG8/view?usp=drivesdk
@aswinp222 I have flashed the ROM twice and I recommend you to remove the step 5,6,7 from instructions because they are useless.
What I do : Flash ROM, k3 patch, kernel, build prop fix.
All of these I flash in this order and reboot only once later.
tanish2k09 said:
Here is a link to devil kernel for all the users. Latest kernel build as of 3rd Feb 2017.
https://drive.google.com/file/d/0BxkDSj8MtdPQeHF2T0J0bDRVcG8/view?usp=drivesdk
@aswinp222 I have flashed the ROM twice and I recommend you to remove the step 5,6,7 from instructions because they are useless.
What I do : Flash ROM, k3 patch, kernel, build prop fix.
All of these I flash in this order and reboot only once later.
Click to expand...
Click to collapse
Whoaaaa. Thanks.
tanish2k09 said:
Here is a link to devil kernel for all the users. Latest kernel build as of 3rd Feb 2017.
https://drive.google.com/file/d/0BxkDSj8MtdPQeHF2T0J0bDRVcG8/view?usp=drivesdk
@aswinp222 I have flashed the ROM twice and I recommend you to remove the step 5,6,7 from instructions because they are useless.
What I do : Flash ROM, k3 patch, kernel, build prop fix.
All of these I flash in this order and reboot only once later.
Click to expand...
Click to collapse
U sure??then once try flasing rom and patch only nothing else,even kernel or ur patch and see if rom boots..plz let me know result
Downloaded aicp12. Will give it a shot.
aswinp222 said:
U sure??then once try flasing rom and patch only nothing else,even kernel or ur patch and see if rom boots..plz let me know result
Click to expand...
Click to collapse
Why would you want me to boot it without flashing the kernel??
And yes I'm sure. Tried twice.
I am getting some weird texts in weird places. Do you get these? (Check images)
When WhatsApp notifications arrive from two different chats, the header becomes "this is important because of the people involved".
1) Internal storage shows weird name.
2) In running services, "paste as plain text" and "replace"should not be there. I get these texts even in dialer during call.
Sorry about second SS.
tanish2k09 said:
Why would you want me to boot it without flashing the kernel??
And yes I'm sure. Tried twice.
Click to expand...
Click to collapse
because the patch is preincluded with kernel,and in my testings the patch wont work unless data is created.
emil_515 said:
Downloaded aicp12. Will give it a shot.
Click to expand...
Click to collapse
i have pre-tested that specific rom bro,it wont boot :crying: it wont even flash unless you extract the system.new.dat
@aswinp222
This ROM has the media glitch too. Why do the same bugs exist in RR and los?? Is there a same dev or base or something??
Someone please confirm YouTube video playback. Try playing two videos consecutively.
aswinp222 said:
i have pre-tested that specific rom bro,it wont boot :crying: it wont even flash unless you extract the system.new.dat
Click to expand...
Click to collapse
Is there any way to fix that ?
Because that ROM seems more stable
I'm getting an error sim card is PUK locked
emil_515 said:
I'm getting an error sim card is PUK locked
Click to expand...
Click to collapse
Just wait for sometime. Will get away itself. You just need to get signal for removing that error. Steps for Jio or any 4g-only sim are given in op.

[ABANDONED][ROM][Pixel 2][UNOFFICIAL] LineageOS 15.1 / 16.0 [walleye]

{
"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 and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM and reboot of flash to TWRP
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing
Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.
Is link not posted yet?
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...
Any chance for an MD5
jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f
TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.
Thanks very much for sharing this. I've got it installed and it's running fantastic.
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.
redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview
Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list

Categories

Resources