Develop Bugs

[RECOVERY]TWRP BETA 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PirateXPERIA Project

{
"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"
}
Hi XDA. I used cyanogenmod ramdisk overclocked by FindYanot.
Thanx FindYanot, awesome work.
Kernel is for Sony Xperia M | C1905 | Nicki
Incudled recoveries:
Team Win Recovery Project
Philz Recovery
ClockworkMod
CyanogenMod Recovery
Click to expand...
Click to collapse
DOWNLOADS
Install instructions:
If updating form older version, is recommended to delete /system/kernel folder.
New files will overwrite old files, but some old files are not needed.
by removing /system/kernel folder before flash you can maybe get some free space.
Via custom recovery:
Code:
1. flash PirateXperiaKernel.zip via custom recovery (CWM/TWRP)
2. flash cm11_addon, cm12_addon or stock_addon (when you flash both, last flashed will be used)
When you dont have any kernel with custom recovery:
Code:
1. extract boot.img form PirateXperiaKernel.zip, and flash it via fastboot.
2. BUT THEN DONT FORGET TO FLASH PirateXperiaKernel.zip VIA TWRP!
3. flash cm11_addon, cm12_addon or stock_addon (when you flash both, last flashed will be used)
Dont forget to flash PirateXperiaKernel.zip again, after system formating!!!
Click to expand...
Click to collapse
What do you need?
Xperia M device (C1505 cnofirmed)
CyanogenMod 12 based ROM (can flash after kernel)
15MB free space in /system partition
Click to expand...
Click to collapse
Why use PirateXPERIA Kernel:
+ Overclocked CPU to 1.6GHz.
+ 4 recoveryes
+ Downloadable backgrounds
Click to expand...
Click to collapse
Preview Wallpapers
Download Wallpapers
Boot Logo:
Boot Animation:
It is one bootanimation. but i cannot make gif, that wil loop from part1.
First is part0, and part1 preview. Second is only part1 (bootanimation loop) preview.
DOWNLOAD: bootanimation.zip in DOWNLOADS / misc
To apply bootanimation, just copy bootanimation.zip into /system/media folder, and "chmod 644 /system/media/bootanimation.zip"
If you like my work, press Thans button, but first press thanks button on FindYanot´s thread .
And sorry for my bad english.
Using:
To boot system only turn on your phone.
To boot recovery menu press vol+/vol- during blue led flashes.
To boot TWRP first boot to recovery menu, then press vol+/vol- during cyan led flashes.
To boot Philz Recovery first boot to recovery menu, then press vol+/vol- during amber led flashes.
To boot CWM first boot to recovery menu, then press vol+/vol- during yellow led flashes.
To boot CM Recovery first boot to recovery menu, then press vol+/vol- during green led flashes.
To boot Recovery from FOTA partition first boot to recovery menu, then wait to white led flashes.
Click to expand...
Click to collapse
XDA:DevDB Information
PirateXPERIA Project, Kernel for the Sony Xperia M
Contributors
gouster3
Kernel Special Features: MultiRecovery OverClock
Version Information
Status: Testing
Created 2015-02-09
Last Updated 2015-03-01

Reserved
Changelog:
- Project paused until i will have time to look up kexex, and it´s use.
//EDIT: Project died with my device. So no more updates.
- Versions uses date, inside of numbers.(from next version)
- Downloads moved to BasketBuild
- Created bootanimation. (bootanimation.zip in downloads)
Version 2.1.1
- Kernel patch copy is recursive, you can add folders to pach.
Version 2.1.0
- Fixed kernel patch function. (thanx thichthat)
- Added support to run user's script before boot. (thanx thichthat)
- Changed CM Recovery Version for touch support (Fixed power-down bug too).
Version 2.0.0:
- Added CM11 Support
- Auto boot into recovery if ramdisk not found
- Load build-in recovery, when recovery not found
- need to flash cm11_addon.zip or cm11_addon.zip to get working
- added stock ROM support (with some extra optimalizations)
Version 1.10.0:
- TWRP Downgraded to 2.8.0.0 for mtp fix
- Fixed boot without config
Version 1.9.0:
- Can define kernel type (IMG/CPIO/FOLDER)
- TWRP recovery moved from /recovery to /sbin
- some bug fixes
Version 1.8.0:
- TWRP Updated to 2.8.4.0
- Changed logo colour
- Automatic patch kernel files from /system/kernel/patch
- Load recovery from FOTA
Version 1.7.0:
- Fixed logo position
- recoveries located in /system/kernel/recovery (TWRP located in kernel too)
- ramdisk located in /system/kernel/boot.cpio
- config file in /system/kernel/cofing
Version 1.6.0:
- Fixed Logo resultion
- Some bug fixes
- cpio images will deleted from ramdisk after one of it unpacked.
Version 1.5.0:
- Changed Logo
- Project renamed from MultiRecovery
to PirateXPERIA Project
Version 1.4.0:
- Added Philz Recovery
Version 1.3.0:
- Added CWM Recovery
- Added CyanogenMod Recovery
- Updated Kernel Version
Version 1.2.0:
- Updated Kernel Version
Version 1.0.0:
- Initial relase
- TWRP Recovery
- BattleField Boot logo
//When you see new version in challengelog, but not in downloads, just wait until i will upload it.
//Newest version can be relased few days after added to changelog. (time to test and compile it.)
Click to expand...
Click to collapse

Reserved
Woking on:
- Incudle MULTIROM by alvinhochun
- Higher freq. for manual overclocking. (use is optional)
- More variants of BootAnimation
- Fix screen shift bug in CWM and Philz Recovery.
- PirateXPERIA ROM
Click to expand...
Click to collapse
Know bugs:
- Screen shift bug in CWM and Philz Recovery.
- Phone will not in turn off when pressed Power off in CM Reovery
Click to expand...
Click to collapse
You can report bug here.
For advanced users, look into /system/kernel folder
config - configuration file. open with notepad++ (you can here change paths)
boot.cpio - ramdisk (overclocked cyanogenmod factory ramdisk)
recovery - folder with recoveryes.
script.sh - execute this file before boot to system/recovery.
patch -
this folder will copyred after ramdisk extract, and before execute ramdisk startup file.
here you can patch files from kernel. Applyed to boot.cpio and recoveries.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

awesome
Ill try this. I cant see the installation progress / logs in the cm recovery included in the cm12 package

Can it work on C1904/C2004?
Hi. Great job with the kernel dev. Have been waiting for an OC kernel for CM12. Problem is, I have a C2004 with C1904 firmware cross-flashed on it, on top of which i have CM-12 based Resurrection Remix ROM running. Will this kernel be able to run on my device, since you have mentioned only C1905 in your post?

manal.21sinha said:
Hi. Great job with the kernel dev. Have been waiting for an OC kernel for CM12. Problem is, I have a C2004 with C1904 firmware cross-flashed on it, on top of which i have CM-12 based Resurrection Remix ROM running. Will this kernel be able to run on my device, since you have mentioned only C1905 in your post?
Click to expand...
Click to collapse
Hi, i think no, just try. When it will no work, just flash your prevous kernel. Hope it works.

Tommienots said:
Ill try this. I cant see the installation progress / logs in the cm recovery included in the cm12 package
Click to expand...
Click to collapse
I will try to fix it.

SystemUI FC on c1904/2004
gouster3 said:
Hi, i think no, just try. When it will no work, just flash your prevous kernel. Hope it works.
Click to expand...
Click to collapse
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
---------- Post added at 12:33 PM ---------- Previous post was at 11:58 AM ----------
manal.21sinha said:
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
Click to expand...
Click to collapse
Also, Philz recovery doesn't load when I do the necessary steps. Also, the CWM recovery included has a screen shift bug. Please look into this if you can. Thanks!

I Will try this awesome kernel on pa 4.6 beta 6, i will report soon if this kernel works perfectly or not ..
Edit: i get only blank screen after boot logo appear ..
But i'm really confused, OP says support cm11, so this kernel probably work with kitkat rom, but i'm wrong .. :crying:
Sorry for my bad engelish

manal.21sinha said:
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
Click to expand...
Click to collapse
Thank you. C2004 Not supported. Maybe later.
manal.21sinha said:
Also, Philz recovery doesn't load when I do the necessary steps. Also, the CWM recovery included has a screen shift bug. Please look into this if you can. Thanks!
Click to expand...
Click to collapse
Yes. I have it in to-do list.

itsnie said:
I Will try this awesome kernel on pa 4.6 beta 6, i will report soon if this kernel works perfectly or not ..
Edit: i get only blank screen after boot logo appear ..
But i'm really confused, OP says support cm11, so this kernel probably work with kitkat rom, but i'm wrong .. :crying:
Sorry for my bad engelish
Click to expand...
Click to collapse
Working just on CM12 (Lollipop) //Edit: now cm11 & stock supported

Can i boot any roms with this multirom?

itsnie said:
Can i boot any roms with this multirom?
Click to expand...
Click to collapse
No. This is not multirom, but MultiRecovery. (you can have TWRP, Philz, CWM and CM Recoveryes in one kernel)
if you mean cm11_addon cm12_addon and stock_addon, you can use only one of this.
i dont want to upload new kernel versions for both, so you must install kernel first. and then one of addons.
if you flash more of addons, it will use last flashed addon.
MultiRom is another project by alvinhochun
but i want implement it in my MultiRecovery kernel in future.
But, when you want, you can extract ramdisk from kernels, replace recovery cpio´s in /system/kernel/recovery
and now you can boot 4 different kernels. but without editing this kernels you can use kenrel only for rom located in /system.
only cm11, cm12 and stock rom are supported.
but if you want boot "unsupported" rom with this kernel, you must unpack ramdisk.cpio from rom kernel, and then move it in /system/boot.cpio.
cm11_addon, cm12_addon and stock_addon flashes only thit boot.cpio. so you can support any ramdisk you want.
but you will not have OC.

I copied my fstab.qcom and init.qcom.rc to /patch folder but it didn't replace the original files
I found this code in your init.sh:
Code:
busybox cp /system/kernel/patch /
And I think it should be changed to
Code:
busybox cp /system/kernel/patch/* /
We should also have an option to run user's script before system boot. I added this line:
Code:
exec /system/kernel/script.sh

Thanx. I have not trayed patch function yet.
I will change this in next version.

gouster3 said:
Thanx. I have not trayed patch function yet.
I will change this in next version.
Click to expand...
Click to collapse
i think using -R is allowed in busybox. or not? cp -r /system/kernel/patch/* /

Help!! Overclock works, but UI force closes and nav buttons, notifications and status bar dissapear.... Help please... thanks

ByronFer said:
Help!! Overclock works, but UI force closes and nav buttons, notifications and status bar dissapear.... Help please... thanks
Click to expand...
Click to collapse
Which rom are you using? i have same problem with Resurrection Remix 5.3.3.
Try cm-12-20150123-UNOFFICIAL-nicki by PecanCM´s CM12
Now i am using Resurrection Remix 5.3.3, with my kernel, but i have copyred ramdisk from rom into /system/kernel/boot.cpio.
it is solution too. but you will have not overclock.

[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][arm64]TWRP Recovery [3.2.2-r1] [10 July 18]

{
"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.
This is my own unofficial customized build of 64 bit twrp for athene. It can be used on both Nougat and Oreo (32 bit and 64 bit ROMs) without any problem.
Known Bugs:
Encryption will not work. (Will be hopefully fixed in future builds) Not tested yet.
Changelog:
~~ -r2
* Overhaul twrp tree and add arm64 support
~~ -r1
* Based on AOSP/OmniROM 8.0.0_r32 release
* Fix stuck on 'black' screen entering recovery
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
How to flash:
By fastboot:
* You should have an unlocked bootloader and adb and fastboot set on your computer properly. Check this thread if you haven't done it already.
* Download the .img file on your computer and keep it in your adb folder (Windows only)
* Boot to fastboot mode and then connect your phone to the computer. Open a command window/terminal and
type this command:
To temporarily boot twrp:
Code:
fastboot boot <filename.img>
To flash it to the recovery partition:
Code:
fastboot flash recovery <filename.img>
~Note: Linux users might want to add "sudo" before the respective commands.
*Now manually reboot to the recovery mode using the volume down keys. The current ROM will patch the recovery partition to its earlier state if this step isn't performed and you directly reboot to the system.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
~From presently installed TWRP on the device:
* Copy the .img file to your phone and reboot to recovery
* Tap Install > Choose Flash Image > Navigate to the path where you copied the .img file and choose it.
* Choose Recovery Partition
* After the install being successful, go to home and tap Reboot > Reboot Recovery.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
Downloads:
Latest build: Direct Link
Older Builds: [url]https://sourceforge.net/projects/twrp-athene/files/[/URL]
XDA:DevDB Information
twrp-athene, Tool/Utility for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: [url]https://github.com/omnirom/android_bootable_recovery[/URL]
[url]https://github.com/rajatgupta1998/android_kernel_motorola_msm8952[/URL]
Version Information
Status: Beta
Created 2017-12-20
Last Updated 2017-12-20

is it compatible with shreps twrp backup?

Ayan Uchiha Choudhury said:
is it compatible with shreps twrp backup?
Click to expand...
Click to collapse
Yes, should work :good:

thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem

arun4777 said:
thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem
Click to expand...
Click to collapse
That's not related to twrp. Restoring the whole data partition from one rom to another causes problems for sure. Better to use titanium backup and backup/restore user apps with it.

This should work with the G4 (Regular non Plus model) Right?

Vaizen said:
This should work with the G4 (Regular non Plus model) Right?
Click to expand...
Click to collapse
Yes [emoji106]
Sent from my Moto G4 Plus using Tapatalk

tywinlannister7 said:
Yes [emoji106]
Click to expand...
Click to collapse
Actually it didn't let me flash latest RR. Had to flash official version for it to flash correctly.

Update: 30 Dec 2017
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download

tywinlannister7 said:
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download
Click to expand...
Click to collapse
Will i able to flash 32 bit also and does backup restores?

Can I Flash 32 bit ROM and 64 with this recovery?

Luis Infante said:
Can I Flash 32 bit ROM and 64 with this recovery?
Click to expand...
Click to collapse
Yes u can

StevenFernandes said:
Yes u can
Click to expand...
Click to collapse
Thanks

i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev????

arun4777 said:
i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev
Click to expand...
Click to collapse
It's a bug found on many twrp builds. I don't know if it's device specific.

I notice they Ghost touch with they USB cable and PC connected for ADB Sideload (and this affect to the ROMs)
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
I forgot to say that in this recovery for arm64 3.2.1.0 I don't have the arrow of the mouse appearing sometimes in the center of the screen (always on recovery, and sometimes on the system)

When i flash via fastboot the reovery, fastboot send me this error?
target reported max download size of 536870912 bytes
sending 'recovey' (14840 KB)...
OKAY [ 0.589s]
writing 'recovey'...
(bootloader) Invalid partition name recovey
FAILED (remote failure)
finished. total time: 0.597s
Click to expand...
Click to collapse

striplex said:
When i flash via fastboot the reovery, fastboot send me this error?
Click to expand...
Click to collapse
Yeah, see what you type: "recovey" but the partitions name is recovery

work roms 32 and 64 bits?

biel.paes said:
work roms 32 and 64 bits?
Click to expand...
Click to collapse
If you looked a few posts before you would clearly know that, yes, this build of twrp supports both 32 and 64 bit roms. Please use the search function before posting!