Database Users

[Q] Galaxy S-5360 No Download Mode, but Recovery Mode Works

I am new to posting, but I have followed XDA for a long time and used it to install custom ROM's on other phones. However, I now have a problem with my wife's Samsung Galaxy GT-S5360L. I have searched for hours, but can not find a solution.
The phone is stuck in a boot loop. I can enter stock recovery mode. When I try to perform a factory reset, I get the following message:
E:format folume: rfs format failed on /dev/stl11
formatting /cache
Data wipe complete
After wiping the cache partition, the phone continues to be stuck in the same boot loop after reboot (Samsung logo appears on screen, followed by animation, back to Samsung logo).
The phone will not enter into download mode. When I press power+volume down+home, I see a white screen, followed by a black sreen, followed by another white screen. the suggested method of removing the battery, SIM, and SD card, and plugging into the computer while holding both volume buttons does not work. Odin will not recognize that the phone is connected.
I tried to connect the phone to two different computers. One runs Linux mint with Windows XP on a VM. This computer has always worked for flashing ROM's to other phones. Odin would not recognize the phone, and I received messages that the device was not properly installed.
I then tried to connect the phone to another computer with Windows Vista. This PC has Kies installed and Samsung drivers. Kies would not connect to the phone, and I also received messages that the device was not properly installed. Odin would not recognize the phone. I should note that the phone has interfaced with this computer sucessfully before.
This phone has never had a custom recovery or ROMs installed. It only has the original stock ROM. Is the phone's hardware defective, or can it somehow be fixed? Please post any links to threads that I may have missed. Thanks.

Download mode is only effected by a change in bootloader normally by Flashing incompatible firmware or a hardware fault
For flashing via odin kies is not required - its useless as it's not compaitable with the galaxy y for this purpose
You just need the Samsung USB drivers available from my firmware thread (links in signature)
It maybe possible to still flash the device
Once USB drivers installed
Enter download mode
Connect USB to pc
When the white screen appears push Vol up
Wait a few seconds
Open odin
Put the 3 firmware files in their places & flash
If it doesn't flash you will either need to flash a new bootloader via a jtag (repair shop) Or replace the motherboard - either way unless you can get it done very cheap it's more economical to buy a new phone

Thank you marcussmith2626 for your sound advice. The phone is working again. I will share the problems I solved in order to flash the stock ROM. Hopefully this will help anyone else that may have a similar problem.
The Samsung USB drivers had been previously installed on my PC running windows vista. I installed the drivers so that I did not have to use the bloated Kies software. However, when I tried to connect the corrupted phone to the PC via USB, it was not recognized, even though the correct drivers were installed. Below is the procedure I had to follow in order to connect the phone:
1. I connected the phone to the computer via USB. The phone had the battery installed and was powered off. After connecting to the computer, the phone started charging (battery icon on screen). Connecting in download mode at this point did not work. The phone must be powered off.
2. When the "found new hardware" notification box appeared, I had to make a note of each device that had been discovered.
3. I then had to open Device Manager from the control panel and find each device (the name in Device Manager matched the name in the new hardware notification).
4. I right clicked on each unknown device and selected "update driver software"
5. In the next menu, I selected "Browse my computer for driver software"
6. In the following menu, I selected "Let me pick from a list of drivers on my computer"
7. This brought up a list currently installed drivers. I selected the Samsung phone driver.
8. The driver then installed for the selected device..
9. Steps 2 through 9 were repeated for each new device discovered by Windows (each device listed in the "found new hardware" dialog).
10. I started the phone in boot mode (power+home+volume down, phone still connected to PC). I saw only a white screen. However, when I pressed the volume up button, the phone connected to the PC. Odin recoginized the phone and the stock ROM was flashed.
So, even if you only see a white screen, download mode can still be active. In my case, the drivers on the PC were not working correctly, probably due to the corruption of the original stock ROM. The drivers can only be added on my PC using the above method. The option to choose from a list of currently installed drivers was not available from the found new hardware wizzard.
Also, I will also say for reference that in the USA, the stock ROM from Brazil is the one that should be used so that the phone broadcasts on the proper GSM frequencies.

My tablet samsung galaxy tab e get stuck on the logo

hi everybody, i got a problem with my tablet, it's a samsung galaxy SM-t113Nu, i modified stupidly the file build.prop(cause my menu button doesn't work)and get stuck on the logo.
My pc can't recognize as a mobile, multimedia or usb device (appears as "SAMSUNG-Android" ) but recognize it as a device not specified
when i tried to enter into recovery mode i select "apply update from adb", why this is the only way that my pc can install a driver as mencioned above, else , just is an "unknown device", even in download mode is an "unknown device"
in adb mode appears as :
List of devices attached:
300492ee86641200 sideload.
so, i think i need a update.zip that contains a factory file build.prop, sideload maybe is the only way to send a package to mi tablet via pc.
please help

Galaxy s7 edge won't connect to computer

I had tried to root it and it was working fine. Until i tried to restart it and now it just says Kernel is not seandroid enforcing and custom binary blocked by FRP lock. I have oden and the stock firmware but now when i try to plug it into my computer in the downloading screen. On my computer it comes up as "Unknown USB Device (Device Descriptor Request Failed). I have tried to use smart switch, samsung kies 3, and downloading samsung usb drivers. I have tried switching ports and cables. I cannot start up the phone and I cant connect it to the computer?? PLEASE HELP

If you cannot startup your phone eg put into download mode than your phone is bricked and you should send it for repair.

You are giving conflicting messages. You state that your phone cannot start up. Yet you also say that you are getting the seandroid enforcing and custom binary blocked by FRP lock message which means that the phone does start, only does not follow though to the start screen. I have stated in a previous post from you on the same subject that the Unknown USB Device is a windows error message and not an android error message. I would suggest trying someone elses android phone and see if you pc recognizes that. Or/And you could install the Samsung drivers on someone elses pc and see if you can connect your android to that pc.

Galaxy A3 A300F Too many issues. Look at the list.

Hello guys, my friend give me Galaxy A3 A300F. This device has many issues.
1. Device stuck on black screen with text "Samsung Galaxy A3" in middle & "Powered by android" in bottom. (I'm talking about the very first screen)
2. After 20 minutes, it proceeds to coloured samsung logo animation and boots up.
3. I noticed that it heats up during booting process & after too.
4. After boot up, it will restart automatically after few minutes.
5. If it holds up after booting for few minutes, i tested whether my computer detects it but i got no signal. I check it under DEVICE MANAGER and i found nothing. (With & without USB debugging enabled)
6. When i connect it to computer, the device start charging but there's no notification of USB plugged in.
7. I dial up *#0808# or whatever to configure usb settings to USB + ADB. Still there is no connectivity.
8. No IMEI found.
9. I put it in DOWNLOAD mode and connect it to PC but still there is no detection.
10. The still have access to stock recovery but no sign of detection. No adb devices found.
11. And ofcourse, ODIN did nothing.
I think that if somehow, PC detect it, then i'll do something.
Now, if you guys have any method left, plz share it. I'm so interested to fix this device. Waiting for your messages.

adnanahmed008 said:
Hello guys, my friend give me Galaxy A3 A300F. This device has many issues.
1. Device stuck on black screen with text "Samsung Galaxy A3" in middle & "Powered by android" in bottom. (I'm talking about the very first screen)
2. After 20 minutes, it proceeds to coloured samsung logo animation and boots up.
3. I noticed that it heats up during booting process & after too.
4. After boot up, it will restart automatically after few minutes.
5. If it holds up after booting for few minutes, i tested whether my computer detects it but i got no signal. I check it under DEVICE MANAGER and i found nothing. (With & without USB debugging enabled)
6. When i connect it to computer, the device start charging but there's no notification of USB plugged in.
7. I dial up *#0808# or whatever to configure usb settings to USB + ADB. Still there is no connectivity.
8. No IMEI found.
9. I put it in DOWNLOAD mode and connect it to PC but still there is no detection.
10. The still have access to stock recovery but no sign of detection. No adb devices found.
11. And ofcourse, ODIN did nothing.
I think that if somehow, PC detect it, then i'll do something.
Now, if you guys have any method left, plz share it. I'm so interested to fix this device. Waiting for your messages.
Click to expand...
Click to collapse
First thing that you need to do is to talk with your friend if he has a valid warranty and tell the problems to him.
Method 1 (if he can't fix it, then it's your time to make a difference)
If you ever get the connection, try to google as fast as possible on how to install the stock rom for the A300F to your device (if you need any help, I will... just toss me a ???PRIVATE??? message and...yeah :good: )
Just try, it's always good to try and since this is the socail era, you have help just everywhere in the internet

Samsung Tab 4 SM-T230NU reboots after attempt to unroot

I have a Samsung Tab 4 SM-T230NU that was rooted and working fine until I booted to recovery to unroot the device in preparation to donate the device to a local service organization. The device now boots to the customized splash screen I loaded after rooting the device, plays a part of the audio I loaded, then hangs up or reboots. I can boot to TWRP, but it seems I may have uninstalled or deleted system files by mistake in my recovery attempt. The device is not being detected when it is connected to my laptop, so I cannot sideload a Samsung ROM or the Samsung USB Drivers with ADB or Odin. Any ideas are greatly appreciated.

Additional information
I connected the Tab to my laptop and you can head the audio notification that the TAB connected, but it does not show in the quick Access Panel of Windows 10. The Odin software does not detect the Tab either.

You can ADB sideload in twrp (look in the settings)