Database Develop

[RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A5(2015) SM-A500F/FU/G/H/M

Unofficial release -TWRP recovery for the Galaxy A5 - SM-A500F/FU/G/H/M, Qualcomm MSM8916
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
SEANDROID warning fix
Recovery reboot fix
Modem, APNHLOS, EFS and Recovery partition backup
29/4/2016 - Time offset fix
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.
Flash with TWRP:
Extract the recovery.img from the tar archive then in TWRP select Install>>Install image.
twrp_3.0.2-1_sm-a500
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:
http://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
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- icesehman, -CALIBAN666-, jimbomodder
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
.
.

I'll be keeping an eye on this thread

Thankyou.... Working Fine..
No reboot issue.. A500G

Any tried to see if aroma files now flash OK?
From the giver of stock roms
Edit..
Works fine finally [emoji122] [emoji122]

Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!

jazzzzy said:
Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!
Click to expand...
Click to collapse
Isn't there already twrp for A700FD?

ashyx said:
Isn't there already twrp for A700FD?
Click to expand...
Click to collapse
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!

only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.

icesehman said:
only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.
Click to expand...
Click to collapse
Thank you.
OK, I'll try to disable wanam's power menu and flash TWRP. I'll write the result. ...
I disabled wanam's power menu, flashed TWRP 3.0.0 without autoreboot ticked and rebooted into recovery.
Then I set time settings in TWRP and started backup. Backup completed...
Reboot from TWRP (Reboot System) - Reboot normal !!!
I will watch its behavour ... and perhaps the problem is solved.

jazzzzy said:
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!
Click to expand...
Click to collapse
I'll see what I can do, time permitting.

So Far So Good.
Good job Mr. @ashyx , I've tested this recovery and two problems fixed out of three.
SEANDROID Error: Fixed.
Recovery reboot : Didn't fixed
EFS, APNHLOS etc... partitions Backup : Fixed
I reverted back to 2.8.7.0 recovery until recovery reboot get fixed.
I'll post a recovery log soon.
I'm using A500H Duos.
Thanks.

Ahmed_Khalifa said:
Good job Mr. @ashyx
Recovery reboot : Didn't fixed
Click to expand...
Click to collapse
Others say this issue is fixed?

ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
That links for a300
Sent from my SM-A500FU

Whoops wrong thread!
Sent from my HTC One_M8 using XDA Free mobile app

Little Confused.
ashyx said:
Others say this issue is fixed?
Click to expand...
Click to collapse
Are they using A500H or other variant?

Ahmed_Khalifa said:
Are they using A500H or other variant?
Click to expand...
Click to collapse
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?

recovery reboot problem.
ashyx said:
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?
Click to expand...
Click to collapse
Here is what I did:
I flashed the recovery via flashify.
I rebooted the device normally.
After the phone restarts, it shows the Yellow colored warning Set warrenty bit: recovery.
The device boots into TWRP recovery mode.
After that I press reboot -> system.
After restart, it goes back to step 3.
Thank you.

That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app

If we reboot directly to recovery, i mean through wannam xpossed power menu, recovery reboot issue occurs.. Pls fix this too..
Otherwise all are perfect

the error still exists.
ashyx said:
That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I used the flash option in TWRP but it still reboots into recovery.
I posted a recovery log maybe it'll help you fix the problem.
by the way, can you tell me which baseband,pda,csc you're using?
my software might be a little old?
Thanks.

Unable to Unbrick phone

Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.

abdullah.ahsan11 said:
Hey guys,
My younger brother had TWRP installed on his OP3. Yesterday he applied OTA and his phone got bricked. I unbricked it from MSMtool method (Qualcom Driver). It got unbricked and i have stock rom now however phone is stuck at android is upgrading (45 minutes). I tried restarting it and now it is in boot loop. i tried to flash latest OxygenOS from adb sideload and it got bricked again. Can anyone tell me what to do now or what is wrong with the device.
Click to expand...
Click to collapse
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.

Puddi_Puddin said:
You have TWRP installed? Use Method 2 of the unbrick guide. Now you want to wipe every partition then adb push your rom (not sideload) and manually flash it. Make sure you are on the latest Bluspark twrp.
Click to expand...
Click to collapse
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working

abdullah.ahsan11 said:
I am using method 2, the OS gets stuck on bootloop that's why i tried to sideload later
I don't have a working recovery, all i can get is stock recovery, how can i install twrp?
I've tried flashing (fastboot flash recovery recovery.img) it but it is not working
Click to expand...
Click to collapse
Why is it not working? Does it give an error or something?

Puddi_Puddin said:
Why is it not working? Does it give an error or something?
Click to expand...
Click to collapse
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.

abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.

Puddi_Puddin said:
Nah, In windows, go to Device Manager. How does your device show up? It has to do with wrong drivers.
Click to expand...
Click to collapse
Yes It shows up correctly.

abdullah.ahsan11 said:
Yes It shows up correctly.
Click to expand...
Click to collapse
What is correctly? What does it say? You might want to try different ADB drivers. You should be able to always flash In fastboot..

abdullah.ahsan11 said:
Yes, it says flashing partition not allowed.
I suppose it is because usb debugging is off.
Click to expand...
Click to collapse
Check again the bootloader to be unlocked. Use the tool for that, is it on OP3 forum, then retry to get a stock rom up before anything else (TWRP, custom rom, etc)
Sent from my OnePlus3 using XDA Labs

follow this instruction -
1- go into twrp and wipe everything even internal and formate it .
2- unistall all adb driver and oneplus driver also .. then clean tmp file from window
3rd- install latest adb+ oneplus 3 driver ..again restrat ..
4th-boot in fastboot mod and lock your bootloader
5th-flast latest build of oxygen stock recovery from fastboot
6th than again wipe or factory reset the device via stock recovery
7th open stock recoery than flash latest build of oxygen os via sideload
8th reboot the device and setup quikly
9th-unlock bootloader, flash bluespark recovery , flash rom, flash supersu ..
10th play with device

Root para android 9.1?

Root can be done on Emui 9.1?
root for emui 9.1
Please

nothing yet?

nesoler said:
nothing yet?
Click to expand...
Click to collapse
Maybe this works with a magisk patched recovery_ramdis from EMUI 9.1 firmware?
I found the firmware here.

it gives me the error, error: cannot load 'recovery_ramdiskMagiskAL00-b7f69238.img': No such file or directory

htcdesire-hd said:
Maybe this works with a magisk patched recovery_ramdis from EMUI 9.1 firmware?
I found the firmware here.
Click to expand...
Click to collapse
it gives me the error, error: cannot load 'recovery_ramdiskMagiskAL00-b7f69238.img': No such file or directory

nesoler said:
it gives me the error, error: cannot load 'recovery_ramdiskMagiskAL00-b7f69238.img': No such file or directory
Click to expand...
Click to collapse
You first have to be on EMUI 9.1 and then patch your recovery_ramdis via Magisk (like with EMUI 9.0).
And you have to flash it via fastboot and the patched recovery have to be in the same folder. (fastboot flash recovery_ramdisk <your patched recovery>.img)

htcdesire-hd said:
You first have to be on EMUI 9.1 and then patch your recovery_ramdis via Magisk (like with EMUI 9.0).
And you have to flash it via fastboot and the patched recovery have to be in the same folder. (fastboot flash recovery_ramdisk <your patched recovery>.img)
Click to expand...
Click to collapse
I did everything and it didn't work

nesoler said:
I did everything and it didn't work
Click to expand...
Click to collapse
So you also did a full wipe after flashing the patched recovery?
What symthoms do you have if you say it did not work?

htcdesire-hd said:
So you also did a full wipe after flashing the patched recovery?
What symthoms do you have if you say it did not work?
Click to expand...
Click to collapse
I have not done factory reset. Is it mandatory to do so?

nesoler said:
I have not done factory reset. Is it mandatory to do so?
Click to expand...
Click to collapse
Yes unfortunatelly it is mandatory.
I would do the following:
backup all data
do a factory reset via settings
boot to fastboot after setup
flash your magisk-modified recovery via fastboot
reboot to recovery directly afterwards (unplug and press power and volume up until device is booting to recovery)
there should be the stock recovery surface where you do the factory reset again
phone should boot up rooted (Magisk Manager has to be installed afterwards)
(did not test it myself)
P.S.: due to a new filesystem it is probably not possible to modify the system folder I found out...

htcdesire-hd said:
Yes unfortunatelly it is mandatory.
I would do the following:
backup all data
do a factory reset via settings
boot to fastboot after setup
flash your magisk-modified recovery via fastboot
reboot to recovery directly afterwards (unplug and press power and volume up until device is booting to recovery)
there should be the stock recovery surface where you do the factory reset again
phone should boot up rooted (Magisk Manager has to be installed afterwards)
(did not test it myself)
P.S.: due to a new filesystem it is probably not possible to modify the system folder I found out...
Click to expand...
Click to collapse
I will hope that there is a safer method, thanks

nesoler said:
I will hope that there is a safer method, thanks
Click to expand...
Click to collapse
Not now due to the new filesystem-type... Maybe it will be fixed in the future by Magisk dev team...

s10e boot loop

after i shut down twrp i am stuck in this loop
youtu .be /52AGLD69B2o
is there any solution ?
i can't run recovery or download mode

didn't make any changes in twrp

did you format and flash the multidisabler?

Player04 said:
did you format and flash the multidisabler?
Click to expand...
Click to collapse
Formated many times and last time flashed TWRP S10e Magisk Prepatched
didn't use any disabler in twrp

fixed by @ZeroXO
fixed by @ZeroXO

Dhowom said:
fixed by @ZeroXO
Click to expand...
Click to collapse
Please tell me how you fixed this, I have the same issue today. Willing to wipe everything or whatever, but I need to get it to boot into recovery first which it just won't.

[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 :>