my galaxy note 2 phone got stuck in a boot loop and i wanted to flash a new stock rom for it
the problem is that no matter what i do odin won't be able to recognize my device even at download mode
i've tried reinstalling samsung usb drivers, running odin as admin, trying older versions of odin, trying different usb cables
nothing worked
before soft break the phone had a stock rom on it and was not rooted
USB DEBUGGING WAS NOT ENABLED
if i've missed anything or doing anything wrong please help
try different PC or Odin version, for me only 3.09 worked for the first time
try odin and download the right file for odin
Related
Was updating to FD26 phone died..... got back into odin mode with jig, plugged into comp now it says USB Device not recognized and cant odin any firmware and wont boot since it didnt finish the last firmware upgrade. Any suggestions?
Jaromewg said:
Was updating to FD26 phone died..... got back into odin mode with jig, plugged into comp now it says USB Device not recognized and cant odin any firmware and wont boot since it didnt finish the last firmware upgrade. Any suggestions?
Click to expand...
Click to collapse
I hate to say it but it sounds like it might be a brick.
Are you getting the flashing blue light with a blank screen when you try to boot our are you getting a boot loop? Are you able to boot into Recovery?
no it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again. " i cant boot into recovery, i can into dl mode. ima try a different comp.
Jaromewg said:
no it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again. " i cant boot into recovery, i can into dl mode. ima try a different comp.
Click to expand...
Click to collapse
If you're getting that message I can tell you its not going to work. It sounds like you were trying to flash the international version kernel for the SGSII rather than the Epic 4G Touch. When you try to flash the international version it will fail and gives you the error you're getting. Another unfortunate side-effect is that it ruins your USB (due to differences in the way the USB works). I've heard that some JTAG services can fix it but I haven't done it myself.
At this point you unfortunately are stuck with a brick. :-(
Sorry!
I might have misunderstood the other posts but I thought flashing the international version completely disabled the USB port. Yet OP seems that device is being picked up in Windows but not successfully installed.
OP, can you please confirm? Check Device Manager and look for a device with a yellow exclamation point or triangle (if Win). If you can see it here you may just need to reinstall the Samsung drivers and get it installed that way. At the worst you're not any further along than you were before...
Alternatively you could try updating the driver manually, search C:\Program Files\SAMSUNG to see if it picks up.
If you haven't done so already, uninstall Kies and download the full Samsung driver suite from here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Install the driver and maybe we can help you from there. Or if it works, there ya go.
I just went through this...what happened on my end:
-computer froze up while i was doing stock odin repack
-went to boot up phone and that messaged flashed
what i did:
-flashed stock el26 kernel(if you can't get into odin but pull the battery and keep trying..thats what i did)
-flash a rom like you normally would
PROFIT!
I was trying to ODIN the latest JB stock ROM to see if that would help with the RR/SOD/etc. The ODIN flash failed during the system partition and now ODIN/KIES/HEIMDALL won't even see the device in download mode. I've tried uninstalling w/ccleaner and reinstalling the USB drivers with and without KIES. I'm not sure if there's anything else I can do before giving up on this phone.
I'm thinking about reinstalling windows and seeing if the phone will be recognized. Anything else to try before going to that extreme?
Edit: To be more specific, I'm stuck on the triangle downloading mode (bad flash download mode). Apparently a USB jig may help. Any other ideas?
So I rooted the device and for some reason recovery didn't work anymore. So I tried flashing a new one which didn't work because of Odin getting stuck at setup connection. Now I get a phone, a triangle and computer. It seems I can get the phone into download mode but it will still give me the same error message.
I have tried with 2 computers, different versions of odin as well as different cables. Samsung drivers have been installed on both computers, kies is not installed.
Any ideas how to unbrick?
Had wrong version of Odin. 4.42 needs to be used.
I bricked my Galaxy Ace GT-5830 and I need help un-bricking it with a stock ROM or one of these shiny Cyanogen ROMs. I've got all the tools I need from what I understand and hopefully someone can help guide this noob through the process and perhaps help me upgrade to a new OS. The phone will boot to and hang on the Samsung logo and to recovery mode but there seems to be some issue putting it into download mode so I'm stuck at the point of connecting it to Oden for download mode.
What I have:
Bricked phone
Oden 3.07 and 3.09
SD Card
Stock Firmware S5830XWKPY_S5830CPWKP1_CPW
My issues:
Firstly the stock ROM for a UK Carphone Warehouse phone I need that I found on SamMobile and another hosting site isn't in a tar.md5 format but I'm trying another stock ROM which is in the proper format for another UK provider to see if it will work, I'm not aware of how this would effect the phone if at all.
Secondly booting the phone to download mode doesn't seem to work as no connection is made with Oden. The phone boots to an empty charging battery which will disappear after a minute or so before the phone switches itself off again. Oden does recognise the phone when it boots and hangs on the Samsung boot logo and also when it boots into recovery mode. Multiple installs/versions of the USB drivers and Oden running in admin have been unsuccessfully attempted with various Samsung USB cables. Should I try to start Oden when a connection is made it hangs on setupconnection but I guess that is because it needs to be in download mode?
When attempting to wipe data/factory reset and cache partition it returns with the errors rfs format failed on /dev/stl13 and /dev/stl14.
brianx87 said:
I bricked my Galaxy Ace GT-5830 and I need help un-bricking it with a stock ROM or one of these shiny Cyanogen ROMs. I've got all the tools I need from what I understand and hopefully someone can help guide this noob through the process and perhaps help me upgrade to a new OS. The phone will boot to and hang on the Samsung logo and to recovery mode but there seems to be some issue putting it into download mode so I'm stuck at the point of connecting it to Oden for download mode.
What I have:
Bricked phone
Oden 3.07 and 3.09
SD Card
Stock Firmware S5830XWKPY_S5830CPWKP1_CPW
My issues:
Firstly the stock ROM for a UK Carphone Warehouse phone I need that I found on SamMobile and another hosting site isn't in a tar.md5 format but I'm trying another stock ROM which is in the proper format for another UK provider to see if it will work, I'm not aware of how this would effect the phone if at all.
Secondly booting the phone to download mode doesn't seem to work as no connection is made with Oden. The phone boots to an empty charging battery which will disappear after a minute or so before the phone switches itself off again. Oden does recognise the phone when it boots and hangs on the Samsung boot logo and also when it boots into recovery mode. Multiple installs/versions of the USB drivers and Oden running in admin have been unsuccessfully attempted with various Samsung USB cables. Should I try to start Oden when a connection is made it hangs on setupconnection but I guess that is because it needs to be in download mode?
When attempting to wipe data/factory reset and cache partition it returns with the errors rfs format failed on /dev/stl13 and /dev/stl14.
Click to expand...
Click to collapse
You forgot to tell us how you got it bricked in the first place. Was your device rooted and do you have stock recovery or CWM? Try taking out the battery and then put it back. Press and hold Vol Down+ Home+ Power button and see if you enter the Download Mode. Once you are in the Download Mode, there should be a yellow text saying "Downloading". Do post the result.
mahithm said:
You forgot to tell us how you got it bricked in the first place. Was your device rooted and do you have stock recovery or CWM? Try taking out the battery and then put it back. Press and hold Vol Down+ Home+ Power button and see if you enter the Download Mode. Once you are in the Download Mode, there should be a yellow text saying "Downloading". Do post the result.
Click to expand...
Click to collapse
I rooted the device and tried installing a custom ROM through recovery mode from what I remember and it's using a stock recovery. I've tried removing the battery and replacing while holding Vol Down+ Home+ Power button and it goes straight to the yellow text saying "Downloading" at which point the usb connection becomes unrecognised by my PC. Tried several different ports with various cables using the USB drivers from Samsung Kies and standalone drivers and I have yet to get it to recognise the device. What about "Emergency Download Mode," the device is recognised then but of course Oden hangs on the "setupconnection."
brianx87 said:
I rooted the device and tried installing a custom ROM through recovery mode from what I remember and it's using a stock recovery. I've tried removing the battery and replacing while holding Vol Down+ Home+ Power button and it goes straight to the yellow text saying "Downloading" at which point the usb connection becomes unrecognised by my PC. Tried several different ports with various cables using the USB drivers from Samsung Kies and standalone drivers and I have yet to get it to recognise the device. What about "Emergency Download Mode," the device is recognised then but of course Oden hangs on the "setupconnection."
Click to expand...
Click to collapse
It's just a soft-brick so nothing to very about The reason it was bricked was because you tried to install the custom rom from stock recovery mode. Always make sure to install custom rom from custom recovery mode like CWM. The reason your odin can't identify your device is because the odin is probably outdated and/ or maybe due to drivers. You can never use Emergency Download Mode to flash back stock rom from odin. When you use Emergency Download Mode, your connection will be recognized but you will end up getting set up connection error while flashing. Now to unbrick your device, just use the following thread,
[Share] All Samsung Galaxy Ace S5830 Stock Firmwares (2.3.X) Ever Released
First download the required firmware for your region from the first post. Once you have done that, go to the link in the second post. Download all the files (usb drivers, odin and ops) except firmwares (which you have already downloaded from the first post) in the "Preparation" section. Now install the USB drivers and follow the "Single Firmware File Installation". Once you have finished flashing, go to stock recovery mod and do a wipe data/ factory reset & wipe cache (otherwise bootloop might occur). Then restart. Now you have successfully flashed the stock rom. Here is the link for rooting and installing CWM 5 on Samsung Galaxy Ace which you can install from stock recovery mode (always root first and then install CWM),
How To Root and Unroot Samsung Galaxy Ace?
CWM 5.0.2.6 fix for Samsung Galaxy Ace S5830
Once you have installed CWM, you can flash any custom rom. CM 11 (KitKat) roms usually need CWM 6 but there is one CM 11 rom name KitKat for All that works well with CWM 5. Do post the result. Hope I Helped
My GT5830 Galaxy Ace is stuck in bootloop. I was flashing some file using recovery mode. Now the PC can not recognise the phone when it is in downloading mode although the PC recognise it in Emergency Download mode. I have tried all the USB drivers suggested in this forum.
Please help me.
Hi, I have an N7105 running android 4.2.2 latest version in my country. Recently, my phone got semi bricked, not sure why, and wouldn't get past the logo. I flashed the stock rom (N7105XXUFNJ1_N7105OLBFNJ1_MM1) for the first time via ODIN 3.07 and ODIN failed. However, I still manage to get into download mode. So i decided to update the samusng mobile phone drivers via kies, used a different USB port and charged the battery for awhile before trying again. I flashed the same firmware with the same ODIN version (3.07) and unfortunately, it failed again. As in it didn't even managed to inject the system successfully. Now, I have a bricked device that neither will boot into download/recovery mode. May I know what's the cause of the issue? Is there any way to revive it? Thanks so much.