Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version down below
2) Reboot to your current recovery or flash the recovery.img with dd on your recovery partition
3) Flash the provided archive
TWRP L7
Thanks @WinterR my tester
Great work, it works beautifully!
Thank you to keep supporting the old Optimus L7
thanks!!!
Thank you for posting this, but I cannot install ROMs on my P705 now, as my device thinks it's a P700. Is there a way around this?
stephendt0 said:
Thank you for posting this, but I cannot install ROMs on my P705 now, as my device thinks it's not a P700. Is there a way around this?
Click to expand...
Click to collapse
I wiil see
Jonas Cardoso said:
I wiil see
Click to expand...
Click to collapse
Thanks. I believe all you would need to do is duplicate this and modify the device ID P705? I can of course modify the updater script of a ROM but that's always not fun.
Good work
Jonas Cardoso said:
I wiil see
Click to expand...
Click to collapse
Any luck?
stephendt0 said:
Any luck?
Click to expand...
Click to collapse
It's kind of hard to do, because the recovery will be different model of ROM, there will always give error in flash
Jonas Cardoso said:
It's kind of hard to do, because the recovery will be different model of ROM, there will always give error in flash
Click to expand...
Click to collapse
It's easy just remove model check from script
aidasaidas75 said:
It's easy just remove model check from script
Click to expand...
Click to collapse
If I am to remove all model check the script of ROM, it would be I make recovery image for each model would result in the same result, and taking into account que there are always two versions of the zip ROM p700 and P705 (P708 with a specific kernel and the camera libs), one without and one with nfc, it would be logical to use the nfc destroyer from caliban, gives same so that occurs at the L5 e612 and e610
Jonas Cardoso said:
If I am to remove all model check the script of ROM, it would be I make recovery image for each model would result in the same result, and taking into account que there are always two versions of the zip ROM p700 and P705 (P708 with a specific kernel and the camera libs), one without and one with nfc, it would be logical to use the nfc destroyer from caliban, gives same so that occurs at the L5 e612 and e610
Click to expand...
Click to collapse
You don't use nfc and camera in recovery and recovery kernel does not effect actual rom kernel so i think it would be better idea to build one recovery. Plus I will be releasing new twrp and cm12.1 then you could merge my changes to it
aidasaidas75 said:
You don't use nfc and camera in recovery and recovery kernel does not effect actual rom kernel so i think it would be better idea to build one recovery. Plus I will be releasing new twrp and cm12.1 then you could merge my changes to it
Click to expand...
Click to collapse
I know not have nfc or camera in recovery but for me to build a recovery for each model l7 she will have their IDs even though the same kernel, that's why he asked to build for the p700 and separate P705, when I update the recovery will separate them, by the way many users are having problems with your new TWRP to cm12.1 and baseband that comes with it
Jonas Cardoso said:
I know not have nfc or camera in recovery but for me to build a recovery for each model l7 she will have their IDs even though the same kernel, that's why he asked to build for the p700 and separate P705, when I update the recovery will separate them, by the way many users are having problems with your new TWRP to cm12.1 and baseband that comes with it
Click to expand...
Click to collapse
I havent release new baseband or new cm12.1 but people already has problem with it?
aidasaidas75 said:
I havent release new baseband or new cm12.1 but people already has problem with it?
Click to expand...
Click to collapse
I do not if you do not know or your ignorance but Androrid File Host is open by standard, and anyone can see the files, of course if visible, I'm just warning you, with that some users are having serious problems with that, my friend Antonio is helping, but if you do not mind is no longer my problem
Update twrp to 3.0.2-0
https://www.androidfilehost.com/?fid=24499762636002461
Jonas Cardoso said:
Update twrp to 3.0.2-0
https://www.androidfilehost.com/?fid=24499762636002461
Click to expand...
Click to collapse
I flashed the new version, boot splash now lasts much less, so the phone boots faster [emoji1] [emoji1]
Jonas Cardoso said:
Update twrp to 3.0.2-0
https://www.androidfilehost.com/?fid=24499762636002461
Click to expand...
Click to collapse
Filename is with p700. Is it good for p705?
Any problem for installing p705 ROM with this recovery? TIA!
Thanks for your hard work as always!! :good::good:
ecapella said:
Filename is with p700. Is it good for p705?
Any problem for installing p705 ROM with this recovery? TIA!
Thanks for your hard work as always!! :good::good:
Click to expand...
Click to collapse
You have no problem, only if you have the misidentification of the zip rom change in the script to the P705 that will work
Related
Team Win Recovery Project is a custom recovery built with ease of use and customization in mind. It has a fully touch driven user interface. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
Installation/updating instructions and download links can be found on official device page. It is preferred to use official builds unless it is said otherwise in thread, so make sure you have read at least a couple of last pages.
My home builds can be downloaded here (link to the always latest build), it is useful when the latest official build is outdated and for testing new features. Site may sometimes be down due to maintenance.
And, as you remember, we are not responsible for bricked devices, accidental pregnancy or asteroid impact (BTW, this thread is created at Asteroid day).
Warning! Read attentively this post and F.A.Q. below and at least 5 pages of thread before installing this and posting here! Or Dark Lord will come to punish you and take your shallow soul! Also I kill innocent kittens every time when I see someone installs it via fastboot/flashtool. So save kittens and don't ignore provided info.
It uses the same FOTAKernel install method as recoveries in this thread, so you don't need to install it every time you change your ROM or kernel. Also it doesn't work on stock ROM, 'cause we don't have stock kernels supporting extract_elf_ramdisk utility.
To remove recovery from your FOTAKernel follow this (you will use recovery from your boot image after it).
Official TWRP website — here you can find more info about recovery itself, versions changelog, donation URL etc.
Thanks to:
@Dees_Troy and all other TWRP devs
@PecanCM for initial device tree
Linus Torvalds for Linux Kernel, it would not be possible without him
XDA:DevDB Information
TWRP for Xperia M, Tool/Utility for the Sony Xperia M
Contributors
cucumber09, Antrikos48
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.0.1-0
Created 2015-06-30
Last Updated 2016-09-15
F.A.Q. Must be read before installing and posting in the thread!
Q: Is it a kernel?
A: No, it isn't. It is a recovery image, but it is not booting independently, the kernel is using its ramdisk to load recovery. More... (extract_elf_ramdisk is deprecated in some ROMs and kernels, now its functions are implemented in init binary directly, read additional explanation from the next question if you are curious about how it works)
Q: Can I install it via Flashtool/fastboot?
A: No. For holy sake, don't do this! Here is explanation.
Q: Can I flash it with Rashr app?
A: Yes. But flash it as recovery, not as kernel! Read explanation above if you wonder why.
Q: Do I need to flash it every time I update my ROM?
A: No.
Q: Does it work with stock ROM?
A: No.
Q: TWRP says "Unmodified system partition" and asks to allow modifications or keep system read-only.
A: Tick "Never ask" and swipe. You can press "Keep read-only", but that really has no use on our device as we no more receive official OTA and ^look previous question^.
CHANGELOG
TWRP 3.0.1-0
support new CM 13.0 pattern encryption (sultanqasim)
fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
libtar updated to latest upstream and fixes (jcadduono)
fixes for loading custom themes (_that)
TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
translation updates - added Italian, Czech and Polish and significant updates to Dutch
progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
fix input box text display (Dees_Troy)
reboot option after zip install complete (bigbiff)
other mostly invisible bug fixes and improvements
Click to expand...
Click to collapse
TWRP 3.0.0-0
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse
Device-specific changes:
Enabled mass storage
Improved wiping cache speed and removed it from backup list
Increased system wipe speed
Update crypto from JB to current version for adopted storage decryption (1, 2)
Enabled NTFS-3g
Other fixes and improvements (commit history for nicki)
Yes! Yes!
Sir I have 2.8.5.0
can I flash 2.8.7.0 now, forgive me I'm not experience.
Thank you for your efforts[emoji2]
Sent from my C2005 using Tapatalk
Yeay!
Thanks buddy
Try it nowwwwww !!!!!
Sent from my waifu
kh34d said:
Sir I have 2.8.5.0
can I flash 2.8.7.0 now, forgive me I'm not experience.
Thank you for your efforts[emoji2]
Sent from my C2005 using Tapatalk
Click to expand...
Click to collapse
Yes, of course. There is link to instruction in OP.
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
Click to expand...
Click to collapse
I still not understand with resize2fs ?
My question is how to resize my 1gb system to 700mb and move 300mb to /data?
Sent from my waifu
itsnie said:
I still not understand with resize2fs ?
My question is how to resize my 1gb system to 700mb and move 300mb to /data?
Sent from my waifu
Click to expand...
Click to collapse
You are confusing it with repartitioning. Lollipop uses block-based OTA. Some of devices have versions with different storage capacity (e.g. 16 and 32 Gb). And when you install system image for the device with 16 Gb on device with 32 Gb you will have system partition like in 16Gb-version. Also, sometimes custom ROMs' system image is a little bit "cut". So, resize2fs fixes it, you will have as many system storage, as can handle your system partition. And this function is not very useful for our device.
cucumber09 said:
You are confusing it with repartitioning. Lollipop uses block-based OTA. Some of devices have versions with different storage capacity (e.g. 16 and 32 Gb). And when you install system image for the device with 16 Gb on device with 32 Gb you will have system partition like in 16Gb-version. Also, sometimes custom ROMs' system image is a little bit "cut". So, resize2fs fixes it, you will have as many system storage, as can handle your system partition. And this function is not very useful for our device.
Click to expand...
Click to collapse
Woah thngs!
Sent from my waifu
Why I can't find nicki in app?
Sent from my C2005 using XDA Free mobile app
arell said:
Why I can't find nicki in app?
Sent from my C2005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I forgot to mention, in some reason there is no Xperia M in app's list. I'll e-mail app's devs tomorrow if it won't appear.
hi
this recovery work in stock roms?
Miladj said:
this recovery work in stock roms?
Click to expand...
Click to collapse
Yes it will work I think, if you on unlocked bootloader condition
Sent from my C1905 using Tapatalk
Ok ,but can I use ZIP file in other thread or IMG file here??
There is two file now am I right??
Sent from my C2005 using Tapatalk
Nicklas Van Dam said:
Yes it will work I think, if you on unlocked bootloader condition
Sent from my C1905 using Tapatalk
Click to expand...
Click to collapse
not working!
Miladj said:
not working!
Click to expand...
Click to collapse
Calm down bro, why not working? You have to flash it with dd command right? And after that are you see some led pink when you restart device ?
Sent from my C1905 using Tapatalk
Finally its official!! All your hard work has paid off. .
Thanks a lot & congrats @cucumber09.
kh34d said:
Ok ,but can I use ZIP file in other thread or IMG file here??
There is two file now am I right??
Sent from my C2005 using Tapatalk
Click to expand...
Click to collapse
You can use both of them, if zip you must flash it via recovery mode but if boot.img you must flash it via adb with command dd if
Sent from my C1905 using Tapatalk
---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------
Nicklas Van Dam said:
Calm down bro, why not working? You have to flash it with dd command right? And after that are you see some led pink when you restart device ?
Sent from my C1905 using Tapatalk
Click to expand...
Click to collapse
If all what I said is still not working, you must flash old twrp boot.img that have function like recovery but not in fota partition. I've that file if you want it . but please try it before and calm down OK [emoji4]
Sent from my C1905 using Tapatalk
Miladj said:
this recovery work in stock roms?
Click to expand...
Click to collapse
Please, read the OP. It is clearly stated there:
Also it doesn't work on stock ROM, 'cause we don't have stock kernels supporting extract_elf_ramdisk utility.
Click to expand...
Click to collapse
So, stock is not supported, 'till someone builds stock kernel with all needed changes.
kh34d said:
Ok ,but can I use ZIP file in other thread or IMG file here??
There is two file now am I right??
Click to expand...
Click to collapse
Recovery in zip in other topic is compiled on my PC. Image file on TWRP download server is compiled by official TWRP build-bot. There is no difference in them, 'cause they share the same source code (but maybe official TWRP build uses a little bit older code, snapshoot when current version was released).
{
"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"
}
TeamWin's TWRP Touch Recovery for LG Optimus G (geehrc).
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 from Play Store or flash in your current recovery. Otherwise use adb.
Remember to do backup of your current recovery before installing.
Changes:
compiled on omnirom-7.1 source
latest twrp updates included
updated device trees
prebuilt kernel
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 modem backup
Download Links:
TWRP-3.0.0-0: geehrc
Device Source:
https://github.com/Split-Screen/android_device_lge_geehrc
https://github.com/TeamHorizon/android_kernel_lge_gee
XDA:DevDB Information
Unofficial TWRP-3.0.3-3 for LG Optimus G variants by dadi11, Tool/Utility for the LG Optimus G
Contributors
dadi11
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2016-02-06
Last Updated 2017-01-27
Reserved
Changelog:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse
E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')
Great work! Im new to this how do i install it?
enapah said:
E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')
Click to expand...
Click to collapse
I have the same errors
can someone create a flashable zip?
@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".
Guys sorry for errors. I have no OG anymore but still wanted to release something for you guys! I will try to fix it and release update in some minutes
please download and try this one: https://mirrors.c0urier.net/android/Dadi11/TWRP/TWRP-3.0.0-0_GEEHRC.img
enapah said:
@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".
Click to expand...
Click to collapse
He can easily flash TWRP or CWM by using FreeGee App.
I have done this 10minutes ago.
---------- Post added at 08:31 PM ---------- Previous post was at 08:16 PM ----------
Now recovery is working very well!
AROMA Installers are working too
pawelelos said:
Now recovery is working very well!
AROMA Installers are working too
Click to expand...
Click to collapse
Thanks for confirmation
good job
Thanks dadi11. Very generous, especially considering LGOG is not your primary device anymore.
@dadi11 Thank you very much for your time, specially given this is no longer a device at your hand.
I do have one "small" request to make, for those of us who run the official CM builds, it would mean the world to us if we had an image with e975 as device name (instead of geehrc). Any chance you could make one extra build?
Code:
ro.build.product=e975
ro.product.model=LG-E975
ro.product.device=e975
Stable, not bugs:
http://xyyx.ga/nitrogen-os/geehrc/twrp-geehrc-3.0.0.zip
File manager doesn't work properly, cannot list contents in some folders (ex: system)
hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it
gledis96 said:
hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it
Click to expand...
Click to collapse
Install as any other zip, then chose reboot recovery from ur recovery which u use.
tiennhu89 said:
Install as any other zip, then chose reboot recovery from ur recovery which u use.
Click to expand...
Click to collapse
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now
gledis96 said:
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now
Click to expand...
Click to collapse
Ok.u r wellcome.☺
tiennhu89 said:
Ok.u r wellcome.
Click to expand...
Click to collapse
another thing do you know how to install xposed cause i tried flashing it but my phone gets stuck in boot i have this rom
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-aosp-5-1-1r8-optimus-g-t3160195
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[dora] TWRP 3.0.2-0 touch recovery, Tool/Utility for the Sony Xperia X Performance
Contributors
AndroPlus
Version Information
Status: Stable
Created 2016-10-08
Last Updated 2016-10-08
Wow that's good news! Hoping to see twrp support for full X-series
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
AndroPlus said:
Now it's official
Click to expand...
Click to collapse
Great! Now we need to wait root on locked bootloader but it can be very looooong waitng
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Hi AndroPlus,
Is that means your future builds will be also compatible with xperia XP, specially and as i known the XP and XZ has about the same processor (core)? Or you will abandon the XP definitively [emoji22].
And another question: as i now have an xperia XP for about 1 month, and i decided now to rooting it with the help of your modified kernel, is it confirmed that the kernel will contouring the consequences of deleting the DRM keys a cause of unlocking bootloader and leading to restore the functionality (or at least most of them) of DRM features?.
Thanks
Envoyé de mon Xperia x performance
baha76_s said:
Hi AndroPlus,
Is that means your future builds will be also compatible with xperia XP, specially and as i known the XP and XZ has about the same processor (core)? Or you will abandon the XP definitively [emoji22].
And another question: as i now have an xperia XP for about 1 month, and i decided now to rooting it with the help of your modified kernel, is it confirmed that the kernel will contouring the consequences of deleting the DRM keys a cause of unlocking bootloader and leading to restore the functionality (or at least most of them) of DRM features?.
Thanks
Envoyé de mon Xperia x performance
Click to expand...
Click to collapse
I'll continue building kernel for XP even after buying XZ
DRM function restore is working well for XP with my kernel.
AndroPlus said:
I'll continue building kernel for XP even after buying XZ
DRM function restore is working well for XP with my kernel.
Click to expand...
Click to collapse
Thank you very much for your reply.
I'm glad to hear that you will continue the development for this flag.
And final question: is there any chance that you will find a way to modify the kernel in android 7 (nougat) in this flag?, specially as i read that the new android 7 core has a new feature to detect any changes in W/R status of the system partition and leading to become the (boot.img) inaccessible and consider as corrupted file, i.e more secure options to kernel level.
Thanks
Envoyé de mon Xperia x performance
baha76_s said:
Thank you very much for your reply.
I'm glad to hear that you will continue the development for this flag.
And final question: is there any chance that you will find a way to modify the kernel in android 7 (nougat) in this flag?, specially as i read that the new android 7 core has a new feature to detect any changes in W/R status of the system partition and leading to become the (boot.img) inaccessible and consider as corrupted file, i.e more secure options to kernel level.
Thanks
Envoyé de mon Xperia x performance
Click to expand...
Click to collapse
I think it can be disabled in kernel.
Let's wait 7.0 for our device...
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Was hoping for an other answer but I can understand your decision! It's nice to see some support for the xp & XZ, keep up the good work!
Verstuurd vanaf mijn F5121 met Tapatalk
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Hi, do you think this variant will work for the Sony X (not Performance) too?
I had some bad experiences flashing TWRP (i.e. with TWRP for Huawei M2, that wasn't suitable for the European device, only the Chinese one, leading to a bootloop) - I guess X and X Perf. aren't too different, but I'd like to make sure it fits
Thanks!!
xtools said:
Hi, do you think this variant will work for the Sony X (not Performance) too?
I had some bad experiences flashing TWRP (i.e. with TWRP for Huawei M2, that wasn't suitable for the European device, only the Chinese one, leading to a bootloop) - I guess X and X Perf. aren't too different, but I'd like to make sure it fits
Thanks!!
Click to expand...
Click to collapse
X has different SoC, so it won't work...
AndroPlus said:
X has different SoC, so it won't work...
Click to expand...
Click to collapse
So twrp for the x compact should/could work for the x? They have the same soc
kistigun said:
So twrp for the x compact should/could work for the x? They have the same soc
Click to expand...
Click to collapse
Maybe.
AndroPlus said:
Maybe.
Click to expand...
Click to collapse
okey, would like to test this. If it's not compatible could I just restore everything by reflashing original firmware ftf from sony?
kistigun said:
okey, would like to test this. If it's not compatible could I just restore everything by reflashing original firmware ftf from sony?
Click to expand...
Click to collapse
Yes, you can restore stock recovery by flashing FTF (FOTAKernel is recovery)
@AndroPlus bro, I can't get it working on my F8131 (custom kernel, not yours).
This is the flashing output:
Code:
[B][I][COLOR="Blue"]fastboot flash recovery twrp-3.0.2-0-dora.img[/COLOR][/I][/B]
target reported max download size of 268435456 bytes
sending 'recovery' (20600 KB)...
OKAY [ 0.638s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.797s
Combo keys (Power + Volume Down) turn device off after the "Your device has been unlocked..." message (and before sony logo shows up)!
Am I doing something wrong or forgetting something?
Btw, if I try to just boot into twrp while in fastboot, I get this error:
Code:
[B][I][COLOR="blue"]fastboot boot twrp-3.0.2-0-dora.img[/COLOR][/I][/B]
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
[B][COLOR="Red"]FAILED (remote: dtb not found)[/COLOR][/B]
finished. total time: 1.068s
Thanks in advance!
serajr said:
@AndroPlus bro, I can't get it working on my F8131 (custom kernel, not yours).
Click to expand...
Click to collapse
Try to use my TWRP for MultiROM, it's fully functional from hardware recovery boot too.
Adrian DC said:
Try to use my TWRP for MultiROM, it's fully functional from hardware recovery boot too.
Click to expand...
Click to collapse
And it did work flawlessly at first try (downloaded multirom-20161116-recovery-fota-dora.zip > extracted twrp.img > fastboot flash recovery twrp.img)!
Thank you so much!! :highfive:
It really looks like Androplus needs to fix something on this!
hmm, maybe I missed something... when I build TWRP on my own, it's working.
I'll look into it.
AndroPlus said:
hmm, maybe I missed something... when I build TWRP on my own, it's working.
I'll look into it.
Click to expand...
Click to collapse
Thank you!
We're all waiting for that, once this is the official one!
tbalden's
CleanSlate kernel
for HTC U11+
The User Experience Kernel leaning towards Stock Stability plus UX features.
Stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"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"
}
Version 1.7.13 - 25 Sep, 2018
Version 1.7.6 - 15 Mar, 2018
Version 1.7.1 - 4 of Jan, 2018
Version 1.7.0 beta1 - 1 of Jan, 2018
Version 1.0.0 - 14 of Dec, 2017
Works on Stock/Custom ROM bases Oreo from 1.05 to 1.24 (TW U11+ base kernel source)
Features:
- WireGuard VPN Thread here But go to the wireguard IRC for help!
- Supported with CleanSlate companion app and CleanSlate Configuration app - requires no root permission! check downloads+
- Squeeze Control (Wake,Peek,Sleep,Swipe)
- Fingerprint doubletap sleep
- Backlight dimmer
- K.AdAway - kernel adblocking feature for browsing and in app (not for youtube stream etc)
- Smart Notification Control
- Flashlight Notification
- Vibrating Notification Reminder
- Notification Booster on vibrating notifications when screen is off
- Gradient battery charging led turning from amber to green based on battery level percentage, then at full charge it starts to smoothly change from full bright green to golden and the back to full green cycling, signalling 100% battery for easy spotting
- Fading notification led fading/pulsating type notification LED blinking
- Upper grill RGB LED light brightness level you can lower the brightness level of the upper grill RGB led now
- Adrenoboost version 2.2 - smooth gaming, battery friendly, fixing GPU handling of stock HTC kernel -- battery friendly conservative governor. Three levels (1 is the most battery friendly), and off state.
- Wakelock reduction patch by fransiscofranco
- NTFS/ReadWrite
- Hacked texfat loading for all ROM bases to work with sdcard
- doesn't modify system partition. Androidpay should work on phones with stock system image
Facts:
- built on top of kernel sources released on htcdev
- built with standard toolchain for stability and efficiency
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Squeeze control:
Pulsating notification LED video:
Flashlight notification
Chromatic gradient colors for battery percentages while charging..
Will gently pulse green when reaching 100%
Requirements
- Unlocked HTC U11+ with TWRP and sideloaded kernel ZIP on external SDCard. No need to decrypt data or system (FOR NOW EVEN AVOID THAT ON U11+ UNOFFICIAL TWRP)
- BACKUP: make sure you backed up your original Boot partition in TWRP, before installing this! Installer only modifies BOOT (kernel zImage)
- INSTALL: Side load, or install the zip from your external sdcard through TWRP
- Reboot.
- CHECK THIS DESCRIPTION FOR SAFE WAY: https://forum.xda-developers.com/showpost.php?p=74875149&postcount=14 --- DO NOT DECRYPT YOUR DATA PARTITION!! IT WILL BE LOST WITH UNOFFICIAL U11+ TWRP.
-- If not using PlayStore Donation apps, then install CleanSlateCompanion-x.y.z.apk / CleanSlateConfig-x.y.z.apk from SDCARD (copied by installer if internal memory was mounted) Please grant Notification Access and the permission to read/write SDCard, read phone call status.
------ !! IF YOU UPDATED THE COMPANION APP, Don't forget to Open it again as well after update !!
--- use CS Configuration App to configure stuff without rooting
Companion application writes /sdcard/uci_sys.cfg to communicate with kernel, you'll find it there after first running the app, don't delete it.
Known bugs:
- None (so far), you tell
Download
1.7.13 -- For Bases 1.05-1.24 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=1322778262904013428
1.7.12 -- For Bases 1.05-1.24 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=890278863836291339
1.7.8 -- For Bases 1.05-1.24 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=962339331458991743
1.7.7 -- For Bases 1.05-1.24 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=673956719939827567
1.7.6 -- For Bases 1.05-1.24 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=890129502657585045
1.7.3 -- For Bases 1.05-1.24 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=746010030569948224
1.7.2 -- For Bases 1.05-1.24 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=673791459329072009
1.7.1 -- For Bases 1.05-1.23 installer for TWRP:
Installer flashable: https://www.androidfilehost.com/?fid=745849072291698678
Companion App 1.5.6 -- Donation premium version from PlayStore here: https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 1.10.9 -- Donation premium on playstore:
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
Companion App 1.5.6 -- Normal free download: https://www.androidfilehost.com/?fid=889964283620775783
Configuration App 1.10.9 -- Normal free download: https://www.androidfilehost.com/?fid=890278863836284924
Donation:
If you appreciate this, don't forget to hit the Thanks button, Vote 5 stars on Thread, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
Src: https://github.com/tbalden/htc-kernel-ocm
Special thanks to AnyKernel installer developer: osm0sis
To @Captain_Throwback
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.
XDA:DevDB Information
tbalden's CleanSlate kernel for HTC U11+, Kernel for the HTC U11+
Contributors
tbalden
Source Code: https://github.com/tbalden/htc-kernel-ocean/commits/master_oreo
Kernel Special Features: UX features
Version Information
Status: Testing
Current Stable Version: 1.7.13
Stable Release Date: 2018-09-25
Created 2017-12-14
Last Updated 2018-09-24
Changelogs
Release Stable 1.7.1 - 2018-01-04
Release Beta 1 - 2018-01-01
Pre-alpha 1 / 2 /3 - 2017-12-14
Read more about all the features in the U11 thread here:
https://forum.xda-developers.com/u11/development/kernel-cleanslate-v1-0-t3623310
"Teaser" video from u11:
[/B]
If anyone brave enough, backup, flash, test and report
I don't have this wonderful device yet.
Planning on adding more features gradually, to keep stable
I will as soon as I get my u11+ thank you
I am gonna get soon as well , whenever come to india, looking to update from htc 10 and using your kernel as well
As long as there are HTC Flagship phones, I hope there will always be Clean Slate Kernel
Awaiting my U11+, still in backorder..:crying:
When i have it for sure i will try and come back to you..
Great, good to know there's interest. I'm not yet sure if I'll be able to purchase one for easier development and the excellent phone experience, but I'll try to manage this based on your feedback till then.
Already have a little fix to add based on u11 experience, and adding rootless kcal color control config possibility with cleanslate configuration application.
Today or tomorrow I'll patch it up and share here
Update 1.0.1
- add unrooted configuration for KCal with CleanSlate Kernel Configuration app
- fixed magisk booting problem
https://www.androidfilehost.com/?fid=673791459329067613
Thanks to xda for the mention! https://www.xda-developers.com/htc-u11-kernel-source-cleanslate-kernel/
tbalden said:
Thanks to xda for the mention! https://www.xda-developers.com/htc-u11-kernel-source-cleanslate-kernel/
Click to expand...
Click to collapse
That is awesome!! Congrats! I am going to flash today once I get the courage to do so because of recovery issues we have at the moment. I'll have to try flash fire. Or if you know a fastboot way or adb I can do?
cameljockey1 said:
That is awesome!! Congrats! I am going to flash today once I get the courage to do so because of recovery issues we have at the moment. I'll have to try flash fire. Or if you know a fastboot way or adb I can do?
Click to expand...
Click to collapse
Firstly getting a recovery partition for the exact base you have, don't know if it's already listed somewhere. So you can get back to stock recovery for ota.
Then for flashing
Putting in an sdcard, careful to not mounting data, and backup to external sdcard and also flash from there.
@nkk71 I think that already possible and doesn't hurt phone system. Right?:angel:
tbalden said:
Firstly getting a recovery partition for the exact base you have, don't know if it's already listed somewhere. So you can get back to stock recovery for ota.
Then for flashing
Putting in an sdcard, careful to not mounting system, and backup to external sdcard and also flash from there.
@nkk71 I think that already possible and doesn't hurt phone system. Right?:angel:
Click to expand...
Click to collapse
If you mean the *no longer decryptable data partition in booted ROM*, then it still eludes me, but seems to get triggered any time twrp tries to decrypt it (doesn't matter whether successful or failed).
Though TWRP is able to decrypt it successfully (even when the ROM no longer *wants*), so the data is recoverable, but will cause a headache since data/media isn't backed up.
TWRP itself isn't triggering verity, I'm assuming when vold_decrypt is running for some reason, a *key upgrade* is triggered leading the ROM to no longer be able to (or rather allow) userdata to be decrypted.
I've never used FlashFire to be able to give any opinion about it.
If using TWRP, using external sdcard as you mentioned is a good idea, but in addition data decryption should not even be attempted, so I think the following would be safe:
1- Set a PIN on boot in the ROM
2- Reboot and confirm all is OK
3- Flash TWRP
4- When entering TWRP you will be prompted for a password, CANCEL THAT PROMPT
If you even attempt any decrypt the ROM will likely no longer decrypt data
5- Once you've cancelled the decrypt prompt, you can go ahead and safely backup and/or flash from external sdcard
PS: and as you mentioned, when prompted whether to allow system modifications choose NO. Keep system mounted read only.
Thanks @nkk71
uhm, must be my general messing up basic terms time to time, I meant to mention the data partition , but my idea was this what you described. Good that in the end system partition came up. Indeed it is essential to keep it intact for ota, or backup intact system image to external card
Good to see you here @tbalden. Would you spoiler what you have in the Pipeline for the beautiful U11+?
Cryptycat7 said:
Good to see you here @tbalden. Would you spoiler what you have in the Pipeline for the beautiful U11+?
Click to expand...
Click to collapse
All cleanslate features from the u11 which is possible.
Check my signature for what's there on the u11.
I'll need more feedback yet on the first release, but hopefully the recent shipping happening in UK will boost the scene around here
tbalden said:
All cleanslate features from the u11 which is possible.
Check my signature for what's there on the u11.
I'll need more feedback yet on the first release, but hopefully the recent shipping happening in UK will boost the scene around here
Click to expand...
Click to collapse
Thanks for the lightning fast reply. I am from Germany and pre-ordered my U11+ directly from HTC, it arrived today.
Cryptycat7 said:
Thanks for the lightning fast reply. I am from Germany and pre-ordered my U11+ directly from HTC, it arrived today.
Click to expand...
Click to collapse
Cool ?
I wish I'd meet the device in real life someday. I hate to develop blindly but I hope the similarities will help.
But it's too much for the budget at the moment, with two u11s this year. :laugh:
Anyway it's good that @nkk71 helped describing a way to stay safe with kernel flashing. I hope it's gonna work out without sacrificing safe upgrade ota possibility.
Cheers
tbalden said:
Cool ?
I wish I'd meet the device in real life someday. I hate to develop blindly but I hope the similarities will help.
But it's too much for the budget at the moment, with two u11s this year. :laugh:
Anyway it's good that @nkk71 helped describing a way to stay safe with kernel flashing. I hope it's gonna work out without sacrificing safe upgrade ota possibility.
Cheers
Click to expand...
Click to collapse
Wow you are supporting a device, that you don't own, that's very generous. Thank you very much and keep doing what you are doing.
{
"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"
}
PixelExperience for Xiaomi Mi 5 [Gemini]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wifi
Wifi hotspot
RIL
Mobile data
GPS
Sensors
Camera
Flashlight
Camcorder
Bluetooth
NFC/GPAY
Lights
Sound / vibration
Fingerprint
WiFi Display
VoLTE
Double Tap To Wake
Buttons swap
Google Voice Match
SELinux enforcing
Safetynet
DON'T FLASH GAPPS, ALREADY INCLUDED
Download standard version from Android File Host
Download PLUS version from Android File Host
Flashing Instructions:
Pre-installation:
Pixel Experience Recovery (Download from here)
First time installation:
Fastboot or flash recovery image
Reboot to new recovery
Click on Factory Reset --> Format data/factory reset
Click on apply update and sideload the zip file or install it using an USB OTG
Enjoy
About Camera App: default camera app is GCAM version SGCAM_8.4.400.42.XXX_STABLE_V35 by Shamim. Everything works fine except 240 fps (1/8) slow motion videos
mandayugana shared his config xml file, which add the specific noise model for Gemini with Shamim GCAM, dowload it from my Github (sgcam-8.4-v35-pe13.xml) or from his post, apply to GCAM following this tutorial and say thanks to him for his great work
XDA:DevDB Information
Pixel Experience, ROM for the Xiaomi Mi 5
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
ROM Firmware Required: MIUI V10.2.2.0.OAAMIXM as minimum target
Based On: AOSP
Source Kernel repo: Link
Gemini device tree repo: Link
Xiaomi msm8996-common repo: Link
Vendor repo: Link
Special thanks to
LineageOS
Pixel Experience
Shamim
xNombre
mandayugana
I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)
ademuhamad said:
I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)
Click to expand...
Click to collapse
I haven't tried but could work. Just be sure to format internal storage before rebooting into system
the rom is very laggy, and cpu usage between 50%-100% with nothing open :/
Echidna_Kawaii said:
the rom is very laggy, and cpu usage between 50%-100% with nothing open :/
Click to expand...
Click to collapse
Check what process is eating your cpu in the background, i have no problems at all with cpu usage on screen and with deep sleep
and also this giving Random reboot here :/
Echidna_Kawaii said:
and also this giving Random reboot here :/
Click to expand...
Click to collapse
No one reported random reboots, i never had once in a week of usage. Logs or never happened
-+BB+- said:
I haven't tried but could work. Just be sure to format internal storage before rebooting into system
Click to expand...
Click to collapse
ERROR:1 )l
暗夜很无语 said:
ERROR:1 )l
Click to expand...
Click to collapse
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery
pretty much very stable rom... working everything very smothly...but one issue...after usung 1 or 2 shot with gcam its freeze the cam...and then can't open the gcam anymore...
Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.
after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time
İST1907 said:
Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.
Click to expand...
Click to collapse
Could you please post the log of the error during the flash?
mrinfinity0007 said:
after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time
Click to expand...
Click to collapse
1 and 5 are AOSP/PE bugs, hopefully will be fixed in QPR2 release
2 don't use Gcam for now, i've fixed hdr+ photos on recent Gcam version in my internal builds but it's still crashing causing a reboot after a minute, i had no time to inspect yet because i was focused on EAS and power HAL port
3 correct, no OTA update app on unofficial builds
4 i'm not 100% sure but if i remember well it's a feature of plus version
@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.
JackSlaterIV said:
@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.
Click to expand...
Click to collapse
Unfortunately Pixel Experience doesn't support natively TWRP compiling, and i don't have space on my NVME for another build enviroment. Also as far as i know they did not release yet an Android 13 recovery, they are working right now on it, but i don't know if works. Do you know if TWRP supports FBE on other devices? if TWRP supports FBE then best thing would be compile TWRP in an Android 12 build enviroment with a 4.4 kernel with FBE support. you can use my repos or los repos, it' the same. The only requested changes are a makefile with a basic conf for mi5 and convert the fstab in a compatible version for TWRP
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive
@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.
-+BB+- said:
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery
Click to expand...
Click to collapse
Let me try another TWRP version
-+BB+- said:
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive
Click to expand...
Click to collapse
i don't root my phone? does it work without it?
JackSlaterIV said:
@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.
Click to expand...
Click to collapse
I will take a look this weekend and let you know because I don't remember where but I'm pretty sure that I read a tutorial for TWRP compiling some years ago
暗夜很无语 said:
Let me try another TWRP version
Click to expand...
Click to collapse
If your goal is to flash the ROM without format the internal memory won't work, you may be able to flash the zip but after the flash you'll be forced to format the internal memory without fbe support
mrinfinity0007 said:
i don't root my phone? does it work without it?
Click to expand...
Click to collapse
Yes it's a root shell, you have root permissions only with ADB, not in your phone. If you want to roll back to selinux enforcing and stop the rooted shell simply reboot the phone, that changes doesn't survive after the reboot
@JackSlaterIV found it, it's old and some things may be slightly different but this is a good tutorial.
Here's the link of the minimal manifest 12.1 is the correct branch but decryption is WIP at the moment, don' t think will work, unless you don't set a password/PIN/pattern, in that way should be fine
@mrinfinity0007 never mind, i've fixed It, Gcam was crashing because it was trying to use hexagon for HDR+, but SELinux was blocking it. Now it's wotking fine even in enforcing mode
PS: i've decided to upload the latest personal build i made, some thing may change because i'm still testing them, but more or less (on device side) this will be the next official release when PE devs will merge QPR2 changes and feb security patch.
Here's the direct link
And here's the changelog:
ROM:
- Synced code with latest PE changes
Kernel
- Ported EAS and set it as default scheduler
- Ported Stune Boost and use it as default
- Fixed almost all compiling warns
- Ported misc optimisations from infinity kernel
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
- Misc fixes from upstream
Recovery
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
Device Tree
- Ported EAS
- Move to EAS compatible power HAL
- QCOM audio HAL: add missing audio power hints support
- Fixed Google Camera crash when trying to use Hexagon
- Camera: move to Gcam Version MGC_8.1.101_A9_GV2b_ENG big thanks to BSG. Camera can be updated with all APKs released by BSG, just be sure to download the ENG version
- SELinux: fixed all denials
- Ported various improvements from my old 12.1 ROM
- Tuned ZRAM size for 3Gb devices
- Camera: improved camera HAL + misc fixes
- Configure SQLite to operate in MEMORY mode
- Set CFQ as default scheduler
- Added pixel animated wallpapers to build
For more detailed changes take a look at my repos
PS: i cannot test GPAY at the moment because i'm testing other things and i'm running in permissive mode, if someone decide to try the update and use GPAY please let me know if works, i made some changes to sepolicy and i want to be 100% sure that Google pay isn't broken before the official release.