I have stock 4.1.2 rooted. I tried installing cwm 6.0.2.9 using odin and instead of pass it said reset on top. Now it shows yellow triangle but doesn't turn on after that. Please help.
Sent from my Nexus 4
Dozeris said:
Hi,
I have a problem while trying to root my device in order to install new custom roms.
My device is: s2 i9100 4.1.2.
Problem: <ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
*I had rooted my device a year ago in order to unlock it, then i have unrooted it, and instaled stock firmware.
*I tired to reinstal drivers many times, i tired to shut down kies while trying to root.
*I tried to install other official firmware and i have the same problem. What ever I am doing with Odin every time the same issue.
Does someone have any desicion?
Click to expand...
Click to collapse
Read that thread by Hopper about odin troubles.
Related
Hi all i just tried to flash a offical rom with odin than it fails so i unplug it now whenever i switch on i see Firmware upgrade encountered an issue, Please select recovery mode in kies. I believed it is semi brick the reason that cause the brick probably because i select the wrong option in bootloader however i have not fiddel with the pit or partition. which is the best way to get out? i have been googling awhile but no clear definte answer
Just go to Download Mode (Vol Down+Home+Power) and flash a full firmware again, via Odin, this time don't do anything wrong
Regards.
ithehappy said:
Just go to Download Mode (Vol Down+Home+Power) and flash a full firmware again, via Odin, this time don't do anything wrong
Regards.
Click to expand...
Click to collapse
Hi ithehappy i have just tried and it failed agian here are some logs
<ID:0/011> modem.bin
<ID:0/011> param.lfs
<ID:0/011> Sbl.bin
<ID:0/011> zImage
<ID:0/011> boot.bin
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011>
<ID:0/011> Receive Response form LOKE
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time i just tick pda phone and csc i have been trying to use http://forum.xda-developers.com/showthread.php?t=1075278 official rom according to the logs what do you think it may went wrong?
That's the correct thread. Don't know what is wrong!
You sure you are flashing a Full firmware, i.e- around 300MB size? Just extract it, you will get a .tar, add to the PDA section of Odin.
Regards.
X807 said:
Hi ithehappy i have just tried and it failed agian here are some logs
<ID:0/011> modem.bin
<ID:0/011> param.lfs
<ID:0/011> Sbl.bin
<ID:0/011> zImage
<ID:0/011> boot.bin
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011>
<ID:0/011> Receive Response form LOKE
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time i just tick pda phone and csc i have been trying to use http://forum.xda-developers.com/showthread.php?t=1075278 official rom according to the logs what do you think it may went wrong?
Click to expand...
Click to collapse
Your phone is not bricked it's a fault from your phone
Give me more details so I can help you!
PS here are official firmwares >>> http://www.samfirmware.com/fwandroid.htm
wow thanks ! i just try to fiddling an now got it rebooted with nothing wrong: This is what i have done i have just choosen csc and pda and leave the phone without any option will that be fine?
is quite weird the phone basiclly updated to a new firmware lost the root but the clockworkrecovery is still intact, so i tried to root it again, and it works fine, so i think is possible to flash without selecting the phone option in odin??????????
You just need to select PDA in Odin, nothing else.
And when you flash a ROM, even the same old ROM you had, you will lose Root, you've to Re Root.
Regards.
So I just got a Galaxy Note II SCH-i605 (Verizon) and decided to root the phone. Unfortunately, I didn't unlock the bootloader before flashing the rom and the phone is currently soft bricked. No problem, before I started I had downloaded the stock rom from samsung-updates.com for the make and model of my phone. I begin to reflash the stock rom and about 10% in Odin displays an error and stops flashing the new rom. I attempted to download roms from other places for my phone but they all stop at the same spot when flashing (including the one found here).
Could someone kindly tell me what I'm doing wrong?
This is what the message log is displaying:
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'd go try and flash imnuts stock rom and follow the instructions to get back fully to stock. It is in the original dev section.
http://forum.xda-developers.com/showthread.php?p=34891181
Section 1b. Make sure you follow the steps for people in the L4 OTA. Your phone is failing at writing sboot because the new ota blocks that
Sent from the dark on a Note 2
kintwofan said:
http://forum.xda-developers.com/showthread.php?p=34891181
Section 1b. Make sure you follow the steps for people in the L4 OTA. Your phone is failing at writing sboot because the new ota blocks that
Sent from the dark on a Note 2
Click to expand...
Click to collapse
It's weird, I just tried reflashing the rooted OS and this time it wiped the old image completely and is working fine now. I really hate the "magically fixes itself" solution. Because I don't exactly learn anything from it. However thanks for the information because I'll be sure to note that before trying anything else.
SailorDeath said:
So I just got a Galaxy Note II SCH-i605 (Verizon) and decided to root the phone. Unfortunately, I didn't unlock the bootloader before flashing the rom and the phone is currently soft bricked. No problem, before I started I had downloaded the stock rom from samsung-updates.com for the make and model of my phone. I begin to reflash the stock rom and about 10% in Odin displays an error and stops flashing the new rom. I attempted to download roms from other places for my phone but they all stop at the same spot when flashing (including the one found here).
Could someone kindly tell me what I'm doing wrong?
This is what the message log is displaying:
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Just try flashing only the PIT file, it worked for me just by re partitioning it.
i really want Cyanogenmod thats why i am already 3 days working on it, first try i install cm 10.2 because this is what i saw in IBM times, btw my S3 is stock 4.3 before i start flashing cm. after flashing cm10.2 got unknown IMEI and unknown baseband, wht i did is to flash again stock firmware via odin,I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar, after flashing, everything went fien, my imei and baseband restore to normal, again i root my s3, and flash again the CM10.2, success and the baseband and IMEI still ok, BUT THE problem is no service, no signal/network....flash again stock, and my friend told me to try from http://get.cm after that success, BUT still the problem is no service.......... i root again and try to patch with ariza, but cant, when i check odin mode, i see the binary counts: YES 3counts, and after that i use triangle away, to reset, success, reseted.
now i want to flash with stock firmware and stop using custom rom, (frustrated).........
first try, flashing complete! but after restart...samsung logo only...
try again flash by ODIN, it doesnt continue this time,
OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i hope somebody will try to help me...back to stock!
thnks
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 try to flash this ,if it fails then emmc chip is damaged, new motherboard required
flash again with stock 3 times, back to normal thanks for reply
Hey everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<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)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.
Hi guys. I have a galaxy s6 that I tried to flash with official firmware 5.1.1 via odin. I was rooted before that. The flash failed and now it says to use Verizon's software utility to restore the phone. That utility doesn't work and the reps at the store had never heard of it.I literally can't fix the thing. No amount of flashing in download mode helps. It always fails.
Anyway, I went to Verizon and they are sending me a replacement in two days. In download mode it still says that the firmware is official. However it also says samsung custom. (Assuming the root) I don't know if Verizon will backcharge me for this. Is there any way to get rid of the custom status? When I put it in the box to return it I'll leave it on the System Software Update Failed screen.
Remember I can't flash via odin, that just fails. Samsung smartswitch doesn't recognize the device. Recovery mode is a no go.
Thanks for the help!
What's the error message in Odin?
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
es0tericcha0s said:
What's the error message in Odin?
Click to expand...
Click to collapse
in seems to always fail. I can go back to download mode or be instructed to restore via Verizon's software assistant. Here is what odin has to say. It fails at the system.img Verizon G920V
<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..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mrao said:
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
Click to expand...
Click to collapse
I was not on 5.1.1 at the time. I downloaded 5.1.1 from sammobile or one of the other firmware hosting sites. I also tried 5.0.2 but that gives me a nand error.
Would perhaps flashing a pit file work? The problem is the the one firmware I originally tried to flash (5.1.1) doesn't have a pit file. The other firmware 5.0.2 does have one but it's only 4kb. I'm not sure if that's right.
Just in case anyone finds this in the future. I figured out how to fix this. I had have a working phone to install verizon's upgrade assitant. It would not work from the exe I found on the internet. From there I had to install it in a virtual machine because it did not like Win 10. From there I simply plugged in my device and it restored it. Use this method if odin doesn't work. I WILL NEVER ROOT AGAIN!
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
es0tericcha0s said:
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
Click to expand...
Click to collapse
Odin failed a flash and I could not reflash with odin again. I don't ever want to have that happen again. It wasn't the firmware I triple verified it before I flashed it. It was the correct firmware.