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).
Related
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.
{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on a Rom compatible with one of these kernels and flash it
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)
FAQs can be found here.
CREDITs
Tasssadar
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
If you think I deserve a donation, I won't stop you
Thanks a lot to those who have donated!
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the Z3
XDA:DevDB Information
MultiROM for Sony Xperia Z3, Tool/Utility for the Sony Xperia Z3
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2015-01-23
Last Updated 2016-06-06
CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
M5 Kernel
AndroPlus Kernel (starting with V19)
If you want your favorite kernel to support kexec tell the dev to merge my commits.
Reserved
General Informations about Kexec are coming here soon.
I will test it when i come home and report the result.
Edit: all is stable only Multirom menu needed to be fixed but that you have reported, thanks
Now i can use stock as daily driver and cm12 to see the progress. many thanks.
Whaaaaaaat. This is amazing! Thanks for your work, keep at it! I will surely use the multirom a bit later, when some more roms like PA are avaiable.
Wow great work! A noob question but one assumes that I would not be able to have one rom on 4.4.4 and another on Lollipop 5.0 due to the fact the base Kernel AndroPlus is designed for 4.4.4 or does Multi Rom allow 2 different Kernels? Thanks in Advance.
Sent from my D6603 using XDA Free mobile app
panzerscope said:
Wow great work! A noob question but one assumes that I would not be able to have one rom on 4.4.4 and another on Lollipop 5.0 due to the fact the base Kernel AndroPlus is designed for 4.4.4 or does Multi Rom allow 2 different Kernels? Thanks in Advance.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
It actually is possible. The Base Kernel is patched to be kexec-hardboot compatible. This means it is able to load other kernel to the RAM and run them from there. The host kernel is just a middleman loading the kernel to the RAM, it is not doing anything else which means it is not affecting the secondarys kernel at all.
I used to do this on Nexus 5, loading 4.4.4 with kexec kernel and then 5.0 preview as the other rom and it worked, so it should be possible here as well.
Myself5 said:
It actually is possible. The Base Kernel is patched to be kexec-hardboot compatible. This means it is able to load other kernel to the RAM and run them from there. The host kernel is just a middleman loading the kernel to the RAM, it is not doing anything else which means it is not affecting the secondarys kernel at all.
Click to expand...
Click to collapse
Oh wow thats fantastic news for sure. Lollipop here I come. I was hesitant before due to lollipop not being daily driver material but now it does not really matter. Do you get an option to select which rom upon phone boot up?
Thanks guys and great work
Sent from my D6603 using XDA Free mobile app
panzerscope said:
Oh wow thats fantastic news for sure. Lollipop here I come. I was hesitant before due to lollipop not being daily driver material but now it does not really matter. Do you get an option to select which rom upon phone boot up?
Thanks guys and great work
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
see the pic in the op ? Thats what is going to appear after the Sony scrren and before the initial Rom bootup.
Myself5 said:
see the pic in the op ? Thats what is going to appear after the Sony scrren and before the initial Rom bootup.
Click to expand...
Click to collapse
Woops I thought all that was is a logo but did not check, my bad and thanks!
Sent from my D6603 using XDA Free mobile app
Wow it's already here for the Z3, thanks guys, this is awesome!!
Sorry but my english is to bad to understand what to do... Can anyone create please a step by step tutorial i have the d6603 whith androplus kernel v 19a please help me
Just confirming, looking at your files I assume that the Leo folder is for the z3?
Sent from my D6603 using XDA Free mobile app
panzerscope said:
Just confirming, looking at your files I assume that the Leo folder is for the z3?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
yup, leo is the Z3's codename. Sirius is Z2 and n801x is my Samsung Galaxy Note 10.1. Guess thats what happens when CM breaks the naming law and calling it just z3..
Myself5 said:
yup, leo is the Z3's codename. Sirius is Z2 and n801x is my Samsung Galaxy Note 10.1. Guess thats what happens when CM breaks the naming law and calling it just z3..
Click to expand...
Click to collapse
Yeah I knew it use to be Leo but after checking the CM website it was Z3 so I just wanted to confirm before fracking my phone lol. Thanks!
Sent from my D6603 using XDA Free mobile app
---------- Post added at 10:47 PM ---------- Previous post was at 10:04 PM ----------
So far so good, Modified Recovery and Multirom Installed. Now to flash CM12
Sent from my D6603 using XDA Free mobile app
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
Reporting back after testing.
This is either my ignorance or a possible bug.
So I am ready to add a second ROM. These are the steps I take.
Select Add ROM
Select Internal Memory ( I did get another option called ''/dev/block/mmcblk1p1 (exfat) ....Should that have been used instead ? )
Select Next
Select ZIP File
Select The Rom To Flash (CM12)
The flashing Process starts but fails with the following message
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Please see below for full Flashing Log.
Updating Partition Details.....Done
Full Selinux Support Is Present
Installing ROM cm12
Creating folders and images for type 1
Flashing Zip File cm12
Rom: cm12
Preparing zip file
Copying ZIP to /tmp
Changing mounts to ROM cm12
Current Boot Sector was used as base for fake boot.img !
Zip uses block updates
Creating system.img
Installing 'tmp/mr_update.zip.....
Checking for MD5 File
Skipping MD5 Check: No MD5 File Found
This Package Is For devices: D6602,D6603,D6633,D6643; This device is Leo
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Failed To Install ZIP
Restoring Mounts
Updating Partition Details.....Done
Erasing Incomplete ROM
Click to expand...
Click to collapse
I hope this helps.
panzerscope said:
Yeah I knew it use to be Leo but after checking the CM website it was Z3 so I just wanted to confirm before fracking my phone lol. Thanks!
Sent from my D6603 using XDA Free mobile app
---------- Post added at 10:47 PM ---------- Previous post was at 10:04 PM ----------
So far so good, Modified Recovery and Multirom Installed. Now to flash CM12
Sent from my D6603 using XDA Free mobile app
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
Reporting back after testing.
This is either my ignorance or a possible bug.
So I am ready to add a second ROM. These are the steps I take.
Select Add ROM
Select Internal Memory ( I did get another option called ''/dev/block/mmcblk1p1 (exfat) ....Should that have been used instead ? )
Select Next
Select ZIP File
Select The Rom To Flash (CM12)
The flashing Process starts but fails with the following message
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Please see below for full Flashing Log.
I hope this helps.
Click to expand...
Click to collapse
see there we go with the Leo thingy again Seems like I need to edit the device tree to make the Phone in Recovery appear as some D**** device instead of Leo. Will do tomorrow and release a update. /dev/block/mmcblk1p1 is your physical SD Card (it is formatted as exFat which is what TWRP is displaying).
change updater-script to leo. this should help.
Yeah when I saw that in the log I figured it was incorrectly detecting the device. I look forward to the update. I also guess that's why the Multirom app does not work?
Sent from my D6603 using XDA Free mobile app
Possible use for the Z3 compact?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TeamWin's TWRP Touch Recovery for LG Optimus G (geehrc).
https://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Screenshots:
Flashing Instructions:
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise use adb.
Remember to do backup of your current recovery before installing.
Changes:
compiled on omnirom-7.1 source
latest twrp updates included
updated device trees
prebuilt kernel
fixed AROMA installer
fixed screen brightness
extra languages + Polish by me
permissive selinux
enabled logd/logcat in recovery
enabled fuse exfat, ntfs-3g, jpeg
external storage as default storage
enabled usb-otg support
enabled modem backup
Download Links:
TWRP-3.0.0-0: geehrc
Device Source:
https://github.com/Split-Screen/android_device_lge_geehrc
https://github.com/TeamHorizon/android_kernel_lge_gee
XDA:DevDB Information
Unofficial TWRP-3.0.3-3 for LG Optimus G variants by dadi11, Tool/Utility for the LG Optimus G
Contributors
dadi11
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2016-02-06
Last Updated 2017-01-27
Reserved
Changelog:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse
E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')
Great work! Im new to this how do i install it?
enapah said:
E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')
Click to expand...
Click to collapse
I have the same errors
can someone create a flashable zip?
@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".
Guys sorry for errors. I have no OG anymore but still wanted to release something for you guys! I will try to fix it and release update in some minutes
please download and try this one: https://mirrors.c0urier.net/android/Dadi11/TWRP/TWRP-3.0.0-0_GEEHRC.img
enapah said:
@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".
Click to expand...
Click to collapse
He can easily flash TWRP or CWM by using FreeGee App.
I have done this 10minutes ago.
---------- Post added at 08:31 PM ---------- Previous post was at 08:16 PM ----------
Now recovery is working very well!
AROMA Installers are working too
pawelelos said:
Now recovery is working very well!
AROMA Installers are working too
Click to expand...
Click to collapse
Thanks for confirmation
good job
Thanks dadi11. Very generous, especially considering LGOG is not your primary device anymore.
@dadi11 Thank you very much for your time, specially given this is no longer a device at your hand.
I do have one "small" request to make, for those of us who run the official CM builds, it would mean the world to us if we had an image with e975 as device name (instead of geehrc). Any chance you could make one extra build?
Code:
ro.build.product=e975
ro.product.model=LG-E975
ro.product.device=e975
Stable, not bugs:
http://xyyx.ga/nitrogen-os/geehrc/twrp-geehrc-3.0.0.zip
File manager doesn't work properly, cannot list contents in some folders (ex: system)
hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it
gledis96 said:
hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it
Click to expand...
Click to collapse
Install as any other zip, then chose reboot recovery from ur recovery which u use.
tiennhu89 said:
Install as any other zip, then chose reboot recovery from ur recovery which u use.
Click to expand...
Click to collapse
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now
gledis96 said:
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now
Click to expand...
Click to collapse
Ok.u r wellcome.☺
tiennhu89 said:
Ok.u r wellcome.
Click to expand...
Click to collapse
another thing do you know how to install xposed cause i tried flashing it but my phone gets stuck in boot i have this rom
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-aosp-5-1-1r8-optimus-g-t3160195
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
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
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[dora] TWRP 3.0.2-0 touch recovery, Tool/Utility for the Sony Xperia X Performance
Contributors
AndroPlus
Version Information
Status: Stable
Created 2016-10-08
Last Updated 2016-10-08
Wow that's good news! Hoping to see twrp support for full X-series
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
AndroPlus said:
Now it's official
Click to expand...
Click to collapse
Great! Now we need to wait root on locked bootloader but it can be very looooong waitng
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Hi AndroPlus,
Is that means your future builds will be also compatible with xperia XP, specially and as i known the XP and XZ has about the same processor (core)? Or you will abandon the XP definitively [emoji22].
And another question: as i now have an xperia XP for about 1 month, and i decided now to rooting it with the help of your modified kernel, is it confirmed that the kernel will contouring the consequences of deleting the DRM keys a cause of unlocking bootloader and leading to restore the functionality (or at least most of them) of DRM features?.
Thanks
Envoyé de mon Xperia x performance
baha76_s said:
Hi AndroPlus,
Is that means your future builds will be also compatible with xperia XP, specially and as i known the XP and XZ has about the same processor (core)? Or you will abandon the XP definitively [emoji22].
And another question: as i now have an xperia XP for about 1 month, and i decided now to rooting it with the help of your modified kernel, is it confirmed that the kernel will contouring the consequences of deleting the DRM keys a cause of unlocking bootloader and leading to restore the functionality (or at least most of them) of DRM features?.
Thanks
Envoyé de mon Xperia x performance
Click to expand...
Click to collapse
I'll continue building kernel for XP even after buying XZ
DRM function restore is working well for XP with my kernel.
AndroPlus said:
I'll continue building kernel for XP even after buying XZ
DRM function restore is working well for XP with my kernel.
Click to expand...
Click to collapse
Thank you very much for your reply.
I'm glad to hear that you will continue the development for this flag.
And final question: is there any chance that you will find a way to modify the kernel in android 7 (nougat) in this flag?, specially as i read that the new android 7 core has a new feature to detect any changes in W/R status of the system partition and leading to become the (boot.img) inaccessible and consider as corrupted file, i.e more secure options to kernel level.
Thanks
Envoyé de mon Xperia x performance
baha76_s said:
Thank you very much for your reply.
I'm glad to hear that you will continue the development for this flag.
And final question: is there any chance that you will find a way to modify the kernel in android 7 (nougat) in this flag?, specially as i read that the new android 7 core has a new feature to detect any changes in W/R status of the system partition and leading to become the (boot.img) inaccessible and consider as corrupted file, i.e more secure options to kernel level.
Thanks
Envoyé de mon Xperia x performance
Click to expand...
Click to collapse
I think it can be disabled in kernel.
Let's wait 7.0 for our device...
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Was hoping for an other answer but I can understand your decision! It's nice to see some support for the xp & XZ, keep up the good work!
Verstuurd vanaf mijn F5121 met Tapatalk
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Hi, do you think this variant will work for the Sony X (not Performance) too?
I had some bad experiences flashing TWRP (i.e. with TWRP for Huawei M2, that wasn't suitable for the European device, only the Chinese one, leading to a bootloop) - I guess X and X Perf. aren't too different, but I'd like to make sure it fits
Thanks!!
xtools said:
Hi, do you think this variant will work for the Sony X (not Performance) too?
I had some bad experiences flashing TWRP (i.e. with TWRP for Huawei M2, that wasn't suitable for the European device, only the Chinese one, leading to a bootloop) - I guess X and X Perf. aren't too different, but I'd like to make sure it fits
Thanks!!
Click to expand...
Click to collapse
X has different SoC, so it won't work...
AndroPlus said:
X has different SoC, so it won't work...
Click to expand...
Click to collapse
So twrp for the x compact should/could work for the x? They have the same soc
kistigun said:
So twrp for the x compact should/could work for the x? They have the same soc
Click to expand...
Click to collapse
Maybe.
AndroPlus said:
Maybe.
Click to expand...
Click to collapse
okey, would like to test this. If it's not compatible could I just restore everything by reflashing original firmware ftf from sony?
kistigun said:
okey, would like to test this. If it's not compatible could I just restore everything by reflashing original firmware ftf from sony?
Click to expand...
Click to collapse
Yes, you can restore stock recovery by flashing FTF (FOTAKernel is recovery)
@AndroPlus bro, I can't get it working on my F8131 (custom kernel, not yours).
This is the flashing output:
Code:
[B][I][COLOR="Blue"]fastboot flash recovery twrp-3.0.2-0-dora.img[/COLOR][/I][/B]
target reported max download size of 268435456 bytes
sending 'recovery' (20600 KB)...
OKAY [ 0.638s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.797s
Combo keys (Power + Volume Down) turn device off after the "Your device has been unlocked..." message (and before sony logo shows up)!
Am I doing something wrong or forgetting something?
Btw, if I try to just boot into twrp while in fastboot, I get this error:
Code:
[B][I][COLOR="blue"]fastboot boot twrp-3.0.2-0-dora.img[/COLOR][/I][/B]
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
[B][COLOR="Red"]FAILED (remote: dtb not found)[/COLOR][/B]
finished. total time: 1.068s
Thanks in advance!
serajr said:
@AndroPlus bro, I can't get it working on my F8131 (custom kernel, not yours).
Click to expand...
Click to collapse
Try to use my TWRP for MultiROM, it's fully functional from hardware recovery boot too.
Adrian DC said:
Try to use my TWRP for MultiROM, it's fully functional from hardware recovery boot too.
Click to expand...
Click to collapse
And it did work flawlessly at first try (downloaded multirom-20161116-recovery-fota-dora.zip > extracted twrp.img > fastboot flash recovery twrp.img)!
Thank you so much!! :highfive:
It really looks like Androplus needs to fix something on this!
hmm, maybe I missed something... when I build TWRP on my own, it's working.
I'll look into it.
AndroPlus said:
hmm, maybe I missed something... when I build TWRP on my own, it's working.
I'll look into it.
Click to expand...
Click to collapse
Thank you!
We're all waiting for that, once this is the official one!