[UBL] Latest TWRP with f2fs support for Xperia SP (huashan) - Xperia SP Android Development

http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks

This work in miui v6

Thanks a lot for this quick update :thumbup:

Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.

Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.

pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing

Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?

@pilger i'm here, what to do next?

Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.

pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?

J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.

pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!

pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash

There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.

Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk

kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.

Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk

kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.

Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.

Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk

Related

[DISCONTINUED][RECOVERY] TWRP 2.7.0.0 [4.4 KitKat Compatible] - 3/25/2014

NOTICE: I no longer have a copy of the recovery image since goo.im went down. If anyone still has it, feel free to post a link. I'll leave the instructions here. Also, I won't be updating this since I no longer have a TF201 and ROM development seems to have shifted to a modified bootloader, which requires a different recovery image anyway.
Original post:
Warning: You must be on the 4.1.1 Bootloader to use this. Androwook and other stock based ROMs supply their own recovery.
With 4.4 based ROMs starting to come to our tablet, and official TWRP not flashing them, I thought I'd take a crack at updating it. As some of you may know, attempting to flash a KitKat ROM using the current version of TWRP fails, resulting in a "set_metadata_recursive" error. This updated version, based on the OmniROM fork of TWRP, fixes that.
Latest Version: 2.7.0.0-Voyager2k_v1.2
Instructions:
1.(Highly Recommended) Enable NVFlash if you haven't already. Check here for details.
2. Make sure you are on the 4.1.1 Jellybean Bootloader. If you are already running ParanoidAndroid or CyanogenMod, you're fine.
3. Download the recovery image here. The latest file is recovery1.2.img. EDIT: Links are broken. See above
4. You can use the same instructions that are on the TWRP page, but for convenience, I'll add them here. You have two options:
A. Fastboot. Boot the tablet into fastboot and use "fastboot -i 0x0b05 flash recovery recoveryX.X.img" (no quotes, replace X.X with whatever numbers are in the filename) from your computer to flash the recovery.​B. Flash from terminal within the tablet. Open a terminal emulator within android and type "su" (no quotes) to get root access. Then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4" (no quotes, replace X.X with whatever numbers are in the filename) to flash the recovery and reboot normally. This is critical, as the recovery won't flash until the system has rebooted normally.​
If successful, the version number should read: "2.7.0.0-Voyager2k-vX.X" (X.X being my revision number)
Known Issues:
1. /system/media doesn't get backed up for some reason. Restoring backups works, but you won't have sounds or a boot animation. (I think this is fixed in the newest version, but I'm waiting on other reports before I remove this item)
Ususal disclaimer: I am not responsible if this messes up your tablet in any way.
Credits:
TWRP for making the recovery
Built from the OmniROM fork. Source is here.
Changelog:
Version 1.1 - 2/19/2014
Added support for the dock keyboard
Fixed /system/media not backing up properly
Synced with latest OmniROM recovery sources
Version 1.2 - 3/25/2014
Updated to TWRP version 2.7.0.0
A little cleanup behind the scenes
one more.
Works Great! Flashed without problems via fastboot :victory:
Thank You!
Now I just need an awesome 4.4. ROM to flash :fingers-crossed:
works also with the second instruction over the tablet
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
thanks, it works through terminal. jut make sure to be root (su) and adjust the path of the recovery image
Sent from my EPAD using Tapatalk
thanks! This rec works and I have flashed cm11. Terminal works. U should insert "su" first
Sent from my GT-N7102 using Tapatalk
To use the second method you need to run su command first before using dd
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4
Terminal
Just would like to ditto.
The process worked in the terminal on the device.
Thank you for this!
Bug report!
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Dasdranamin said:
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Click to expand...
Click to collapse
Thanks for the report. I'll look in to it.
Cyrozo said:
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
Click to expand...
Click to collapse
Are you sure you placed the new "recovery.img" in the root directory of the sdcard? Won't work if the file is anywhere else.
Note 3 4.4.2
Does it work on note 3 with 4.4.2??
SAMERKAD said:
Does it work on note 3 with 4.4.2??
Click to expand...
Click to collapse
Nope, check your devices fora for compatible recoveries.
Bastaerd said:
Nope, check your devices fora for compatible recoveries.
Click to expand...
Click to collapse
can i bring back backed up data with other recovery?
SAMERKAD said:
can i bring back backed up data with other recovery?
Click to expand...
Click to collapse
You should be able to do so. Anyways, this isn't the recovery for your device.
Bastaerd said:
You should be able to do so. Anyways, this isn't the recovery for your device.
Click to expand...
Click to collapse
yeah i know, but i had it on 4.3 and backed up data via TWRP
now im on 4.4.2 with CWM Recovery...
want to restore my System data
Thankss
What bootloader is this compatible with? Does it work with the TF300T Bootloader? I am guessing not but someone from the Androwook thread might try it and that will not be good.
Seeing this is for kk support/ROMs, why would a wookie fastboot this?
Thank you Voyager for the ongoing support for the prime!
Sent from my VS980 4G using Tapatalk

[RECOVERY][bacon] Unofficial TWRP 2.7.1.0 [7-13]

Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Recovery flashable version here
Credits: Dees_Troy
dr87 said:
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Mount and unmount issues *may* be fixed (I haven't been able to reproduce them)
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Credits: Dees_Troy
Click to expand...
Click to collapse
Awesome job bro! Running like a champ!!
Sent from my One using XDA Premium 4 mobile app
Thanks a lot!
Now I can run Mahdi without problems!
thanks for this- but it's still not working- will i need to reflash madhi? i just fastbooted the recovery across and it boots into the recovery no worries and recognises all partitions but rom won't boot...
***edit*** it just booted up, about 5th attempt.. no boot animation though...ignore me...
Flashed recovery.img, bootet into recovery, no partitions..
Klarooo said:
Flashed recovery.img, bootet into recovery, no partitions..
Click to expand...
Click to collapse
Which rom were you running when you rebooted into recovery?
Stock, so CM11s.
mine still is not good. i treid to reboot to get it to hold the no hardware buttons. didn't reboot. tried about 10 times. eventually booted intot this new recovery and reflashed rom and booted it up. it's a bloody weird looking boot- no boot animation- made me think it was screwed again.
did you have to do anything to get it working again? Wipe entire device or just data partition?
Working good here, but I had no issues with the official build. I have an international version, 64GB OPO.
It's nice to see some additional features added, though.
Just helping out, packaged in a flashable zip for those with current CWM or TWRP recoveries, tested and working, enjoy everyone.
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Chris123NT said:
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Click to expand...
Click to collapse
Guys i wonder when you press efs restore is it
fastboot format modemst1 & st2
or
fastboot erase modemst1 & st2
or may be both? in that case in what order?
I flashed the one in OP, but the system does not see any partition ?
Can I flash 15th without bricking the phone
[EDIT] I tried a second time, and now it´s ok, partitions are there and backup is currently running
Any chance at adding F2FS support direct for this recovery for the ONE Plus?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Looks like the official .img version has been incremented to 2.7.1.1
More here: http://techerrata.com/browse/twrp2/bacon
A flashable zip for v2.7.1.1 would be nice.
Changelog? Hopefully they fixed those Partitions issues
2.7.1.1-Bacon Recovery Flashable zip
Mikey said:
2.7.1.1-Bacon Recovery Flashable zip
Click to expand...
Click to collapse
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
playya said:
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
Click to expand...
Click to collapse
Correct, easy huh
Delete the twrp.img......drag and drop the new img into the zip......dont uncompress the zip and compress it again.

[RECOVERY][G3][F400] TWRP-3.1.1 (Testing/170519)

TeamWin's TWRP Touch Recovery for LG G3 - currently available only for F400 variants​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/​
Flashing Instructions
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
OR
1. Move recovery.img to internal storage.
2. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
About this TWRP
compiled on LineageOS-14.1 source
always up-to-date
fixed screen brightness
permissive selinux
disabled logd/logcat in recovery
fuse exfat, ntfs-3g, jpeg, usb-otg support
external storage as default storage
touch to wake
backup of all partitions including modem, efs
crypto/decryption may work or not..
Changelog
* 170430
- Initial Build
- Disabled HW crypto due to build fails
* 170501
- Deleted unused flags
- Add back HW crypto
- exfat support
* 170507
- Disabled logd/logcat (fix for "device or resource busy", hopefully)
* 170519
- Updated to v3.1.1
- Fix Aroma Installer crash (hopefully)
Known issues
ZIP files with date check assert can't be installed (eg. crDroid) - Users should delete date check assert in binary by themselves.
AROMA Installer stucks at loading - will be fixed soon..
Download Links
Unofficial | Official
Sources​
https://github.com/TheNoFace/android_device_lge_g3-common-TWRP/tree/twrp
(Based on https://review.lineageos.org/#/c/160056/)​
Remember to do backup of your current recovery before installing​
Any plans for suporting other G3 variants in future?
@fprhqkrtk303: Now have 2 version twrp to flash. Which one to choose to flash? Unofficial or official? Thanks!
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
ahk31 said:
Any plans for suporting other G3 variants in future?
Click to expand...
Click to collapse
Planning to support more devices when F400 version is stable.
You can build your own TWRP using my source.
@chuyennho184 @andrewKode Official version from TWRP uses older device tree and actually no one maintains. Recommend using unofficial version.
@fprhqkrtk303: I saw update firmware on March 22th for F400 variants but I don't have a link. Do you have a link? Thanks for bother you.
Updated to v3.1.1 (170519)
fprhqkrtk303 said:
Updated to v3.1.1 (170519)
Click to expand...
Click to collapse
Is aroma bootloop problem fixed in this new version?
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Not tested yet. Can you check?
fprhqkrtk303 said:
Not tested yet. Can you check?
Click to expand...
Click to collapse
Yes. Tried it yesterday. Bootloop problem is still present.
andrewKode said:
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
Click to expand...
Click to collapse
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
ZjemCiKolege said:
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
Click to expand...
Click to collapse
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
andrewKode said:
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
Click to expand...
Click to collapse
1. I try but did not happen.
2. Build of lineage?(i flash each version from february to 21.04) no any issue.
3. Issue of custom rom(problem with turn on charger and boot same issue..) ;]
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Hello, apparently no...
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
If it's a software problem, it would be the problem of AROMA devs, but if it's related to software keys incompatibility it's will be the work of TWRP devs.

[RECOVERY][UNOFFICIAL][09/26] TWRP 3.1.1 w/F2FS for Shamu

No longer supported
Unofficial TWRP 3.1.1 w/F2FS
> For the Nexus 6 Shamu
This work is inspired by @The Flash's F2FS TWRP builds. I based this build off of the TWRP Minimal Repo.​​Features:
TWRP 3.1.1
F2FS Mounting and Formatting supported (En/Decryption not supported, however)
Built atop my kernel
Works
Changelog:
3.1.1-3
Updated sources to 7.1.2_r33, which includes updated f2fs-tools (1.8.0)
Minor GUI tweaks (splash screen, odd gap under "Advanced")
Bump to subversion 3
Installation:
You should know the drill of installing custom recoveries if you found this thread, but anyways:
Have an UNLOCKED Bootloader
Boot to fastboot/bootloader mode (Power + Vol Down from power off)
In adb (replace X with appropriate subversion):
Code:
fastboot flash recovery twrp-3.1.1_X-f2fs-unofficial-shamu.img
You can now reboot to your shiny, new TWRP!
How Do I convert to F2FS?
Backup important data to an EXTERNAL source; if formatting /data, entire internal sd will be wiped.
Ensure your kernel/kernel you will flash supports F2FS. You can use my kernel if you desire.
Reboot to this (or any other) F2FS supported TWRP
Go to -> Wipe -> Advanced Wipe
Tick the desired partition you want to format (ONLY do /data and/or /cache)
Select "Repair or Change Filesystem"
Select "Change File System"
Select "F2FS"
Swipe to Change
Done. Flash all your stuff!
Disclaimer:
I am not responsible for broken devices etc... Flash at your own risk. I am also not affiliated with the official TWRP crew nor Omni ROMs, so please don't complain to them about bugs unique to my own builds. ​
Sources:
Manifest
TWRP Recovery
Device Tree
Kernel​
XDA:DevDB Information
Unofficial TWRP for Shamu w/F2FS, Tool/Utility for the Nexus 6
Contributors
Black_Hat01, Omni Rom, and the great devs of TWRP itself
Source Code: https://github.com/BlackHat01/
Version Information
Status: No Longer Updated
Current Stable Version: 3.1.1-3
Stable Release Date: 2017-09-26
Created 2017-06-27
Last Updated 2018-02-10
Downloads
Download Latest 09/26 Build - 3.1.1-3
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Thanks a lot for this. Does it properly decrypt F2FS data?
Neejay said:
Thanks a lot for this. Does it properly decrypt F2FS data?
Click to expand...
Click to collapse
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
TMG1961 said:
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Click to expand...
Click to collapse
It should not reset your settings every time you boot into recovery, unless there is something wrong with your /sdcard/TWRP folder. Can you send a recovery log (Advanced > Copy Log)?
Will do that after finishing the install of the rom i am doing now.
TMG1961 said:
Will do that after finishing the install of the rom i am doing now.
Click to expand...
Click to collapse
Thank you. I ask because I am not having that issue at all. Maybe also try re-flashing recovery via fastboot before everything too.
what i did was this. Booted into bootloader. erased recovery, flashd your recovery and booted into it. wiped to allow changes and made changges to settings. Then booted back into rom. The rom i tried it with was stock 7.1.1.
I just finished installing velocity rom and flashed your twrp, same result. I did copy the log. said in twrp that it was copied to /data/media/recovery.log but the log is no were to be found on the phone. Did search the whole phone with root explorer
---------- Post added at 20:00 ---------- Previous post was at 19:59 ----------
when i try to do a backup i get error unable to mount storage
---------- Post added at 20:10 ---------- Previous post was at 20:00 ----------
I think the problem is something else. Not sure but twrp does not see my storage
Black_Hat01 said:
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
Click to expand...
Click to collapse
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Neejay said:
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
Click to expand...
Click to collapse
Thanks for the update. Will look into it.
Black_Hat01 said:
Thanks for the update. Will look into it.
Click to expand...
Click to collapse
No problem. I tried to look for his source, but couldn't find one for shamu directly. Here's where I downloaded his img (if it helps at all): https://forum.xda-developers.com/showpost.php?p=70452221&postcount=29
TMG1961 said:
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Click to expand...
Click to collapse
Can you flash my twrp and send log please? It is the correct log. I just need to see what's going on with mine. Thanks.
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
TMG1961 said:
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
Click to expand...
Click to collapse
That's odd. I was on Flash's 3.1.0-4 F2FS build and flashed mine right over that build and everything works fine for me (log copying works, settings stick fine, etc..), so maybe try flashing his build, then mine. Without a log, I can't really do much, since I, and nobody else yet has experienced the same issues. I'm going to do some work on it today, and I'll try to get a new build out tonight.
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
TMG1961 said:
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
Click to expand...
Click to collapse
Perhaps it is just your device. Anyways, I uploaded a new build, maybe try this one out. If it does not, try reflashing stock twrp 3.1.1 and then coming back to an F2FS modified one. Hope the best.
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
TMG1961 said:
...I just finished installing velocity rom
Click to expand...
Click to collapse
I thought that ROM ceased development a long time ago? Happen to have any links with more info on it? https://www.android-port.de/themen/rom-n-7-1-1-velocity-shamu.9596/
espionage724 said:
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
Click to expand...
Click to collapse
Thing is, by the time I posted, I hadn't realized he updated his. But the things that are different are basically the kernel the recovery image is built with (we use our own kernels), and the support. I will be actively building and supporting while The Flash has pretty much moved on from shamu to angler. Any bugs that arise I will try to fix and I will always be trying to keep everything updated. Over time our builds will start to become more and more different.

Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project

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.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 lite 5G
bugs:
backup/restore is unreliable
adb sideload and fastbootd
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Contributors:
@VladV1V , @TheMalachite
Tree:
GitHub - TeamWin/android_device_xiaomi_renoir
Contribute to TeamWin/android_device_xiaomi_renoir development by creating an account on GitHub.
github.com
Kernel:
https://github.com/VladV1V/kernel_xiaomi_renoir
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
Sorry, but the installation did not work for me... :-( What i have done:
- i renamend the downloaded file to "twrp.img"
- i copied this file to the internal storage
- i startet the phone in fastboot mode
- then i startet adb
- i used the command "fastboot boot twrp.img"
Then i saw the following:
downloading 'boot.img'...
OKAY [ 2.826s]
booting...
OKAY [ 0.201s]
finished. total time: 3.027s
But the phone only switched off and nothing happend. What's wrong?
EDIT: i solved the problem! I forgot to put the file "twrp.img" into the adb folder. After doing this, the installation worked! Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Hi, thank's for your work for our device...
I read somewhere, that if we have TWRP installed, that we cannot flash update with fastboot...I want to know if it's true and if yes, how can we flash update..we have to find recovery update, or we can extract from fastboot archive and flash it??
thanks for your answer
Rainman67 said:
Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Click to expand...
Click to collapse
certainly not available yet...you have to backup in internal storage and then copy to SD...
Another question: how to go back to stock recovery?
Rainman67 said:
Another question: how to go back to stock recovery?
Click to expand...
Click to collapse
I'm on Xiaomi EU ROM. After last update via fastboot Miui Recovery 5.0 comes back.
Great hopefully this leads to development of some easy to flash roms, cant wait to get rid of this buggy MIUI trash.
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
same with #8 boot into twrp and no touchscreen
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
Boot TWRP from fastboot and touch will work.
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
How did you flash it?
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Peterpaulmarie said:
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Click to expand...
Click to collapse
pm me on telegram if you can get logs and have adb access
dannejanne said:
Boot TWRP from fastboot and touch will work.
Click to expand...
Click to collapse
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
i just boot to try if it can boot in twrp lol, no need to flash it so far,if needed it i will use the method u guys said(real flash in)
Well then both of you make sure you're actually using the build from afh and only use it for fastboot boot, when you want to flash use flash current twrp don't flash it with fastboot
Touch works when using fastboot boot and when flashed, it Was already tested on multiple devices
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
doclucas said:
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
Click to expand...
Click to collapse
Touch already works normally without fastboot
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Yes, I can confirm. After start recovery wait 10-15sec touchscreen will work
With the test builds from telegram twrp was not able to recognize my SD card. Is this now fixed?
Is it possible to flash Xiaomi.eu weekly rom only by starting twrp from fastboot without installing it?

Categories

Resources