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

Search This thread

kilabdg

Senior Member
Aug 20, 2009
190
12
Bydgoszcz
Hey. I don't know why, but it doesn't work for me. I've done it many times, but now - I can't!

After flashing root package in TWRP, system is booting with two informations:
Code:
KERNEL IS NOT SEANDROID ENFORCING
Code:
Set Warranty Bit : Kernel

When Im clicking in SuperSu icon, I have a information that SuperSu is not installed and it can't be - there is a problem! (some kind of it - translating from polish -> english).

What can be wrong?
 

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,087
9,930
Hey. I don't know why, but it doesn't work for me. I've done it many times, but now - I can't!

After flashing root package in TWRP, system is booting with two informations:
Code:
KERNEL IS NOT SEANDROID ENFORCING
Code:
Set Warranty Bit : Kernel

When Im clicking in SuperSu icon, I have a information that SuperSu is not installed and it can't be - there is a problem! (some kind of it - translating from polish -> english).

What can be wrong?
Flash the latest Supersu beta v2.79
 

kellyjelly34

New member
Feb 15, 2017
2
0
Hi there. After successfull flash of TWRP 3.0.2, when booting with hardware keys into recovery, I only get to the standard Android recovery, not TWRP. What am I doing wrong? I have a A500FU with 6.0.1...

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.

So I was able to get int TWRP once after flashing... How do I get back there once I leave it... Home+Vol-Up+Power only brings me in the standard Android Recovery and Home+Vol-Down+Power into Download-Mode. A hint would be appreciated...

On first start I was asked to mount read-only or sth... I have chosen that... So I assume I have to do the other to prevent the TWRP to be overwritten upon first 6.0.1 boot?

I flashed with Odin 3.12.5, have 6.0.1 on an A500-FU and put "twrp-v3.0.2-0" on the phone.

Okay after flashing the TWRP two more times, it's persistent now. Don't know why and how...
 
Last edited:

josephpatrick

Senior Member
Jan 24, 2012
1,211
237
Bangalore
Hi there. After successfull flash of TWRP 3.0.2, when booting with hardware keys into recovery, I only get to the standard Android recovery, not TWRP. What am I doing wrong? I have a A500FU with 6.0.1...



So I was able to get int TWRP once after flashing... How do I get back there once I leave it... Home+Vol-Up+Power only brings me in the standard Android Recovery and Home+Vol-Down+Power into Download-Mode. A hint would be appreciated...does

On first start I was asked to mount read-only or sth... I have chosen that... So I assume I have to do the other to prevent the TWRP to be overwritten upon first 6.0.1 boot?

I flashed with Odin 3.12.5, have 6.0.1 on an A500-FU and put "twrp-v3.0.2-0" on the phone.

Okay after flashing the TWRP two more times, it's persistent now. Don't know why and how...

My understanding is this, if you use twrp and reboot into recovery either using a 3rd party app or via reboot to recovey option available in power menu, the phone seems to get stuck in recovery, it does not boot into the Rom, the only way to get it to boot is to flash twrp recovery again

But this will happen every time you use the above method to get into recovery. Everything works just fine if you power off the phone and use the 3 hardware keys to get into recovery
 

Quisuff

Member
Mar 20, 2016
17
1
Samsung Galaxy S9
Hi there. After successfull flash of TWRP 3.0.2, when booting with hardware keys into recovery, I only get to the standard Android recovery, not TWRP. What am I doing wrong? I have a A500FU with 6.0.1...



So I was able to get int TWRP once after flashing... How do I get back there once I leave it... Home+Vol-Up+Power only brings me in the standard Android Recovery and Home+Vol-Down+Power into Download-Mode. A hint would be appreciated...

On first start I was asked to mount read-only or sth... I have chosen that... So I assume I have to do the other to prevent the TWRP to be overwritten upon first 6.0.1 boot?

I flashed with Odin 3.12.5, have 6.0.1 on an A500-FU and put "twrp-v3.0.2-0" on the phone.

Okay after flashing the TWRP two more times, it's persistent now. Don't know why and how...
I have the same problem. I stuck on stock recovery... :crying:
 

PJK2011

Senior Member
Dec 19, 2011
108
22
A500f Boot Loop Problem

I've spent all day fighting with the boot loop on my A500f.

I had the phone running really well with Ahmed's Resurrection Remix ROM on this post:

https://forum.xda-developers.com/sa...om-resurrection-remix-5-8-2-sm-a500h-t3572062

He doesn't detail TWRP installation, so I used DeadSquirrel's 3.1.0 post here:

https://forum.xda-developers.com/sa...overy-twrp-3-0-2-0-samsung-galaxy-a5-t3439233

I hadn't seen that TWRP can be installed without root, so I rooted with Chainfire first. I'm not sure, but I think I got the Chainfire file from this post:

https://forum.xda-developers.com/sa...-to-root-galaxy-a5-a500fu-lollipop-5-t3137613

The file I downloaded for the A500f is "CF-Auto-Root-a5lte-a5ltexx-sma500f.zip" (contains tar.md5)

The post says it is for Lollipop, but the instructions say this is a Chainfire root zip for Android 4.4.4. One post suggested this might be the cause of my boot loop.

The instructions say that this Chainfire Auto Root solution also contains a recovery file, but I was never able to boot into this recovery, so I went directly to installing DeadSquirrel's TWRP. I was able to boot into this recovery. From there I installed the Resurrection Remix ROM. WIthin the ROM, I installed SuperSU from the Play Store, but SuperSU informed me the phone was not rooted, so I flashed the SuperSU root zip from their website, which I believe was the file, A500FXXS1CQC2_A500FOJV1CPH3_XFE.zip

SuperSU now reported root was present, so I installed WiFi Connection Manager from the Play Store, granted it root access in SuperSU, and used the Fix Problems menu item to repair the wifi shutting off the phone problem that I was originally working on. That fix worked well, so I left the wifi on and ran YouTube on Autoplay for about 4 hours. Deciding the problem was solved, I gave the phone back to my son, and he brought it back to me dead 5 minutes later. I'm not sure if it already had the boot loop problem at that point.

The phone would no longer boot. I noticed a seandroid enforcing notification, and thought it might be a security issue preventing boot. I found a thread that said that flashing back to a Samsung ROM would remove the seandroid notice, and that I needed to update to Android 6.0.1 before installing TWRP to solve the boot loop issue. I went to Sammobile and found the newest 6.0.1 ROM for my A500f was the A500FXXS1CQC2_A500FOJV1CPH3_A500FXXU1CPH2_HOME.

I installed this in Odin, and the phone has never come back to me since then. I've made endless retries throughout the day, trying different combinations of the Chainfire root, different versions of TWRP, and different root methods, but all to no avail. One post even suggested that if you flash factory ROM from Odin just once, it will create a boot loop, but if you flash twice, it solves it, but it didn't work for me. It's also gotten increasingly difficult to get into recovery. Whether in stock ROM or TWRP, I was only able to get in about 10% of the time. Boot loop behavior has varied between boot logo - vibration - black screen and battery charge logo - vibration - black screen.

I found this thread, and tried these versions of root and TWRP, but it didn't help. At the moment, I'm on stock ROM. On power up, you get the Galaxy A5 screen, then it vibrates and goes black, then the lightening battery logo comes up, it vibrates, and goes black, and then the green battery status logo comes up, and then the phone goes black. It's also booting into stock recovery okay, and I can do the recovery functions. I just can't boot the phone.

So now, I try the instructions again in the original post here. Now I can get into TWRP. I power up and the phone sticks on the Galaxy A5 boot screen for a long time. Then it vibrates and repeats. It's basically the same as above, but there is a long delay before rebooting instead of instantly as before. Now I go back into TWRP and flash the Resurrection Remix ROM and the behavior is the same. Power up and get the Galaxy A5 boot screen for 8 seconds (this time sporting a warranty bit: kernal notice), 2 seconds of black screen, vibration, battery/lightening logo blinks on, then off, vibration, battery/lightening logo blinks on then off. Black screen, then standard battery charging percent indicator. I did that three or four times to make note of the behavior. Then the power switch wouldn't work, so I used the technique to press the volume up and down key together with the power key to turn it back on. Now it is in a non-stop 5 second cycle of vibrate - flash the icon - black screen that won't quit. Throughout the day I've been stuck with this in both stock and custom ROM. Only once during the day did I see the custom ROM boot all the way through. The stock ROM has never booted. I have done plenty of cache wipes and factory resets before and after flashing as well.

Now the recovery key combination won't boot TWRP either. The key combination just makes the Galaxy A5 screen flash instead of the battery icon. But I can get into TWRP by rebooting with the recovery key combination on leaving Download mode.

If anyone understands what's wrong here, I'd appreciate it.

Thanks
 
Last edited:

wooser

Senior Member
Jun 14, 2013
233
61
Hello ashyx. I am kind of a noob,so plz don't mind if I say something wrong.
I had installed twrp recovery a long ago I don't remember the thread. But at that twrp installation I was stuck on twrp. After that I never have tried to install that again . But now I need to install a hades kernel. Can you plz confirm me if I can rely
Advanced thankS ☺☺☺
 
Jun 30, 2015
6
1
I flash it via custom twrp and via odin both ways when i enter into the recovery and press reboot to system it stuck into boot lop keep entering custom recovery what can i do to prevent this??
thank you!
 

Top Liked Posts