[UB][RECOVERY] TWRP v3.2.2 for Xperia Tablet Z [POLLUX/POLLUX_WINDY] - Xperia Tablet Z Original Android Development

[UB][RECOVERY] TWRP v3.2.2 for Xperia Tablet Z [POLLUX/POLLUX_WINDY] - Xperia Tablet Z Original Android Development

{
"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"
}
WARNING!
TWRP builds version 3.2.1-0 and higher are not compatible with Android Lollipop (5.0/5.1.1) due to SELinux rejection
OFFICIAL DOWNLOADS FOR POLLUX/POLLUX_WINDY :
https://dl.twrp.me/pollux/ ,
https://dl.twrp.me/pollux_windy/
twrp-3.x.x-x-pollux.img , twrp-3.x.x-x-pollux_windy.img : Official TWRP image
How to install : All informations available on TWRP.me
DEVELOPMENT DOWNLOADS FOR POLLUX/POLLUX_WINDY :
https://www.androidfilehost.com/?w=files&flid=202356
twrp-3.2.x-x-pollux.zip , twrp-3.2.x-x-pollux_windy.zip : Flashable TWRP 3 to FOTA installer
twrp-3.2.x-x-pollux.img , twrp-3.2.x-x-pollux_windy.img : Fastboot bootable TWRP 3 image
cleaner-fota.zip : Flashable FOTA formatter (optional)
HOW TO INSTALL EASILY TO FOTA :
* (Optional) : Download the TWRP bootimage and flash it to boot
fastboot flash boot twrpfilename.img
* Boot to recovery : Enter the Recovery as usual
* Flash to FOTA : Install the TWRP FOTA zip
* (Optional) : Flash the ROM you want
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
ADDITIONAL LINKS :
* Easy ADB and Fastboot for unexperienced users :
https://forum.xda-developers.com/showthread.php?p=48915118
Thanks to the TWRP Team
Current local manifest of the TWRP build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/fusion3-common/twrp_development_sony -->

Oreo needs TWRP 3.2.x.x.
Does the appearance of this thread mean that there are ongoing work on Oreo for Tablet Z?

ze7zez said:
Oreo needs TWRP 3.2.x.x.
Does the appearance of this thread mean that there are ongoing work on Oreo for Tablet Z?
Click to expand...
Click to collapse
Yes, we are working on android 8.1.0 for all fusion3 devices

For me links are dead. Here i found it
https://androidfilehost.com/?fid=673791459329066468
Anyone installed 3.2.1.0 on windy ? Is it OK ?
Sent from my [device_name] using XDA-Developers Legacy app

phillipssat said:
For me links are dead. Here i found it
https://androidfilehost.com/?fid=673791459329066468
Anyone installed 3.2.1.0 on windy ? Is it OK ?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
To me it works pretty well, don't see any difference. Running now the unofficial OREO LineageOS.

Does anyone know why original links are dead ? Any problems with the 3.2.1.0 at link from first post ?
Sent from my [device_name] using XDA-Developers Legacy app

Thank you Very much for your efforts for this device! Great!!!

phillipssat said:
Does anyone know why original links are dead ? Any problems with the 3.2.1.0 at link from first post ?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
All the download links work, I checked them.

@CyberWalkMaN, are you planning on eventually submitting your 3.2.1-0 builds for official support? I'm asking because I built my own TWRP for both pollux and pollux_windy (see the BasketBuild link in my signature) from my dedicated device trees, not directly from Lineage source repos. I was thinking of creating my own thread and submitting my repos to TeamWin, given enough positive feedback, especially since only pollux_windy has an official TWRP page and it's most recent official version is 3.0.2-0. I've built TWRP for a number of devices since version 3.2 was released and submitted them for official support.

ripee said:
@CyberWalkMaN, are you planning on eventually submitting your 3.2.1-0 builds for official support? I'm asking because I built my own TWRP for both pollux and pollux_windy (see the BasketBuild link in my signature) from my dedicated device trees, not directly from Lineage source repos. I was thinking of creating my own thread and submitting my repos to TeamWin, given enough positive feedback, especially since only pollux_windy has an official TWRP page and it's most recent official version is 3.0.2-0. I've built TWRP for a number of devices since version 3.2 was released and submitted them for official support.
Click to expand...
Click to collapse
Yes, I plan to do it this week. I think that our device trees are cleaner and more relevant for this -
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux_windy

CyberWalkMaN said:
Yes, I plan to do it this week. I think that our device trees are cleaner and more relevant for this -
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux_windy
Click to expand...
Click to collapse
Great! Hey, whatever works best is what's most important

Please test first official builds:
pollux - http://build.twrp.me/twrp-3.2.1-0-pollux.img
pollux_windy - http://build.twrp.me/twrp-3.2.1-0-pollux_windy.img

CyberWalkMaN said:
Please test first official builds:
Click to expand...
Click to collapse
What is a difference between unofficial and official builds?

ripee said:
@CyberWalkMaN, are you planning on eventually submitting your 3.2.1-0 builds for official support?
I'm asking because I built my own TWRP for both pollux and pollux_windy (see the BasketBuild link in my signature)
from my dedicated device trees, not directly from Lineage source repos. I was thinking of creating my own thread and submitting my repos to TeamWin, given enough positive feedback, especially since only pollux_windy has an official TWRP page and it's most recent official version is 3.0.2-0. I've built TWRP for a number of devices since version 3.2 was released and submitted them for official support.
Click to expand...
Click to collapse
Is already out of date?
I do not see any TWRPs for pollux*

Rootk1t said:
What is a difference between unofficial and official builds?
Click to expand...
Click to collapse
Before official builds come out, TeamWin runs official preview builds to make sure that the images their Jenkins builder churns out are actually functional and true to the code submitted by the developer, relative to the developer's own unofficial builds.
Once everything is confirmed to be working the same as unofficial builds, TeamWin runs the actual official builds, which get linked on their site and made available on the official TWRP app. Official support also ensures that future version of TWRP will be attempted to be built using existing repos without the need for the developer's further input unless and until the source repo become too outdated, at which point a new branch would need to be created with code that follows a more recent android API.

ze7zez said:
Is already out of date?
I do not see any TWRPs for pollux*
Click to expand...
Click to collapse
TWRP for pollux/pollux_windy is now officially maintained by me -
https://twrp.me/sony/sonyxperiatabletzlte.html (pollux),
https://twrp.me/sony/sonyxperiatabletzwifi.html (pollux_windy)

There must be something wrong with my pollux_windy. :crying:
Flashing v3.2.1.0 causes a TWRP boot looping.
The only way to boot LineageOS 14.1 was flashing again TWRP-3.1.1-pollux-FOTA-20170928.zip from CaHbKaUp.
Any idea what's going on?
BTW, thanks for updating TWRP! :good:
Edit:
Finally solved the problem.
Downloaded TWRP 3.2.1.0 from official page and I've followed the dd Install Method even though my tablet is not rooted (su command wasn't recognized -su: not found- but dd worked in TWRP Terminal).

Help-as written I cant flash this twrp on 5.1.1 right so i hve to downgrade it to 4.2.2 and then flash it
Can I flash it with Flashtool?
What is FOTA?? Can I flash it from Flashtool if yes then how

Hi,
any version for TWRP 3.2.2-0 ???
Thx

djibe89 said:
Hi,
any version for TWRP 3.2.2-0 ???
Thx
Click to expand...
Click to collapse
images are available on official site.

Related

[Recovery][Kenzo/Kate][Unofficial] TWRP-3.1.1

Flashing Instructions:
To install recovery images use Flashify / Rashr / TWRP Manager from Play Store or flash in your current recovery:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
Changes in unofficial version:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support (ext4 & f2fs)
f2fs file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup (fstab)
ADB root
Full SELinux support
compiled on omnirom-7.1 source
up-to-date with android-7.1 branch
up-to-date device trees
fixed AROMA installer
fixed screen brightness
extra languages + Polish by me
enabled logd/logcat in recovery
enabled fuse exfat, ntfs-3g, jpeg
external storage as default storage
removed mouse cursor
There are 2 versions of my Unofficial TWRP available:
* twrp_3.0.3-0_kenzo_16-12-25.img - with precompiled kernel from official twrp kenzo device tree. For kenzo only
* twrp_3.0.3-6_kenzo-inline_17-02-24.img - with kernel compiled from source inline with recovery. For kenzo only
* twrp_3.0.3-7_inline_17-03-04.img - with kernel compiled from source inline with recovery. This recovery is currently the only one supported and suitable for both kenzo and kate variants
Download:
Attention: this recovery is no longer maintained by me and will have no more updates.
TWRP: Unofficial TWRP
fichl's theme pack: [THEME][TWRP] TWRP 3.0.2 dark stock theme pack w different colors v2 [07.03.2016]
Remember to do backup of your current recovery before installing.
XDA:DevDB Information
Unofficial TWRP-3.1.1 for Xiaomi Kenzo/Kate, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
dadi11
Source Code: https://github.com/dadi11/twrp_kenzo
Version Information
Status: No Longer Updated
Created 2016-08-24
Last Updated 2017-07-21

Source:
Device: https://github.com/dadi11/twrp_kenzo
Kernel: https://github.com/TeamHorizon/android_kernel_xiaomi_kenzo
Attention: this recovery is no longer maintained by me and will have no more updates.

That TWRP is better the cofface, the official or yours?

dadi11 said:
TeamWin's TWRP Touch Recovery for Xiaomi Redmi Note 3 Pro - Kenzo.
https://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Screenshots:

Flashing Instructions:
To install recovery images use Flashify / Rashr / TWRP Manager from Play Store or flash in your current recovery:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
Changes in unofficial version:
compiled on omnirom-5.1 source
always up-to-date
updated device tree
fixed AROMA installer
fixed screen brightness
extra languages + Polish by me
permissive selinux
enabled logd/logcat in recovery
enabled fuse exfat, ntfs-3g, jpeg
external storage as default storage
enabled usb-otg support
enabled backup of all partitions
enabled thermal control
crypto/f2fs may work or not..
red theme by @fichl
removed mouse cursor
decreased size by compiling kernel inline
There are 2 versions of my Unofficial TWRP available:
* (kenzo) - with precompiled kernel from official twrp kenzo device tree
* (kenzo-inline) - with kernel compiled inline with recovery. It decreases half of recovery image size, gives some modification options... and needs testing.
Download:
TWRP: Unofficial TWRP
Remember to do backup of your current recovery before installing.
XDA:DevDB Information
Unofficial TWRP-3.0.2-0 for Xiaomi Kenzo, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
dadi11
Source Code: https://github.com/dadi11/twrp_recovery
Version Information
Status: Stable
Created 2016-08-24
Last Updated 2016-08-24
Click to expand...
Click to collapse
Great work mate!
Will it be possible for you to push the commits to the official TWRP, then we can have best of both worlds

Thanks a lot for your work, is it possible to have it in a more dark color?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

@dadi11, Since TWRP 3.0.2-0 is pl.xml already been uploaded so why is your merit? (Such curiosity)
Thanks for the alteration, I just had to run TWRP so by the way check

m4dbra1n said:
Thanks a lot for your work, is it possible to have it in a more dark color?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
check out fichl's or any other twrp themes
Daviteusz said:
GOOGLETRANSLATE: @dadi11, Since TWRP 3.0.2-0 is pl.xml already been uploaded so why is your merit? (Such curiosity)
Thanks for the alteration, I just had to run TWRP so by the way check
Click to expand...
Click to collapse
https://gerrit.omnirom.org/#/c/16935/

No more horrible mouse cursor, thank you.

Could you pls add the option to patch the MIUI boot.img?
Thank you.

abhis3k said:
Great work mate!
Will it be possible for you to push the commits to the official TWRP, then we can have best of both worlds
Click to expand...
Click to collapse
Please refrain from quoting the whole OP thread! It's against the rules.

Great work. I have just the one query. Do we have to flash the boot.img patcher after flashing MIUI or will the recovery take care of that?
And, hearty thanks for your work.

I am on TWRP coffe 3.0.0, Should i upgrade it?
Sent from my Redmi Note 3 using Tapatalk

Is your kernel suppport display the battery for newer device variant?
Sent from my Redmi Note 3 using Tapatalk

qlm2009 said:
Could you pls add the option to patch the MIUI boot.img?
Thank you.
Click to expand...
Click to collapse
ayush3051 said:
Great work. I have just the one query. Do we have to flash the boot.img patcher after flashing MIUI or will the recovery take care of that?
And, hearty thanks for your work.
Click to expand...
Click to collapse
I will look at it later, but as for now it is more like official twrp than cofface one. Would be easier if he has any source or speak english
can you send me a link to this patcher? I am not familiar with miui, cofface twrp or patchers...
kakarotvn said:
I am on TWRP coffe 3.0.0, Should i upgrade it?
Click to expand...
Click to collapse
if you want
khangozzy said:
Is your kernel suppport display the battery for newer device variant?
Click to expand...
Click to collapse
it seems like it doesn't work with prebuilt kernel. try kenzo-inline version if you need battery level in recovery

I confirm that battery level works with inline version, on a kenzo with newer battery controller (the one that many kernels/ROMs have 50%/-2% problem with).
Thank you for this recovery.

cheeze.keyk said:
Please refrain from quoting the whole OP thread! It's against the rules.
Click to expand...
Click to collapse
Ah yes, sorry about that. I did that post in a hurry and didn't notice. Thanks for reminding

dadi11 said:
I will look at it later, but as for now it is more like official twrp than cofface one. Would be easier if he has any source or speak english
can you send me a link to this patcher? I am not familiar with miui, cofface twrp or patchers...
if you want
it seems like it doesn't work with prebuilt kernel. try kenzo-inline version if you need battery level in recovery
Click to expand...
Click to collapse
Thanks, flashed the inline version and battery correctly displays. Good job, bro!
Sent from my Redmi Note 3 using Tapatalk

used the non-inline variant...
mtp and adb doesn't work...

psndna88 said:
used the non-inline variant...
mtp and adb doesn't work...
Click to expand...
Click to collapse
will be fixed in next update. Thanks for reporting

Happy to see u psndna88 on redmi note 3 forum
Sent from my Redmi Note 3 using Tapatalk
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
I have used agni kernel on Samsung Galaxy note 2
Sent from my Redmi Note 3 using Tapatalk

[OFFICIAL]LineageOS 14.1 for ZTE Axon 7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lineage OS
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the N Bootloader and approriate Modem package below. You must have an unlocked
bootloader as well! Failure to do so could lead to an unrecoverable bricked device.
Instructions:
1. Install the Universal bootloader and your model specific modem.Failure to do so will not allow flashing the ROM!
2. Update recovery [Recommended -> Official TWRP for Axon7
3. Factory reset if coming from another ROM.
4. Install ROM
5. Install GApps (optionally) [Recommended -> Open GApps (arm64) (7.1) 2017-02-01 or Newer
What is CAF?
codeaurora.org
Code Aurora Forum, a Linux Foundation Collaborative Project, is a consortium of companies with projects serving the mobile wireless industry. The projects provide the tested code needed to bring innovative, performance optimized, open source based products to market and also serves as a staging area for code that is submitted to upstream projects such as the kernel and Android. Code Aurora Forum welcomes the participation of projects for multiple architectures. QuIC, as one of the members of Code Aurora Forum, provides support for Qualcomm hardware via the code it contributes to Code Aurora Forum. Code Aurora Forum also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Download:
Universal Bootloader and Modem packages for A2017, A2017G, and A2017U
Lineage Official Weekly Builds
Lineage Unofficial Builds
-----------------------------------------------------
XDA:DevDB Information
LineageOS 14.1 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
Unjustified Dev, DrakenFX, tdm
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Nougat Bootloader+Modem
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 2017-02-01
Beta Release Date: 2017-02-01
Created 2017-01-27
Last Updated 2017-03-28

Questions and Answers
Q. I hate you and your unstable LineageOS. I want to go back to stock could I?
A. Sure, just make sure to use the full firmware zip from ZTE
Q. I have a Chinese model. Could I install this ROM?
A. No, we don't have access to the updated bootloader and modem. We have added checks to prevent installing on older firmware
A.Yes, ZTE has provided an up to date modem compatible with B15 firmware

Working:
Audio (Distorted on media playback)
GPS
Camera
RIL (Data+Calling+VoLTE)
WI-FI
Bluetooth
Double Tap to Wake
Video Playback
Fingerprint Sensor
Not Working:
Please let me know!

G model coming soon hold off guys until we get proper testing.

.
Q. Lineage comes pre-rooted?
A. NO, Lineage does NOT comes pre-rooted, if you want root privileges/access you need to flash the following SuperSU after flashing Lineage.
[STABLE][2016.12.15] SuperSU v2.79 or [BETA][2017.01.14] SuperSU v2.79 SR3
Or here Lineage Root Binary Flashable zip
Use su arm64 zip file.
----------------------------------------------------------------------------------------------------
Q. Daydream is not working what can I do?
A.
CandyFoxJ said:
I got a private message from a Mr. Fitzie that recommended switching the VR setting under display from reduce blur to reduce flicker and daydream works now.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------
Q. I'm receiving SMS or MMS what can I do?
A. This seems to be a current issue with T-Mobile at moment and Disabling VoLTE (Enhanced 4G LTE Mode) under SIM Settings is a temporary fix, till permanent is found.
----------------------------------------------------------------------------------------------------
Q. why can't I modify system?"
A. It seems, System Write Protection is enable, so let's get it fix
Using ADB :
Code:
adb shell reboot disemmcwp
Using your device Terminal :
Code:
su
reboot disemmcwp

What a surprise!!!!! Thanks!!!!!

thanks Guys , my Axon is in the road to me

Nice! Thanks for all the hard work everyone has put in to this!

Confirmed working on the G model. Working on the last few issues and I'll publish the ROM online for everyone.

Unjustified Dev said:
Questions and Answers
Q. I hate you and your unstable LineageOS. I want to go back to stock can I?
A. No, if you attempt to do so you'll be kissing your device goodbye!
Click to expand...
Click to collapse
Ok, so there is no way back. But, why we would be bricking the device if we try to do so? I thought EDL bootstrap would allow to flash the boot and recovery. And using TWRP we could flash the complete 2017U bootstack. Does this mean that LOS 14.1 is modifying the EDL mode? Just curious about this.

Double posty thingy...

Oki said:
Ok, so there is no way back. But, why we would be bricking the device if we try to do so? I thought EDL bootstrap would allow to flash the boot and recovery. And using TWRP we could flash the complete 2017U bootstack. Does this mean that LOS 14.1 is modifying the EDL mode? Just curious about this.
Click to expand...
Click to collapse
Flashing the bootstack from B29 is what will brick you. We are giving you all the updated N stack from N from ZTE. It changes the structure of booting and no zip on XDA and from ZTE will restore the changes it does. Just hold off until I can test downgrading my device.

Why do we need to update Twrp2?

GREAT!
I did not think this would be released until official N was out.
THANKS to all that made this possible.
I don't care if I can down grade If you need a guinea pig.

borijess said:
Why do we need to update Twrp2?
Click to expand...
Click to collapse
You don't have to, but that would be nice so we can make sure everyone is using the same setup to trace down issues.

Ok guys everything is ready. Please let me know if you have issues and make sure to follow the steps and read correctly. The links are up! and if you downloaded a bootstack earlier please delete it and download the new one's for your model. Enjoy!

Unjustified Dev said:
Flashing the bootstack from B29 is what will brick you. We are giving you all the updated N stack from N from ZTE. It changes the structure of booting and no zip on XDA and from ZTE will restore the changes it does. Just hold off until I can test downgrading my device.
Click to expand...
Click to collapse
I understand that your kernel requires that new bootstack in order to boot properly. The previous unofficial alpha version of LOS 14.1 was able to boot using the current B29 bootstack. However that old version had many non functional features.

Hey so wat if I have a TWRP backup of my stock Os.....Can I restore to that if this doesn't work out??
Sent from my ZTE A2017U using Tapatalk

Iancort said:
Hey so wat if I have a TWRP backup of my stock Os.....Can I restore to that if this doesn't work out??
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
No. Read the topic, it's only 2 pages.

xtermmin said:
No. Read the topic, it's only 2 pages.
Click to expand...
Click to collapse
Hmmmm no finger print scanner and no way to go back....It's a tricky situation but with the delay by ZTE leave me no choice... Anyways rooting is possible using TWRP?? Or is it pre rooted?
Sent from my ZTE A2017U using Tapatalk

[ROM][11][OFFICIAL] lineage-18.1 for Pixel 3/XL (blueline/crosshatch)

lineage 18.1 is EOL for this device. 19.1 is now available:
https://forum.xda-developers.com/t/...rosshatch-android12-1-lineageos-19-1.4380097/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, 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. If you would like to contribute to LineageOS, please visit our Wiki for more details.
Downloads:
pixel 3 - blueline: https://download.lineageos.org/blueline
pixel 3 xl - crosshatch: https://download.lineageos.org/crosshatch
gapps zip (arm64): (optional): https://wiki.lineageos.org/gapps.html
Google Fi addon: https://sourceforge.net/projects/ra...-gapps-addon-arm64-11.0-20210212.zip/download (if you're on Google Fi, install this zip right after installing gapps zip.)
Android Auto addon: https://sourceforge.net/projects/ra...-gapps-addon-arm64-11.0-20201121.zip/download (if you want android auto, install this after installing gapps zip. note: this is only needed with opengapps)
Initial Install Instructions:
https://wiki.lineageos.org/devices/blueline/install
https://wiki.lineageos.org/devices/crosshatch/install
Update Instructions:
https://wiki.lineageos.org/devices/blueline/update
https://wiki.lineageos.org/devices/crosshatch/update
Upgrade Instructions: (from 17.1 to 18.1)
https://wiki.lineageos.org/devices/blueline/upgrade
https://wiki.lineageos.org/devices/crosshatch/upgrade
Notes:
1. lineage-18.1 comes with adb root that you can enable in developer options, but if you want root for apps, you can grab the magisk apk and rename it to .zip and install it in lineage recovery.
An alternative install method is to follow these boot.img patching instructions. You can get the boot img directly from the lineage download site. It's labeled as the recovery img but it's actually the boot img.
2. The newest vendor, radio, & bootloader are included in the lineage rom zip, so no need to worry about updating those manually.
Known issues:
1. when you format data in lineage recovery, you might see "cant send spi message". you can ignore it.
2. there's an issue with sprint mobile data not working. we're looking into it. there's an easy workaround though. send me a pm and i'll walk you through it.
Changelog:
blueline
crosshatch
Bug reporting:
https://wiki.lineageos.org/bugreport-howto.html
Source Code:
crosshatch device tree: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-18.1
blueline device tree: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-18.1
kernel tree: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-18.1
vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-18.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community.
Android version: 11
Kernel version: 4.9.248
Status: nightly

Lovely!

Beauty and the beast
Havent tried it but many thanks for the active development...

I loved this rom I hope it continues the development

Can I update to or dirty flash from lineage 17.1 to lineage 18 on pixel 3?

New build with November security patch level. :good:
blueline rom zip - https://androidfilehost.com/?fid=10763459528675579025
blueline boot img - https://androidfilehost.com/?fid=10763459528675579024
i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
crosshatch rom zip - https://androidfilehost.com/?fid=10763459528675580134
crosshatch boot img - https://androidfilehost.com/?fid=10763459528675580133

On crosshatch alternate build it's working very smooth and incredible well for first build, so far the only problem it's that gaming heats faster than usual.

razorloves said:
New build with November security patch level. :good:
crosshatch - i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
Click to expand...
Click to collapse
Thank you so much, it works fine on crosshatch, any updates are highly appreciated!
For me, it is an exclusion criteria if there is no root and no lineageos available for a device.
____
The only problem for me was to use the wrong version of Magisk ending up in a non booting device.
So if you update to lineage-18 and want to get root, you will want to take the canary version of magisk manager to patch the boot.img.

#Crosshatch
great to see the simplest rom available
it booted with the first link provided.
much obliged
I will use it and report my experience with it.
---------- Post added at 07:23 PM ---------- Previous post was at 07:21 PM ----------
beanaman said:
Can I update to or dirty flash from lineage 17.1 to lineage 18 on pixel 3?
Click to expand...
Click to collapse
its highly recommended to clean flash it since its in beta status

razorloves said:
New build with November security patch level. :good:
blueline rom zip - https://androidfilehost.com/?fid=10763459528675579025
blueline boot img - https://androidfilehost.com/?fid=10763459528675579024
crosshatch - i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
Click to expand...
Click to collapse
What is the ADB command to flash gapps? I have only flashed ROMs with gapps included

Zehlek said:
What is the ADB command to flash gapps? I have only flashed ROMs with gapps included
Click to expand...
Click to collapse
Just side load the zip file for the gapps

razorloves said:
New build with November security patch level. :good:
blueline rom zip - https://androidfilehost.com/?fid=10763459528675579025
blueline boot img - https://androidfilehost.com/?fid=10763459528675579024
i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
crosshatch rom zip - https://androidfilehost.com/?fid=10763459528675580134
crosshatch boot img - https://androidfilehost.com/?fid=10763459528675580133
Click to expand...
Click to collapse
Crosshatch boot img it won't boot, it will go straight to bootloader, know bugs so far lte status bar icons aren't present on Nov patch update

Thanks to Razor we have the opportunity to have LOS .
I'll try it after work ?

Can anyone confirm if Android Auto works with this? A lot of the Android 10 roms did not, and that was a huge deal breaker for me, as I use Android auto daily.

New builds with some changes and fixes.
blueline rom zip - https://androidfilehost.com/?fid=10763459528675581018
blueline boot img - https://androidfilehost.com/?fid=10763459528675581017
crosshatch rom zip - https://androidfilehost.com/?fid=10763459528675580705
crosshatch boot img - https://androidfilehost.com/?fid=10763459528675580704
significant changes:
added power menu options (advanced restart) - https://review.lineageos.org/q/topic:eleven-powermenu
added support for skipping tracks with remote control - https://review.lineageos.org/292052
fixed missing status bar icons on devices with a notch - https://review.lineageos.org/292038

lineage recovery won't boot.
Hi razorloves. Thanks for all your hard work. But I'm having serious issues booting into any lineage recovery (I've tried multiple nightly builds from 17.1 and multiple boot.img from this thread). All are failing. I do fastboot flash boot boot.img (I've also tried both boot_a and boot_b) but once i reboot it goes back into fastboot and give me an error with the boot img. Yet when I do htis with twrp-3.3.0-0-blueline.img i boot into twrp fine. (only issue there being that the zip files for lineage os fail to flash when installing from twrp. I've also tried with stock recovery and that give the same error as twrp).
I should also note that when i do fastboot boot boot.img the boot just hangs and never goes through.
Any suggestions?

tantonj said:
Hi razorloves. Thanks for all your hard work. But I'm having serious issues booting into any lineage recovery (I've tried multiple nightly builds from 17.1 and multiple boot.img from this thread). All are failing. I do fastboot flash boot boot.img (I've also tried both boot_a and boot_b) but once i reboot it goes back into fastboot and give me an error with the boot img. Yet when I do htis with twrp-3.3.0-0-blueline.img i boot into twrp fine. (only issue there being that the zip files for lineage os fail to flash when installing from twrp. I've also tried with stock recovery and that give the same error as twrp).
I should also note that when i do fastboot boot boot.img the boot just hangs and never goes through.
Any suggestions?
Click to expand...
Click to collapse
Razorloves contacted me directly and help me sort out the issue. My problem is I first needed to flash to the CORRECT stock rom. (I was using the oldest android 9 rom. for 17.1 I needed newest 10 rom, for this I needed newest 11 rom).
Thanks,

xFaultx said:
Can anyone confirm if Android Auto works with this? A lot of the Android 10 roms did not, and that was a huge deal breaker for me, as I use Android auto daily.
Click to expand...
Click to collapse
Android Auto is not working for me. Crashes immediately after opening. I attached a logcat that should contain three failures right in a row.

tantonj said:
Razorloves contacted me directly and help me sort out the issue. My problem is I first needed to flash to the CORRECT stock rom. (I was using the oldest android 9 rom. for 17.1 I needed newest 10 rom, for this I needed newest 11 rom).
Thanks,
Click to expand...
Click to collapse
Is this a step that everyone needs to follow when upgradeing from LineageOS 17.1 to 18, or only if your still on OEM?

beanaman said:
Can I update to or dirty flash from lineage 17.1 to lineage 18 on pixel 3?
Click to expand...
Click to collapse
the migration changes are still in-work, so something might go wrong if you don't wipe data. you can follow the progress here: https://review.lineageos.org/q/topic:"eleven-db-migration"
ktdt00 said:
Android Auto is not working for me. Crashes immediately after opening. I attached a logcat that should contain three failures right in a row.
Click to expand...
Click to collapse
thx for log. will look into it.
FeralG said:
Is this a step that everyone needs to follow when upgradeing from LineageOS 17.1 to 18, or only if your still on OEM?
Click to expand...
Click to collapse
only when you're on stock rom

Development [ROM][OFFICIAL] Omnirom for zenfone8 [Android-13.0]

{
"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"
}
What is Omnirom ?
Selinux Status:
Enforcing
Instructions :
Follow this Steps by steps
* Remove all Security pwd/pin/pattern on you current Rom
* Download the ROM (see Dl section)
************************************************************
For the first install.
************************************************************
- reboot to fastboot (fastboot reboot fastboot or adb reboot fastboot, depend if you're on running system or bootloader)
- fastboot boot name_of_your_twrp.img
- flash omnirom.zip
* Permanent TWRP. Go to Advanced --> Flash Current TWRP
* Wipe userdata ( by typing yes)
* reboot and profite
************************************************************
Update Rom
************************************************************
- Go to settings -> system --> system updates --> (enable local flash) select the zip file and flash --> reboot
Or wait OTA (All Sundays)
if u did something else. we dont need/wanna know about it in the thread
Device Maintainers
@micky387
What's not working ?
Smartkey didn't work for the moment...
ROM OS Version: Android 13.0
ROM Kernel: Linux 5.4
Download:
Rom with Microg packages
Rom with Gapps include packages
Telegram Group:
What's our MicroG version ?
OmniROM zenfone8 chat
Official OmniROM Community
TWRP
Official TWRP realease
Source Code
Omnirom
Omnirom gerrit
XDA:DevDB Information
Omnirom for zenfone8, ROM for the ASUS zenfone8, Rom Asuszenfone8
Contributors
micky387
ROM OS Version: Android 13.0
ROM Kernel: Linux 5.4
ROM Firmware Required: Lastest stock Asus Official website for the firmware
Version Information
Status: Stable
Created 2021-06-26
Last Updated 2022-11-16

me

Nice
Linked rom have gapps inclued or microG version?

NisseGurra said:
Nice
Linked rom have gapps inclued or microG version?
Click to expand...
Click to collapse
gapps for the moment ( for unofficial)

Ok, thanks, i await microg version. Nice to see omni for ZF8

Awesome!

NisseGurra said:
Ok, thanks, i await microg version. Nice to see omni for ZF8
Click to expand...
Click to collapse
I'm on an nice day
OP uopdated with microg version

Nice work, thanks a lot!
I just noticed; On the OmniROM website, it says that the version for ZenFone 8 is official. Also, there is a picture of the ZenFone 6. Maybe you can bring this up with the maintainer of the website.

DerSteppo said:
Nice work, thanks a lot!
I just noticed; On the OmniROM website, it says that the version for ZenFone 8 is official. Also, there is a picture of the ZenFone 6. Maybe you can bring this up with the maintainer of the website.
Click to expand...
Click to collapse
yes, it's an leftover. I need to update it

Getting a 404 error now :-(
OmniROM - zenfone8

Using the ROM in the original post is great. Do we report bugs here?
SIM 1 doesn't work. It'll show your carrier but won't work. I tried with 1 and 2 SIMs at once. Only SIM 2 will work.
When you select the option to hide the nav bar (which is great because then it pushes the keyboard down), even if you're using gesture navigation, the back gesture stops working. Hiding the pill isn't as good because the keyboard and some apps leave a huge gap at the bottom.
Not necessarily a bug, but it looks like the GAPPs version can't get system updates? What's the best way to have Google apps but also utilize the system updates feature. (I know there probably aren't any updates available at the moment.)

thatguy222 said:
Getting a 404 error now :-(
OmniROM - zenfone8
Click to expand...
Click to collapse
Same

Omni for ZF8 not out yet, that's why you get 404 errors

Yeah, I figured. I do check out @micky387 's Gerrit activity, though. Excited for what is to come.

Official omni out for ZF8

I would really appreciate if someone who is anyway gonna try this ROM and use it to post some kind of short review. I am mostly interested in stability, battery life and camera (as usually on custom ROMs camera quality is way worse compared to stock)

NisseGurra said:
Official omni out for ZF8
Click to expand...
Click to collapse
Looks like only microG version. Anyone know how to install gapps on it? I can't get into recovery to flash the gapps zip.

TikiThePug said:
Looks like only microG version. Anyone know how to install gapps on it? I can't get into recovery to flash the gapps zip.
Click to expand...
Click to collapse
OmniROM - zenfone8

Woops

I don't know if this is coincidence or ROM-related, but has anyone else had adb and fastboot problems? Since flashing the June version of OmniROM I can't get my computer to recognize my phone in fastboot or recovery ADB. Nothing shows up in Device Manager at all.
Everything works fine from within Android, but once I get into recovery it's just silence. Same symptoms on my Win10 desktop, Win10 laptop, and terminal on OnePlus 5. As far as I'm aware I can't update the ROM, restore factory firmware, or root the phone without fastboot and/or ADB.
EDIT: I tried several other Windows, Linux, and Android devices and none would even acknowledge that I had plugged something in, but yesterday I tried my mom's ASUS laptop and my phone showed up in Device Manager without even needing drivers. I was able to fastboot flash TWRP and update the ROM. I still have no explanation for why so many devices didn't work or why this one did, but at least all of that is behind me.

Development [ROM][11][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord CE/ebba]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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
Fingerprint
Wi-Fi
Bluetooth
Camera
Audio
Sensors
Flash
GPS
NFC
DT2W
Known issues :
-
In order to prevent problems please use the recovery image included in this release!
Instructions :
-Download the ROM and recovery image
-Boot into bootloader: adb reboot bootloader
-Flash the recovery image: fastboot flash recovery recovery.img
-Format data / do a factory reset in recovery
-Reboot into recovery: click advanced --> reboot to recovery
-Go to Apply update and choose Apply from ADB
-Sideload the rom: adb sideload rom.zip
Downloads :
-Recovery image: *Link*
-LineageOS 18.1 with GApps included: *Link*
Android OS version: 11
Build author/ROM Maintainer: @GriefNorth
Kernel Source: *Link*
Device Tree: *Link* and *Link*
Based on: LineageOS
Status: Stable
Current Stable Version: 18.1
Stable Release Date: Updated monthly
Created: 2022-02-13
Last Updated: 2022-02-13
Special Thanks:
- to the LineageOS team
- @KakatkarAkshay for maintaning PixelExperience avicii device tree on which this build is heavily based on.
Donate link

CHANGELOG:
- sync with last source
- fix wi-fi for EU and GLO
- etc
UPDATING THE ROM:
Unless I say the opposite in the update announcement, this ROM can be updated using by two steps:
1. OTA update method
- SystemSettings
- Update system
- Download new version
- let the system do everything by itself
2. the dirty flash method.
In order to do so, follow these steps:
-Download the new version of the ROM you are using (microG/vanilla)
-Reboot into recovery: adb reboot recovery
-DO NOT CLICK ON FACTORY RESET / WIPE DATA
-Flash the Zip-File of the new ROM: adb sideload rom.zip

Hi, Great, thanks a lot for releasing LineageOS for this phone!!
Would it be possible to add a build without gapp?
Greetings seven
EDIT:
Hey,
Have tested today, installed with their OrangeFox recovery build, Boots not, endless the Linage logo.
Thanks, that sucks
Edit:
Finally Solved with your Revovery.img + Instructions,
It was not possible to avoid the formatting.

This is what I have been waiting for, finally some development!!

Finally something pleasing for this phone. Here're offficial LineageOS device sources for Redmi Note 9 Pro 5G / Mi 10T Lite / Mi 10i, the phones use the same SoC as ours. Maybe it could help to improve your code.
GitHub - LineageOS/android_device_xiaomi_gauguin
Contribute to LineageOS/android_device_xiaomi_gauguin development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_xiaomi_gauguin
Contribute to LineageOS/android_kernel_xiaomi_gauguin development by creating an account on GitHub.
github.com

Can you provide a Google Drive link?
Thx

novato97 said:
Can you provide a Google Drive link?
Thx
Click to expand...
Click to collapse
I can't, not enough space in GDrive. Maybe someone else

Seven1993 said:
Hi, Great, thanks a lot for releasing LineageOS for this phone!!
Would it be possible to add a build without gapp?
Greetings seven
EDIT:
Hey,
Have tested today, installed with their OrangeFox recovery build, Boots not, endless the Linage logo.
Thanks, that sucks
Edit:
Finally Solved with your Revovery.img + Instructions,
It was not possible to avoid the formatting.
Click to expand...
Click to collapse
I built the rom without gapps.
Link: https://www.dropbox.com/s/t2iiu5dfrgiokuk/lineage-18.1-20220224-UNOFFICIAL-ebba.zip?dl=0

asasamo said:
I built the rom without gapps.
Link: https://www.dropbox.com/s/t2iiu5dfrgiokuk/lineage-18.1-20220224-UNOFFICIAL-ebba.zip?dl=0
Click to expand...
Click to collapse
Thx for the effort!
What 3rd party gapps package would you suggest to use (Like opengapps, nikgapps, flamegapps etc.)?

Sony make.believe said:
Thx for the effort!
What 3rd party gapps package would you suggest to use (Like opengapps, nikgapps, flamegapps etc.)?
Click to expand...
Click to collapse
I always used opengapps in the past. Recently i started using microg for better battery life and little to no tracking.

asasamo said:
I built the rom without gapps.
Link: https://www.dropbox.com/s/t2iiu5dfrgiokuk/lineage-18.1-20220224-UNOFFICIAL-ebba.zip?dl=0
Click to expand...
Click to collapse
How would you add microg to lineage os? Do i need magisk for that?

Fisuxcel said:
How would you add microg to lineage os? Do i need magisk for that?
Click to expand...
Click to collapse
Look at this well made guide. Follow all the steps and you'll have a fully working microg install.

I'm glad to see there's active development for this device. Thanks for that.
I was looking into sources and noticed there's TARGET_CPU_VARIANT_RUNTIME = kryo385 (cortex A75 and A55) in boardconfigcommon.mk file but Snapdragon 750G is kryo570 which is cortex A77 and A55.

Flashing_Expert said:
I'm glad to see there's active development for this device. Thanks for that.
I was looking into sources and noticed there's TARGET_CPU_VARIANT_RUNTIME = kryo385 (cortex A75 and A55) in boardconfigcommon.mk file but Snapdragon 750G is kryo570 which is cortex A77 and A55.
Click to expand...
Click to collapse
You can join the development and fix what you think is wrong.

GriefNorth said:
You can join the development and fix what you think is wrong.
Click to expand...
Click to collapse
It wasn't meant that bad and I've never said something's wrong. Just an information.

Flashing_Expert said:
It wasn't meant that bad and I've never said something's wrong. Just an information.
Click to expand...
Click to collapse
I know, too, had nothing wrong, just one to miss some things

@GriefNorth ... The download link for your rom is no longer working.
Can you please create a new one?
Thank you!

Discombobulated85 said:
@GriefNorth ... The download link for your rom is no longer working.
Can you please create a new one?
Thank you!
Click to expand...
Click to collapse
updated link
if you still have problems with access, try using vpn, I'm from Russia and your ISPs may block access to us.

GriefNorth said:
CHANGELOG:
- sync with last source
- fix wi-fi for EU and GLO
- etc
UPDATING THE ROM:
Unless I say the opposite in the update announcement, this ROM can be updated using by two steps:
1. OTA update method
- SystemSettings
- Update system
- Download new version
- let the system do everything by itself
2. the dirty flash method.
In order to do so, follow these steps:
-Download the new version of the ROM you are using (microG/vanilla)
-Reboot into recovery: adb reboot recovery
-DO NOT CLICK ON FACTORY RESET / WIPE DATA
-Flash the Zip-File of the new ROM: adb sideload rom.zip
Click to expand...
Click to collapse
Just to make sure, I have the lineageos without gapps. I can update it with dirty flash and it won't install the gapps right?

Fisuxcel said:
Just to make sure, I have the lineageos without gapps. I can update it with dirty flash and it won't install the gapps right?
Click to expand...
Click to collapse
only for the version without gapps

Database Develop

welcome