Hello everyone,
I have a Galaxy a3 2016 of a friend with a broken screen (completely blank, no light, no touch).
I need to recover the data inside but, until now at least, I had no luck.
The device is completely stock (no usb debugging, no oem unlock etc.), so i cannot access it from kies or explorer on windows.
After installing Samsung USB Drivers and adb/fastboot on my pc i tried to connect in download mode but "adb/fastboot devices" command shows nothing.
I tried to flash a twrp recovery with odin but it fails in the beginning trying to write recovery.img.
In this thread
https://forum.xda-developers.com/samsung-a-series/help/help-broken-screen-recover-files-t3473540
a user states that i don't need usb debugging or anything to flash a custom recovery...but i still can't do it...
Am I missing something?
Thanks in advance!
Related
Hi everybody,
I formatted my note 4 using twrp and since my phone bootloops. When I connect it via USB, my pc doesn't detect it at all especially Odin (my phone is in download mode). Other devices like my S6 are normally recognised.
I only have access to recovery and download modes.
I tried to reinstall drivers in my pc but nothing changes.
Help please.
did you deleted some apps/bloatware if yes please restore this app called : MtpApplication , this can be the reason your pc cannot recognize your device.
I think you may formated system partition.so just download custom rom and flashi it via recovery
Hello,
I have installed a custom rom (Marshmallow) for my SM-A500FU through the adb. Now when I want to install a different rom I have to either boot into TWRP and I can't do that because booting into recovery simply restarts a phone, or I have to boot into Download mode and install it with the adb. The problem is that when the system is running, the phone simply charges, no Windows notifications or devices appear and when the phone is in Download mode Windows detects that a device is plugged in but can't recognize it. I have all the adb drivers, KIES and all that so it's not a problem. Can I somehow boot into TWRP or make Windows recognize my phone so I can use adb?
Thanks.
before installing a rom, have you wiped system, cache, dalvik and data? If yes try with a hard reset and if it doesn't work, too flash stock firmware
Hey,
yes, I wiped everything, I have flashed many roms earlier and I believe I have flashed it properly. I have managed to get into TWRP so I can actually flash FWs. I have only updated my rom to the newest CW13 build there is for my A5. Is there any way to flash a stock FW (for example a XEO KitKat) without ODIN? I can only use ADB through TCPIP and TWRP, so there is no way for me to flash it through ODIN.
Thanks.
so, if you press power+home+vol- it doesn't reboot in download mode, right?
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
whzq said:
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
Click to expand...
Click to collapse
Well, you can't flash samsung firmwares with twrp. Try flashing another rom through twrp
Alright, I have tried to flash multiple ROMs. Currently sitting on a Lollipop. Nothing changed, though. On every single ROM the problem still persists. It's not a problem with the PC as I've tried to connect my A5 to a laptop with freshly installed Windows and KIES and it behaved the same way as on my PC. The cable is fine as well, I have tested it with my old SGS3, it worked just fine on both my PC and laptop. Frankly, I have no idea what to do next, I'm starting to think that the port is physically broken. It's weird though, as I can still charge my phone and there is a response when the phone is in Download mode, just that Windows can't recognize it.
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
zyxw-androidiani said:
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
Click to expand...
Click to collapse
Yes, ihlf his device can boot he can use mobile odin. Have you tried with other PCs, just to see it isn't a problem of your pc?
In my experience usb device descriptor errors are related to the specific PC the error occurs on due to device driver conflicts, but if you get the same error on another pc then it could be the hardware.
I'd certainly be trying another cable first on a fresh PC.
Anyway regardless of all that you can flash the stock firmware with FLASHFIRE available on play as long as you have root.
Sent from my SM-T280 using XDA-Developers mobile app
Can i install any rom,recovery, with the help of stock recovery?
My device is not booting at all, it stock at galaxy s4 logo.
I can go to stock recovery & download mode
My pc & odin is not detecting my phone in download mode& recovery mode(I had changed about 10 data cables & 2 laptops windows 7,10 & all version of odin, I had tried installing every samsung drivers,kies, just every thing)
So plz help me out.
No, you can't.
And since your phone is not being detected, the only solution is to take it to a shop.
But if you can boot into odin or download mode then you have still a chance. Be sure you have a samsung driver to be able your computer and odin detect your phone
Is it possible the phone's USB port is damaged?
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Have you tried Download mode ( vol - home button and power button) ?
Viesuliss said:
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Click to expand...
Click to collapse
Just download official firmware and flash with odin. (Make sure not to downgrade os version. )
go to downloadmode, be sure drivers are installed, COM must be green,flash firmware with odin "only PDA", return into bootlader after reboot, flash twrp, boot into recovery mode done
Same thing happened to me.
Don't search for any file, the solution is very simple: download Samsung Smart Switch (only Windows, Mac version didnt work for me).
On menu click "Others" then "Emergency software recovery". Write A510F and then your phone Serial Number. Wait 30/60 mins ?
Sent from my SM-A510F using XDA-Developers Legacy app
Hello,
Recently I have rooted my samsung galaxy J5 SM-J500F phone. Next I opened OEM and enabled USB debugging, and then flashed TWRP with Odin. All went well, made a full backup (i.e. all the options were selected). I have stored the files on my PC, and then foolishly closed the OEM and USB debugging. Some time after I restarted my phone and I was met with the "Custom Binary blocked by FRP" screen. I could not boot into recovery, the only screen accessible was the download screen. I have hunted for a few firmware files, tried to flash them all to no avail. They are either being blocked by the FRP, or the "secure check fail" error (when trying to flash the PIT). I would like to
a) Repair the phone (my personal files can be deleted, no need for me to keep anything)
b) Prevent this issue for recurring (perhaps by disabling this FRP permanently in some way if possible)
Thanks in advance.
Kaizen-85 said:
Hello,
Recently I have rooted my samsung galaxy J5 SM-J500F phone. Next I opened OEM and enabled USB debugging, and then flashed TWRP with Odin. All went well, made a full backup (i.e. all the options were selected). I have stored the files on my PC, and then foolishly closed the OEM and USB debugging. Some time after I restarted my phone and I was met with the "Custom Binary blocked by FRP" screen. I could not boot into recovery, the only screen accessible was the download screen. I have hunted for a few firmware files, tried to flash them all to no avail. They are either being blocked by the FRP, or the "secure check fail" error (when trying to flash the PIT). I would like to
a) Repair the phone (my personal files can be deleted, no need for me to keep anything)
b) Prevent this issue for recurring (perhaps by disabling this FRP permanently in some way if possible)
Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572 That might be worth trying the OEM unlock needs to be left alone when it is unlocked and never touched again.