Develop Bugs

Root SM-A510F [A5 2016]

Hey,
I've tried rooting my SAmsung A5, however, I somehow cant access the teamwin/twrp menu.
I put the SUFile on my phones internal storage, USB DEBUG mode is on and OEM Mode as well-
I've flashed the twrp file with odin on the mobile successfully, however, now I'm stuck.
Whenever I press the volume up, homebutton and powerbutton after leaving the download mode the mobile just restarts the whole time and never accesses recovery mode until I release the keys and afterwards the phone just boots like usually, when I restart the phone and try to access the menu again a menu opens which says no command or something like that...
I also bricked the mobile after trying a few thing but restored it to stock firmware again, however, rooting still does not work..
can someone help me out?

MEHEYVISSE said:
Hey,
I've tried rooting my SAmsung A5, however, I somehow cant access the teamwin/twrp menu.
I put the SUFile on my phones internal storage, USB DEBUG mode is on and OEM Mode as well-
I've flashed the twrp file with odin on the mobile successfully, however, now I'm stuck.
Whenever I press the volume up, homebutton and powerbutton after leaving the download mode the mobile just restarts the whole time and never accesses recovery mode until I release the keys and afterwards the phone just boots like usually, when I restart the phone and try to access the menu again a menu opens which says no command or something like that...
I also bricked the mobile after trying a few thing but restored it to stock firmware again, however, rooting still does not work..
can someone help me out?
Click to expand...
Click to collapse
Sorry, you are in the a5 2017 forum not 2016. Anyway I think this should help you. DO NOT use the twrp files from there though. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

Cannot boot into download mode

Hi everybody, yesterday I was playing with my old Galaxy A50 trying to install a custom rom unsuccessfully.
I repeated the procedure three times installing TWRP and then Havoc OS but every time I tried to reboot from TWRP to OS I was stuck at the warning screen saying that the phone bootloader was unlocked and booting into download mode to reflash TWRP was blocked as it showed "only official binaries can be installed" (yes I installed Samsung disabler but still).
Still I was able to get the phone into download mode and reinstall the stock firmware as it seemed to be the only way to install and boot TWRP.
But at 4th time repeating the process I got frustrated, shut down the computer and left the phone on the warning screen still connected to computer usb cable.
Then I got back and noticed the phone was off as the battery died.
Indeed the battery died, so I put the phone in charging and after it reached 100% I tried to boot into download mode again to reflash stock firmware.
But here's the strange thing, I cannot boot into download mode anymore as pressing vol up+vol down while connecting usb cable, shows the lightning charge logo for 5 secs and then reboots infinitely with the same pattern.
If I force reboot by pressing vol down+power it shows the Samsung logo with the warning below it, then skips to another screen with another warning suggesting to press power button to continue (which does nothing) and after a while reboots to samsung logo.
So it doesn't seem it is bricked, it looks more like a battery controller fault, so I tried to detach the battery flex from the board, hoping it would reset the controller but it's still the same.
Also I tried with the flex detached and still no download mode is possible.
Was the download mode somehow erased? (if it's even possible considering it's the motherboard firmware)
If you need photos, videos or even a call on zoom, Skype, webex I would be glad to show you

same i got the same problem i can't find nothing for this when i press volume up and down and put the otg cable its simply charges but it gets stuck on the logo image there's no way to fix this but the only way is to open the phone,change the emmc and put one from samsung,close the phone flash a custom rom and you are done.

If you can enter recovery, do it. As soon as your phone gets into it, select the power off variant and then try to enter the download mode.
It seems like you did not unlock the bootloader, did you?

The bootloader Is unlocked i can't enter in the recovery because the phone locks on charging logo and its fully charged but when i try without charger It doesn't start.

Which Combination file for T830XXU5CUE2?

Hello,
I bought a "bricked" Galaxy Tab S4 on ebay. The only info I got was, that it is stuck in a bootloop since the last automatic update.
The bootloop is similar to this one. The tablet starts with the Samsung logo, then nothing happens and after a while I end up in recovery mode. Further, if I restart or hardreset the tablet, the screen stays black. The only way to boot it up again is to empty the battery while it is stuck in the bootloop. Afterwards I can enter download mode by holding "vol up and down" and plugin the usb cable.
In download mode this text appears at the bottom left:
#reboot recovery cause [unknown]
API: 3
manual mode 1.0.0
(Similar to this thread.)
OEM lock is on and of course I can't change this being stuck in the bootloop, or can I?
I successfully flashed the stock rom T830XXU5CUE2 with Odin3_v3.14.4 and latest samsung drivers. Unfortunately it does not help or fix anything. (I used virtualbox, but it worked and said "PASS" at the end).
After some research I would like to try my luck with a combination rom, but I can't find a U5 version which I should use because of T830XXU5CUE2, is that correct?
Any ideas how I could proceed from here? With OEM lock I guess there is no chance to flash TWRP on it?

Question S21 FE - endless bootloop and download mode/recovery not working (properly)

Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯

I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks

Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.

Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.

Question Pixel 6 Pro stuck in fastboot, not from downgrading.

Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.

I assume you didn't have OEM Unlocking enabled before this happened. Without an unlocked bootloader, there is nothing you can do to fix it, because the bootloader will reject any of the necessary commands to reflash the device. If you're still under warranty, seek warranty repair; this is going to require replacing the mainboard, because no one has the necessary tools to perform a low level reflash.
If the bootloader was unlocked, fixing this would be fairly simple because you'd just have to reflash the boot image. But, as I described above, a locked bootloader rejects all the commands that would help in this situation, and there is no way to unlock the bootloader if OEM Unlocking was not enabled.

dch29 said:
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
Click to expand...
Click to collapse
Kind of sounds like a stuck hardware button, either power and volume that's makes the phone think you are holding down buttons during boot to get into bootloader

Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google

Juuuuune said:
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Click to expand...
Click to collapse
Thanks but no change sadly, still completely booked.