Develop Bugs

[RECOVERY] KANG TWRP TF300T [email protected] JULY 28

TWRP for Transformer Pad TF300T
{
"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"
}
MUST BE ON A BOOTLOADER ENDING IN 27.1 or 27.5​​
Changelog 2.8.7.2
- All Upstream changes
- Small changes to the 'new theme' (thx z31s1g)
- Added flash to staging partition, via flash image feature
Changelog 2.8.7.1
- Removed ability to flash raw .img files....
- gui: keyboard: support longpress label offset, code cleanup ( Thx @_that)
- Added flashable zip
- merged upstream changes
Changelog- 2.8.7.0
- Fully merged 2.8.7.0 source from upstream
- Removed SU from twrp ( Its useless & only takes up extra room)
Changelog- 2.8.6.5
- New theme fully implemented ( Huge thx to @z31s1g ) Still a WIP
- Fix mount -o bind error on recreating /data/media/0 (Huge thx to @xiaolu ) & ( @_that )
- All upstream merges by Team Win
Changelog 2.8.6.1
- GUI: Prevent duplicate page overlays. Thx Matt & _that
- Replace legacy DEVICE_RESOLUTION with the new TW_THEME
- Using new common repo to build recovery.
- Build with grimlocks-5.1 kernel from zombi
- All upstream changes. Thx TeamWin
Changelog- 2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Changelog- 2.8.5.1
- Added dock sd card support to twrp
Changelog- 2.8.5.0
- Added formatting of ext sdcard for ROM2SD & DATA2SD
- Added ability to backup ext sdcard partitions
- Added reboot to recovery & reboot to bootloader from with TWRP
- Fixed error formatting /data to f2fs <- Thx Dees Troy for this fix
- A few upstream changes
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS​----------------------------------------------------------------------------------------------------------------------------------------
- Flashing recovery with fastboot.
- Boot tablet into fastboot.
Code:
fastboot -i 0x0B05 flash recovery foo.img
- Replace foo with the file name.
- Once flashed reboot into bootloader.
Code:
fastboot reboot-bootloader
- Enter recovery.
-FLASHING WITH 'dd'
You will need a super user terminal to make this work .....
Code:
su
Code:
dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4
Replace foo.img with the recovery image name .....
This will move the recovery image to /staging so on the next boot it flashes it to /recovery
So make sure you do a reboot before trying to enter recovery .......
This command also expects the image to be in /sdcard
----------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
TWRP for TF300T [KANG], Tool/Utility for the Asus Transformer TF300T
Contributors
lj50036, hardslog, DrBeaker
Source Code: https://github.com/zombi-x
Version Information
Status: Testing
Created 2015-03-05
Last Updated 2015-07-21

Downloads
OLDER VERSIONS
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FLASHABLE ZIP FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1

The more you know
JOIN US ON IRC !!!​https://webchat.frt/
Channel: ##zombi-x
HOW TO TAKE A RECOVERY LOG​You will be taking this log cause of some kind of error message .....
Once you get and error message, here is how to retrieve a recovery log ....
Using a PC with adb/fastboot installed on it, and if windows the correct drivers. ....
Code:
adb pull /tmp/recovery.log
This log will be in the same directory as the terminal/cmd window is cd'd into ....
Now you have the log, upload it to a pasting site or for download, and give us a link....

You are a sneaky bugger aren't you? :laugh:

hardslog said:
You are a sneaky bugger aren't you? :laugh:
Click to expand...
Click to collapse
You know me @hardslog .....

Could you remove showing the kernel boot and add dock SD card mount in next relese?

You may also want to add instructions for noobs... Is it a blob, img or zip... Is it flashable in recovery, fastboot... ijs...

Dredz said:
You may also want to add instructions for noobs... Is it a blob, img or zip... Is it flashable in recovery, fastboot... ijs...
Click to expand...
Click to collapse
it is a blob file for fastboot flashing.

Clamor said:
it is a blob file for fastboot flashing.
Click to expand...
Click to collapse
This, I know... However noobs and people just picking up this tablet may not. It's good to have the info in the OP to keep it from being asked hundreds of times in the thread.

Clamor said:
Could you remove showing the kernel boot and add dock SD card mount in next relese?
Click to expand...
Click to collapse
Yes I add the dock sd card, the framebuffer is part of the zImage and something we have for debugging ....
The framebuffer is going to stay, but I may be able to repack the recovery with a different zImage.....
I just dont know how much demand for it or time I would like to spend on it .....
Thx Josh
Dredz said:
You may also want to add instructions for noobs... Is it a blob, img or zip... Is it flashable in recovery, fastboot... ijs...
Click to expand...
Click to collapse
I will add some instrution over the next few days, yes ..... :good:
Yes for it is a blob, but the build outputs a recovery.img and I see no need to rename it .....
Thx Josh

I had in the 2.8.1 being able to repair an exfat 64GB external micro sd card.
Upgraded to 2.8.5 the only option is to change the file system. Went back to 2.8.1 and it no longer is available now.
Is this the same for others?
Regards
Duke

NEW KANG !!!
NEW TWRP 2.8.6.0 FOR ALL YOUR FLASHING NEEDS !!!!!
Changelog -2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Click to expand...
Click to collapse
Thx Josh

lj50036 said:
NEW KANG !!!
NEW TWRP 2.8.6.0 FOR ALL YOUR FLASHING NEEDS !!!!!
Thx Josh
Click to expand...
Click to collapse
is this for use with any rom or only for KANG Omni

lbeavisc said:
is this for use with any rom or only for KANG Omni
Click to expand...
Click to collapse
You should be able to use it to install any rom of your choice ...... :good:
Thx Josh

lbeavisc said:
is this for use with any rom or only for KANG Omni
Click to expand...
Click to collapse
Works great with KatKiss 5.1!
Just make sure that you do not try to install it from within TWRP, using the image installation functionality. I did that yesterday, and ended up without a recovery and with a tablet that would not allow me to install one. I had to do a backup/full wipe/restore of my tablet to revive it. No harm done, but I got a big scare!

KritonK said:
Works great with KatKiss 5.1!
Just make sure that you do not try to install it from within TWRP, using the image installation functionality. I did that yesterday, and ended up without a recovery and with a tablet that would not allow me to install one. I had to do a backup/full wipe/restore of my tablet to revive it. No harm done, but I got a big scare!
Click to expand...
Click to collapse
Its not an image ? its a blob .... :good:
Thx Josh

lj50036 said:
Its not an image ? its a blob .... :good:
Click to expand...
Click to collapse
Which is why one should definitely not do what I did, no matter how tempted one is!
BTW, can someone point me to a description of what the .img and .blob formats are? I haven't been able to find anything.

KritonK said:
Which is why one should definitely not do what I did, no matter how tempted one is!
BTW, can someone point me to a description of what the .img and .blob formats are? I haven't been able to find anything.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=36925180
Check out this thread by @_that lots of good info in there ....
Thx Josh

lj50036 said:
http://forum.xda-developers.com/showpost.php?p=36925180
Check out this thread by @_that lots of good info in there ....
Click to expand...
Click to collapse
Very enlightening. So, if I understood things correctly, if I unpack the recovery blob with blobunpack, then twrp_tf300t_kang_2.8.6.0.img.SOS, which is contained therein, is the actual image, which I could, theoretically, use with tools that handle images, such as the TWRP image installer. (I've learned my lesson, however, and will stick to the tried and true methods!)

KritonK said:
Very enlightening. So, if I understood things correctly, if I unpack the recovery blob with blobunpack, then twrp_tf300t_kang_2.8.6.0.img.SOS, which is contained therein, is the actual image, which I could, theoretically, use with tools that handle images, such as the TWRP image installer. (I've learned my lesson, however, and will stick to the tried and true methods!)
Click to expand...
Click to collapse
No the device will not flash an image.... It has to be a blob .....
There is alot of info in that guide......
Thx Josh

[Recovery][Official]TWRP for Xperia M

Team Win Recovery Project is a custom recovery built with ease of use and customization in mind. It has a fully touch driven user interface. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation/updating instructions and download links can be found on official device page. It is preferred to use official builds unless it is said otherwise in thread, so make sure you have read at least a couple of last pages.
My home builds can be downloaded here (link to the always latest build), it is useful when the latest official build is outdated and for testing new features. Site may sometimes be down due to maintenance.
And, as you remember, we are not responsible for bricked devices, accidental pregnancy or asteroid impact (BTW, this thread is created at Asteroid day).
Warning! Read attentively this post and F.A.Q. below and at least 5 pages of thread before installing this and posting here! Or Dark Lord will come to punish you and take your shallow soul! Also I kill innocent kittens every time when I see someone installs it via fastboot/flashtool. So save kittens and don't ignore provided info.
It uses the same FOTAKernel install method as recoveries in this thread, so you don't need to install it every time you change your ROM or kernel. Also it doesn't work on stock ROM, 'cause we don't have stock kernels supporting extract_elf_ramdisk utility.
To remove recovery from your FOTAKernel follow this (you will use recovery from your boot image after it).
Official TWRP website — here you can find more info about recovery itself, versions changelog, donation URL etc.
Thanks to:
@Dees_Troy and all other TWRP devs
@PecanCM for initial device tree
Linus Torvalds for Linux Kernel, it would not be possible without him
XDA:DevDB Information
TWRP for Xperia M, Tool/Utility for the Sony Xperia M
Contributors
cucumber09, Antrikos48
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.0.1-0
Created 2015-06-30
Last Updated 2016-09-15

F.A.Q. Must be read before installing and posting in the thread!
Q: Is it a kernel?
A: No, it isn't. It is a recovery image, but it is not booting independently, the kernel is using its ramdisk to load recovery. More... (extract_elf_ramdisk is deprecated in some ROMs and kernels, now its functions are implemented in init binary directly, read additional explanation from the next question if you are curious about how it works)
Q: Can I install it via Flashtool/fastboot?
A: No. For holy sake, don't do this! Here is explanation.
Q: Can I flash it with Rashr app?
A: Yes. But flash it as recovery, not as kernel! Read explanation above if you wonder why.
Q: Do I need to flash it every time I update my ROM?
A: No.
Q: Does it work with stock ROM?
A: No.
Q: TWRP says "Unmodified system partition" and asks to allow modifications or keep system read-only.
A: Tick "Never ask" and swipe. You can press "Keep read-only", but that really has no use on our device as we no more receive official OTA and ^look previous question^.

CHANGELOG
TWRP 3.0.1-0
support new CM 13.0 pattern encryption (sultanqasim)
fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
libtar updated to latest upstream and fixes (jcadduono)
fixes for loading custom themes (_that)
TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
translation updates - added Italian, Czech and Polish and significant updates to Dutch
progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
fix input box text display (Dees_Troy)
reboot option after zip install complete (bigbiff)
other mostly invisible bug fixes and improvements
Click to expand...
Click to collapse
TWRP 3.0.0-0
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse
Device-specific changes:
Enabled mass storage
Improved wiping cache speed and removed it from backup list
Increased system wipe speed
Update crypto from JB to current version for adopted storage decryption (1, 2)
Enabled NTFS-3g
Other fixes and improvements (commit history for nicki)

Yes! Yes!

Sir I have 2.8.5.0
can I flash 2.8.7.0 now, forgive me I'm not experience.
Thank you for your efforts[emoji2]
Sent from my C2005 using Tapatalk

Yeay!
Thanks buddy
Try it nowwwwww !!!!!
Sent from my waifu

kh34d said:
Sir I have 2.8.5.0
can I flash 2.8.7.0 now, forgive me I'm not experience.
Thank you for your efforts[emoji2]
Sent from my C2005 using Tapatalk
Click to expand...
Click to collapse
Yes, of course. There is link to instruction in OP.
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
Click to expand...
Click to collapse

I still not understand with resize2fs ?
My question is how to resize my 1gb system to 700mb and move 300mb to /data?
Sent from my waifu

itsnie said:
I still not understand with resize2fs ?
My question is how to resize my 1gb system to 700mb and move 300mb to /data?
Sent from my waifu
Click to expand...
Click to collapse
You are confusing it with repartitioning. Lollipop uses block-based OTA. Some of devices have versions with different storage capacity (e.g. 16 and 32 Gb). And when you install system image for the device with 16 Gb on device with 32 Gb you will have system partition like in 16Gb-version. Also, sometimes custom ROMs' system image is a little bit "cut". So, resize2fs fixes it, you will have as many system storage, as can handle your system partition. And this function is not very useful for our device.

cucumber09 said:
You are confusing it with repartitioning. Lollipop uses block-based OTA. Some of devices have versions with different storage capacity (e.g. 16 and 32 Gb). And when you install system image for the device with 16 Gb on device with 32 Gb you will have system partition like in 16Gb-version. Also, sometimes custom ROMs' system image is a little bit "cut". So, resize2fs fixes it, you will have as many system storage, as can handle your system partition. And this function is not very useful for our device.
Click to expand...
Click to collapse
Woah thngs!
Sent from my waifu

Why I can't find nicki in app?
Sent from my C2005 using XDA Free mobile app

arell said:
Why I can't find nicki in app?
Sent from my C2005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I forgot to mention, in some reason there is no Xperia M in app's list. I'll e-mail app's devs tomorrow if it won't appear.

hi
this recovery work in stock roms?

Miladj said:
this recovery work in stock roms?
Click to expand...
Click to collapse
Yes it will work I think, if you on unlocked bootloader condition
Sent from my C1905 using Tapatalk

Ok ,but can I use ZIP file in other thread or IMG file here??
There is two file now am I right??
Sent from my C2005 using Tapatalk

Nicklas Van Dam said:
Yes it will work I think, if you on unlocked bootloader condition
Sent from my C1905 using Tapatalk
Click to expand...
Click to collapse
not working!

Miladj said:
not working!
Click to expand...
Click to collapse
Calm down bro, why not working? You have to flash it with dd command right? And after that are you see some led pink when you restart device ?
Sent from my C1905 using Tapatalk

Finally its official!! All your hard work has paid off. .
Thanks a lot & congrats @cucumber09.

kh34d said:
Ok ,but can I use ZIP file in other thread or IMG file here??
There is two file now am I right??
Sent from my C2005 using Tapatalk
Click to expand...
Click to collapse
You can use both of them, if zip you must flash it via recovery mode but if boot.img you must flash it via adb with command dd if
Sent from my C1905 using Tapatalk
---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------
Nicklas Van Dam said:
Calm down bro, why not working? You have to flash it with dd command right? And after that are you see some led pink when you restart device ?
Sent from my C1905 using Tapatalk
Click to expand...
Click to collapse
If all what I said is still not working, you must flash old twrp boot.img that have function like recovery but not in fota partition. I've that file if you want it . but please try it before and calm down OK [emoji4]
Sent from my C1905 using Tapatalk

Miladj said:
this recovery work in stock roms?
Click to expand...
Click to collapse
Please, read the OP. It is clearly stated there:
Also it doesn't work on stock ROM, 'cause we don't have stock kernels supporting extract_elf_ramdisk utility.
Click to expand...
Click to collapse
So, stock is not supported, 'till someone builds stock kernel with all needed changes.
kh34d said:
Ok ,but can I use ZIP file in other thread or IMG file here??
There is two file now am I right??
Click to expand...
Click to collapse
Recovery in zip in other topic is compiled on my PC. Image file on TWRP download server is compiled by official TWRP build-bot. There is no difference in them, 'cause they share the same source code (but maybe official TWRP build uses a little bit older code, snapshoot when current version was released).

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

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version down below
2) Reboot to your current recovery or flash the recovery.img with dd on your recovery partition
3) Flash the provided archive
TWRP L7
Thanks @WinterR my tester​

Great work, it works beautifully!

Thank you to keep supporting the old Optimus L7

thanks!!!

Thank you for posting this, but I cannot install ROMs on my P705 now, as my device thinks it's a P700. Is there a way around this?

stephendt0 said:
Thank you for posting this, but I cannot install ROMs on my P705 now, as my device thinks it's not a P700. Is there a way around this?
Click to expand...
Click to collapse
I wiil see

Jonas Cardoso said:
I wiil see
Click to expand...
Click to collapse
Thanks. I believe all you would need to do is duplicate this and modify the device ID P705? I can of course modify the updater script of a ROM but that's always not fun.

Good work

Jonas Cardoso said:
I wiil see
Click to expand...
Click to collapse
Any luck?

stephendt0 said:
Any luck?
Click to expand...
Click to collapse
It's kind of hard to do, because the recovery will be different model of ROM, there will always give error in flash

Jonas Cardoso said:
It's kind of hard to do, because the recovery will be different model of ROM, there will always give error in flash
Click to expand...
Click to collapse
It's easy just remove model check from script

aidasaidas75 said:
It's easy just remove model check from script
Click to expand...
Click to collapse
If I am to remove all model check the script of ROM, it would be I make recovery image for each model would result in the same result, and taking into account que there are always two versions of the zip ROM p700 and P705 (P708 with a specific kernel and the camera libs), one without and one with nfc, it would be logical to use the nfc destroyer from caliban, gives same so that occurs at the L5 e612 and e610

Jonas Cardoso said:
If I am to remove all model check the script of ROM, it would be I make recovery image for each model would result in the same result, and taking into account que there are always two versions of the zip ROM p700 and P705 (P708 with a specific kernel and the camera libs), one without and one with nfc, it would be logical to use the nfc destroyer from caliban, gives same so that occurs at the L5 e612 and e610
Click to expand...
Click to collapse
You don't use nfc and camera in recovery and recovery kernel does not effect actual rom kernel so i think it would be better idea to build one recovery. Plus I will be releasing new twrp and cm12.1 then you could merge my changes to it

aidasaidas75 said:
You don't use nfc and camera in recovery and recovery kernel does not effect actual rom kernel so i think it would be better idea to build one recovery. Plus I will be releasing new twrp and cm12.1 then you could merge my changes to it
Click to expand...
Click to collapse
I know not have nfc or camera in recovery but for me to build a recovery for each model l7 she will have their IDs even though the same kernel, that's why he asked to build for the p700 and separate P705, when I update the recovery will separate them, by the way many users are having problems with your new TWRP to cm12.1 and baseband that comes with it

Jonas Cardoso said:
I know not have nfc or camera in recovery but for me to build a recovery for each model l7 she will have their IDs even though the same kernel, that's why he asked to build for the p700 and separate P705, when I update the recovery will separate them, by the way many users are having problems with your new TWRP to cm12.1 and baseband that comes with it
Click to expand...
Click to collapse
I havent release new baseband or new cm12.1 but people already has problem with it?

aidasaidas75 said:
I havent release new baseband or new cm12.1 but people already has problem with it?
Click to expand...
Click to collapse
I do not if you do not know or your ignorance but Androrid File Host is open by standard, and anyone can see the files, of course if visible, I'm just warning you, with that some users are having serious problems with that, my friend Antonio is helping, but if you do not mind is no longer my problem

Update twrp to 3.0.2-0
https://www.androidfilehost.com/?fid=24499762636002461

Jonas Cardoso said:
Update twrp to 3.0.2-0
https://www.androidfilehost.com/?fid=24499762636002461
Click to expand...
Click to collapse
I flashed the new version, boot splash now lasts much less, so the phone boots faster [emoji1] [emoji1]

Jonas Cardoso said:
Update twrp to 3.0.2-0
https://www.androidfilehost.com/?fid=24499762636002461
Click to expand...
Click to collapse
Filename is with p700. Is it good for p705?
Any problem for installing p705 ROM with this recovery? TIA!
Thanks for your hard work as always!! :good::good:

ecapella said:
Filename is with p700. Is it good for p705?
Any problem for installing p705 ROM with this recovery? TIA!
Thanks for your hard work as always!! :good::good:
Click to expand...
Click to collapse
You have no problem, only if you have the misidentification of the zip rom change in the script to the P705 that will work

[RECOVERY][arm64]TWRP Recovery [3.2.2-r1] [10 July 18]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This is my own unofficial customized build of 64 bit twrp for athene. It can be used on both Nougat and Oreo (32 bit and 64 bit ROMs) without any problem.
Known Bugs:
Encryption will not work. (Will be hopefully fixed in future builds) Not tested yet.
Changelog:
~~ -r2
* Overhaul twrp tree and add arm64 support
~~ -r1
* Based on AOSP/OmniROM 8.0.0_r32 release
* Fix stuck on 'black' screen entering recovery
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
How to flash:
By fastboot:
* You should have an unlocked bootloader and adb and fastboot set on your computer properly. Check this thread if you haven't done it already.
* Download the .img file on your computer and keep it in your adb folder (Windows only)
* Boot to fastboot mode and then connect your phone to the computer. Open a command window/terminal and
type this command:
To temporarily boot twrp:
Code:
fastboot boot <filename.img>
To flash it to the recovery partition:
Code:
fastboot flash recovery <filename.img>
~Note: Linux users might want to add "sudo" before the respective commands.
*Now manually reboot to the recovery mode using the volume down keys. The current ROM will patch the recovery partition to its earlier state if this step isn't performed and you directly reboot to the system.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
~From presently installed TWRP on the device:
* Copy the .img file to your phone and reboot to recovery
* Tap Install > Choose Flash Image > Navigate to the path where you copied the .img file and choose it.
* Choose Recovery Partition
* After the install being successful, go to home and tap Reboot > Reboot Recovery.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
Downloads:
Latest build: Direct Link
Older Builds: [url]https://sourceforge.net/projects/twrp-athene/files/[/URL]
XDA:DevDB Information
twrp-athene, Tool/Utility for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: [url]https://github.com/omnirom/android_bootable_recovery[/URL]
[url]https://github.com/rajatgupta1998/android_kernel_motorola_msm8952[/URL]
Version Information
Status: Beta
Created 2017-12-20
Last Updated 2017-12-20

is it compatible with shreps twrp backup?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

work roms 32 and 64 bits?

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

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

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

Reserved

Reserved

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

hi, is there any plan to support encryption??

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