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.
Related
After half an hour trying I have just found a working solution how to connect your SGS in Kies. Here is the deal:
Start Kies, put phone's USB settings in Kies mode. Connect your phone to the PC. Wait until MTP App show "Connected". Go to your PC's Device manager, find Portable Devices and select Disable on GT-I9000. Do not wait for the disabling process to be completed, just disconnect the USB cable. Now connect the USB cable again, wait the MTP App on the phone to show you the message "Connected" and choose Enable on GT-I9000 in Device Manager. After a few seconds your phone should be ready in Kies
I tried this both on x86 and x64 Windows 7 and it works for me.
I hope this will help! And I hope there isn't another thread with this solution. If there is - I'm sorry
i cant wait to get home and try this... another 10h to go
but if this helps ur a geniues
celeronix said:
After half an hour trying I have just found a working solution how to connect your SGS in Kies. Here is the deal:
Start Kies, put phone's USB settings in Kies mode , go to your PC's Device manager, find Portable Devices and select Disable on GT-I9000. Do not wait for the disabling process to be completed, just disconnect the USB cable. Now connect the USB cable again and choose Enable on GT-I9000 in Device Manager. After a few seconds your phone should be ready in Kies
I hope this will help! And I hope there isn't another thread with this solution. If there is - I'm sorry
Click to expand...
Click to collapse
Will put this in the FAQ if we have some confirmations for its effectiveness
when i first bought my phone it worked with kies, but after flashing it to a different firmware there was nothing i could do to get it to connect. i had deleted drivers, re-installed, etc etc but nothing worked. what ended up working was putting the phone in download mode, plugging in the usb to both phone and pc, then putting the phone into recovery mode, and as soon as the recovery menu popped up my device was recognized and the correct drivers were reinstalled and all was fine again
hondaguy said:
when i first bought my phone it worked with kies, but after flashing it to a different firmware there was nothing i could do to get it to connect. i had deleted drivers, re-installed, etc etc but nothing worked. what ended up working was putting the phone in download mode, plugging in the usb to both phone and pc, then putting the phone into recovery mode, and as soon as the recovery menu popped up my device was recognized and the correct drivers were reinstalled and all was fine again
Click to expand...
Click to collapse
If you still have this problem, please try my method and tell me if it works
I had issues and I also tried this method. But it didn't help
Last thing I tried was to format the internal SD. That did the trick for me....
The biggest problem with getting the phone to connect to Kies is two fold:
1) MTP application will ONLY launch from the home screen (touchwiz screen). NOT from any app. drawer / launcher screen
2) If USB mode on the phone is set to Ask on Connection, MTP won't launch due to the USB app. being open (see 1) above)
If you set USB to Kies mode and then ensure you are on the home screen of the phone with nothing else running, Kies WILL connect
Also remember the 16+ size extension bug.
So a full wipe on ur I internal sd card is a good solution just make sure u back it up tour hdd
I also did a "Driver recovery" from Kies and it worked after that. Although MTP driver failed to install for me in this case.
Make sure to update to the latest version of Kies ( Now 1.5.1.0074.45 ) as this version seems far more reliable when connecting the phone
I recently discovered that the culprit of Kies continuously trying to connect to phone was caused by wrong MTP driver selected.
Under WinXP
After phone connected in Kies Mode..Go to Device Manager/Portable device..
If you see a device labeled as "MTP xxx or Portable device.." ,wrong MTP driver or older driver has been used..For my case, a Microsoft 2004 MTP driver was selected.
To fix it.
1) Do a manual driver update..for my case ,i let the driver wizard to search automatically..this round, another newer Microsoft driver was found..in fact 2 of them.. after installing the drivers(Microsoft 2006 MTP driver,2 are listed..). .Now Device Manager/Portable device listed "GT-i9000" ,Kies immediately found my phone.
Driver name that worked are "wpdusb.sys" and "wudfrd.sys" found under \windows\System32\drivers\..
celeronix said:
If you still have this problem, please try my method and tell me if it works
Click to expand...
Click to collapse
You must not understand English. The entire reason I posted a comment was to share how I overcame this issue, so that would mean I no longer have this issue
Probable Fix for Kies
Friends,
I have also faced the same problem (while connecting my SGS via Kies MTP was crashing). It used to work earlier so I started to remove Applications and data in the reverse order of Installation. After I removed "Dolphin Browser HD" and all saved bookmarks it started working.
This may be a probable solution if you also have Installed Dolphin Browser.
~Gaurav
India.
2 different issues.
MTP crashing on phone is independent from Kies on PC cant detect phone.
i couldnt use kies either but i wasnt worried as i hardly have free time now..
this was a simple fix and now it workes perfectly for me.
sorry about the late replay.
thanks
I'm glad that it works for you
try this
try #9 on
http://forum.xda-developers.com/showthread.php?p=8046872#post8046872
You might be interested in my little APK (SGS Toolbox). I first created it to have it read the product code from the nv_data file to allow you to check whether it has been modified after a firmware update. But now I added some extra options, of which one is the option to check whether there are new firmware updates available in KIES by issuing the same request KIES does when checking for new firmware. This way you don't have to connect your phone to your computer all the time to check for new updates in KIES. Note: It sends JM1 as the current firmware version to find the latest. I might send the actual phone's firmware version once I figured out how to find it. See: http://forum.xda-developers.com/showthread.php?t=778244
Thanks, I'll give it a try
Deleted. Wrong thread.
Greetings all
Apologies in advance for being a total noob, but I have looked all over the place and not seen a solution to the following:
Having recently replaced my Spica with an S II, I thought I'd try rooting/flashing my old phone.
1) With USB debugging enabled, the device is visible in Keis. I'm using 32-bit Win 7 and everything looks correct under Device Manager. When I turn off Keis and try switching to Odin (v4.03), the phone isn't detected and it seemingly fails to install drivers. Device Manager shows unhappy "SAMSUNG Android USB Modem" and "SAMSUNG Android USB Composite Device". I tried using NPS and that basically said go away, I'm too old. I can run a repair in Keis and it's OK until I fire up Odin, which kinda puts me into a faulty driver loop.
2) If I'm understanding this correctly, I need JC3 and above, in order to move to Froyo and above using LeshaK's 2,2 kernel.My current firmware states that it's 2.1 update 1 and the baseband is I570EXXJC1.
Any ideas please on getting the USB talking happily? (Yes, I have tried different ports etc). Also would I need to "flash up" to the later 2.1 and then go from there? The JC3 has me a little confused as the closest thing I see to this is the baseband version.
Many thanks to everyone who may be able to decipher my probs and come back with suggestions.
Doood Bear said:
Any ideas please on getting the USB talking happily?
Click to expand...
Click to collapse
Once you have installed Kies (so Samsung drivers are present on your computer), you need to connect the phone in download mode.
If I'm not wrong, with the the phone powered off and the USB unplugged, press Vol down + Camera + Power, the phone will start on download mode, then you can plug your USB (to both, PC and phone), and you should see it deteceted in ODIN (a COM port is assigned to it).
Once you flash Leshak's 2.2, you can apply other updates (even gingerbread alphas) from recovery menu (Vol down + Hung up + Power).
Hope this helps.
Do not hesitate to ask further questions if needed.
So I have bought a L7 and when I have it the phone is not working, the seller doesnt want to take my money back so I need help with this :S!
No appears to do anything when connected to charger
No led
No vibrates
No emergency mode
When I connect it to my PC it recognizes it as QHSUSB_DLOAD, but neither KDZ or LG update program recognize it :S!!
Someone know how to reinstall OS I think is software issue but I dont know how fix it
Thanks!
Try following the instruction I got from a website.
What is 'qhsusb_dolad' ?It is the situation when you can't boot into your phone,recovery mode and any other visible interface. When you connected your phone to the PC, the LED will flash and your PC will show that they were searching for the drivers needed(win7/8) but they couldn't find .......If it is commom for you to remove the battery when the phone did not shutdown completely or when you ran into 'No-Response' , as time goes by ,it will be inevitable that you come across the 'QHSUSB_DLOAD' situation .
But from now on ,you needn't worry about that for I have found a way out.
Tools needed:
Hardware: A PC running XP and higher (win7/8 recommended) and your usb cable
Software : MIflash and MIAssistent and a certain mi update rom(It is a *.exe file---fastboot file)
Steps :
1. Install the first two softwares described above(Run as administrator) in your PC (You need to disable the enforcement of digital signature while on win8 in the advanced startup (press 7 or F7)
2.Boot into fastboot mode(you just need to do with your two buttons and usually you cann't see the interface for your screen just won't show in this situation) before connecting to PC
3.Connect you MI2/S to your PC via the usb cable and the pc will recongnise it in the device manager panel(if not, update its driver in the unknown device---qhsusb_dload)
4.Open the miflash and click fresh to load your phone's serial number
5.Flash the update rom(the self-extracted-to folder) into your phone and reboot .
Explanations:
Miassistant contains the 'qhsusb_dload' driver for any phone and it enables the PC(Miflash) to recongnise your CPU serial which is the key part of updating by wire.
Tips:
Try this with your other phone, I believe it will work ,too.
I'm supposed to just copy/paste the link.. but the protocol won't let me since I still don't have more than 10 posts. I just want to help. Try this
So I'm attemping to use CF AutoRoot on my Note 4. I'm familiar with the process as I've used it on a few Samsung phones at this point. I went through the steps verbatim (installed Samsung Driver, Kies 3, start Odin, select firmware, power off phone, power on with vol-down/home/pwr, select up to put it in "downloading ..." steate, and then connect to USB). However, it never shows up in the ID:COM section. I thought it might be the cable, so I tried 3 different onces. I thought it might be something on the PC, so I tried 2 laptops and a desktop (2 WIndows 7 and 1 Windows 8.1, all of which I have admin on). Tried starting Odin as an Admin too. Rebooted all of the machines. Took out the battery on the phone for a couple minutes and booted in to the loader again. No dice.
Anyone know of any other way I can get this phone to show up on the PC?
Thanks!
Does your device detect by PC in explorer ?
May be your USB pin is faulty. Many times I have seen device can charge but can't connect to PC bcoz of faulty USB socket
And try with the stock cable. Sometime the aftermarket ones don't work as expected.
Sent from my SM-N910P
You need to make sure that KIES is not running (press SHIFT+CTRL+ESC, click on Processes, find the KIES processes and kill them all by clicking on "End Process").
Actually, KIES is completely unnecessary and does more harm than good. All you need are the Samsung drivers, which can be downloaded from here:
http://developer.samsung.com/technical-doc/view.do?v=T000000117
The thing is: if KIES is running in the background, it won't allow Odin to recognize the device, so that is why you should either kill it or (preferably, IMO) uninstall it and keep the drivers. Then you run Odin.
It was the cord on mine.
I dont have the stock cord.
I first plugged it in and it found hardware and started searching and installing drivers, even though I had installed the samsung drivers prior to plugging it in. There were 4 drivers it installed.
Then Odin wouldnt see it. So I tried another cord, with no effect, then a third cord and when I plugged it in, it found and installed 2 more drivers..
Then odin was able to see my note 4.
Hope that helps.
If u are using windows, install samsung drivers in compatibility mode. Right click on drivers icon setup, select install in mode compatibility eith windows 7, and follow the instructions. It must work. Saludos
So I'm trying to flash a Samsung SM-7387V Galaxy Tab A with new firmware as it currently has Knox / Mobicontrol
So it is locked down and you can't do a factory reset. I'm using Odin 3.13.1 and have the firmware which has the 4 files needed. I was able to initially get it to show up on Com6 is Odin but after a few min it complained it couldn't connect to the com port. After that any time I'm in Download mode windows complains it doesn't recognize the device. No amount of uninstalling / re-installing the Samsung USB Drivers, changing USB ports, windows reboots has fixed anything.
The only time I can get Winblows to detect the USB device properly is when booting it up normally.
So any suggestions on what gives? Also suggestions on if I'm on the right path to restore the device to remove Mobicontrol.
rickblues said:
So I'm trying to flash a Samsung SM-7387V Galaxy Tab A with new firmware as it currently has Knox / Mobicontrol
So it is locked down and you can't do a factory reset. I'm using Odin 3.13.1 and have the firmware which has the 4 files needed. I was able to initially get it to show up on Com6 is Odin but after a few min it complained it couldn't connect to the com port. After that any time I'm in Download mode windows complains it doesn't recognize the device. No amount of uninstalling / re-installing the Samsung USB Drivers, changing USB ports, windows reboots has fixed anything.
The only time I can get Winblows to detect the USB device properly is when booting it up normally.
So any suggestions on what gives? Also suggestions on if I'm on the right path to restore the device to remove Mobicontrol.
Click to expand...
Click to collapse
Additional notes: I've tried on a second PC with a different USB cable, same results as soon as you connect it in the boot loader mode. Both systems complain it can't recognize the device. Windows 10 systems.
I was going to include some photos of the boot screen / windows error, but it seems you can't attach photos or new members can't?
New here so this was my first post, do first posts show up automatically as it seems to be a ghost town? Not sure if this topic is viewable? Thanks!