Related
The captivate cannot boot at all when pressing the power key, actually all three keys seems unresponsive. I can only use a Jig to get in into download mode, but it freezes using OdinV3 one click.. It freezes at dbdata.rfs or factoryfs.rfs.. If I waited long enough, it will show a green screen or sometime a yellowish orange screen..
So is my cap hard bricked then...?
I used the same computer/setting/cable to odin other devices and every time works..
Try installing the samsung driver, then restart your computer.
Now, go to development, find the odin thread by designgears, download those drivers. Install drivers. Restart computer. Start odin. Plug usb into port on backof computer. Put phone in dl mode. By now you should be ready to hit start. I would post a link for you, but it's hard to do from my phone.
I used that method for a numbers of cap and worked every time but not for this one. Think it is hardware malfunctioned..
sometimes the phone is actually on when the screen is black. see if you can see the phone in odin without being in download mode. if you can run master clear in odin one click. then try download again. try different firmware versions too. odin one click would fail to flash my phone untill after i flashed the jh2 leak with full odin. i dont know why but now both odins work. you can try to flash rogers stock 2.2 firmware. it wont hurt anything.
Keep trying, third has happened to me before. Eventually it went through. Also its possible different pc, or cable
Sent from my SGH-I897 using XDA Premium App
A good rule of thumb for checking if you have a hard brick is "Did something show up on the screen at any point?" If so, you aren't hard bricked. A hard bricked phone will be completely unresponsive to anything, including a jig.
I'd say keep trying. Odin is pretty buggy and sometimes refuses to work. You might also want to try a different usb cable, and a different usb port on your computer. It may be simply that you have a faulty cable or port, and it's losing connection to your phone in the middle of your flash.
Also, have you tried using Odin with repartition checked?
I used other ports and cables, but now it won't even boot into d/l mode with a jig.. just get warm at the back between the camera and TF slot.. think its really hard bricked now..
modest_mandroid said:
A good rule of thumb for checking if you have a hard brick is "Did something show up on the screen at any point?" If so, you aren't hard bricked. A hard bricked phone will be completely unresponsive to anything, including a jig.
I'd say keep trying. Odin is pretty buggy and sometimes refuses to work. You might also want to try a different usb cable, and a different usb port on your computer. It may be simply that you have a faulty cable or port, and it's losing connection to your phone in the middle of your flash.
Also, have you tried using Odin with repartition checked?
Click to expand...
Click to collapse
The Odin one click has no repartition option. When I tried to use Odin3 V1.7, the jig failed to take the phone into d/l mode and the phone got warm. btw, the jig is working.
Do you by chance have kies running. I once thought I had it off... But it was just minimized and it stopped odin from working.
Just a shot in the dark.
sent using a phone.
I had never installed Kies.. I actually odin another cappy right before this one, and that one works.. Think there is no hope and have to sell it for for parts then .
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
I was previously running MIUI (not sure which version) and something went wrong with it. Random processes just kept "unexpectedly stopping." I found the Heimdall One-Click and tried it. The process never finished (failed to upload FACTORYFS everytime :/). I tried checking the Flash Bootloaders option. It got the FACTORYFS upload percent a bit further along, but still failed. Opened up Odin, and it wouldn't find any device plugged in.
After a couple more tries at this, suddenly, no matter which USB port I plug in to, my computer fails to recognize the device when previously it would on a couple specific ports. Odin will not recognize it, either.
Am I screwed?
Edit:
I've gotten the USB to recognize. I'm scared to do anything now, for fear I won't get it to recognize again. Odin still does not see the device. What other tools can I use to unbrick this?
I believe the driver for heimdall "takes over" the port. You have to use a different port or uninstall the driver to use Odin on it again. Also it seems when the upload won't complete most have success with another cable....nothing wrong with qksters uclb3 return to stock. I've used it several times.
Sent from my SGH-I897 using Tapatalk
I had the same issue a few days ago. SCARED me to...
Powered the phone off.
Unpluged USB
Rebooted Windows PC
Rebooted phone
Started at step one again
This time try another USB Port on computer
This time everything worked
I've had this happen before. After much panicking, I used GTG unbrick.
Thread located here → http://forum.xda-developers.com/showthread.php?t=1116251
download is here → http://www.mediafire.com/?i57410xodydx5l1
Follow it verbatim. Worked like a charm!
unistall
i had the same thing happen the other day i opened device manager and unistalled the driver for the phone then pluged the phone back in let it reistall and away i went may have to reistall drivers from kies
All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.
AdamOutler said:
All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.
Click to expand...
Click to collapse
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux
cobraa783 said:
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux
Click to expand...
Click to collapse
No. The device is controlled by windows in a virtual machine.
AdamOutler said:
No. The device is controlled by windows in a virtual machine.
Click to expand...
Click to collapse
Actually ur windows didn't even need drivers for the device ur using in a vm
cobraa783 said:
Actually ur windows didn't even need drivers for the device ur using in a vm
Click to expand...
Click to collapse
It does. Otherwise it will be an unrecognized device and you can't connect it to the VM.
just wanted to chime in here and verify. had a similar problem with odin not working after using heimdall.. used another usb port and odin now sees my infuse.. no problems. thanks guys
Also, wanna say that, for some reason, I had better luck using different version of Odin. Can't remember exactly but I think 1.7 worked & 1.8 didn't - not at PC right now to verify.
Sent from my SAMSUNG-SGH-I997 using XDA
once you install zadig...driver installation for heimdall, it takes over that 1 port.
you can always go back to that 1 port or designate it for heimdall.
odin will not be usable for that port unless you re install samsung drivers again.
I have an (old -6yrs) pc with 1 usb same cord ($1) and 1 usb back port...same 1 for 6 months with heimdall - never had to mess with anything else...successful restore everytime...
use what you're comfortable with.
save that 1 configuration as your rescue if possible.
This topic was as close as I could find to my issue... Heimdall One-Click Kernel...
First of all, let me say that I appreciate all the work everyone has done on the Infuse forums. It has expanded my knowledge by leaps and bounds just by reading for about 5 hours today. I know this will be a long post, and I apologize. I am just trying to show that I have done everything (so far) that is within my ability to try.
I inherited a "mostly working" (sound doesn't work at all) AT&T Infuse 4G, and am trying to install CWM and root the bugger in order to use it on WiFi as a mini tablet. I Do Not have a SIM card for it (I am on SIMple Mobile, not AT&T), and do not plan to use it for calls (already have a phone for that). It was already running UCLB3, but I wasn't sure if that was how the phone came, or if it had been upgraded from Froyo at some point with or without the bootloaders. I had planned to play with this phone some and maybe try out some Jelly Bean since my T-Mobile G2x has lost most of the wonderful devs that it had.
First, I used the Settings>Privacy>Factory Data Reset to clear all the information on my phone and my internal SD card. I made sure that Java was the latest version on my laptop and DL'd qkster's [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3. I spent the next 2 hours reading and re-reading the OP and all the resulting posts to make sure I had a firm grasp on how to do everything. I first booted into stock Recovery and did another Factory Reset from there and also cleared Cache. I booted into Download mode on the Infuse 4G and ran Heimdall One-Click. Installed the Heimdall driver, closed all programs, rebooted the computer, went back into Heimdall One-Click, put the phone back into Download mode, clicked Flash, waited for phone to reboot, turned phone off, went back into Download mode and flashed again, this time with BL checked.
This entire process went off without a hitch. Phone boots into GB and all is glittery gold. It's when I come to the next step in the thread that I started having the issue. Again, from an overabundance of caution, I made sure that I read the thread again, absorbing all the information pertinent to loading the Kernels from One-Click. Deciding to try InfuZen-A16 Kernel, I downloaded it and ran it just as I had the previous One-Click. Opened the .jar, booted the phone to Download mode, clicked Flash, and let the phone reboot. Uh oh. Samsung splash screen is staying on my screen now...
Maybe it just needs a while to process. Left the phone plugged in so it wouldn't lose too much battery life and went and did some more reading on the forums. 5 minutes, still Samsung screen. 10 minutes, still Samsung... No biggie, I'll just read some more. Maybe this is just a longer process than I thought. 30 minutes later, still Samsung. Okay, something must be wrong... Hold down power button to shut it off. 3 minutes holding button, still on. Battery pull...
3-button workout for recovery... Nope, no such luck, still showing the persistent Samsung screen. Back to Heimdall One-Click for recovery to UCBL3. That works. Back into stock recovery. Again, Factory Reset, clear Cache. Download mode, try again. Flash InfuZen-A16 Kernel a couple more times (flashing back to Stock between attempts), using a different USB cable and different USB ports, but still same thing each time, leaving the phone for at least 15 minutes on the Samsung splash screen to see if it moves anywhere. I then tried the ENTROPY512's 4.4.2012 kernel, hoping for different results. Same thing. Tried it 2 more times with different cables and different ports. Each time that I flashed back to Stock, it worked on each USB port and cable I was trying, so I don't "think" it could be the cables or the ports that are causing the issue.
Any help is greatly appreciated. It is my understanding that to get root on UCLB3 and above, I need to have CWM installed, but other than Heimdall One-Click Kernels, the only way to get CWM on a phone is by having it already Rooted. If I am erroneous in this understanding, please point it out and I will happily do my due diligence to fix my own problem.
Thanks in advance for any help anyone gives me.
The custom GB kernels for infuse start a file system conversion immediately upon reboot (from rfs to ext4). If your sound was working, you would hear a robotic female voice providing status updates. This process typically takes no more than 20 minutes to complete, usually less.
If the phone is just sitting there at a samsung logo, try leaving it longer to see if it completes and boots the phone OS.
If it still doesn't work, try the jscott30 Odin package instead:
http://forum.xda-developers.com/showthread.php?p=27286083
Here are the custom kernels in Odin packages:
http://forum.xda-developers.com/showthread.php?t=1698367
IMPORTANT: If you try Odin, use a different USB port than the one you set up for Heimdall. Reserve the Heimdall port for only Heimdall flashing.
For Heimdall, make sure you are using this one (kernels in posts 2 & 3):
http://forum.xda-developers.com/showthread.php?t=1524081
(looks like you are based on the files you referenced above)
Regardless, make sure your USB connection is 100% reliable and you do not interrupt the flashing process - otherwise you may brick the phone.
Thanks for the reply, Zen. I'll try it again when I get home and just let it run for at least an hour.
I have a minor aversion to using Odin, just because it is closed source as opposed to open source for Heimdall. I will take it under advisement, though.
Thanks for all the words of wisdom you give to all the members of xda. :thumbup:
*edit* - Well, decided to just let it ride for over an hour. Took an extended nap after I got home, so after flashing, the phone has been on the Samsung screen for well over 3 hours. I am going to presume that the Heimdall kernel install packages are a no go for me. I will read up on Odin and give it a shot. Thanks again. - *edit*
Sent from my LG-P999 using xda app-developers app
Okay so yesterday I decided that I wanted to restore the factory EP4 ODIN package from imnuts' website so that I can factory upgrade to FP1 and re-root.
So I downloaded the factory image and the PIT file and started the flash process with ODIN - yes, all checkboxes were selected appropriately. Well about 10 seconds into the flash, a little red message popped up on the top left corner of my phone while in DL mode that says "RX_TIMEOUT". However, the flash continued on to eventually (after about an hour) succeed.
When I went to boot up my phone, I got a Samsung logo for about an hour. Pulled the battery, tried again, same thing. Tried the flash again, same thing. Tried a few more times (each time taking 30-50 minutes, sometimes an hour) and same thing. Downloaded EE4 and tried that - same thing.
Here are the things I've tried:
- flash with battery in AND out
- flash with PIT file and without
- downloaded the EP4 image again, in case of bad download
- downloaded EE4 and tried to flash it (same result)
- let the phone charge for a bit
- tried ALL USB ports
A few flashes ago, I ended up in factory recovery (thought that was a good sign) but when I clicked reboot, I got the Sammy logo again.
EDIT: Well, after the last failed flash, I lost download mode it's toast. Any advice?
What version of Odin are you using?
Does the charging icon come up if you plug it into the wall? Maybe the cable is bad.
I've noticed that either my cable, or the mini usb port on the phone are going bad. If I move the cable/phone even slightly, it loses USB connection with the comp. Now I make sure there is a good connection, and I don't move the phone/cable AT ALL when I am flashing via ODIN.
edit: this is actually being discussed in another thread RIGHT NOW: http://forum.xda-developers.com/showpost.php?p=24412728&postcount=290
I would guess cable, though I would have tried a new cable before going through so many bad flashes.
Thanks for the replies - yes, I know it's being discussed in that thread, I started the discussion. I just figured it would be easier to post a new thread than to extend that one.
Anyway, Imnuts, I actually did try a different USB cable and the funny thing is that the ODIN flash was WAY faster, but failed (actually reported as failed). With the first cable, it was taking a really long time but it the flash passed.
But it doesn't matter anyway because I figured since I managed to (somehow) get into the stock recovery (even though I was unable to do anything), the phone must have been wiped and restored to factory, although bricked. So, I called up Big Red and they sent me a new one under factory warranty
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
n1ghtwish said:
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
Click to expand...
Click to collapse
After USB1 pass, phone off, three button press didn't work? (Vol. up, home, power) try quick boot app from market see if that'll get you in recovery.
Sent from my SCH-I510 using xda premium
n1ghtwish said:
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
Click to expand...
Click to collapse
I suggest try someone else computer. Obviously, there is data drops and caused between the driver and your O/S or hardware.
After a few more tries and almost throwing the laptop and the phone out the window, it passed and I now have recovery and stock rooted FP1.
Good lord.
For future reference, I would avoid using Odin with the phone connected to a USB hub. It only adds a failure point in the connection. Given that you already have one bad USB port the way it sounds, odds are the other one is partially bad as well, given your issues with Odin.
imnuts said:
For future reference, I would avoid using Odin with the phone connected to a USB hub. It only adds a failure point in the connection. Given that you already have one bad USB port the way it sounds, odds are the other one is partially bad as well, given your issues with Odin.
Click to expand...
Click to collapse
Well, that's why I tried without the hub. Oh well, it's done.
I'm not much of a computer person really, I only use this thing for breaking my phone
n1ghtwish said:
Well, that's why I tried without the hub. Oh well, it's done.
Click to expand...
Click to collapse
That's what imnuts was saying, though. Using a hub adds a failure point, which is a bad thing, but you also said one of the USB ports on the laptop had already gone bad. Two side-by-side ports are typically linked, whether out at the ports or back at the controller. If one went bad, the other is also likely to not function properly. The main point is that in the future I would avoid flashing using that laptop all together.
Alright, here's the story. I've been here a while, flashed a lot and never had an issue. My S3 locked up and shut down after loading a ROM so I decided to flash back to stock and start over. I have unlocked the bootloader and flashed many ROM's, modems, rpm, etc. before.
My phone was in download mode in ODIN and had begun flashing when the cord was pulled out of the phone (don't ask). Since then I can still get into download mode. Odin recognizes the phone but won't move beyond NAND WRITE Start!!!. Occasionally, it will boot telling me to repair update with KIES. I have tried KIES but it won't recognize the phone. I have downloaded the stock PIT and attempted flashing that while having root66 in in the PDA column. While ODIN continues to recognize the device I cannot get a flash past NAND WRITE start.
I have tried flashing the bootchain, CWM, and bootloaders in ODIN all with the same result. I have tried several cables and different USB ports. Did I manage to hard brick my phone even though I can get to Download mode?
Thanks.
Any ideas?
Try a different computer and make sure you are plugging into a usb 2.0 plug. Check the MD5 sums of your downloads too.
Tried that. I think I need a way to fix the NAND partition. Flashing the correct PIT doesn't work either.
Did you pull battery and press appropriate buttons, then put battery back in while holding button combo?
Also, nothing will flash unless you can actually get into download mode.
I'm in download mode but nothing will get past the nand flash write... I can get into download mode and ODIN recognizes the device. Flashing anything seems to start fine but I cannot get past Nand flash write... it just stays there forever. I need some advanced help as I think pulling the cord while flashing in ODIN jacked up my partitions.
It's still doa. Any ideas?