I gave the gf's kid an old S2 Skyrocket to use with CM9 I believe on it. Something went wrong and the kid couldn't boot it anymore. I took a look. Flashed it with an old Odin but tried something else, flashed it with a newer Odin and completely screwed it up now. It's been a couple months since I tried fixing it so what I can remember is I think i accidentally wiped Clockwork recovery somehow and then the PIT file. Tried using a newer ODID to flash and just kept getting errors. The only way I can get into download mode now is with that little USB device that boots it into download mode. Otherwise it just stalls at SAMSUNG logo.
So i tried messing with it again today. Using Odin 3.04 I tried flashing to stock firmware and just get this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
Cant seem to find any PIT files for the i727 Skyrocket. I found something called SGH-I727-PIT(modified_6GB) but no clue what that is. Tried it anyway and just get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
After messing with hours I'm about to give up and throw it in the trash...but read that if you can get into download mode then it could be fixed and i'm just doing it wrong.
Any ideas?
Odin can be quite finicky. Keep trying and with different usb ports (the ones in the back of the pc if you're using a desktop) and cables. You shouldn't need a pit file. Do not have re-partition checked in Odin.
Sent from my Nexus 9 using XDA-Developers mobile app
I've flashed a bunch of phones with Odin before no problem. But with this phone I really screwed with stuff. I'm usually good about being careful but not this time. I might have had repartitioned checked the one time. I can't remember. I think I screwed up the pit on the phone. Hence the no. Pit error. Never had that before.
Ill try the other USB ports thought. Can't use Kies emergency restore because it won't connect to the phone. I have all drivers installed. First time I'm baffled as to flashing a Samsung phone. I don't even need the phone but my OCD just wants it working again.
u can read this, might help, http://forum.xda-developers.com/showthread.php?t=2023328
Thanks for the link vincon. Gave it a shot but still no love. Tried to flash that celox PIT file with Odin 1.85 but all I get is the same damn error
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried it again selecting the PIT and a stock ATT firmware file and same thing...the darn Complete(Write) operation failed.
If i try just using the stock tar file I get:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried different USB ports, rebooted computer...nothing. I'm about to give up on it
Related
This is what happens every time:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> cache.rfs
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried 3 different computers with antivirus off and no other programs running and every usb port on those computers with 3 different cables each using [ODIN][UCKD5] GTG's Ultimate Unbrick following every step exactly. also tried using [ODIN][UCKD5] Odin - Stock (100% or Root+3e). ive been working on this for about 3 days and i able to get into download mode every time just fine no matter what state the phone is in and every computer recognizes the phone. no matter what it fails with the same error above.
Darthstygeon said:
This is what happens every time:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> cache.rfs
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried 3 different computers with antivirus off and no other programs running and every usb port on those computers with 3 different cables each using [ODIN][UCKD5] GTG's Ultimate Unbrick following every step exactly. also tried using [ODIN][UCKD5] Odin - Stock (100% or Root+3e). ive been working on this for about 3 days and i able to get into download mode every time just fine no matter what state the phone is in and every computer recognizes the phone. no matter what it fails with the same error above.
Click to expand...
Click to collapse
run Odin as an administrator. you may need to right click on the icon to get that option.
mfpearson said:
run Odin as an administrator. you may need to right click on the icon to get that option.
Click to expand...
Click to collapse
i forgot to mention that in my original post...i ran everything as administration with no different results. thanks though.
mfpearson said:
run Odin as an administrator. you may need to right click on the icon to get that option.
Click to expand...
Click to collapse
Have you tried to run Odin with no sd card in the phone?
no sd card no sim card or anything,,,,just the phone
Sorry to say, i tried to root Samsung GT-I9300 with help of Odin and CF-Autoroot, but got similar Messages as glenf (http://forum.xda-developers.com/showthread.php?t=2202563) and got stuck - no way to reaktivate handy (stockrom) but could manage to activate downloadmode .
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
.....
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write start!!
<ID:0/004> cache.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used Odin 3.04 and CF-Auto-Root-m0-m0xx-gti9300.tar.md5 .
I rmoved battery to get into download mode again and tried to use Odin with a stockrom - the same effect.
I had a stockversion 4.3 MAX-I9300XXELLA-20130104192229 and thougt it would work to root - as in thread http://forum.xda-developers.com/showthread.php?t=1957273&page=63.
Anyone who can help me,Samsung is new to me, i did rooting and custom roms on HTC before, never had problems. I did not find a way out.
Regards Manfred
lavgold said:
Sorry to say, i tried to root Samsung GT-I9300 with help of Odin and CF-Autoroot, but got similar Messages as glenf (http://forum.xda-developers.com/showthread.php?t=2202563) and got stuck - no way to reaktivate handy (stockrom) but could manage to activate downloadmode .
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
.....
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write start!!
<ID:0/004> cache.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used Odin 3.04 and CF-Auto-Root-m0-m0xx-gti9300.tar.md5 .
I rmoved battery to get into download mode again and tried to use Odin with a stockrom - the same effect.
I had a stockversion 4.3 MAX-I9300XXELLA-20130104192229 and thougt it would work to root - as in thread http://forum.xda-developers.com/showthread.php?t=1957273&page=63.
Anyone who can help me,Samsung is new to me, i did rooting and custom roms on HTC before, never had problems. I did not find a way out.
Regards Manfred
Click to expand...
Click to collapse
hi im having a similar problem with my s3 gt-19300.
its not rooted . suddenly it just went dead
and using samsung kies it failes after downloading the os.
using odin i get the following.:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMJ9_I9300VFGGMJ5_I9300BUUGMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
any help??
Hey guys,
exactly the same Problem here... Tried diffrent USB ports, Odin versions and cables...
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The reason I was rooting mainly was being unable to copy files to my phone... wtf. If you have any other solution for that on hand, I couldn't care less about rooting, so shoot
Thanks in Advance
Sorry to hear you're having problems try using Odin 3.07 instead of 3.04 worked for me.
Sent from my D5803 using XDA Free mobile app
I got a Samsung Galaxy Tab (GT-P5110) of which the tablet did not startup anymore, and know nothing about the prehistory.
I downloaded stock firmware from samsung site: http://samsung-updates.com/device/?id=GT-P5110
and downloaded the latest EUR version named : P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5
With Odin 3.07 I installed that image in download mode with default options left on. After that I got the following screen message on the tablet:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably something went wrong. Then I downloaded Kies from samsung site, installed it with all extra drivers and I got the problem that Kies never recognized the tablet. Reinstalled many times, tried different options, but the problem persisted (took me 8 hours totally). Battery of the tablet was fully loaded and before this problem I saw that it was loading correctly.
Then I read this excellent document : http://forum.xda-developers.com/showthread.php?t=1652398
Tried again with Odin 3.07 and 1.85 and could install the image with only the reboot option on in Odin, flashed successfully the image, but still the problem:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I do not have much options left to look for. I was thinking about:
- driver issue
- wrong image
- wrong method
Can somebody help me to have this problem fixed ? I am willing to reinstall Windows 7 on this laptop.
Really nobody knows ?
never had problems here on Windows 8.
Maybe try flashing using Heimdall
But will I need a Heimdall image for that, because it does not accept the samsung image.
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
Click to expand...
Click to collapse
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
Click to expand...
Click to collapse
I am located in The Netherlands, and downloaded the specific image for the Netherlands, region PHN, used Odin 3.07 to install it, but still the same problem.
What can I do, wait for somebody who can give me a hint ? This is the first time I do a recovery of a Samsung tablet, and don't know how to continue with it.
Your help will be very much appreciated.
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Joery360 said:
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Click to expand...
Click to collapse
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
proconsoles said:
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Do you think that this problem is hardware related ??
Nobody knows ?
Same for me
I'm dealing with almost the same issue, except for my ODIN flashes it doesn't even succeed. I know this happened to it after I tried to use heimdall to update my CWM, but I have had no success getting anything to work. I've been without a tablet for like a week now, doing everything I can think of or find a walk through for. I mean for me, I wouldn't mind going back to stock as long as it works again. Here's what my ODIN is doing:
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm about to try the TWRP someone recommended above, I'll let you know how it goes
---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------
I tried flashing a different version of TWRP and it looked like it was going to do something, but it isn't going. Here's what it did this time:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_TWRP_2.7.0.1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Forgot to mention that I'm using Odin 3.09 on a p5113. Not that it makes huge difference.
Two things to try:
If you can boot into recovery, try the factory reset.
If not, have you tried Kies recovery mode?
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Maybe because Samsung / KIES Process running in background on your PC?
A Case of bad partitions
Deucethehero said:
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Click to expand...
Click to collapse
Try flashing with .pit file, partitioning set to on. Should correct partition problems. Somebody might have installed a non-android OS that botched. Look for a .pit file around the forum, you should find one. Good luck.
Thank you
Thanks for the tip, I'll give it a shot and post back with results!
Sorry for the late reply
Hey guys, I could have sworn that I posted back on Friday, but it's not here. Anyway, it's been a crazy few days for me traveling and school starting and all that.
About the tablet, I downloaded a pit file and it looked like it was going to work, but unfortunately it did not. I'm working on getting the tablet charged and set up to try again because I got a zip that had 2 pit files, so I'll try the other one soon. I'll post the results when I get them, thanks again for all the help!
Still not working, but I think some progress
Sorry to take so long responding, it's been a busy week.
So I just attempted to flash the .pit again, and it failed. Here's what Odin gave:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
It says, "There is no PIT," but that's what I'm trying to flash, right? I'm a little confused, but I hope someone knows what that means.
Thanks for all the help guys!
New info!
So today I was messing around with the .pit file that I had, and I used an editor to make it exactly the same as one I found in another forum. After Odin told me that it failed, I went to reset the tablet, and it showed me the Galaxy Tab 2 screen, which it has not done for a few weeks now. Then I plugged it in and it shows the battery charging symbol. Currently it is a 18%, so I'm going to let it charge and then try booting it up again and see what I get. Hopefully all is well now, but we shall see here in a few hours.
I also was not aware that I needed to flash the system along with the pit, and once I had that going it made a little more sense to me.
I'm going to try to post that pit here if anyone wants it. Hopefully it will help someone else in the future.
Odin Flashed, but failed
So I got into normal old download mode on the device using that .pit file. Yay! However upon attempting to flash the stock os back on Odin gave me this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UEBLH3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm going to look into other avenues, but this did set me back to the "Firmware upgrade encountered an issue... blah blah"
So i recently rooted my i925 with this universal method...
http://forum.xda-developers.com/showthread.php?t=2403230
https://www.youtube.com/watch?v=QCBLOhWavT0
Then I decided to try and run the casuall "Jailbreak" software to get a custom recovery and unlocked bootloader and i just checked "I did it" during the root portion since I already was... and now I'm soft bricked. I can only get into the download mode and tried flashing with odin but no luck might be doing something wrong... Also tried following the cyanogen instructions which involve flashing a cwm recovery in download mode but still no luck. Any help would be greatly appreciated!!! If I hold power the screen will just flash the download mode screen on and off. I pulled the back off and pulled power. No difference.
Any ideas guys? This is the first time I've bricked anything since I've been here and it's got me pretty worried...
Still stuck is anyone has any ideas.
2rz_taco_sr5 said:
Still stuck is anyone has any ideas.
Click to expand...
Click to collapse
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.
tselling said:
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.
Click to expand...
Click to collapse
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.
2rz_taco_sr5 said:
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.
Click to expand...
Click to collapse
Maybe try Heimdall commandline. You can flash individual pieces.
tselling said:
Maybe try Heimdall commandline. You can flash individual pieces.
Click to expand...
Click to collapse
I'm just going to warranty it out with verizon. Ive warrantied phones before with no issue. usually for amoled screens that get shadows before the year warranty is up. Hoping all goes well.
im having this same issue, device keeps starting and then fails out, is there a solution to this?
Q&A for [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Attempted to follow the guide here on my old Infuse to breathe some life back into it, but I can't get it to work. Installed the drivers through Kies, Odin detects my phone in yellow. I follow the guide to the letter, but after flashing 'reset' in blue and getting the green 'pass' my phone simply doesn't reboot, nor can I boot it manually. I've removed the battery a few times and it doesn't change the situation. I can still boot into download mode with no issue and have tried flashing a few times, but I'm having no success booting the phone after Odin is done, nor can I get into recovery mode.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> modem.bin
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Any ideas?
SG2Tiger said:
Attempted to follow the guide here on my old Infuse to breathe some life back into it, but I can't get it to work. Installed the drivers through Kies, Odin detects my phone in yellow. I follow the guide to the letter, but after flashing 'reset' in blue and getting the green 'pass' my phone simply doesn't reboot, nor can I boot it manually. I've removed the battery a few times and it doesn't change the situation. I can still boot into download mode with no issue and have tried flashing a few times, but I'm having no success booting the phone after Odin is done, nor can I get into recovery mode.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> modem.bin
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Any ideas?
Click to expand...
Click to collapse
I never tried this flash before, but I do have a couple questions before proceeding...
Is your phone AT&T or Rogers?
Are you able to get back into download mode (that is, by method of device fully turned off, holding down both Volume Buttons and inserting the USB cable)?
joel.maxuel said:
I never tried this flash before, but I do have a couple questions before proceeding...
Is your phone AT&T or Rogers?
Are you able to get back into download mode (that is, by method of device fully turned off, holding down both Volume Buttons and inserting the USB cable)?
Click to expand...
Click to collapse
AT&T, the model is I997. I can still get into download mode, but I can't boot normally, nor into recovery mode (by holding volume up + volume down + power button; Samsung logo never appears). I used the included version of Odin with both the UCLB3_Unbrick_1.1.zip and UCLB3_Unbrick_root_1.1.zip files on the linked thread (I tried both).
SG2Tiger said:
AT&T, the model is I997. I can still get into download mode, but I can't boot normally, nor into recovery mode (by holding volume up + volume down + power button; Samsung logo never appears). I used the included version of Odin with both the UCLB3_Unbrick_1.1.zip and UCLB3_Unbrick_root_1.1.zip files on the linked thread (I tried both).
Click to expand...
Click to collapse
I always recommend this one for AT&T (could never try it myself, as I was a Rogers user), but you may have more luck with this (option A or D).
http://forum.xda-developers.com/showthread.php?t=1613523
joel.maxuel said:
I always recommend this one for AT&T (could never try it myself, as I was a Rogers user), but you may have more luck with this (option A or D).
http://forum.xda-developers.com/showthread.php?t=1613523
Click to expand...
Click to collapse
Tried this a few times and it keeps failing. It'll get about 1/3 of the way there and then my computer will make the 'device disconnected' noise and Odin will fail. I left it in download mode, plugged in, without attempting the download to see if it was an issue with my cable or port, and it didn't disconnect...it seems to only be happening when I attempt to flash the md5.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
SG2Tiger said:
Tried this a few times and it keeps failing. It'll get about 1/3 of the way there and then my computer will make the 'device disconnected' noise and Odin will fail. I left it in download mode, plugged in, without attempting the download to see if it was an issue with my cable or port, and it didn't disconnect...it seems to only be happening when I attempt to flash the md5.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Even with option D? I see C was used, based on the log...
Sent from my Asus MeMO Pad 8"
joel.maxuel said:
Even with option D? I see C was used, based on the log...
Sent from my Asus MeMO Pad 8"
Click to expand...
Click to collapse
For some reason option D is taking an unreasonable amount of time to download (it's been over an hour now), so I had initially skipped it and tried options A and C, with the same results. I'll report back once I am actually able to get option D downloaded.
Same problem with every option. Progress reaches about halfway, then fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
SG2Tiger said:
Same problem with every option. Progress reaches about halfway, then fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Last thing I can think of, you are using the Odin that comes with the package right?
joel.maxuel said:
Last thing I can think of, you are using the Odin that comes with the package right?
Click to expand...
Click to collapse
Yes, it should be Odin3 v1.7.
The dev-host file mirrors are down? Does anybody have copies of them to upload?
I need the one with root.
Umaroth said:
The dev-host file mirrors are down? Does anybody have copies of them to upload?
I need the one with root.
Click to expand...
Click to collapse
Sorry, no option A here, but I do have option C (with CWM, deodex, etc) on mirror. See the following link:
http://forum.xda-developers.com/showpost.php?p=58392432
Hope this helps.
Link Are Broken
Umm the link cant be downloaded.. i m trying to restore my infuse but most of the downloadable file is broken or file not found
ZExNos said:
Umm the link cant be downloaded.. i m trying to restore my infuse but most of the downloadable file is broken or file not found
Click to expand...
Click to collapse
Good evening,
Try my mirror:
http://forum.xda-developers.com/showpost.php?p=58392432
Options are limited, only "Option C" but it should be enough to get the job done.
Cheers.