G930TUVS4BQJ2.rar
Getting Desperate
I have a T-Mobile Galaxy S7, and I've tried to load this firmware to it but I keep getting the "All threads completed. (succeed 0 / failed 0)" result when I "start" from Odin (after loading the AP, CP, & CSC). I am using Odin v3.12.3, which seems to be the latest.
Any idea what I could be doing wrong?
HyperChicken said:
I have a T-Mobile Galaxy S7, and I've tried to load this firmware to it but I keep getting the "All threads completed. (succeed 0 / failed 0)" result when I "start" from Odin (after loading the AP, CP, & CSC). I am using Odin v3.12.3, which seems to be the latest.
Any idea what I could be doing wrong?
Click to expand...
Click to collapse
Which CSC are you loading?
I tired both actually. I did learn my knox isn't tripped, so I guess I just have a custom OS installed.
HyperChicken said:
I have a T-Mobile Galaxy S7, and I've tried to load this firmware to it but I keep getting the "All threads completed. (succeed 0 / failed 0)" result when I "start" from Odin (after loading the AP, CP, & CSC). I am using Odin v3.12.3, which seems to be the latest.
Any idea what I could be doing wrong?
Click to expand...
Click to collapse
your PC isn't recognizing your device. that's why it didn't fail OR succeed in either thread
bkup said:
your PC isn't recognizing your device. that's why it didn't fail OR succeed in either thread
Click to expand...
Click to collapse
Hmm, ok. I'll try it again and see what's going on. My phone says "Custom" when loading, so I guess that means the stock OS was at a minimum modified. I'm going to try again and see how it goes. appreciate the help.
---------- Post added at 08:43 PM ---------- Previous post was at 07:55 PM ----------
bkup said:
your PC isn't recognizing your device. that's why it didn't fail OR succeed in either thread
Click to expand...
Click to collapse
Hey - I just want to thank you because even though the cable I was using make that connection sound, I tried another one and that solved the problem for me. I'm in the sign on process and it looks like I'm good to go. Thank you SO much, man. I hate/love when it's something stupid like a bad wire.
Related
i just picked up my Note 3 the other day from verizon (SM-N900V) and i attempted to root it using Root_de_la_vega. It was my fault for not doing more research, but i thought since i wasn't going to do anything fancy other than remove all the bloat ware that it should be simple enough. Now when i use Odin (3.09) it keeps failing and now my phone is bricked and now it says i need to use the software repair assistant.I have tried downloading Kies 3 as one site suggested, but for some reason it does not recognize the device What is the quickest way to repair this? I don't care if it goes back to default. I really need to fix it ASAP! Please help!
Below is the script that shows up in odin when i try to root it:
ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> cache.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
ok, im new to this, and its my fault for jumping in the deep end without doing my proper due diligence. I dont have a good clue what you mean my MJE odin file? Are you refering to the AP file that i drop into odin?
droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
i also tried using different versions of odin. Can you link to a good root file for SM-N900V?
When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.
theicro was
bftb0 said:
When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.
Click to expand...
Click to collapse
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Just to Add Here Are 2 Other Good Places To Look
http://forum.xda-developers.com/showthread.php?t=2576104
How To Flash in ODIN
http://forum.xda-developers.com/showthread.php?t=2543386
Root Recovery Roms
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
Download root checker from play store
thanks all for the help, and thanks for not chastising me much for my ignorance. Ill def make sure to do much much much more research before i try to do something like this again lol.
Your all back up and running with root I take it then ?
Root checker says that my device was not correctly rooted.....ill look into i more, not sure why it did not take.....it seems like verizon makes it more difficult than any other carrier to root their devices
deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
The Odin factory image stuff returns everything back to 100% factory, so you shouldn't be rooted if that's all you did.
And since you didn't mention anything else, I suppose that's exactly what we should presume.
Normally when you use that Odin procedure, you are returning to square one - you need to root. Probably with kingo.
As btfb0 said.... root with KingoApp (dot) com.
drag&fly said:
As btfb0 said.... root with KingoApp (dot) com.
Click to expand...
Click to collapse
As you seem to have figured out, the more research you do, the more likely you are to succeed at stuff like this. At least you were able to recover it.
That being said, KingoApp is definitely the best/easiest way to root this phone.
Hi guys, I'm new to this site. I have a specific problem that I can't seem to find the answer for.
My phone: At&t Samsung Galaxy S4 (I made a typo in the title... )
Model: SGH-I337
I had MF3 version/4.2.2
I used various threads to eventually root my phone.
I was very happy.
I had to use safestrap
I was happy with safestrap
I had my stock in the stock rom slot
I had [ROM] Google Edition 4.3 [Clean][Deodex][276MB][2013.11.21] in first slot.
I was very happy with it.
Here is the thread http://forum.xda-developers.com/showthread.php?p=47718525#post47718525
I made a stupid move when I was finally done, I had my phone rooted, I had everything I needed, but it wasn't enough...
I did something in the mount options area in safestrap.. switched my sd to internal memory
My phone has been in a boot loop ever since on Samsung Image
I had Slot 1 active when this happened.
When I'm in recovery mode, all the options, including wipe data/factory reset doesn't work
I tried using a pit file in Odin to fix/failed
I tried using Odin 3.09 with stock firmware I found in some threads to try and get factory/failed
I get this in Odin along with fail "All threads completed. (succeed 0 / failed 1)"
I really want to fix my phone.
Preferably I would like it to stay as mf3
Does anyone have a solution?
A link to a thread I missed?
Something more recent?
I also tried Kies, but it was giving me trouble, I'll try it again as a last resort.
I hope there's a solution.
Kies 3
Kies 3 didn't work as well with emergency upgrade.
worried
joeydija said:
Kies 3 didn't work as well with emergency upgrade.
Click to expand...
Click to collapse
SW Rev Check Fail fused 2 Binary 1
Whoa.
Here is the solution!
Place all files found in the zip he gives in Odin 3.09
Top - BL
Bottom - CSC
http://forum.xda-developers.com/showthread.php?t=2716482
Makes sense, makes sense?
WOWza, very happy.
:good:
I spoke too soon.
joeydija said:
Here is the solution!
Place all files found in the zip he gives in Odin 3.09
Top - BL
Bottom - CSC
http://forum.xda-developers.com/showthread.php?t=2716482
Makes sense, makes sense?
WOWza, very happy.
:good:
Click to expand...
Click to collapse
Failed at the end.. I guess that's not the right order.. farthest I've got so far though, now when I boot I see Odin.
[Not the God]
hoorah!
The solution. FINALLY.
The file order goes like this...
AP gets the biggest file size
The one that starts with Base Loader goes in BL
The one that starts with CSC goes in CSC
The last one goes in CP
[solved] happy
joeydija said:
The solution. FINALLY.
The file order goes like this...
AP gets the biggest file size
The one that starts with Base Loader goes in BL
The one that starts with CSC goes in CSC
The last one goes in CP
[solved] happy
Click to expand...
Click to collapse
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
of course
SnowDot said:
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
Click to expand...
Click to collapse
Download link: https://mega.co.nz/#!MwAhlDyC!UOnkMFsUSctakHRfE1Mr95c1ymVwy1wBPu2yiPerros
If you've never used this site before
It's kind of weird
Press the DOWNLOAD button, it's RED
Wait for 100%
When you reach 100% it either starts downloading by itself or you press the download symbol
Good luck!
Summon odin
SnowDot said:
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
Click to expand...
Click to collapse
Also, you can find Odin3 v3.09 here: https://www.androidfilehost.com/?fid=23321874045862094
Remember to run Odin3 v3.09 as administrator
Right click Odin3 v3.09, press Run as administrator
Make sure you have your USB connected to back of computer
Take out battery from device
Place battery back in
Hold Volume Down + Home Button + Power Button
When you see WARNING! press Volume Up
Plug in USB
Wait for Odin3 v3.09 to recognize your phone
Leave all default settings
Place files from mf3. Tar in slots
Press START and wait 5 minutes
Good luck!
Another Soft Bricked SGH-I337...
joeydija said:
Also, you can find Odin3 v3.09 here: https://www.androidfilehost.com/?fid=23321874045862094
Remember to run Odin3 v3.09 as administrator
Right click Odin3 v3.09, press Run as administrator
Make sure you have your USB connected to back of computer
Take out battery from device
Place battery back in
Hold Volume Down + Home Button + Power Button
When you see WARNING! press Volume Up
Plug in USB
Wait for Odin3 v3.09 to recognize your phone
Leave all default settings
Place files from mf3. Tar in slots
Press START and wait 5 minutes
Good luck!
Click to expand...
Click to collapse
Joey, thanks for the resources as there are so many broken links out there.
I'm having the same issue; however, I'm finding very little success flashing with Odin to return back to stock.
Following the same steps you've outlined above, I receive a the following from Odin:
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and the following from the prompt on the S4 screen:
SW REV. CHECK FAIL : fused : 4, Binary : 2
Click to expand...
Click to collapse
I've tried multiple prescribed methods, including the one you outlined, using Kies, and using nkhater's method for Unbricking I337 posted here.
I'm not entirely sure what steps to take next but any thoughts would be greatly appreciated.
mythandier said:
Joey, thanks for the resources as there are so many broken links out there.
I'm having the same issue; however, I'm finding very little success flashing with Odin to return back to stock.
Following the same steps you've outlined above, I receive a the following from Odin:
and the following from the prompt on the S4 screen:
I've tried multiple prescribed methods, including the one you outlined, using Kies, and using nkhater's method for Unbricking I337 posted here.
I'm not entirely sure what steps to take next but any thoughts would be greatly appreciated.
Click to expand...
Click to collapse
The SW REV. CHECK FAIL : fused : 4, Binary : 2 error means you are trying to flash an earlier version than your phone had before. You'll need to flash the same version you were using before, either MK2 or NB1. You can find the ODIN TAR files for them in the General section.
777
DeadlySin9 said:
The SW REV. CHECK FAIL : fused : 4, Binary : 2 error means you are trying to flash an earlier version than your phone had before. You'll need to flash the same version you were using before, either MK2 or NB1. You can find the ODIN TAR files for them in the General section.
Click to expand...
Click to collapse
Thanks for helping that guy out,
I have a question...
What ROM would you recommend for a 4.2.2 MF3 At&t Galaxy S4 SGH-I337?
I've been using the ROM found in here.
I am new to the rooted world.
It's the first ROM I tried and I love it.
I can go a whole day with, at most, losing 25% battery life.
I love the minimalist aspects of it.
I don't know how to keep track of new ROMs for my build though.
I don't really want to change ROMs at the moment, because I have everything I need with this one,
but if you can give me some cool advice, that would be awesome.
Any help, information, would be appreciated.
-Joey
Hi all,
Have attempted to fix this multiple times, and I think I've boned myself pretty hard at this point. Here's the situation:
Rooted, Safestrap'd, flashed Jasmine. All was muy bueno, but then I attempted to turn on mobile hotspot and it destroyed my mobile data by connecting and disconnecting every half a second. Perhaps there's some baseband issue or something.
I've gone through all the steps on Verizon support, and read a bunch online, but I can't come up with a solution. I'm just trying to flash back to stock/unrooted to see if that fixes the LTE radio issue, don't want to pay for an Asurion device if I can avoid it. Please give me aid!
Right now, I have Kies3 on my Macbook, and Odin v3.07+ Kies3 on my VMware, and the completely correct stock ROM for my 4.4.2 device from what I can tell, labeled "N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5". Do I need to attempt to flash a PIT file as well?
Last night, Odin failed on me multiple times, and now I'm stick at the "Firmware upgrade issue encountered" screen. I can boot into Odin, but I still keep failing when I try to flash the PDA file listed above (don't need any other CSC since I'm in the US, right?).
Kies is all FUBAR'd on my VMware as it says my device is unsupported and asks to connect my "MSM8960" which is clearly not my device and I think might be the root of my issue (See what I did there?).
On my Mac, Kies just hangs on the "Connecting..." and never connects.
I've exhausted myself trying to figure this out and am half-ready to just spend $$ and get an insurance phone but c'mon, I know this just has to be a hardware issue, amirite? Thoughts? Thanks!
KyleLinden said:
Hi all,
Have attempted to fix this multiple times, and I think I've boned myself pretty hard at this point. Here's the situation:
Rooted, Safestrap'd, flashed Jasmine. All was muy bueno, but then I attempted to turn on mobile hotspot and it destroyed my mobile data by connecting and disconnecting every half a second. Perhaps there's some baseband issue or something.
I've gone through all the steps on Verizon support, and read a bunch online, but I can't come up with a solution. I'm just trying to flash back to stock/unrooted to see if that fixes the LTE radio issue, don't want to pay for an Asurion device if I can avoid it. Please give me aid!
Right now, I have Kies3 on my Macbook, and Odin v3.07+ Kies3 on my VMware, and the completely correct stock ROM for my 4.4.2 device from what I can tell, labeled "N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5". Do I need to attempt to flash a PIT file as well?
Last night, Odin failed on me multiple times, and now I'm stick at the "Firmware upgrade issue encountered" screen. I can boot into Odin, but I still keep failing when I try to flash the PDA file listed above (don't need any other CSC since I'm in the US, right?).
Kies is all FUBAR'd on my VMware as it says my device is unsupported and asks to connect my "MSM8960" which is clearly not my device and I think might be the root of my issue (See what I did there?).
On my Mac, Kies just hangs on the "Connecting..." and never connects.
I've exhausted myself trying to figure this out and am half-ready to just spend $$ and get an insurance phone but c'mon, I know this just has to be a hardware issue, amirite? Thoughts? Thanks!
Click to expand...
Click to collapse
You have a friend with a real PC?
Also, what error is Odin giving...and I'd use 3.09 rather than 3.07.
Sent from my Note 3 via Tapatalk
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
KyleLinden said:
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried a different USB cable or port?
KyleLinden said:
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Yes...that really could be an issue. Odin goes directly to the hardware.. and in your case....there is no hardware...only a software emulation. Also...if memory serves me right (of course it might be serving me wrong), Odin uses .tar.md5 files not .img.ext4 files.
Sent from my Note 3 via Tapatalk
Interesting, makes sense. Will seek out a real Windows machine and try the new ports/cable and report back. You're right about the tar.md5 file extension, but that's what seems to generate in the dialog panel when I use the aforementioned stock ROM file.
Thanks for advice so far.
donc113 said:
Yes...that really could be an issue. Odin goes directly to the hardware.. and in your case....there is no hardware...only a software emulation. Also...if memory serves me right (of course it might be serving me wrong), Odin uses .tar.md5 files not .img.ext4 files.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
the indidual partitions boot, recovery, system within the .tar are .img files so that is not the problem.
Easter Day miracle.. I took out my old laptop, reinstalled a copy of windows 7, moved the stock ROM and the pit file I found to a USB drive, used the OEM cable, installed all drivers available for Samsung mobile devices, rebooted, and finally Odin was happy with me and decided to flash stock! Phones fixed! Thanks everybody.
Got the G955USQS5DSE5 update on my sprint S8+ last night and it basically killed my network connection. I have tried a bunch of things and nothing is working. Do I need anything special to downgrade to the previous firmware? Also, is there a best place to get the file? My phone isn't rooted or anything. It's all stock.
DAREALGUMMY said:
Got the G955USQS5DSE5 update on my sprint S8+ last night and it basically killed my network connection. I have tried a bunch of things and nothing is working. Do I need anything special to downgrade to the previous firmware? Also, is there a best place to get the file? My phone isn't rooted or anything. It's all stock.
Click to expand...
Click to collapse
From what you quoted ( G955USQSS5FSE5 ) you can only down grade to versions that had a version 5 bootloader ( 5th number from right of firmware name ). In your case version 5.
Firmware can be downloaded from sammobile or updato ( websites ). There are other sites as well.
You will need latest Samsung drivers ( for PC ) and Odin version 3.13.3 to flash firmware.
As for network issues don't know what you have tried but you could start with wiping cache in recovery mode.
spawnlives said:
From what you quoted ( G955USQSS5FSE5 ) you can only down grade to versions that had a version 5 bootloader ( 5th number from right of firmware name ). In your case version 5.
Firmware can be downloaded from sammobile or updato ( websites ). There are other sites as well.
You will need latest Samsung drivers ( for PC ) and Odin version 3.13.3 to flash firmware.
As for network issues don't know what you have tried but you could start with wiping cache in recovery mode.
Click to expand...
Click to collapse
Thank you for the instructions. I guess my only problem is getting Odin to work. I keep getting an error after hitting start.
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've tried different usb ports and wires, made sure I had samsung drivers but no luck.
DAREALGUMMY said:
Thank you for the instructions. I guess my only problem is getting Odin to work. I keep getting an error after hitting start.
I've tried different usb ports and wires, made sure I had samsung drivers but no luck.
Click to expand...
Click to collapse
Some things to try:
https://forum.xda-developers.com/ga...ning-to-ota-oreo-beta-3-t3920885/post79593856
spawnlives said:
Some things to try:
https://forum.xda-developers.com/ga...ning-to-ota-oreo-beta-3-t3920885/post79593856
Click to expand...
Click to collapse
Finally tried a different PC after everything. It actually begins to attempt to flash but then it fails with a FAIL! (Auth) error.
Is there something I need to do? I run Odin as Admin.
DAREALGUMMY said:
Finally tried a different PC after everything. It actually begins to attempt to flash but then it fails with a FAIL! (Auth) error.
Is there something I need to do? I run Odin as Admin.
Click to expand...
Click to collapse
Auth errors are usually flashing older firmware than on device
DAREALGUMMY said:
Finally tried a different PC after everything. It actually begins to attempt to flash but then it fails with a FAIL! (Auth) error.
Is there something I need to do? I run Odin as Admin.
Click to expand...
Click to collapse
It will also help to know what Odin is saying before the failed message.
What firmware are you try to flash?
After downloading firmware did you unzip the file?
S8 with stock ROM crashed, now have "dm-verity verification failed". Please help.
I'm trying to flash the latest update to try and fix this through Odin, but no luck. Just keeps failing.
alexnader said:
I'm trying to flash the latest update to try and fix this through Odin, but no luck. Just keeps failing.
Click to expand...
Click to collapse
what version of Odin do you have and what firmware are you trying to flash? Odin version is critical and you have to be flashing a firmware with at least the same or newer bootloader than what was previously on the phone
---------- Post added at 04:21 PM ---------- Previous post was at 04:12 PM ----------
the thing with samsung devices is that if you can get to Odin mode, they re likely easily fixable. Make sure you have the latest version of Odin, sometimes youll even need a modified version of Odin depending on what youre trying to do. Use the factory cable or another that you know to have good data throughput, battery at a minimum 50%, a firmware version that is compatible with your phone (which is commonly based on the version of Android you last flashed because you cannot go backwards on bootloader revisions). I always keep several version of Odin on my computers at all times just in case. Also hang on to the firmwares youve flashed in case you need to reflash them
youdoofus said:
what version of Odin do you have and what firmware are you trying to flash? Odin version is critical and you have to be flashing a firmware with at least the same or newer bootloader than what was previously on the phone
---------- Post added at 04:21 PM ---------- Previous post was at 04:12 PM ----------
the thing with samsung devices is that if you can get to Odin mode, they re likely easily fixable. Make sure you have the latest version of Odin, sometimes youll even need a modified version of Odin depending on what youre trying to do. Use the factory cable or another that you know to have good data throughput, battery at a minimum 50%, a firmware version that is compatible with your phone (which is commonly based on the version of Android you last flashed because you cannot go backwards on bootloader revisions). I always keep several version of Odin on my computers at all times just in case. Also hang on to the firmwares youve flashed in case you need to reflash them
Click to expand...
Click to collapse
I'm using Odin 3.13.3 (but also tried 3.0.7 and 3.10)
and trying to flash the latest official samsung update (8/1), but have also tried the last two.
The phone gets to the blue download mode, appears in odin as [0:COM4], but whatever I try to flash to it, it says:
<OSM> All threads completed. (succeed 0 / failed 1)
Not sure what else to do.
alexnader said:
I'm using Odin 3.13.3 (but also tried 3.0.7 and 3.10)
and trying to flash the latest official samsung update (8/1), but have also tried the last two.
The phone gets to the blue download mode, appears in odin as [0:COM4], but whatever I try to flash to it, it says:
<OSM> All threads completed. (succeed 0 / failed 1)
Not sure what else to do.
Click to expand...
Click to collapse
try a new cable. i know it sounds dumb, but its a common culprit. I used to use an old blackberry cable that was excellent for data throughput.
diff cable and/or diff usb port
hell, ive even had to go to a different computer in some instances. but if you can get to download mode, youre still in good shape
oh, how full is the battery?