Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
beastmaster6964

I bricked my Samsung Galaxy A5 2016 (FIXED)

Recommended Posts

Posted · Original PosterOP

Hello there,

First of all I'm new here... So I hope this is the right category. ^^ 
Today I tried to root my Galaxy A5 2016 with the Model Number SM-A510F. My goal was to flash Lineage OS 17 so I can try some sweet Android 10. Unfortunately I was not able to get TWRP working in the first place... It failed after the bootloader mode, even though I switched on USB Debugging and OEM. So I decided to try it with Odin. But even with Odin and my device being in the download mode I was not able to get the TWRP image working. It simply did not install it (Odin even said it was installed successfully, but it didn't. Woops.) After that I tried CF-Auto-Root (https://autoroot.chainfire.eu/). Surprisingly this one actually worked! My device now was rooted. I then decided to give the official TWRP App a try and install the image twrp-3.4.0-0-a7xelte.img directly onto my phone. (I think this is where my error began, I should not have tried this right?) The installation was successful, but I was not able to go into the TWRP recovery mode where I could flash Lineage OS and Gapps... So I selected the "reboot in recovery mode" option in the TWRP App. The device shut down, but then froze in the boot loading screen. Since then I was not able to boot it again. Furthermore I was not even able to get into Samsung own recovery mode from now on (by pressing the home button, power button and volume up). The only mode I actually got working was the download mode, in which I also installed CF-Autoroot in the first place. And now I have no clue how I can get my device working again... I'm not able to boot or even do a factory reset (since I cannot even enter the recovery mode). My PC does not recognize my phone. Only when I turn the download mode on, but then I does not recognize it as "Samsung Galaxy A5", my PC tells me I have connected something different. 
What should I do now? Should I wait until the battery is empty and then try to reboot it? You guys are my only hope. Help would be greatly appreciated. :(

Link to post
Share on other sites

Did you properly unlock the bootloader in Fastboot, or just enable OEM unlocking which allows you do proceed to unlocking bl?

 

Did you flash TWRP to recovery only, or just to the entire device?

 

Can you make it into Fastboot?


Quote me to see my reply!

SPECS:

CPU: Xeon X5650 OC'd to 4.4GHz @ 1.36V (courtesy of @XR6) Motherboard: Asus Sabertooth X58 RAM: 4x4GB G.Skill DDR3 1866MHz GPU: Asus RX 570 Strix Storage: WD Blue 1TB and a 128GB Kingston UV400 PSU: EVGA 600B Case: Fractal Design Define C Monitor: 3x Dell P2210 on a Steelcase Eyesite triple monitor stand Mouse: Logitech G403 Prodigy Wireless Keyboard: It changes, but usually Focus FK-9000 Mousepad: Steelseries QcK XL Headphones:  Sennheiser HD598SE

 

 

 

 

i use arch btw

Link to post
Share on other sites
Posted · Original PosterOP
9 minutes ago, kelvinhall05 said:

Did you properly unlock the bootloader in Fastboot, or just enable OEM unlocking which allows you do proceed to unlocking bl?

 

Did you flash TWRP to recovery only, or just to the entire device?

 

Can you make it into Fastboot?

Yes, well at least I think so. I typed "adb reboot bootloader" in cmd, It asked me If I want to grant permission and then rebooted into bootloader mode.

I only flashed TWRP to recovery via the App.

Nope, I does not let my Fastboot 

Link to post
Share on other sites
Posted · Original PosterOP

Okay, fixed it. Tbh I don't exactly how this worked, but it let me flash the stock firmware via Odin and wiped out TWRP and CF-Autoroot. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×