just another issue with firmware encountered a issue boot loop, but i.m reading bosible all treads, and try all methods sown here, but everry time odin says fail! im try stock rom from some site posted in this forum, but progressbar on tablet reach only 10% then odin says fail! i,m try Install TWRP and CWM - again both fail with odin, i,m try stock recovery, same effect, only difference if install the recovery, the progressbar in all cases, on tablet reach 100%, after odin says fail! any idea?
Odin can be finicky... Try a different usb port and cable and see if it will work for you.
Related
Hi a few days ago my phone was restarted and it got stuck on the samsung galaxy s3 screen. It is a t-mobile sgh-t999 model. It will boot into download mode but not recovery. After trying Kies to no result. I have deleted it from my pc and attempted to recover by flashing the stock rom using odin. I've tried that many times and always fails as well.
I have reinstalled s3 drivers. Made sure Kies is completely gone. I have downloaded the stock rom and three versions of Odin 3.04 3.07 and 3.09 and I get the same results. A write failure. Does anyone have any ideas how to proceed?
One observation I've noticed is that the bar underneath the Android in Download mode never appears. Which leads me to think that it never starts the process of taking the firmware.
Any ideas what to do next?
What is the error message?
Having same trouble
hi Serio22
NAND Write Start!!
FAIL!
Complete(write) operation failed.
serio22 said:
What is the error message?
Click to expand...
Click to collapse
Hi Serio22
NAND Write Start!!
FAIL!
Complete(write) operation failed.
Same exact issue on my sgh-t999
This morning it restarted itself (plugged into charger all night) and stuck at Samsung Galaxy SIII on screen. Recovery doesn't work and it will go into download mode. I am downloading the stock firmware from (sammobile firmwares SGH-T999) and will try installing with Odin tomorrow.
I will likely fail like you guys. I have taken such good care of the phone, never drop it, not a scratch on the screen...and this randomly happens in the middle of the night.
Please update!
Same exact issue on my SGH-T999 which makes me wonder that this is some software update issue that has possibly impacted many phones at this time.
In my case, it also restarted by itself this morning and got stuck at Samsung Galaxy SIII on screen. I started from figuring out if it was a hardware issue but the phone seems OK physically (i.e. the power button is not stuck, etc.). Recovery doesn't work and it will go into download mode like indicated by others above. I tried downloading the stock firmware SGH-T999 from Sammobile (actually a couple of different versions and tried installing via Odin 3.-07 many times but always failed with the error message above or
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
I also tried installing non-stock recovery files (TWRP, trying CWM at the moment) and that worked but without success in changing anything in the initial issue.
Sounds like they are sending bad firmware bricking our phones over night. Sorry I've found no solution yet.
whattheschmidt said:
Same exact issue on my sgh-t999
This morning it restarted itself (plugged into charger all night) and stuck at Samsung Galaxy SIII on screen. Recovery doesn't work and it will go into download mode. I am downloading the stock firmware from (sammobile firmwares SGH-T999) and will try installing with Odin tomorrow.
I will likely fail like you guys. I have taken such good care of the phone, never drop it, not a scratch on the screen...and this randomly happens in the middle of the night.
Please update!
Click to expand...
Click to collapse
Just an observation. I too was only getting the
"Complete (Write) operation failed." message at first.
After trying to flash the stock rom via Odin multiple times, I now get
"NAND Write Start!!"
"FAIL!"
Hope I didn't make it worse.
MarcinT said:
Same exact issue on my SGH-T999 which makes me wonder that this is some software update issue that has possibly impacted many phones at this time.
In my case, it also restarted by itself this morning and got stuck at Samsung Galaxy SIII on screen. I started from figuring out if it was a hardware issue but the phone seems OK physically (i.e. the power button is not stuck, etc.). Recovery doesn't work and it will go into download mode like indicated by others above. I tried downloading the stock firmware SGH-T999 from Sammobile (actually a couple of different versions and tried installing via Odin 3.-07 many times but always failed with the error message above or
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
I also tried installing non-stock recovery files (TWRP, trying CWM at the moment) and that worked but without success in changing anything in the initial issue.
Click to expand...
Click to collapse
SGH -t999 Pit File
Does anyone have any idea if flashing the stock rom with the T999 pit file in Odin possibly fix this problem? I've been reading about it, but can't really determine if this is the next step to troubleshoot this problem.
Write start and immediate fail in my case as well.
Keep looking into this and updating thread. I already ordered a new phone because of this but will want to fix this phone to sell it if not just sell the new one and stick with this longer...
I tried updating to the newest version of ROM using Kies but that did not work, either. Sometimes the phone cannot be recognized by Windows and sometimes Kies says it is "connecting" with the phone. When I tried updating, Kies did not see the phone, so maybe it had a negative impact on the download. I am going to uninstall the drivers and install them again just before connecting the phone to Kies and try updating again. This stuff is really time consuming.
I could not find a good CWM recovery file to flash via Odin so I did not try that. The interesting thing is that successfully flashing TWRP recovery file did not do anything - I still cannot get into recovery mode. Then I tried flashing stock recovery file again - and got the FAIL! message from Odin.
I've seen other threads talking about this issue, but don't remember if it was ever fixed. Have you guys tried different cables or computers?
I've tried a different cable (non-stock) but that did not help at all. I can try a different computer and will report here.
No update on fixing the phone...I tried everything I could on my end really. I think I will have to look at sending it in to Samsung?
I bought a used S5 on ebay. Much faster and nicer...liking it quite a bit. Samsungs update to break my phone and buy a newer Samsung worked I guess.
Daughter's SIII crashed also, her phone was bootlooping. Since her volume button doesn't work, I used a jig to put into D/L mode. Flashed T999LUVUBOH1_T999LTMBBOH1_T999LUVUBOH1_HOME.tar.md5 from Sammobile and ODIN said it passed. The phone will not go passed the "T-Mobile 4G LTE" screen. I've tried several times, always passes, always gets stuck.
Daughter doesn't mind, she's been using the Note II that I didn't want to part with after getting myself the Note 5
When flashing the stock rom with Odin, do not check anything except f.reset time. After flashing, and seeing the word reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery, assuming the volume up me home button work, no perform a factory wipe.
The volume up and down button don't work?
Had stock AT&T SGH-I747 at Android 4.2.2 rooted with chainfire working fine. Today an update installed automatically and now I'm dead.
At first, it would show the Samsung logo and maybe another, then just go black.
Now normal booting, or attempting to boot into recovery gives: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
If attempt to boot into download mode, it succeeds. But everything will end up with "FAIL!" in Odin and show "fused 3 > binary 0" on the phone. I've tried multiple Odins: v3.10.6, 3.09, 3.07 and multiple recoveries (Clockwork 6.0.4.7, etc.) and stock ROMS (UCALG1, UCDLK3).
Even Kies "Firmware Upgrade and Initialiasion" option, where you enter in SGH-I747 and the serial number will go through all the motions and then fail, with the same "fused" message showing on the phone.
Grendelin had the most similar situation (I can't post external links yet, but you can get to it at http:__androidforums.comthreads_at-t-gs3-at-t-issues-after-downloading-newest-update.860382_ by replacing _'s with /'s) as me but the difference is that he was able to flash a recovery image which led to further restoration.
Please help. If it's not possible to recover this, I would just like to get a couple years' worth of pictures from /sdcard/DCIM/*.
When you boot into download mode, do you see anything about warranty bit?
You could try and flash TWRP using Odin, then boot to TWRP and mount the data partition to see if you can copy the data from the phone to your computer.
audit13 said:
When you boot into download mode, do you see anything about warranty bit? You could try and flash TWRP using Odin, then boot to TWRP and mount the data partition to see if you can copy the data from the phone to your computer.
Click to expand...
Click to collapse
I tried TWRP (specifically twrp-2.8.7.0-d2att.img.tar) using Odin and it gave all the usual signals that it's working before the box turns red and it says "FAIL!" on it. Here's its log in case it's useful:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialization..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yes download mode does mention the waranty bit. Here's the full text:
Code:
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 3
Are you using version 3.07 of Odin? Did you uncheck everythign except f.reset time before flashing?
What about flashing Philz Touch for the d2lte? I was suggesting TWRP because you may be able to re-flash a rooted nj1 system and boot img.
I asked about warranty bit to make sure that the phone was running a 4.3 or newer bootloader. As you may know, the 4.3 bootloader cannot be downgraded so you can't flash anything from sammobile.
Yes, 3.07, and there were only two things checked, "F. Reset Time" and "Auto Reboot". At your suggestion I unchecked the latter but it appeared to have no effect on the flashing success.
Can't get to philz's dev files at the moment since his page at goo.im is down.
I don't understand what is meant by 4.3 bootloader. Isn't 4.3 referring to the Android version? While Android lists the bootloader version in its properties, Android in principle shouldn't be concerned about what lower level, hardware specific bootloader brought it up, should it?
I really need my phone back
dreamluvr said:
Yes, 3.07, and there were only two things checked, "F. Reset Time" and "Auto Reboot". At your suggestion I unchecked the latter but it appeared to have no effect on the flashing success.
Can't get to philz's dev files at the moment since his page at goo.im is down.
I don't understand what is meant by 4.3 bootloader. Isn't 4.3 referring to the Android version? While Android lists the bootloader version in its properties, Android in principle shouldn't be concerned about what lower level, hardware specific bootloader brought it up, should it?
I really need my phone back
Click to expand...
Click to collapse
I really hate to tell you this but I don't think your going to get this fixed yourself. If Odin is failing like that your probably going to need a debricking service that can flash your emmc directly. If you can get a recovery back on then you'll be fine cause you can then flash firmware to repair the damage the OTA did. Keep trying I guess but ultimately you'll probably need the debricking service.
When bootloaders are refered to as 4.3 or 4.4.2 is just referring it to the OS version they came with in the OTA. And while on a pc this is true windows isn't dependent on the lower lever firmware, Android kinda is... least the OEM's have made it that way.
Most people say that if you can reach download mode then you're OK. I can't believe this ****ing phone is just going to sit here and reject everything that's sent to it. In some cases I'm sending it stock stuff.
It's bull**** that AT&T can just impose their updates like this. Yes I had modifications that probably interfered with their intended update, but they obviously exercised no caution, not checking that everything was in their expected state before overwriting.
I'm upset that I supported a gimped device, one that's cryptographically preventing user modifications when it's user paid for.
Is there no hope in simply making a disc image, mounting it, and recovering /sdcard/DCIM ?
I had a similar problem a week ago. I got this i747 and decided to wipe it using kies. I didn't know about the boot loader problem after the kitkat OTA upgrade. So I had a soft brick like you. I ran into the same problems using Odin to flash the twrp tar and various other images. What I decided to do was flash twrp multiple time using odin. But during one of the reboots I think I removed the cable and put it back (maybe even pulled the battery?) in time for odin to check and say it was successful. Then i had a semi-functional twrp to flash the rooted ucfnj1 image from the i747 dev forum. I still have root issues, but my phone works.
bump before I mail it off to unbrick service
looking for any ideas
short summary: canNOT boot into recovery, CAN boot into download, but Odin always fails and phone says "fused 3 > binary 0"
EDIT (Sept 8, 2015): I used mipick22's JTAG services on ebay and he fixed it. Good price, good communication, etc. Says he's a member on here but didn't give his username.
Hi All
My Note 2 (7100 International) failed. All i can get is the "Firmware upgrade encountered an error" screen.
Cannot enter download or recovery.
Kies doesn't recognise the phone.
Does connect to Odin but cannot flash ROM or PIT. Odin stops at "Get PIT for mapping"
Please ideas?
Thanks
Just connect your phone to Odin.
Even on this screen Odin should be able to detect it.
Flash an official stock ROM first, then if everything is okay, install your favourite ROM again.
It should takes a bit longer than usual, just be patient.
Otherwise do an emergency recovery with kies.
Never mind, sorry
You tried pulling the battery and the button combination can't get into download mode? Do you have a USB jig?
yes, I think it could help
HERE
Thanks I did try this and nothing happened.
if you can't do anything, then maybe it's SDS
Hi i was helping my friend to update his firmware. after doing so the phone is now stuck in a weird bootloop. i had seen my fair share of bootloops but this seems weirder than others. the n7100 logo would loop very quickly (sorta like flash) and keeps doing so. can't enter recovery mode at all, only download mode. plug it to odin and whatever i can throw at it i just got nand write start fail, be it twrp, multiple versions of stock rom. im at the end of my wits, so what should i try next? thank you for any input
What is the Odin error when trying to flash the latest stock ROM from sammobile.com? Tried different USB cables and USB ports?
I kinda have/had the same problem.
N7100 logo would bootloop quiet fast (doesn't get to the point where it should load the rom).
Can't enter recovery bc of that.
Only thing that works is download mode.
After trying to flash newest stock rom (4.4.2) it failed once (I think my cable gets too old...)
Next try it worked without a problem.
Problem persists.
Next step was flashing an older repair firmware (4.1.2) but it failed (I think bc of the 4.4.2 bootloader? IDK)
Then I tried to flash the newest stock again but with the pit file. Flashed without a problem but the problem was still there.
Last step I made was to flash the newest stock with the pit file and nand erase + update bootloader.
Tried it 2 times but it failed.
Now I'm stuck on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Download mode got a red message also: "RPMB: INVALID RPMB DATA"
I don't know what to do now. Please help.
PS: It was a "new" motherboard from aliexpess, it had a chinese version of the stock 4.1.2 if I remember right and was already rooted when I installed it. I wanted to flash the newest 4.4.2 for the new modem and stuff and then upgrade to lineage. :/
i've having issues flashing a tmobile s8+ i've tried odin 3.12.07 odin 3.12.03 with both i either get FAIL Model dismatch or Complete (write) operation failed. i got it to sucessfully flash once and i guess it didn't do like it was supposed to because the phone did not boot up and i can only get into download mode. if i try to get into recovery it gives a few error lines saying failure to mount etc. this is a friends phone that i need to get back operational. please help!
EDIT: i also used prince cosmey odin 3.12.03 with the same result