[Recovery][6633][twrp] Unofficial TWRP 3.0.2 for Z3 Dual D6633 - Xperia Z3 Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bismillahi Alrahmani Alraheem
(in the name of God the most gracious, the most merciful)
Finally Unoffoicial TWRP 3.0.2 is here for Dual sim version of XPERIA Z3 (D6633)!!
Introduction:​
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
And much more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here:
https://github.com/Dees-Troy/extract_elf_ramdisk
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
DOWNLOAD:​
Please notice that it won't work in stock based roms, only custom roms will run it
20160907 (img)
20160907 (zip)
Installation methods
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.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/recovery-twrp-302-z3dual.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Fastboot method:
you should have fastboot in your pc (either downloaded separately or with android SDK)
fire up Terminal (Linux and OS X) or CMD window (MS Windows) in the folder you have the image on it and it is preferred to copy the image to the folder of fastboot so the following command work then type:
Code:
fastboot flash FOTAKernel recovery-twrp-302-z3dual.img
don't forget to put ./ before 'fastboot' if you are using OS X or linux (./fastboot)
ZIP method:
flash the zip using any recovery
Themes and colors:
HERE
(Read Post #2 in the link if you want to customize, I'll be making pre-made themes later on inshaaAllah (God willing) )
NOTE: You are free to repack it and even sharing it without taking my permission
Please Donate If you want me to support Z3 dual more and more, it is back to you ​
XDA:DevDB Information
TWRP 3.0.2 for Z3 Dual D6633, Tool/Utility for the Sony Xperia Z3
Contributors
Muhammad Ashraf
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2016-09-07

Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?

dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
sorry for the late reply, I am not sure why does it act like that
i'll try to make a zip file for that issue

dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Oh, I am SOOOOOOOO Sorry, You have noticed me, By mistake I have uploaded Cyanogenmod Recovery instead of twrp
figuring that out now
I am sorry all of you
thanks man
EDIT: DONE

dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Unlocked or Locked bootloader?
(Does this require an unlocked bootloader?)

I cannot get to recovery mode using DD or fastboot
Command will go through but adb reboot or h/w combos wont get me recovery. How do I install recovery ? . I have a ROM that can only be installed via recovery pl help

I cannot get to recovery mode using DD or fastboot

FAILED (remote: Command not allowed)
it always says "FAILED (remote: Command not allowed)"
should the bootloader be unlocked ?!
what is the problem here?!

Hi, i flashed the .img using my twrp, the only option on "select partition" was kernel, i know i shouldn't have done it, but i did. Now the phone doesn't boot, it keeps on a black screen. I think i need to flash a new kernel, can someone help me? Thanks
edit
Locked bl

Excellent WORK +++++
Bismillahi Alrahmani Alraheem YOU are my god!
Well done. You are the man. Exellent work with this TWRP for my D6633 (z3 dual)
it saved my life!

bryantshurley said:
I cannot get to recovery mode using DD or fastboot
Click to expand...
Click to collapse
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.

"fastboot flash boot recovery-twrp-302-z3dual.img" got me to a new recovery screen and can no longer boot the system.

rzepek2pl said:
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
Click to expand...
Click to collapse
That was a bad advice. Now I only have TWRP on my phone. Only boots into this!
Can it be saved? How?

Your 20160907.zip based on TWRP 3.0.2 was put into root & flashed with TWRP v2.8.7.0 which did not update, when re-launching recovery I was still on v2.8.7.0

Related

[DEV] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
aromafm_galaxy5.zip (v1.91)
http://www.mediafire.com/?p5pdelpib6w8px
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
XDA:DevDB Information
PhilZ Touch Recovery : galaxy5, Tool/Utility for the Samsung Galaxy 5 I5500
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-07
Created 2014-07-12
Last Updated 2014-07-12
Very good recovery. :good:
Everyone should check it out.
I haven't found any bugs as of now.
UPDATE:
Changelog:
-Updated PhilZ sources to 6.23.8 (26.03.2014).
-Updated androidarmv6 sources. So, you'll be able to flash cm-ota without any Signature Verification error.
Below is the recovery.img file, flash using Terminal Emulator method:
recovery.img
Need feedback. If everything is fine, I'll add it to first post.
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
jpeps said:
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't try it until the developer says so!
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
RobsX2 said:
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
Click to expand...
Click to collapse
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Bhargav97 said:
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Click to expand...
Click to collapse
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
EDIT: Recovery has flashed and does work. Thanks!
RobsX2 said:
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
Click to expand...
Click to collapse
Then there is another simple solution.
-Install any CWM recovery (through ODIN).
-Now download any zip file of cwm recovery (use madteam.co if you don't find at xda).
-Open the zip and replace the recovery.img inside with this (PhilZ Recovery) one.
-Now, flash this modified zip file with the current cwm recovery (which you installed using odin).
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
RobsX2 said:
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
Click to expand...
Click to collapse
Have you done all the wipes?
Vagelis1608 said:
Have you done all the wipes?
Click to expand...
Click to collapse
Yessir
RobsX2 said:
Yessir
Click to expand...
Click to collapse
Did you pulled the battery to turn the device off when it hunged (at the "Android" screen)?
Have you tried booting up again?
Also, contact me via PM so that I will help you fix the issue. Let's not spam this thread .
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
deleted
Bhargav97 said:
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
Click to expand...
Click to collapse
ALL HARDKEYS WOORK FINE!
I just have one doubt.
When i reset to "Koush default" it gave me a netted grey background..
Whereas :"Philz default" gave a complete black background..
Is this supposed to happen.
Maybe I am too stupid
But where is on goo.im the PhilzTouch for this little jewel called galaxy5?
wrong post

[2014-09-22] [MT2-L03] TeamWin Recovery Project

Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03​
Team Win Recovery Project 2.x, or twrp2 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 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22
Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311
*Reserved Again*
I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app
Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.
Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Thanks for the great work!
TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.
The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.
xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.
4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.
I second that
Sent from my MT2L03 using XDA Free mobile app
Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.

[Recovery][L3 II][Single/Dual] Custom Recoverys

Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Unlocking Bootloader (Required)
* Because unlocking the bootloader? *
Bootloader bootloader is present on any Linux (Android) and Windows system.
Every manufacturer makes its locked bootloader to "not let any user device end his".
The LG , besides the bootloader lock, removes the command to unlock and still does not tell how to unlock the bootloader, then the only way is to burn an edited bootloader, that being the case.
Via App - thanks @ElDainosor and @vuminhduc_1998
Follow instructions in topic.
Support: All LG Optimus L3 II Variants
How to get into recovery via buttons:
Turn off your cell phone and do so, press the "Volume -" + "Power", after a second tight press "Home" and when vibrate loose and everyone quickly and repeatedly press the "Home". Will need a few tries until you get the delicacy, because that's the base.​
Next Update:
TWRP with support to sd-ext (by @Cobmaster)
TWRP 2.8.6.0 -> TWRP 2.8.7.0​
The CWMA and TWRP when I choose install zip from sdcard it displays the folder "/sdcard/0/" instead of "/sdcard/"
Sorry for my english I hope you understand what I mean xd
This is not bug
This folder is the default location, the CWMA you can change the location in recovery settings
thanks... It works on E425g????
now im trying to build something like that, im just learning so its hard even so i know about linux and building but it a little difernt...
Has not yet been tested, but I suppose that works.
It's hard but if you insist you can
TWRP works, but i cant install some packages like cyclone kernel, there is a problem in updater-script.
obrigado!!!
ensarman said:
TWRP works, but i cant install some packages like cyclone kernel, there is a problem in updater-script.
obrigado!!!
Click to expand...
Click to collapse
But you only tested the TWRP?
Test the CWM Advanced
Caio99BR said:
But you only tested the TWRP?
Test the CWM Advanced
Click to expand...
Click to collapse
lol, ok i will, but later, when i go home
Caio99BR said:
But you only tested the TWRP?
Test the CWM Advanced
Click to expand...
Click to collapse
olá
I have tested the CWM touch and it works perfectly until now I do not test everything buy it works well..
besides I have written a tutorial en spanish at my blog, if you want to check it: I will leave the link:
http://supranet.org/sistemas-operativos/twrp-y-cwm-touch-recovery-y-para-lg-optimus-l3-ii/
thanks
E430 Test
Caio99BR said:
Hello people, today I came to bring the main Recovery's ported and tested by me
TWRP - TeamWinRecoveryProject (by TeamWin) - Touch
CWM - ClockworkMod (by Koush) - Non-Touch
CWM Advanced Edition - 6 PhilZ Touch Recovery (by Phil3759) - Touch
Unlocking Bootloader (Required)
* Because unlocking the bootloader? *
Bootloader bootloader is present on any Linux (Android) and Windows system.
Scheme android bootloader.
{
"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"
}
Every manufacturer makes its locked bootloader to "not let any user device end his" meaningless thing to say.
The LG miserable, besides the bootloader lock, removes the command to unlock and still does not tell how to unlock the bootloader (already tried to communicate how to unlock), then the only way is to burn an edited bootloader, that being the case.
Unlocking the bootloader
Unzip emmc_appsboot.rar and place the file on the SD card
Code:
adb pull emmc_appsboot.bin /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5
Commands to install the CWM:
Put the file on the sdcard
Code:
adb push cwm.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Commands to install the TWRP:
Put the file on the sdcard
Code:
adb push twrp.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Commands to install CWM Advanced Edition:
Put the file on the sdcard
Code:
adb push cwma.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/cwma.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Note:
Tested only on E435 - Lg Optimus L3 Dual II
If someone on the other testing L3 II, leave feedback
How to get into recovery via buttons:
Turn off your cell phone and do so, press the "Volume -" + "Power", after a second tight press "Home" and when vibrate loose and everyone quickly and repeatedly press the "Home". Will need a few tries until you get the delicacy, because that's the base.
Downloads:
ADB - AndroidFileHost - (For PC)
Terminal Emulator - Play - (For Mobile)
Bootloader - AndroidFileHost - (Unlock the Bootloader)
TWRP (01/10/2014) - AndroidFileHost - (twrp.img)
CWM (10/01/2014) - AndroidFileHost - (cwm.img)
PhilZ CWM (01/10/2014) - AndroidFileHost- (cwma.img)
Credits:
IGGYVIP - For unlocked BootLoader :good:
hugo.gabriel999 - For Inspiration
TeamWin - For TWRP
Koush - For CWM
Phil3759 - For A Best And Advanced CWM
Click to expand...
Click to collapse
Hi, I tested PhilZ Touch and TWRP on LG E430 they work very well
Mikk123 said:
Hi, I tested PhilZ Touch and TWRP on LG E430 they work very well
Click to expand...
Click to collapse
Thanks!
Cayo what is the cwms???
ensarman said:
Cayo what is the cwms???
Click to expand...
Click to collapse
It is the CWM however you can use the touch to do the movements, it's good because you stop using the physical buttons.
Besides being easier.
Ok i will tr it, it works with the. New edify syntax like set metadata instead of set permission?
ensarman said:
Ok i will tr it, it works with the. New edify syntax like set metadata instead of set permission?
Click to expand...
Click to collapse
Yes, I have implemented SELinux support that adds support to new syntax.
All these recoverys made by me already have this support. There were already implemented in the second build, because in the first gave installation error (CM 11 test builds) due to lack of SELinux support.
Caio99BR said:
Yes, I have implemented SELinux support that adds support to new syntax.
All these recoverys made by me already have this support. There were already implemented in the second build, because in the first gave installation error (CM 11 test builds) due to lack of SELinux support.
Click to expand...
Click to collapse
great!!! thanks man
These recoverys are ready for CM11!
And who knows
I will delete the CWM and leave only the CWMS because it is better and simpler
Status
Updated CWM and CWM PhilZ Edition, now they are compatible with the CyanogenMod 11 (which will be released soon), for those who want to test will be necessary to update the recovery to the latest version.
I did not update the TWRP because it gave an error in which I could not solve.

[twrp] [montana] [G5s] 3.2.3-0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: twrp-montana-3.2.3.0.img
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2 @lohanbarth
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.3-0
Stable Release Date: 2018-10-08
Created 2018-07-05
Last Updated 2018-10-08
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
lohanbarth said:
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Source Code:
Github
Contributors
@[email protected]@[email protected]
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.2-0
Stable Release Date: 2018-07-05
Created 2018-07-05
Last Updated 2018-07-05
Click to expand...
Click to collapse
Support on Arm64 rom's?
Adamask said:
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
Click to expand...
Click to collapse
go to wipes and click on data format.
rssxda said:
Support on Arm64 rom's?
Click to expand...
Click to collapse
Yes
twrp 3.2.3 in op.
after wipe data and reboot the phone twrp is not there
Cesarcami53 said:
after wipe data and reboot the phone twrp is not there
Click to expand...
Click to collapse
it's normal you have to flash a .zip file so that it stays
Where is the twrp zip..??
Hello ! guys ... I'm without pc can I flash it for this app?
zanduo said:
Hello ! guys ... I'm without pc can I flash it for this app?
Click to expand...
Click to collapse
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
I have root and twrp and bootloader .... the problem and that I am without pc ...
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
Thanks man i use flasify And Works! Thanks ! Now i waiting for 64 roms
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
RuKlowd said:
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
Click to expand...
Click to collapse
flash a .zip file (magisk or a custom rom) to fix it
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
lohanbarth said:
flash a .zip file (magisk or a custom rom) to fix it
Click to expand...
Click to collapse
Thanks, it worked! So the recovery partition won't really (permanently) flash unless you root the device, right? Do I always need to root to permanently flash any other partition, too?
ilovepanda said:
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
Click to expand...
Click to collapse
Sorry, I had difficulties to understand you :/
if you make a backup, the backup will also add the recovery stock, so when restoring, it will also restore the backup of the recovery stock, it would be better to install the stock and before the first boot, install the twrp via .img
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
PhoenixGamer said:
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
Click to expand...
Click to collapse
You can

Development [RECOVERY] [12] [UNOFFICIAL] TeamWin Recovery Project (8T / 9R) (2022-07-27)

{
"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"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Extra Fixes :-
Switched To 60 fps from 30 fps
Variant Script Fixed
Boot Control Revision from 1.1 to 1.2
Added Fix for Transferring File Above 4GB
Added Recovery Recovery Variant Of Fastboot Client
Working :-
Decryption
Fixed TWRP Boot up time
Backup(except data partition)/restore
ADB/MTP
Flashing Rom
stock rom flashing
fastbootd and adb sideload
Etc. Cuz I don't remember What else I fixed and What was working
BUGS :-
Other Bugs You tell me that !!!
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Oneplus 8T/9R
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
@TheIncognito
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Trees:
Device: https://github.com/ApexLegend007/twrp_device_oneplus_lemonades
Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_s_12.1
Download:
https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Flashing Rom :-
Make Sure That you have OOS 12 firmware On both slots before flashing rom based on OOS 12 firmware
Copy Rom.zip in your internal Storage Take Backup if you want to take backup Data Backup instruction are given below
After Flashing rom format data and reboot
(!!!!! Warning After flashing custom rom zip The recovery will get changed to AOSP recovery in the inactive slot in which rom got flashed if you want to flash twrp in that same recovery you can do it in bootloader mode!!!!!)
TWRP for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T/9R are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
VBMETA
VBMETA_SYSTEM
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
Reserved For me
Reserved For me
@Siddhant221 Nice to see you here! Good work, and keep it up!
Twrp Lemonades skirrrrrrrrrrah nice job ...
Oho
Hi, could this recovery be tested on a oneplus 9 (LE2115)? fastboot boot or flash.
thx
javi2246 said:
Hi, could this recovery be tested on a oneplus 9 (LE2115)? fastboot boot or flash.
thx
Click to expand...
Click to collapse
It won't work as oneplus 9 is a gki device which requires other work over on recovery trees you can check on twrp.me for further to check if you device is available or not for twrp
Siddhant221 said:
It won't work as oneplus 9 is a gki device which requires other work over on recovery trees you can check on twrp.me for further to check if you device is available or not for twrp
Click to expand...
Click to collapse
thanks for the reply. I'm following the project in zulip to see if there is any news for op9
Hi, i have installed the latest 1.5 twrp on my 8T phone.
used the flash recovery, recovery is booting! but screen in not responding to any touch.
I can use only the power key and then recovery show lock, and ask to swipe to unlock, but screen is not responding.
I have OOS ROM 12 official.
with rooted kernel.
Unlocked.
Please fix, thank you for recovery!
Thanks! It works fine.
If I have OOS12 I can update it by TWRP? Incremental updates are allowed?
If I flash ROM (update, full rom) I must do it at slot A and after that change slot to B and do it again?
Any possibility to support 9 pro?
Any updates for A11?
As TWRP can sometimes take a long time to load, I modified the ramdisk to show a very dark, black splash screen to avoid the risk of burn-in.
Hey, where do I get the image file? Nothing shows up under the link for the release.
I see by the link provided in this topic's header a new version of TWRP based on OOS13 is available for download:
TWRP_V3.7.0_V1
Download:​https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases​​* Did someone test this version of TWRP already?
Siddhant221 said:
View attachment 5671251View attachment 5671257View attachment 5671259
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Extra Fixes :-
Switched To 60 fps from 30 fps
Variant Script Fixed
Boot Control Revision from 1.1 to 1.2
Added Fix for Transferring File Above 4GB
Added Recovery Recovery Variant Of Fastboot Client
Working :-
Decryption
Fixed TWRP Boot up time
Backup(except data partition)/restore
ADB/MTP
Flashing Rom
stock rom flashing
fastbootd and adb sideload
Etc. Cuz I don't remember What else I fixed and What was working
BUGS :-
Other Bugs You tell me that !!!
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Oneplus 8T/9R
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
@TheIncognito
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Trees:
Device: https://github.com/ApexLegend007/twrp_device_oneplus_lemonades
Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_s_12.1
Download:
https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Flashing Rom :-
Make Sure That you have OOS 12 firmware On both slots before flashing rom based on OOS 12 firmware
Copy Rom.zip in your internal Storage Take Backup if you want to take backup Data Backup instruction are given below
After Flashing rom format data and reboot
(!!!!! Warning After flashing custom rom zip The recovery will get changed to AOSP recovery in the inactive slot in which rom got flashed if you want to flash twrp in that same recovery you can do it in bootloader mode!!!!!)
TWRP for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T/9R are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
VBMETA
VBMETA_SYSTEM
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
Click to expand...
Click to collapse
Hello Siddhant221
* Does this verison (TWRP_V3.7.0_V1) works with Lineageos 20?
Gogi_M said:
Hello Siddhant221
* Does this verison (TWRP_V3.7.0_V1) works with Lineageos 20?
Click to expand...
Click to collapse
Yep try it

Categories

Resources