So after following this link: http://www.cnet.com/how-to/how-to-root-your-samsung-galaxy-s3/ I have a bricked device.
No matter what I do, Odin seems to fail. This is what I think caused the problem in the first place. Also there is the possibility that the guide is way out of date.
So I was wondering if anyone had any advice on how to proceed? The device isnt mine and this isnt my first time rooting a device. I just have never bricked anything before.
Here is the log from ODIN from recreating the process in the link above
<ID:0/004> Added!!
<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> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is the Log from ODIN from my latest attempt to flash something at it.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried flashing a full image, but it gives this error
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried flashing the "stock" image.
Going to try a different PC tomorrow and hope that I get a different result.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.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> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have realized this is in the wrong forum. Please delete this topic.
its a request to developers to make TWRP 3.0.2-0 recovery so then we can flash it by Odin if possible .........
Please try to flash this zip (it's untested, so I don't take any responsibility for it):
[link removed]
tried this but boot loop
This should be flashable with Odin (Pda line):
http://d-h.st/dcnl
Please let me know.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
i m running the marshmallow rom by polishvodka
Please make sure you use Odin3 v3.07.
It it doesn't work, then I think it's not compatible with your rom.
Main problem is that kernel+recovery are tied together in Janice, while in other devices recovery is separated without any kernel interference (and less chances to break things).
But it could be done something if Epirex (or some dev) can take into account a mod like this for our device:
http://forum.xda-developers.com/gal...t/isorec-isolated-recovery-galaxy-s2-t3291176
I proposed it to him, but I think he needs (rightly) more feedback about this over than my opinion.
my odin is Odin3_v3.10.7
ok i will give at a shot in Odin3_v3.07
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
What is it succeed?
does not end after
<ID:0/005> NAND Write Start!!
Oh, very unfortunate. Btw, thanks for the information Bro..
I'm trying to go back to stock and i've tried every which way. When I try to do it through Odin it fails. I've tried on every USB port I have.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I tried through Smart Switch and it says its a Galaxy Edge 7 so it doesn't let me do the emergency restore.
Then I tried to flash any other room though TWRP and it just says failed and give Error 7.
Any help will be appreciated.
You need to download the correct firmware for your device
Hey guys I was going to update my S4 active from 4.4.2(Stock not rooted) to 5.0.1 through Odin but it failed and I don't know what to do. Any help is appreciated
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
EDIT: DOWNLOADED ANOTHER FIRMWARE FROM SAMMOBILE AND NOW IT WORKS!
Download again from sammobile just to be sure file is not corrupted.
Use Odin v3.7
Use good data cabe. Use good USB. Do no use USB hub.
wilsonhlacerda said:
Download again from sammobile just to be sure file is not corrupted.
Use Odin v3.7
Use good data cabe. Use good USB. Do no use USB hub.
Click to expand...
Click to collapse
Thanks for the reply. I already resolved the issue. I downloaded another firmware and now it works
im on infinity pro 8 rom
this is the stock rom i want to flash.
while trying to flash stock rom i get this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
its stuck at the downloading mode. cant boot to twrp, it would just take me to a error page when i reboot and it says:
An error has occurred while updating the device software. Use the emergency recovery function in the smart switch pc software. i tried that but nothing happen.