[Q] Phone Dead after kies restarted PC while updating then using Odin3 to "recover"
So my PC suddenly restarted while installing 2.2 on my phone. When I started up again it could not use its "emergency recovery". I searched for help and found a place where they had the exact same problem fixed it via "Odin3 Flasher" (google "Stock Firmware Odin3 Flasher" to get the exact guide I followed)
My phone is from Norway so I do NOT have at&t but now that i followed those instructions, all my phone does is flash on and off "at&t world phone", and I cannot get into download mode again. When I plug in the USB the at&t logo stops flashing and it goes completly black.
How can I get into download mode or fix this?
same thing happen with me today
the same thing is happened with me today when i used the ODIN3 v1.00.... Please help me...
you will need to make or purchase a usb jig : http://www.1giftbuy.com/p-10279-i9000-i9100-micro-usb-download-mode-jig-/?currency=GBP , then you will be able to use odin to flash a stock rom
Search on the forum, you can install android SDK, set usb debugging and then do an adb reboot quickly from computer after attaching the uab cable. I had the same brick problem, and I fixed it without usb jig.
Sent from my GT-I9000 using XDA App
Hi,
so after using a rom for a week, I didn't like it so I decided to restore back to my previous rom. When booting up, it freezes at Galaxy S GT-I19000. So I decided to use Odin to flash back to stock.I entered download mode however when I connect my phone to the computer, Odin wouldn't detect it. I've tried all usb ports, and different usb cables. Know what I can do? D:
Are you sure no kies proccesses are running? That you first turned on Odin and only then plugged in the phone?
Sent from my SGS using Tapatalk
Try different PC and be sure to install samsung USB driver
Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i switchd the damn thing off completely
I have tried to go in download mode to flash but odin doesnt recognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS- i im not worried about my data , and i have not backed up the rom etc before doing any of these)
Try to reinstall or install a usb driver from samsung
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Yeah, happened to me too, nearly had a sh*t my pants when Odin didn't recognise my Tab.
I would recommend -
charge the Tab fully using wall adapter (4 hrs+)
plug it in with Odin open and using USB cable
don't expect Odin to recognise the Tab immediately
check back after 5 mins or so (I don't know, does Odin refresh?)
I was able to restore my Tab from the PC - ! - Marvin screen.
I don't want to go back there again though!
yea dude.. same here
i kept it on charge for a couple of hours and then tried.. bam it conencts..
Libon
Tab not turning on
HI Guys I have Galaxy 1000 .I was updating it by using kies in between the process my computer shut down and when I am trying to connect my tab again its not turning on .can some one help me please ?
Waiting no charge baterry 2 3 j
Run odin
Connect tab . Wait Long time 20 30min
Tab is. Détect go flashing
Sorry for my english
I m.. French
Envoyé depuis mon GT-P1000
GT P1000 Odin wont detect
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
iamkakers said:
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
Click to expand...
Click to collapse
do u have samsung kies installed in your pc? if does, kill the kies process (Ctrl+Alt+Del). close, and open odin3, put your tab into download mode, and then plug it into usb port. try to change different ports.
i always had this problems.. if all if that didn't work, i'll format my pc
Sent from my GT-P1000
odin3
hi
i also have a gt p1000 and odin3 doesnt detect the tab. i've been trying to root my tab for a while, tried odin and it doesnt detect, tried doomlord and it doesnt even get past the first step. i tried uninstalling kies on my windows 8 laptop and still no luck im not too sure what to do. is there something that i might be doing wrong because i follow all the info thati get from here.
is there another rooting app i can try that doesnt brick my device? and or is there an app that i can get that i am able to use a ps3 controller on my device that does not require a rooted device. please help
thanks
My Galaxy tab also doesn't connect to usb after cache wiped humber os flash
Thanks in advance guys!..
Earlier I was using Cyanogen mode 10 Custom ROM but has few issues like recognize SD card.
later I flashed to Humber OS caused real problem.
It was clock work recovery installed but my tab tab boots stays on screen humber OS.
It goes to recovery mode, and also to some unknown recovery mode.
Either the way not recognized by computer. I tried all options like heimtal an Odin. No help.
Friends any help, would be highly appreciated.
BUMP
Any solution to this given the fact that usb drivers have been installed?
Are you sure it is recognised by the computer before trying Odin or Heimdall?
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
farza(db)astany said:
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
Click to expand...
Click to collapse
reason 1: my phone is samsung and it's detected by ODIN, kies and I transfer files from and to my computer without problems. also tried reinstalling just in case but nothing, so I guess this is not the answer for my problem
reason 2: tried with original cable, but as I didn't use the tablet for a long time I also thought it could be the cable, so I asked a friend of mine if he could lend me one cable, but that didn't work. pity. :/
reason 3: tried 3 different versions of ODIN, and in every version my phone (mentioned above) is detected. shame. :S
reason 4: tried the 3 different USB ports in my laptop. two 2.0 USB ports and one 3.0 USB port, so again I doubt this is the reason of my problem.
extra reason: ~~~ maybe it's the OS version ~~~ // this laptop came with windows 8 preinstalled. nothing. then, I updated to win 8.1. again nothing. now I'm running windows 10 and the same, nothing is detected neither by ODIN nor the computer. also tried in 4 different computers running win xp, win 7 and other with win 8.1.
btw, thank you anyway for your apportation; this may help other people, but unfortunately, it's not my case, so can anybody else join me to think about a new reason and a way to solve it? thank you very much :good: :highfive: :fingers-crossed:
~~~~~~~~~~~~ EDIT ~~~~~~~~~~~~
I have continued researching and found a software. it didn't work for me, but maybe it works for other people.
-first, you have to make sure you have java installed on your computer.
-second, extract the oneclick.rar file on an easy-access directory.
-third, put your tab on download mode (while charging icon when tab is turned off, press power + volume down until a yellow triangle appears).
-fourth, click start unsoft-brick and let the magic begin! 8)
note: if a warning error pops up, trust the software and click on resolution center and follow the instructions of one of the three "alternative ways".
download: https://www.dropbox.com/s/8ix6yygu23a1kjn/OneClick.rar?dl=0
good luck!!
help
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
hi can you plz help me out with the processess you followed to as im suffring the same problum only CWM working and even it shows sd card mount error also not installing any rom via SD card showing error and odin not detecting it nothing happening only CWM and blank screen
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
How did you did it im having the same error???
i did the same thing with my tab exactly like yours plzzzz help me recover it
I currently have a bricked SAMSUNG GALAXY ACE S5830 phone.
When I put it into download mode and try to flash the it using ODIN, ODIN recognizes that the device S5830 is connected at COM8 while the device manager specifies that it is connected at COM9. Here is a screen shot.
Since, I do not have 10 posts, XDA is not allowing me to post links.. So Am not able to 'embed an image'/'post a link'. but here is the link
ht tp://s8. postimage .org/j97vdv1ur/com_port_odin.jpg
And ODIN gets stuck at the first step :
<1> setup connection...
__________
I am guessing it is because of the miss-identified com port.
1] Am I right?
2] How do I resolve this? (so the flashing continues as expected)
Tru diferent pc and usb cable
Sent from my GT-S5830 using xda app-developers app
Hi!
I have a similar problem. I received a Galaxy Ace that is apparently bricked. It seems someone flashed a custom rom on the device, but the device is not rooted. It goes into download mode but when attempting to flash it in Odin it fails after trying to set up connection. Is there any way around this? Device won't start up, it only reads ANDROID and remains that way.
I tried different USB cables and different ports but nothing.
EDIT:now it recognizes the device but when flashing in Odin it says big partition size! MIBIB download and it gets stuck there. I already uninstalled all other manufacuturer device software like PC companion etc. and closed all Kies applications and tried a different PC but still no progress. Anyone?
Harry GT-S5830 said:
Tru diferent pc and usb cable
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
Have tried it using different cables/different usb ports.
Did not help.
Will give it a try on a different computer..
P.S. Pardon for the delayed reply. I was ill.
brajko said:
Hi!
I have a similar problem. I received a Galaxy Ace that is apparently bricked. It seems someone flashed a custom rom on the device, but the device is not rooted. It goes into download mode but when attempting to flash it in Odin it fails after trying to set up connection. Is there any way around this? Device won't start up, it only reads ANDROID and remains that way.
I tried different USB cables and different ports but nothing.
EDIT:now it recognizes the device but when flashing in Odin it says big partition size! MIBIB download and it gets stuck there. I already uninstalled all other manufacuturer device software like PC companion etc. and closed all Kies applications and tried a different PC but still no progress. Anyone?
Click to expand...
Click to collapse
The device that I have doesn't even turn on. But gets recognized via ODIN. But ODIN shows that it is connected to different port.. And haven't had any success till now.
Hello all,
My mother has a GT-N7000 running complete stock.
It updated something according to ehr saying and afterwards it rebooted.
After the reboot it rebooted again and now its bootlooping, it shows samsung and plays the sound.
The bleu glaze comes up and the the device reboots.
I cant get into recovery with vol up+home+power button combo.
It boots to it and it shows the droid with the sort of cubic icon spinning in its belly and after 3 sec the device reboots.
I cant do a factory reset there so i read about Odin and reflash stock image.
I downloaded the proper file and Odin 3.0.9 and installed samsung drivers.
I dont have Kies installed as i read it could give problems.
The device does go i ndownlaod mode but my PC running w7 ultimate 64bit doesnt recognize the device.
I tried 3 different USB ports from the Mobo, and i tried a couple of diferent USB cables.
One of the cables is original Samung U2 cable.
Everyt time i connect the device winodws shows the message: the USB device isnt recognized.
Odin doesnt register anything so i cant flash a thing with it to restore.
Does this mean the device is bricked?
Does the N7000 has some sort of unbrick JTAG mode or something or would linux help to rewrite all partitions?
Thx for any tips.
With best ergards,
Mister_mini
Edit: thinking back it could be possible USB debuuging has been turned on but im not sure on this part.