Hi guys,
I think this doesn't look good, due to the way it failed. It was working just fine, using NeatROM. Just came after a walk, using it no problem. Let it rest for a bit while I was doing other things, and then when I check it again, it's dead.
It doesn't go beyond the Galaxy S2 logo, it doesn't get to the bootloader. Custom Recovery doesn't load. Download mode does start, but Odin hangs in "NAND write start". What would be your recommended steps?
Since I installed the crappy Samsung Link on my home laptop, I'm going to put the blame on that, and will use the work laptop that is clean of Kies or other crap. But i'm not very optimistic of how this looks...
EDIT: OK, so tested on a different laptop. Samsung USB drivers downloaded/installed, ODIN 3 v1.85. Still hangs on "NAND Write start!"
Try with usb drivers first, but kies is always a safe bet (of course, you need to kill its applications before flashing, all four of 'em).
This is probably an usb problem or odin version.
Sent from the little guy
Hi Gastonw,
Thanks for your reply. However I'm now with a "virgin" laptop, with samsung usb drivers installed specifically for this. And still no luck, still hanging and the NAND write
EDIT: Just to confirm, this laptop has never had Kies installed, and I'm just running with the USB drivers, without Kies.
Alright, I want you to try all usb ports and try with different odin versions.
Genuine SII cables?
Sent from the little guy
Related
So, My SGS2 was fine, just a few problems with connecting to my MacBook Pro (bootcamped Win7 & Odin), but after a few attempts it would always connect. I tried to update a rom to the new leaked ICS build via Mobile Odin, but something went wrong and all the charging images failed drawing.
Anyways, yesterday I tried to flash a recovery image via odin, to get back to my NAND and it failed halfway through (dodgy connector on SGS2).
Tried it a second time, and failed on flashing kernel.
I can access download screen, but windows refuses to recognize the phone, installing drivers for a "unknown device".
Tried flashing a kernel through OSX Lion and Heimdell, but it keeps failing to either find a device in download mode, or "claiming interface failed"
I've brought a new cable, but i have a feeling my USB port on the SGS2 has gone. Any help? Insurance most likely won't cover because it now says (2 Custom Binary Downloads) and they don't cover, and surely warranty has voided too.
Please help?
I will make a donation to the the person who can help me.
new leaked ICS build via Mobile Odin
Thats a test pre beta build guess its the problem .
Looks a usb driver problem that what you try .
remove Kies reboot reinstall Kies connect phone in download mode and let windows find drivers .
jje
try reinstalling kies. Or better yet use another computer for flashing. Can you boot into recovery mode? If so try flashing a custom rom to try to boot up your phone for the mean time
Sent from my GT-I9100 using xda premium
@JJEgan
Kies idea isn't working. My guess is the fact its 64bit Win7 on MBP bootcamp.
Or at least I'm hoping. Won't get to a desktop computer till monday, so had to buy a cheap backup phone.
@ephraim033
Flashing the new rom removed recovery, and can only access download mode.
I just get a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
So far, I have noticed I either restart the computer (after uninstalling failed "unknown device" driver) and/or leave it for a while, and bam, it searches for drivers for the phone when I retry , but it seems to be related to pure luck with the positioning of the cable into the phone.
I have cleaned it several times with canned air and computing alcohol (i wont dare spell the name of it, and don't have the bottle to hand right now) so dust and debris is not the issue.
Edit: the failed driver comes up with "Windows has stopped this device because it has reported problems. (Code 43)" so I'm guessing i have to uninstall and reboot each time I try?
SOLVED. Have found the issue. Uninstalled KIES and all drivers. MEGA DEEP clean with a brand new dry tooth brush (infront and behind the protrusion within the usb port on both the phone and laptop).
Several reboots on both phone and laptop.
Second try, installed serial gadget and Samsung drivers automatically, installed CWM.
Many thanks
Danifamous said:
SOLVED. Have found the issue. Uninstalled KIES and all drivers. MEGA DEEP clean with a brand new dry tooth brush (infront and behind the protrusion within the usb port on both the phone and laptop).
Several reboots on both phone and laptop.
Second try, installed serial gadget and Samsung drivers automatically, installed CWM.
Many thanks
Click to expand...
Click to collapse
Glad you fixed it mate
Sent from my GT-I9100 using xda premium
Hi. So I went ahead and installed ICS 4.0.3 on my Galaxy S2. It's still buggy and I can't live with some of the things that are wrong. I want to go back to stock but now Odin isn't recognizing my phone. It shows up on Kies, and in Odin while powered on, just not on download mode. I've tried the following:
Tried with usb debugging enabled and disabled
Uninstalled Kies, cleanead registry, rebboted, installed kies again
Killed all Kies processes before runing Odin
Removed phone's battery
Uninstalled and reinstalled phone drivers on Windows 7
Any idea of what can be wrong? I will appreciate your help.
Try different usb ports (must be a powered/mainboard port, not a hub), try different cables (particularly the original cable that came with the phone), try different versions of Odin.
And lastly, try different PCs/different versions of Windoze.
Thank you very much. Sometimes I think of the most complicated solutions and disregard the most obvious. Turns out that because Kies and Odin while powered on recognized my phone, I never considered changing ubs ports. That was the solution. I'm now back to GB 2.3.6 and glad to. I'll wait on a stable version of ICS for my phone.
No worries Glad you got it sorted. Yep, I'm also often guilty of overlooking the simple stuff too
cannabia said:
Thank you very much. Sometimes I think of the most complicated solutions and disregard the most obvious. Turns out that because Kies and Odin while powered on recognized my phone, I never considered changing ubs ports. That was the solution. I'm now back to GB 2.3.6 and glad to. I'll wait on a stable version of ICS for my phone.
Click to expand...
Click to collapse
Hey guys just wanted to say thanks for all the help you provide on a daily basis, for all the people trying to unlock the potential in their phones. However with that being said I might have tried too hard and messed up my phones. I have a Samsung Vibrant SGH-T595 with 2.1 (update 1) updated officially by Samsung.
I rooted the phone, used clock work recovery mod and then downloaded and installed cyanogenmod 7.1 RC. However in the end I did not like so I tried to go back using my backed up copy created by clockwork mod. Doing this has now what you would call "soft bricked" my phone.
The phone is currently stuck on the Samsung boot screen when trying to power on the device. I am unable to put it into download mode via the three button setup, but I bought a USB jig and it sets it into download mode.
Everything seems great at this point but the Odin program is unable to recognize my phone. I have downloaded the official Samsung Kies, and 64 bit drivers as well for my windows 7 system but it is unable to detect my phone. I believe it maybe a defective USB issue with this phone but not sure since it can be charged through USB but I can't remember the last time I was able to connect it to the PC and transfer files via the USB cable.
My question is what else can I do other then sell it for scrap?
Try another USB cable and different ports. It will recognize it eventually.
As you have a windows 7 x64 bit version i guess Odin may need to be opened by giving Administrator permissions.
Try right clicking odin and click Run as administrator. I guess this should work.
Ran into this issue last night with my wife's Nook Color and moving some file and driver issues. Guess what? It was a bad cord. Actually used my Vibrant cord and it was instantly recognized. Yes sometimes it IS actually THAT simple.
I also suggest you go to the Dev section and download the AIO Toolbox (links are live again and don't forget the .Net files too). Uninstall the drivers you have installed and run to toolbox. It has all the correct drivers, pit/tar files and Odin. It is an invaluable tool.
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Woodrube said:
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Click to expand...
Click to collapse
Exactly. And that is how i tried updating my vibrant to froyo and ended up hard bricking it..
Yeah like someone in here said, download aio vibrant toolkit.. its a surefire way to know your drivers are good and right.. once youve ruled them out, try a diff usb port and cable (mentioned above as well). If nothing works, then you may begin to entertain the idea that your phone is in difficult position.
Probably not hardbricked tho, vibrants are very resilient; just keep trying.
Then ttheres jtag and unbrickable mod if youre absolutely sure lifes over
Sent from a cell tower to the XDA server to you.
Thanks guys I ended up recycling my phones cause nothing I did worked. I did try AIO toolbox got the drivers, tried different cables. My SG II is able to be recognized by odin 1.85 with no issues but not my vibrant. I believe it is an issue with the vibrant's usb port. I originally rooted it by doing the update.zip fix from its external sd card, did not use my usb cable at that time. My other vibrant is completely hard bricked since it wont power on with two different fully charged batteries. Anyway thanks again and next time I will research more before modding my phones.
Hey OP,
I did the same exact thing as you and soft bricked it in the same manner. Then when I tried to get Odin to recognize the phone it wouldn't with my Samsung cable. I thought I was out of luck but I went and bought a USB cable made my Belkin from Meijer and Odin recognized it! I looked at the Samsung cable and the Belkin cable and the black plastic inside the microUSB in the Belkin is thicker than the Samsung. I think that helps create a tighter contact between phone microUSB and the cable. I thought I was screwed like you and I fixed the issue with a new cable!! That simple
I used the Samsung Galaxy S II usb cable which looks like it has a very tight connection with the contacts like you said. Thanks anyway I will try that brand of cable, if I ever run into that issue.
Hello all, I have a GS3 international GT-I9300
I'll try to go through the story as fast as I can and give as much detail so you guys can understand how I got here.
Bought the phone unlocked, I was stock, I rooted and then I decided to install a new ROM. I went with Resurrection Remix, it was working great. I did this on a desktop back home. They released a new update to RR so I did a OTA update with "Update Me" apparently the thing flashed but it didn't, the phone still worked but NFC wasn't working as well as having lost root access and some other stuff wasn't working correctly, but I lived with it.
I moved to Florida (home is in NY) and I have a laptop with me, for some reason my laptop used to be able to transfer files to my S3, but it wasn't doing it any more after a while. So it would just charge it. I was in a hotel room last week trying to tether via USB but the PC wasnt having it, it could not locate the phone. This week I moved to a different hotel with internet and decided I would flash stock on my S3 to get rid of all these bugs and get root again, I tried flashing stock through recovery and it wasn't going, so I tried flashing RR again (this time downloaded from the site RR site) and it worked. Still no USB connection but I had root back. I looked around my PC and apparently the Samsung drives are not installing or something on my PC. I installed Kies, but nothing, I tried a stand alone driver install and nothing, so I just gave up and bought Mobile Odin pro from Gplay to try to flash again.
Mobile Odin for some reason (I blame it on myself) wasn't finding/flashing stock so again I decided to try and flash RR and see what would happen. It flashed RR and turned on fine. Then I just decided to look for an NFC fix on XDA. Once I found my NFC fix (http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367) I decided to just copy the files to the system folder, NFC still not working, rebooted and NFC still no working, so I figured I would try to flash the fix through mobile odin seeing as how I can't get my PC to pick up on the USB. I tried flashing but MO just kept bouncing it back and re-booting into RR. Tried again and no flash. So I decided to again try and flash stock. I tried going into Recovery, the phone shut off like it always does, came back on but stayed in the Galaxy S3 GT-I9300 logo and would not move. I shut it off again, tried turning it on again and still stuck on the galaxy logo. Now, if I leave the phone off and plug in the USB, it won't show the battery charging image, it will actually turn straight onto the galaxy logo again and stay there. I can get the phone into download mode, but like I said my pc won't recognize the drivers.
Now, here are my questions:
What happened?
Can this be fixed?
Am I an idiot?
If I can get the drivers installed on another PC as well as Odin (1.85), will the new PC "see" the S3 or are the drivers on the phone deleted as well? (if that sort of thing can happen, idk.)
I'm going to see if I can borrow a buddy's PC and download the drivers as well as odin to try and bring my S3 back to life, I just want to know, what happens if I can't get the other PC to pick it up ether because the drivers on the phone are deleted (if that's a thing) or what I can expect if it is connected.
What are the steps or guides to follow here? I just got it into Download mode and it says on the top of the screen:
ODIN MODE
Product name: GT-I9300
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Custom
sorry , i am sometime getting headache reading long english text so i just briefly look over.
your PC doesn't recognize your S3 ? is that correct ? hmmm , is it possible that your PC (Microsoft Windows I assume?) system is damaged due to something like virus or some reasons ? i have encountered that kinda problem before and be OK after i reinstalled the system.
If it's a soft brick, then it can defiantly be fixed. You might, however, lose your data along the process.
Be glad it's not hard bricked
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
djembey said:
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Don't forget to delete kies as you only need the drivers
Sent from my GT-I9300 using Tapatalk 2
Thanks for the replies guys. I'll try to fix tit today, I didn't get a chance to do it last night. If anything I'll update you guys with what's going on.
Like I was saying, I'll try using a different PC to fix it. Now, if I can't get Odin to recognize the phone, what would be the next step?
So I soft bricked my S II plus and I when tried to access ODIN to flash an official ROM , ODIN doesnt detect it , i've tried installing all the drivers ,changing USB cables and even pc's still it doesn't work , I got a fried to bring his S III to test with my pc and ODIN doesnt register even his device .
is there any way i can flash to stock ROM and just turn everything back to normal using CWM ? I just dont wanna root my phone no mpre
There was a reply to a thread in Q&A a couple of hours ago where someone listed the troubleshooting steps for when 'Odin doesn't work'. Search for that thread (skim similar threads in Q&A over the past 12 hrs or so), go through the steps.
MistahBungle said:
There was a reply to a thread in Q&A a couple of hours ago where someone listed the troubleshooting steps for when 'Odin doesn't work'. Search for that thread (skim similar threads in Q&A over the past 12 hrs or so), go through the steps.
Click to expand...
Click to collapse
Thanks I'l search it up , if anyone finds that post please do share it and thanks
Pretty sure it was Immortalneo, so have a look at his posts specifically; should help you to narrow it down a bit.
MistahBungle said:
Pretty sure it was Immortalneo, so have a look at his posts specifically; should help you to narrow it down a bit.
Click to expand...
Click to collapse
It was me, but it was actually you.
"To err is human, to forgive is divine"
Sent from my SGS II
Nothing seems to be working to get ODIN to detect it :/
I tried to flash ROM with CWM it just says "(bad)"
If you've tried everything (and I mean everything. Not 2 or 3 things) including trying with different PC's, without a screenshot/pic of the Odin output we'd have absolutely no idea why it's failing. However, if you'd care to give us a pic/screenshot of the Odin output when you try & flash, maybe we can figure out why.
MistahBungle said:
If you've tried everything (and I mean everything. Not 2 or 3 things) including trying with different PC's, without a screenshot/pic of the Odin output we'd have absolutely no idea why it's failing. However, if you'd care to give us a pic/screenshot of the Odin output when you try & flash, maybe we can figure out why.
Click to expand...
Click to collapse
well sorry for being a noob :/ but is this what your asking for?
Well vick...that is Download mode...
Push vol up and se if your pc sees it.
Sent from the little guy
I would have thought my post was pretty clear. You're obviously out of your depth & shouldn't be messing with your phone. What we need is a pic/screenshot of the Odin screen from your PC when it's failing like this
I just got too excited when everyone was rooting their phones , shouldn't have done it at all :/
My problem is no (yellow bar) is coming out from odin when i plug in download mode at first it could but after i formatted my phone from CWM it couldnt detect anymore , and I tried with two other laptops and even a different cable
Im so sorry to take up your time :/
(ODIN just looks like normal when i plug everything in :S)
OK. I thought Odin could detect OK but the flash was failing at that stage. So you still can't get the phone & PC to recognise each other given everything you've tried.
Honestly, I can't think of anything else you can do. I'd suggest you keep trying tho. Not a lot else you can do beyond that (Unless there's something really simple/obvious we're all missing here).
Edit -Right. List everything, and I mean everything you've tried to try and get the phone & PC to recognise each other/get Odin to work. Every single little step. Details. The more details you provide, the better the chance you get your phone fixed. The less details you provide, the less likely that is to happen.
MistahBungle said:
OK. I thought Odin could detect OK but the flash was failing at that stage. So you still can't get the phone & PC to recognise each other given everything you've tried.
Honestly, I can't think of anything else you can do. I'd suggest you keep trying tho. Not a lot else you can do beyond that (Unless there's something really simple/obvious we're all missing here).
Click to expand...
Click to collapse
This gonna sound CRAZY but I'l give it a try , maybe I reformat my pc and try again ? :3
I'l get back to you guys when I tried that?
Don't do that just yet. That's a little drastic. Read my edit to my PP first.
MistahBungle said:
Don't do that just yet. That's a little drastic. Read my edit to my PP first.
Click to expand...
Click to collapse
Ok , I have tried
-Installing Kies , samsung Usb drivers and every driver i could fine for samsung (ADB)
- I tried both ODIN v1.85 ,3.04
-different USB cables
-Diferent pc's (2 laptops)
-Friends S III ( sadly even his wasn't detected)
-Formatting every single option there was in CWM
-tried flashing using CWM (failed with installation aborted *bad*)
- I even ended Kies processor before running ODIN
- windows update
You missed:-
Different USB ports (and different USB ports on different PC's - you must use a 'mainboard' port, if you don't know what it is, Google it).
Try Odin V1.3
Have you used the USB cable that came with the phone ? Uninstall Kies. Reboot. Redownload Kies from Samsung website. Reinstall. Reboot. Run Odin as administrator in Windows (R-click the Odin .exe & choose 'run as administrator').
That's all I got given it's almost 3.30am here.
MistahBungle said:
You missed:-
Different USB ports (and different USB ports on different PC's - you must use a 'mainboard' port, if you don't know what it is, Google it).
Try Odin V1.3
Have you used the USB cable that came with the phone ? Uninstall Kies. Reboot. Redownload Kies from Samsung website. Reinstall. Reboot. Run Odin as administrator in Windows (R-click the Odin .exe & choose 'run as administrator').
That's all I got given it's almost 3.30am here.
Click to expand...
Click to collapse
ah yes i changed port to , to the back of my pc (motherboard) , yup usb cable that came with the phone and my friends one , I'l try it after I wake up , got work :3
Thank you so much for dealing with me man <3
(its 2 a.m here in malaysia hahah)
Vick4272 said:
Ok , I have tried
-Installing Kies , samsung Usb drivers and every driver i could fine for samsung (ADB)
- I tried both ODIN v1.85 ,3.04
-different USB cables
-Diferent pc's (2 laptops)
-Friends S III ( sadly even his wasn't detected)
-Formatting every single option there was in CWM
-tried flashing using CWM (failed with installation aborted *bad*)
- I even ended Kies processor before running ODIN
- windows update
Click to expand...
Click to collapse
There, your friend's SIII wasn't recognised. You wanna pay a friend a visit to use his/her pc with no kies pre-installed. You go and get it's latest version and repeat all steps.
When you say "kies processor" you mean one kies application running or all 4 that there are actually running?
Sent from the little guy
Well now I have reinstalled Kies , but this time when i plug the usb be in , I can hear my pc detecting it but ( Mobile USB Modem 1.0) fails to install in windows update .
and i've tried with my 2 other laptops without kies installed
oh and I end task for KiesPDLR.exe (said by someone in a post here in Xda)
Are you hitting 'end process tree' when you close Kies in Windoze Task Manager ? It's important anything associated w/Kies is closed, not just the main application.