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.

Need Help with hard brick

Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.

Croshio said:
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Click to expand...
Click to collapse
You must have flashed wrong version of the rom .
After trying the linux method, if you cant get into fastboot mode, recovery or not in download mode, then try this : http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
This requires you to open your phone so be cautious .

Thanks I followed that guide. Download mode after. Using the Windows tool instead of Linux then flash tool normally.

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

Oneplus 2 Bricked Windows doesn't recognize the phone

I bought a oneplus 2 and tried to flash a kernel meant for nougat based roms on the stock rom leading to a laggy hot phone so i used the format data tool in TWRP and it deleted my OS. I tried to hook my phone up to my pc in recovery mode, fast boot mode, and qualcomm mode all with the same result. I get this in device manager "Unknown USB Device (Device Descriptor Request Failed)" I've tried every driver every tool. I've tried everything to no avail. The problem isn't that the phone is bricked its just that i can't get the rom on the phone because of the device error. Thank you in advance.

Hello,
Looks like your new to the community so first off welcome! First things first, its practically impossible to brick these phones. I have been in your position before and I didn't know what to do. The quickest way would be to go to one plus live chat and tell them what has happened and they will help you by controlling your PC to fix the phone. They are more than happy to help with a device in this state as its just the software that's gone.
If you want to do it yourself, can you hold the vol down button on your phone and plug it in to your PC (still holding vol down). Then go to device manager and tell me what it says. It should flag up as a Qualcomm device. May have more info (I haven't soft bricked my device in a while)
-Sean

N4 bricked, tried several things, don't know what to do next

Hello,
For some time the fastboot mode doesn't work on my N4. Neither Recovery, it remains inaccessible. (black sceen)
Recently, I formatted the system partition and android now cannot boot any longer (!).
Download mode works though!
So I followed the tutorial from there to unbrick it:
https://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
But I am stuck at the LGNPST step, because my device doesn't appear in the app. I used a Win10 PC, so maybe there is some kind of uncompatibility with the "a bit old" procedure. I tried all three usb ports of the PC, with no luck.
Now, I don't know what to do next.
Is there some kind of procedure that can work with Linux instead of Windows to restore fastboot mode ?
Thanks a lot!

Have you checked whether your phone is appearing in device manager?
Perhaps Windows did not apply the driver to the device automatically (it happens sometimes).