Develop Bugs

[Recovery][Official]TWRP for Xperia M

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).

[RECOVERY][GEEHRC] TWRP-3.0.3-3

{
"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

[Recovery] TWRP 3.0.2-0 for L7(P700/P705/P708)

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

[ROM][10.0][XZ2] Pixel Experience for Xperia XZ2 (akari) [AOSP][2020/02/21]

{
"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 the Sony Xperia XZ2 akari
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 and useful features for the proper functioning of the device
Based on Android 10.0
Whats working?
Wifi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Sony Open Devices bug tracker
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website (Xperia XZ2 Single Sim)
Download from Pixel Experience website (Xperia XZ2 Dual Sim)
Flash instructions and special recovery coming on Monday 24/02/2020
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Sony Specified Telegram channel
Our blog​
Android OS version: 10.0.0_r27
Security patch level: February 2020
Build author/Device Maintainer: fastbooking
Device Source code: https://github.com/PixelExperience-Devices/device_sony_customization
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
​

flash instructions? i think twrp is needed and we currently don't have it

nikkdib said:
flash instructions? i think twrp is needed and we currently don't have it
Click to expand...
Click to collapse
Detailed instructions on Pixel site. There are ROMs for many models, including 8314 and 8324. Yes, it seems that TWRP is needed, and it also seems that someone somewhere has managed to develop one for Q...
********** IMPORTANT: README **********
### Be sure to have the latest ODM, even when you get a OTA!!! ###
To get this ROM and the OTA updater to work fine, you NEED TO follow a few steps:
1. Download Androxyde's FlashTool
2. Flash the latest STOCK firmware for your device, in order to get a
bootloader bugfix for unlocked A/B
3. Before flashing this ROM through your favorite recovery environment,
you *HAVE TO* flash the latest Sony Open Devices binaries for
your device through fastboot. They cannot be distributed in this
zip package because you have to accept their EULA.
** Make sure you flash the Sony ODM image to both slots:
fastboot flash oem_a SW_binaries_for_Xperia_Android_(blahblah)
fastboot flash oem_b SW_binaries_for_Xperia_Android_(blahblah)
P.S.: If you get signature verification errors on TWRP, remember to
disable package signature verification in the TWRP settings!!!
Useful links:
## Androxyde's Flashtool: http://www.flashtool.net/
## Sony ODM binaries:
https://developer.sony.com/develop/open-devices/downloads/software-binaries/

Hey there ! On the previous -beta ish- builds, you have to decompile the zip and all to get the bootimage to flash the zip
Starting monday, I'll distribute a bootimage where you can go to aosp recovery, and flash the rom via sideload.
 @Anti-root @nikkdib

fastbooking said:
Hey there ! On the previous -beta ish- builds, you have to decompile the zip and all to get the bootimage to flash the zip
Starting monday, I'll distribute a bootimage where you can go to aosp recovery, and flash the rom via sideload.
@Anti-root @nikkdib
Click to expand...
Click to collapse
Thank you! I am using Pixel ROM for my OP5, after trying all possible ROMS (there's many) and all possible kernels (there's many) and all possible cameras (there's many), and I can say that its simplicity and smoothness and speed are second to none! My battery drain when idle is 0.12% etc. etc. Let's hope that something similar is cooked for us here!
My XZ2C (H8314) is running android 9, it is rooted but without TWRP, since one has not been available for this phone, debloated, and running without the slightest problem. But, I would try the Pixel! (if you make it available also for the XZ2C).

Anti-root said:
Thank you! I am using Pixel ROM for my OP5, after trying all possible ROMS (there's many) and all possible kernels (there's many) and all possible cameras (there's many), and I can say that its simplicity and smoothness and speed are second to none! My battery drain when idle is 0.12% etc. etc. Let's hope that something similar is cooked for us here!
My XZ2C (H8314) is running android 9, it is rooted but without TWRP, since one has not been available for this phone, debloated, and running without the slightest problem. But, I would try the Pixel! (if you make it available also for the XZ2C).
Click to expand...
Click to collapse
Hey !
Well you have many ROMs available for your OP5 because people is using the same base for builds and it's very easy.
On sod we have an OSS tree.
Which gets constant upgrades and changes, this means that I'll build more than once a month.
Also there's special stuff to do, I'll write them on Monday when the needed oem release come out.
The advantage of this tree is that you can build any ROM pretty much very easily with minimal differences, just like other devices and it's with this process that I decided to settle for PE and maintain it

It happened for the second time for the phone to charge normally without being disconnected regularly. I took logs this time maybe it's helpful to you.
https://mega.nz/#!mkERWKgR!txl1b2HYCtiUl_fKhoCWjQ3m1O1GpvngzwsUQWnDGRU
Sent from my Xperia XZ2 Dual (AOSP) using Tapatalk

ASMstudent said:
It happened for the second time for the phone to charge normally without being disconnected regularly. I took logs this time maybe it's helpful to you.
https://mega.nz/#!mkERWKgR!txl1b2HYCtiUl_fKhoCWjQ3m1O1GpvngzwsUQWnDGRU
Sent from my Xperia XZ2 Dual (AOSP) using Tapatalk
Click to expand...
Click to collapse
Hi !
Thanks for the report, although, if you're using a Quick Charge 1/2/3 charger, it's normal because the charger tries to ramp up the voltage but the device refuses because those chargers aren't supported and it may damage your battery.
I recommend you using a standard 5V1A/1.5A charger or a USB Power Delivery charger.
Cheers !

It's working. But I also have a trouble with a wireless charger. It just didn't charge. Phone says "Pluged, didn't charging". I'm using Sony official qc charger and mi wireless charger pad. Type c in is broken.
Charging working when phone is completely off or just boot up placed on wireless charger pad. But when charging pad disabled - charge stop and didn't work till reboot (it may work, but very-very rare, after many enable/disable wireless pad).
Also, sometimes image didn't smooth and kinda laggy. On stock it was normal.
Offtop: google pay also broken on PE. Magisk hide and props didn't working.
Added: Seems, google pay start working, but battery dissappearing before our eyes. Audio also Is interrupting on YouTube when screen is off.

Does the camera permit to record RAW (DNG) files rather than JPEGs ?

tokumeino said:
Does the camera permit to record RAW (DNG) files rather than JPEGs ?
Click to expand...
Click to collapse
Of course
Camera2api is supported.
If you get any bug please put it in the bug tracker.

may i know how to flash this rom? as we don't have twrp xz2 for android 10?
i am aware of twrp for android 9 though. but how about the recovery for android 10?

wee2000 said:
may i know how to flash this rom? as we don't have twrp xz2 for android 10?
i am aware of twrp for android 9 though. but how about the recovery for android 10?
Click to expand...
Click to collapse
You have to unzip the payload.bin and get the various .img files that you will then flash through fastboot following the steps of any other android 10 aosp rom. Keep in mind that you'll have to flash the 17th of jenuary's oem files as the most recent ones do not work with this rom and you will end stucked in the sony logo

sorry a question; now we have a working twrp for android 10 tell me if these steps to install this rom are fine:
1)flash latest stock firmware
2)install twrp (SODP or STOCK version?)
3)with fastboot flash newest oem binary for our phone on slot a and b
4)reboot to twrp and flash the pixel experience zip without any wipe
5)reboot
ok?

dose this can use gcam？

Somehow i managed to install this rom
- Flash version 52.1.A.0.618
- Unlock Bootloader
- Fastboot flash ODM slot_a
- Fastboot flash ODM slot_b
- Fastboot boot twrp (sodp)
- Twrp format all
- Twrp install from SD (PE 10+)
- Success
But the camera is s**k
Does anyone know how to install working gcam?

was there any battery problem
thismeamirul.88 said:
Somehow i managed to install this rom
- Flash version 52.1.A.0.618
- Unlock Bootloader
- Fastboot flash ODM slot_a
- Fastboot flash ODM slot_b
- Fastboot boot twrp (sodp)
- Twrp format all
- Twrp install from SD (PE 10+)
- Success
But the camera is s**k
Does anyone know how to install working gcam?
Click to expand...
Click to collapse
did you have battery drain problems
btw can you send the twrp image you used

So...this is my first time use sony,I alreay unlock the bootlocker and runing 52.0.A.8.50(latest9.0)
I don't know how to flash,could you help me?:crying:

Sorry guys, i can't find a way to flash the latest firmware. I downloaded through xperifirm the latest but xperia xz2 is not listed in flashtools devices. Could I solve using newflasher? Please help me, I really like pixelexperience!!

matteopola said:
Sorry guys, i can't find a way to flash the latest firmware. I downloaded through xperifirm the latest but xperia xz2 is not listed in flashtools devices. Could I solve using newflasher? Please help me, I really like pixelexperience!!
Click to expand...
Click to collapse
Flashtool and newflasher should work both.

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite

{
"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"
}
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.
Code:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have

Antho02 said:
i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have
Click to expand...
Click to collapse
decryption does not work in this build, im looking into a fix. Custom roms do not support decryption anyways so it's a minor issue for now

The handling of the "Adoptable Storage" still broken.
E:Failed to mount decrypted adoped storage device
Click to expand...
Click to collapse
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)

PC295 said:
The handling of the "Adoptable Storage" still broken.
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)
Click to expand...
Click to collapse
Can you send me logs of that issue (advanced > copy log > tick the "include kernel log" option and swipe in the "bar")? After doing this can you also try official twrp and tell me if that has the same issue?
Thanks for the feedback
PS: Can you join a telegram group (https://t.me/XMiA2Lite)? If /When you join there, mention me (@runrunrun00) and your issue, thanks in advance

The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...

PC295 said:
The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...
Click to expand...
Click to collapse
i might have found a way to fix this issue (in the bootable twrp, the installed one depends on your rom)

again, with twrp Bogdan, for my work fine, no problem with storage external

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what problem do you have with external storage?

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what's your issue exactly?

nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me

dochdoc said:
nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me
Click to expand...
Click to collapse
And what's the issue with this recovery regarding external storage (not scarymen's)?

LinkBoi said:
And what's the issue with this recovery regarding external storage (not scarymen's)?
Click to expand...
Click to collapse
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.

PC295 said:
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.
Click to expand...
Click to collapse
Is it possible to contact me on telegram again? I have one version in test that most likely fixes your issue

When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.

Yyres55 said:
When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.
Click to expand...
Click to collapse
If you want, you can contact me on telegram, I might have a fixed version there

LinkBoi said:
If you want, you can contact me on telegram, I might have a fixed version there
Click to expand...
Click to collapse
It worked. I tried another USB port and it's okay

hi, is there any plan to support encryption??

biladina.id said:
hi, is there any plan to support encryption??
Click to expand...
Click to collapse
Yup, of course. In the next release, 3.5.0, every bug I listed will be fixed, including Decryption, Android 11 support and more. If you want to test the release candidate (which is still 3.4.0 because twrp hasn't released 3.5.0 yet), you can join the telegram group below:
www.t.me/DaisyTestflight
New update will be released in XDA when TeamWin releases 3.5.0