Database Develop

[RECOVERY][v500/palman] OFFICIAL TWRP [3.2.1]

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.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD (palman): https://dl.twrp.me/palman/
DOWNLOAD (v500): https://dl.twrp.me/v500/
More info: https://twrp.me/devices/lggpad83.html
Warning: builds for v500 require kitkat bootloader. If you are stuck on Lollipop bootloader, check this post.
Device source (palman): https://github.com/TeamWin/android_device_lge_palman
* The kernel in palman source is from 5.1 official build (source found here).
Device source (v500): https://github.com/TeamWin/android_device_lge_v500
* The kernel in v500 source is based on cm-14.1 sources.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG G Pad 8.3
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2015-06-15
Last Updated 2017-12-10

Thanks very much for this! Great work! That is really nice that there is now official support for awifi/v500.
I assume the images are bumped?
Are the kernel sources for official twrp using your kernel sources?

Sources
This is the device repo for awifi/v500: https://github.com/TeamWin/android_device_lge_v500
The kernel in awifi/v500 repo was compiled from here, which is V50030A based.
This is the device repo for palman/v510: https://github.com/TeamWin/android_device_lge_palman
The kernel in palman/v510 repo is from 5.1 official build.

So, now we should be able to just flash the .img file directly within TWRP to update.

Deltadroid said:
So, now we should be able to just flash the .img file directly within TWRP to update.
Click to expand...
Click to collapse
Yes!
The repo for v510 is going to be renamed since it doesn't need to follow the "cyanogen" way, which is using the model name instead of the device name. That's why there is a little confusion with the names v500/awifi and v510/palman. The GPE repo will be named palman (which is the correct way) and the non GPE repo will stay as v500 (it should be called awifi), since almost every custom rom uses "cyanogen" way. If we wanted the non GPE to be named correctly we would need the devs of every custom rom to add an assert to their boardconfig so both, v500 and awifi, would be valid at installation time. It's just one line change.

Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?

fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?

luisbraz said:
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
Click to expand...
Click to collapse
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
aidfarh said:
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
Click to expand...
Click to collapse
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?

fefifofum said:
Why would you need to backup recovery partition?
Click to expand...
Click to collapse
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.

fefifofum said:
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
Click to expand...
Click to collapse
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work

I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.

aidfarh said:
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
Click to expand...
Click to collapse
Old versions will still be available to download, so if a new version had issues you could always download and install an older version. No need to backup recovery I guess...
luisbraz said:
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
Click to expand...
Click to collapse
We don't need loki anymore, you just need to be on kitkat bootloader.
luisbraz said:
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
Click to expand...
Click to collapse
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.

fefifofum said:
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
Click to expand...
Click to collapse
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!

luisbraz said:
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
Click to expand...
Click to collapse
Glad to hear that! It seems the app TWRP manager cannot reach the new servers where official builds of TWRP are, so it's better not to use the app installation method to avoid installing old versions.

@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.

bokoy said:
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
Click to expand...
Click to collapse
I guess V50010B bootloader is what you need, but then you will probably have brightness issues while using this recovery.

New version
TWRP 2.8.7.0 released.

fefifofum said:
TWRP 2.8.7.0 released.
Click to expand...
Click to collapse
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!

Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.

D4xel said:
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Click to expand...
Click to collapse
This one is official (without the quotes), doesn't require loki and is adapted to kitkat bootloader backlight. The other one you mention is adapted to jellybean bootloader backlight and requires loki. Just install the one that fits your needs.
cianz94 said:
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
Click to expand...
Click to collapse
You have the install instructions on the first post. You can also download the image and flash it with THIS APP.

[OFFICIAL] TWRP 2.8.7.0 [Materialized Theme] - Xiaomi Redmi Note 4G DIOR

[OFFICIAL] TWRP 2.8.7.0 [Materialized Theme] - Xiaomi Redmi Note 4G DIOR (Single Sim)
NOTE: This is for the QCOM variant of the Redmi Note, otherwise known as Redmi Note 4G, and NOT the MTK variant of the Redmi Note. In short, this ROM will NOT work on the MTK variant of Redmi Note 4G
NOTE: We are looking for active developers and testers to help our team (Team Revior) who are already working on the CyanogenMod 12. If you want to help, please knock us.
You can follow our Google+ Community for new updates on our latest developments of Cyanogenmod 12 and other ROMS:
https://plus.google.com/communities/109685043900289167281
Special Credits
@haoyangw
(I had no idea about making ROMs and Wang constantly helped me with fixing the errors I faced. Without his trees and help, this wouldn’t be possible. )
Credits
Team Revior
@suhasgta
Shubham
@stane1983
@Silesh.Nair
@sm_94
Syhost
CyanogenMod
XDA
Downloads
https://drive.google.com/folderview?id=0B3ezpQ7wyZXlcU9fRFZ0R3g4ems&usp=sharing (select TWRP Custom Recovery Folder)
http://bigota.d.miui.com/tools/MiPhone2015731.exe (download to install fastboot and adb drivers)
Sources
https://github.com/faheemkamal/OMNI_TWRP_android_device_xiaomi_dior
Installation
1. With fastboot:
Extract recovery.img from the zip file
Run fastboot
Enter the following command "fastboot flash recovery recovery.img"
2.With MiRecovery using flashable zip:
Copy the zip file in root of internal storage
Rename it to update.zip.
Enter into recovery (volume up + power)
Install update.zip from SDcard.
Reboot.
3. With CWM or TWRP using flashable zip:
Copy the zip file in root of external sd card
Enter into recovery (volume up + power)
Install zip from SDcard.
Reboot.
The link to my CM12.1 for DIOR can be found in this link : http://forum.xda-developers.com/redmi-note/orig-development/cm12-1-redmi-note-4g-single-sim-t3197441

reserved

reserved

reserved

You finally did it bro! Congratulations! Everything works!

shubhamkarande said:
You finally did it bro! Congratulations! Everything works!
Click to expand...
Click to collapse
hehehe yeah. thanks bro

daviduco said:
It gets stuck every time i choose REBOOT SYSTEM. I have to hard reset the phone.
It happened the first 2 times, now it works, :S
Nope, definitely there's something wrong with this recovery, it gets stuck from time to time and i have o hard reset to exit.
Click to expand...
Click to collapse
Yeah. It's actually a bug on the twrp itself. The developer maybe missed that.

This stable version or not?

Can you release a dark version??
TheAqib
Send from my RedMi Note4G

reboot problem
Is there a problem with rebooting from recovery? Almost never am I ever able to reboot to system from recovery. It just freezes if I click reboot to system. At first, I thought I flashed wrong and there is no OS in the phone, but later I just switched it off and switched it on again, and it worked just fine. Also, later I just went to recovery and selected reboot to system and it froze.

droid_cyborg said:
Is there a problem with rebooting from recovery? Almost never am I ever able to reboot to system from recovery. It just freezes if I click reboot to system. At first, I thought I flashed wrong and there is no OS in the phone, but later I just switched it off and switched it on again, and it worked just fine. Also, later I just went to recovery and selected reboot to system and it froze.
Click to expand...
Click to collapse
same with me , now my device is stucked on recovery its not booting, even after fulll wipe and after flashing miui rom.
someone plz help me out

[Script] Boot/Recovery image signature patcher for Zenfone 2 [Z00A/Z008/Z00X]

Last update: 17.10.2017
Introduction
This is a small flashable script that will add the device signature for z00a, z008 or z00x devices to boot and recovery image. This function is part of my Zenfone 2 toolkit which primary supports stock rom users, but could be useful for any other custom rom user too.
It will fix any kind of missing signatures on boot or recovery that could happen, e. g. if you updated magisk within magisk manager, installed anything that modified boot image with proper device signatures or flashed a new twrp recovery. If you want to patch the recovery image, you should temporary boot a (probably older but) properly signed twrp recovery first of course.
I hope you find it useful. I appreciate any kind of code improvement, just leave me a note.
Usage instructions
​
[SIZE=+1]Just flash attached zip in custom recovery[/SIZE]
Downloads
Main: Downloads tab (see above)
Thanks to/Credits
Code:
:: > topjohnwu
:: > ggrandou
:: > gerasiov
XDA:DevDB Information
Image signature tool for Zenfone 2, Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Beta
Beta Release Date: 2017-10-17
Created 2017-10-18
Last Updated 2018-09-11

Attachments
Most current version:

Great work! This is awesome!
Now I can update OTA LineageOS and keep Magisk without the need of a computer.

rummsbumms said:
Most current version:
Click to expand...
Click to collapse
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily

Big thanks for this great tool bro. :good:

drixse said:
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily
Click to expand...
Click to collapse
Did you succeed with installing twrp 3.2?

sushuguru said:
Did you succeed with installing twrp 3.2?
Click to expand...
Click to collapse
I don't try yet. I would like to be sure how to proceed first.

drixse said:
I don't try yet. I would like to be sure how to proceed first.
Click to expand...
Click to collapse
Well, i don't think you should, twrp is not released yet for our device.

thanks a lot bro..really very helpful :good:

Very useful，but I still don't know why bootloader already unlocked，it still need the signature to boot

Thanks a lot man! Worked like a charm!

Thanks m8! Works like a charm!

Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?

marcossanches said:
Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?
Click to expand...
Click to collapse
Yes
Sent from my ASUS_Z00A using XDA Labs

can you add boot signature for z00d?

Then after installing Magisk...
- I have to flash this ZIP to make the system boot?
- Or just leave it?

Pls make signature fix for z00d?

Nothing to do for z00d?

@rummsbumms, have you got something for z00d?
Thanks in advance

towerman said:
@rummsbumms, have you got something for z00d?
Thanks in advance
Click to expand...
Click to collapse
sorry for the confusion, this script doesn't support the z00d as I don't know anything about this device. i've fixed the typo in the first post.
have you already tried the verified boot signer from chainfire? that tool is the best way to sign boot images! my script just adds a signature, which is a signature generated with oem keys but for an older boot image, to the current boot image. so the signature is valid but doesn't fit to the boot image. this way you can boot but get a red exclamation mark on each boot. if you use the verified boot signer, a signature with a custom key will be generated and added to the installed boot image. that signature is valid and fits to the boot image, but isn't created with oem keys from asus. this way you can boot too but get a orange (or yellow? i don't remember) exclamation mark on each boot.

Redmi 4X: TWRP, LineageOS, Gapps (Cannot update ROM) (nightly) *error*

Hi everyone,
I'm new here though but am a Xiaomi user from the beggining of Xiaomi into devices with Redmi Note 3G Enhanced.
Currently, I own a Redmi 4X and I would like your expert lights please. I've flashed the latest twrp from twrp.me for my santoni device. Then flashed the latest build from LineageOS Official source + Gapps before booting up for first time. Everything was working perfectly until I decided to flash the latest update of LineageOS as I've seen in my updater it was released. So, I downloaded it through the updater and tried to flash it...
I came up with this "Failed to unmount /system (device or resource busy)" after that re-booted to LineageOS and everything was messed up with Google Services & Apps etc. Then I went back to twrp recovery and tried to flash again the rom but I was still getting that message so I understood something am doing wrong. Also santoni has dm-verity enabled which I know something about but just an info. I really wanna stick with LineageOS on my Redmi 4X forever but I'm afraid to flash it again. I've flashed MIUI 10 Beta by fastboot but now I wanna go back to LineageOS forever (addicted).
My only problem is: After successfuly flashing LineageOS and Gapps, I cannot apply (flash) updates to update the ROM to the latest nightly build due to this error above.
Kind regards,
peryson

Try with different recovery. For example with this

Harukey said:
Try with different recovery. For example with this
Click to expand...
Click to collapse
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?

peryson said:
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
Click to expand...
Click to collapse
You can download latest Lineage OS build and dirty flash it (without any wipes) (so you can unmout system parition). And I don't see any issue in using unoffical twrp.

I also have experienced same error once during upgrade "failed to unmount /system"
Eventually I wiped everything and did clean flash from scratch. This is really annoying issue and demonstrates that upgrade system is not 100% reliable for some reason.
I'm not sure however is it Lineage or twrp issue.

[TWRP 3.6.0_9][SERRANOVELTE GT-I9195I] Galaxy S4 miniVE [UNOFFICIAL]

TWRP 3.6.0_9 FOR Samsung Galaxy S4 mini VE (2015)​
* I'm not responsible for bricked devices, dead SD cards
FEATURES
-Standard TWRP 3.6.0_9 features
-Data encryption and decryption support (has to be tested)
-Built with Pie 9.0 sources
BUGS/KNOWN ISSUES
-None so far
INSTALLATION via Odin
1. Download TWRP tar file recovery.tar to your PC
2. Reboot to bootloader mode ( download mode )
3. Open Odin... choose AP and select the downloaded file recovery.tar
4. Connect your phone to usb and click start
DOWNLOAD
TWRP-3.6.0_9-serranovelte
CREDITS
TWRP Team
Sources
TWRP: https://github.com/minimal-manifest-twrp
Kernel: https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
XDA:DevDB Information
[RECOVERY] TWRP 3.6.0_9 for Samsung Galaxy S4 mini VE, Tool/Utility for the Serranovelte GT-i9195i
Contributors
mernurisha
Version Information
Status: Stable
Created 2019-08-06
Last Updated 2021-12-07

Hi,
This TWRP 3.3.1-0 can not detect my SD-card (recovery.log). Your previous TWRP 3.3.1-0 that I got from you, mernurisha, can see the SD-card in the recovery mode.

Hello, I am asked to install the Image whether on the Boot or on the Recovery partition. Which one do I have to take?

Sarahcc said:
Hello, I am asked to install the Image whether on the Boot or on the Recovery partition. Which one do I have to take?
Click to expand...
Click to collapse
Recovery partition.

ffox.pl said:
Recovery partition.
Click to expand...
Click to collapse
Okay, done. And how to full wipe? Mean which partitions? Dalvik, System, Internal storage, Data, Cache? It is been a long time since my last installing :laugh:
Arrghhh, I forgot to wipe now I got Error 7
Oh, I think the PixelExperience cannot be installed on the serranoveltxx (with the two x). I thought because danil's LineageOS 14 was running on my device
Do I have to reinstall the TWRP to an older version now?
Okay, I should have to reboot TWRP *facepalm* :silly:

-----

Hi
i catched a bug.
when backing up more than one partition TRWP restarts after first digest generation of the first backed up partition
thank you for your work and also thanks for providing a more recent build of lineageos 16

new twrp update
New synced TWRP source.

update for SD-Card not recognized
For people with external SD-card problem (ffox.pl, radiac1987, JFK1975) ...
Please test the last twrp and report if your SD-card is recognized in the TWRP.
Maybe I can fix this issue for next LineageOS and PixelExperience rom.

mernurisha said:
For people with external SD-card problem (ffox.pl, radiac1987, JFK1975) ...
Please test the last twrp and report if your SD-card is recognized in the TWRP.
Maybe I can fix this issue for next LineageOS and PixelExperience rom.
Click to expand...
Click to collapse
Works great in the TWRP. I will check later if it also detects my SD-card on your ROMs.

mernurisha said:
For people with external SD-card problem (ffox.pl, radiac1987, JFK1975) ...
Please test the last twrp and report if your SD-card is recognized in the TWRP.
Maybe I can fix this issue for next LineageOS and PixelExperience rom.
Click to expand...
Click to collapse
I confirm the TWRP works perfect. Even the error "/sbin/postrecoveryboot.sh process ended with ERROR: 1" disappeared. Thank you. Your latest ROMs still don't recognize my SD-card.

ffox.pl said:
I confirm the TWRP works perfect. Even the error "/sbin/postrecoveryboot.sh process ended with ERROR: 1" disappeared. Thank you. Your latest ROMs still don't recognize my SD-card.
Click to expand...
Click to collapse
Okay. The last twrp recognizes your sd card, right?
For me it is important first, that the sd card is recognized in the last twrp.
Then I can do that for my next roms updates too.

I have installed CWM recovery and Cyanogen Serranolte android version 6 on my S4Mini
I saw that there is a Lineage OS16 version availabel for the S4 Mini. Tried to flash that with CWM recovery - that failed
So I try to download TWRP 3.3.1 via Odin3 version 3.1.3 over CWM - but Odin Download of TWRP (https://androidfilehost.com/?w=files&flid=297571 ) recovery.tar fails with size error
---------- Post added at 07:55 PM ---------- Previous post was at 07:14 PM ----------
Swellhead said:
I have installed CWM recovery and Cyanogen Serranolte android version 6 on my S4Mini
I saw that there is a Lineage OS16 version availabel for the S4 Mini. Tried to flash that with CWM recovery - that failed
So I try to download TWRP 3.3.1 via Odin3 version 3.1.3 over CWM - but Odin Download of TWRP (https://androidfilehost.com/?w=files&flid=297571 ) recovery.tar fails with size error
Click to expand...
Click to collapse
Succeeded to download TWRP (https://forum.xda-developers.com/galaxy-s4-mini/orig-development/recovery-twrp-3-2-1-0-t3736888) with Odin and boot into TWRP Recovery

mernurisha said:
... The last twrp recognizes your sd card, right?
Click to expand...
Click to collapse
Your August 17 release of TWRP-3.3.1-0 recognizes my portable card. Thank you!

twrp update
_ New synced TWRP source
_ F2FS support
Download on the first page

Hi, is there any chance to have zip or img for flashing like update from older TWRP? Thanks

gnomishe3 said:
Hi, is there any chance to have zip or img for flashing like update from older TWRP? Thanks
Click to expand...
Click to collapse
Extract the recovery.img from .tar and install it via older twrp as an img file. That's all.

The most frequently created copies are damaged. Their creations take up to 30 minutes. This happens when the default digest option is enabled. After switching off digest the process is saved in 4 minutes.

ffox.pl said:
The most frequently created copies are damaged. Their creations take up to 30 minutes. This happens when the default digest option is enabled. After switching off digest the process is saved in 4 minutes.
Click to expand...
Click to collapse
I've never used the digest generation and have no problems restoring backups.

Impossible to download TWRP-3.3.1-0-serranovelte.tar
Hello,
Thanks for your incredible job,
but unfortunately , there is no possibility to download TWRP-3.3.1-0-serranovelte.tar, because any mirror site is found on android file host...
Could you repair that maybe ?
thanks a lot
Laurent
mernurisha said:
TWRP 3.3.1-0 FOR Samsung Galaxy S4 mini VE (2015)​
* I'm not responsible for bricked devices, dead SD cards
FEATURES
-Standard TWRP 3.3.1-0 features
-Data encryption and decryption support (has to be tested)
-Built with Oreo 8.1 sources
BUGS/KNOWN ISSUES
-None so far
INSTALLATION via Odin
1. Download TWRP tar file recovery.tar to your PC
2. Reboot to bootloader mode ( download mode )
3. Open Odin... choose AP and select the downloaded file recovery.tar
4. Connect your phone to usb and click start
DOWNLOAD
UNOFFICIAL BUILDS
https://www.androidfilehost.com/?fid=1899786940962581780
CREDITS
TWRP Team
Sources
TWRP: https://github.com/minimal-manifest-twrp
Kernel: https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
Version Information
Status: Stable
Current Stable Version: 3.3.1
XDA:DevDB Information
[RECOVERY] TWRP 3.3.1 for Samsung Galaxy S4 mini VE, Tool/Utility for the Serranovelte GT-i9195i
Contributors
mernurisha
Version Information
Status: Stable
Created 2019-08-06
Last Updated 2019-08-16
Click to expand...
Click to collapse