Database Develop

[RECOVERY][ROOT][TWRP 3.0.2-1]Galaxy A7 - SM-A710F/FD/Y/M - Exynos7580

Unofficial release -TWRP recovery for the Galaxy A7 - SM-A710F/FD/Y/M Exynos7580
UPDATE 14/4/2016: TWRP 3.0.2-0 released.
https://twrp.me/site/update/2016/04/...-released.html
TWRP is now v3.0.2-1
SEANDROID warning fix
New feature available in TWRP 3.0.0-0 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
F2FS support added.
Internal SUPERSU root option removed. This is to prevent boot loops on 5.11/6.0 devices
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
twrp_3.0.2-1_sm-a710
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
https://download.chainfire.eu/969/SuperSU/
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Credits: Me, Teamwin and my testers - nhthiencp
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

works like a charm 100%
thank u so much :good:

flash supersu error signature

haohoa2308 said:
flash supersu error signature
Click to expand...
Click to collapse
Redownload.

Hi Ashyx,
Saw that you posted TWRP for both A510F and A710F, any chance you could compile for the A310F too?
It would be very much appreciated!
Cheers

thomekh said:
Hi Ashyx,
Saw that you posted TWRP for both A510F and A710F, any chance you could compile for the A310F too?
It would be very much appreciated!
Cheers
Click to expand...
Click to collapse
I suppose one more won't hurt. If you've got the stock recovery, post it up.

ashyx said:
I suppose one more won't hurt. If you've got the stock recovery, post it up.
Click to expand...
Click to collapse
Wonderful, I've attached the stock recovery img (zipped).
Many thanks in advance

I have flashed this version of TWRP on my Samsung Galaxy A7 2016 SM-A710Y device. Many thanks.

Note: Downloads have been blocked until i remove supersu from twrp due to people incapable of reading instructions!

thomekh said:
Wonderful, I've attached the stock recovery img (zipped).
Many thanks in advance
Click to expand...
Click to collapse
Posted in the General section.

From where can I get stock recovery for A710FD...?

new and noob
wanna root my phone but i want to download stock rom first in case anything goes wrong. problem is i don't know which rom should i download. I've attached my phone's software info. thanks in advance

done! it works. I tried it even without backups. thanks button hitted

Many thanks, It works. now i can cheat offline game in my phone ^^.

Xposed installer
In this cell A7 2016 xposed installer running or not
Which modules are support please suggest me
Because i want to buy this cell

From where can I get stock recovery for A710FD...?
please

valiforu said:
From where can I get stock recovery for A710FD...?
please
Click to expand...
Click to collapse
The stock firmware, but why would you?

Incase the mobile has boot loop
For safety i want the stock recovery
From twrp recovery installed xposed installer some times mobile will be in boot loop for that i want the stock recovery

How is stock recovery going to rescue you from a bootloop?
For that you need a custom recovery like twrp to simply make a backup first.

Kk thank u
Can we install xposed installer in A710FD
Please suggest me its working or not

[RECOVERY] [UNOFFICIAL] TWRP_3.0_m86_patched_st0rm77

** BRICK WARNING/Disclaimer/Requirements **
>> Only flash with unlocked bootloader <<
>> Scripts are released under GPlv2 license <<
>> Run at own risk <<
Hi,
I patched the TWRP 3.0 recovery from faust93 to include important partitions
that make switching between different versions of Android/Ubuntu very simple.
All partitions are properly added to the fstab, but out of fear that some of
you will brick your device i disabled most of them.
Next version will contain a backup of all unique partitions, but i will have
to test this thoroughly.
Steps to install:
1. Download the zip file from attachments below
2. Unpack the zip file
3. Check checksum with md5sum -c *.md5
4. Put phone into fastboot mode (boot device with [vol-] and [power] button)
5. Flash recovery with:
# fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img
# fastboot reboot
then boot the device with [vol+] and [power] button, to enter recovery
[Requested by @p82maarj]
Already on an older TWRP version ?
- Flash "update_TWRP_3.0_m86_patched_st0rm77.zip" from TWRP
or
- Unpack the zip and flash the recovery manually in TWRP by selecting "install image"
Enjoy
Warning:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **

Hi @st0rm77
Thanks for your contrubution!
It will be good if you create a flashable zip of your new recovery. It can be flashed directly from the stock recovery or from the other twrp recovery without entering in fastboot.
Furthermore to have a flashable zip is usefull to flash a new rom update. For updating the new rom version I enter in TWRP, flash rom zip, flash unlocked bootloader zip and flash TWRP zip.
I attach the other flashable TWRP zip you can based on (only replace recovery.img by your recovery.img).

Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)

Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?

PYCON said:
Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?
Click to expand...
Click to collapse
Yeah, you get some extra abilities:
- Backup of Boot Logo
- Backup of Device Tree
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.

Thanks for everything you've been releasing, great work!

st0rm77 said:
Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)
Click to expand...
Click to collapse
Done Thanks!

st0rm77 said:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **
Click to expand...
Click to collapse
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!

Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?

PYCON said:
Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?
Click to expand...
Click to collapse
I know the answer to this one!
The first zip contains the img file that you can flash using fastboot.
The second (update) zip is the one you need if you already have (an older) TWRP and you wish to update to this version (use it from inside TWRP).

abePdIta said:
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!
Click to expand...
Click to collapse
boot.img is your boot partition, you need this one :good: (NEEDED)
bootloader is the locked bootloader from meizu, avoid this one as the plague (AVOID)
Dont brick your device, check everything carefully :fingers-crossed:

st0rm77 said:
Dont brick your device, check everything carefully :fingers-crossed:
Click to expand...
Click to collapse
Thank you very much! I will be careful in the future, I promise!

i follow the a to I tutorial
then unlock bootloader
then this
now when i conect meizu to pc i try to pass custom rom to internal memory and the phone restart
what is the problem
---------- Post added at 10:35 PM ---------- Previous post was at 09:56 PM ----------
managed to download the rom in phone browser now i have RR and all it´s ok

I flash stock recovery ( use update 5.1.10.0g) but not success, híc híc, help me restore stock recovery, many thanks!!!!

st0rm77 said:
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.
Click to expand...
Click to collapse
Just to be sure I understood :
Going from Flyme to CM :
-Backup Flyme (system+data+dtd)
-Flash CM archive
Going back to Flyme
-(optional) Backup CM (system+data+dtd)
-Restore Flyme (system+data+dtd)
Is there is a quikier way ?

TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:

help
hi .i change meizu pro 5 from china to national (5.6.1.19 daily )and unlock it and flash recover TWRP 3.0 but not login it the recovery .
i want updated

PYCON said:
TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:
Click to expand...
Click to collapse
I too vote for a port!

3.1.1 was released

munky-head said:
3.1.1 was released
Click to expand...
Click to collapse
Not for PRO5

Please make a detailed video of how to flash stock rom

Any devoloper here please make a detailed video of how to flash stock rom after a user installed custom rom in his phone this would be of a great help thank you in advance

Its so easy make a full wipe data then put the update.app to sd card and shut down the device then click power and vol + and vol - and it will go to stock rom force update...... try it will work

reddy.parameshwar said:
Any devoloper here please make a detailed video of how to flash stock rom after a user installed custom rom in his phone this would be of a great help thank you in advance
Click to expand...
Click to collapse
Can't make video for you, but if you find firmware for your device from here, you should be able to do it with this info.
http://hwmt.ru/hwmtsite/huawei-firmware-finder/
I think zip files from there have META-INF folder in them(check before flashing), so you should be able to flash them in TWRP recovery. If install is succesful, you should then (in TWRP) choose Reboot -> reboot recovery -> (it will boot to stock recover) choose factory reset/wipe data -> reboot -> you should be done now.
I'm not 100% sure will this work, but it should be safe to try if you have download correct firmware for your device.

keikari said:
Can't make video for you, but if you find firmware for your device from here, you should be able to do it with this info.
http://hwmt.ru/hwmtsite/huawei-firmware-finder/
I think zip files from there have META-INF folder in them(check before flashing), so you should be able to flash them in TWRP recovery. If install is succesful, you should then (in TWRP) choose Reboot -> reboot recovery -> (it will boot to stock recover) choose factory reset/wipe data -> reboot -> you should be done now.
I'm not 100% sure will this work, but it should be safe to try if you have download correct firmware for your device.
Click to expand...
Click to collapse
It will only work for full ota

im on lineage os 14.1 i want to install emui this is what i asked not what you thought anyway thanks for the concern

reddy.parameshwar said:
im on lineage os 14.1 i want to install emui this is what i asked not what you thought anyway thanks for the concern
Click to expand...
Click to collapse
My post was answer for your question,(if the site has stock firmwares for your device). Please read it again with care.

reddy.parameshwar said:
Any devoloper here please make a detailed video of how to flash stock rom after a user installed custom rom in his phone this would be of a great help thank you in advance
Click to expand...
Click to collapse
There are few options mate.
1- vua twrp backup
If you have taken twrp backup of stock Emui before flashing the custom rom then you can just restore the backup after clearing the cuatom ROM's system, data, cache, dalvik etc and then restore the twrp backup.
2- via dload method.
Flash the stock recovery for your phone in fastboot mode. Then download thw full stock firmware and put it in sd card under dload folder (extract the zip and out the internal content as meta, update.app and other folders under the dload). Power off the phone and press volume up+volume down+ power key and it will detect the package and start restoring it. Once successful, you will be on atock emui.
Let me know if not clear or doubt anywhere

[Recovery] TWRP (Unofficial/Experimental) for Samsung M40

We got our first recovery for Samsung M40 (SM-M405F). This one is ported using Samsung Auto TWRP recovery porter by Team Hovatek
Please try and let everyone know if it works for you or not.
(If you want to do it yourself for any other Android OS version, you can refer to the original Hovatek post.)
You must disable dm_verity before flashing TWRP.
TWRP based on version: 3.5.*
Details of base recovery used for porting:
Source: Extracted from downloaded firmware
Version: Android 11
Build Date: Mon, 12 Apr 2021 07:54:43 +0000
Security Patch Level: 2021-04-01
Product code: INS
PDA: M405FDDU2CUD2
CSC: M405FODM2CUD2
If this works for you, please post here so everyone will know.
If something goes wrong you need and any stock img/file let me know, I will share that too.
Update 1 =>
NOTE: Unfortunately, I can not test this recovery for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Update 2 =>
Instructions for NON-Rooted and Bootloader locked device-
Unlocking Bootloader:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Disable DM_Verity (Android Verified Boot):
Copy the vbmeta.img (download from attachments) into your adb and fastboot folder
You can now flash the vbmeta.img using fastboot to remove dm_verity from your device
// Enable USB Debugging and enter following commands in CMD/Terminal after connecting device to computer.
adb devices
// You should see your device listed
adb reboot-bootloader
// Device should reboot to bootloader
fastboot devices
// You should see your device listed
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
// OR if the command above doesn't work, try below
fastboot flash vbmeta vbmeta.img
// DONE
////////////////////////////////++++++++++++++++++++++++++////////////////////////////////
Note: For Magisk Rooted devices above steps are not required, as Magisk already patches vbmeta.img and disabled dm_verity (Android Verified Boot)
Flash TWRP with/without Root using Odin
1. Download and install Odin on your PC
2. Download the attached recovery.img, convert it into .tar
3. Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
4. Select recovery.tar under AP_ and Uncheck “Auto Reboot” in Options!
5. Flash the device
6. Now do not power on to System, enter into Recovery/TWRP mode using key combination.
Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
*DONE*
Enjoy TWRP!

Can you tell step by step procedure for flashing twrp in m40.
How to disable dm-verity?

I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.

Shashvatsawar said:
I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.
Click to expand...
Click to collapse
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.

did you already tested it on your device??

rohitrss said:
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.
Click to expand...
Click to collapse
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?

deadinside322 said:
did you already tested it on your device??
Click to expand...
Click to collapse
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.

Thread title and note updated.

Shashvatsawar said:
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.

rohitrss said:
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
Click to expand...
Click to collapse
I tried it But I am not able to boot into recovery then.
It just reboots.

Shashvatsawar said:
I tried it But I am not able to boot into recovery then.
It just reboots.
Click to expand...
Click to collapse
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?

I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know

Akhil137 said:
I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.

rohitrss said:
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?
Click to expand...
Click to collapse
I followed this thread to root my device
https://forum.xda-developers.com/t/root-sm-m405f-galaxy-m40.3951491/
There was no option of dm verity while patching stock rom using magisk.
Though My phone was successfully rooted.
I can't use fastboot as it's not showing my device in devices list ( tried a lot).
Finally I flashed your recovery using odin but after going to recovery mode it rebooted only. For recovery mode I tried key combination first and then a root app after device booted.

Updated post with detailed flashing instructions.

rohitrss said:
Updated post with detailed flashing instructions.
Click to expand...
Click to collapse
did the recovery work for you?

Is there any update?

When i try to go to bootloader, my device always go to download mode. how can i fix this???

rohitrss said:
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Click to expand...
Click to collapse
Bro, I am going to use twrp in my main phone M40.
And I don't care if it gets bricked :>

Question [Solved] Unable to install EU ROM :/

Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?

did you format data after flashing 12.5.20.0

marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)

Only fastboot Version available right now bro. Already using it.

If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only

marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password

why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line

marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved