Code:
Hi, I have a serious problem with my Note 4 (SM-N910F).
Since the phone where lagging a lot from a few days, yesterday I choose to do a restore to factory condition, but after that it begun to bootloot.
So I flashed the latest 5.11 firmware available (this from Sammobile for Italy.
As soon as I did, I thought that all my problems were gone, but no. After the firmware, I wanted to get root, so after a quick search on Internet, I choose to get this kernel.
But after the flash of the kernel, I begun to have A LOT of problem. So I decided to flash again only the firmware.
Today I tried again to flash the TWRP recovery to flash the kernel .zip to get the root, but as soon as I did it, the phone didn't go beyong the Samsung logo.
I tried to take these steps: firmware-recovery-root, but after a while, ODIN gave me the error of "PIT binary missing" (or similar).
So, I downloaded a .PIT file for the 5.1.1 (I don't remember where) and I reflashed the firmware with the .PIT file and I didn't got any errors.
After I checked that there were no problems, I tried again to install that kernel.
And I tried again, and again, with different 5.1.1 firmwares.
A thing that I think it's important, it's that I noticed that sometimes while powering on the phone, it went automatically to Download Mode, with a message saying that it couldn't boot in "normal mode" and "MMC read error".
Also I noticed that everytime a powered off, or I rebooted the phone, I had to take off the battery in order to turn on again the phone. It seems like the phone never really turns off.
Now, the phone doesn't boot, the recovery isn't working, and the only thing I have is the download mode.
I tried on 2 pcs, with 2 usb cables, with 2 ODIN versions (3.09 and 3.10.6) to flash a couple of 5.1.1 firmware with and without the .PIT file.
Every time I start the flash on ODIN, while flashing the SYSTEM.img, the flashing stops and on the phone I get this message "ODIN: flash write failure".
I don't really know what to do, unless took it to a warranty center. I think that this problem could be caused by a faulty EMMC, or a brick caused by me.
PS: this is the log from ODIN
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COH4_N910FITV1COH1_N910FXXU1COH4_HOME.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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>[COLOR="Red"] FAIL! (Write)[/COLOR]
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE:
I successfully installed the TWRP recovery (twrp-2.8.6.0-trltexx.img.tar) with ODIN, so I wiped all the partitions but one: SYSTEM. The error is "E:Unable to mount '/system'.
At this point I think I messed up with the partitions.
UPDATE2:
I installed the CWM PhilZ, and with that I formatted the /system partition.
So I tried to re-flash the firmware with no success, but I tried again with the .PIT file and it succeeded!
Do you think I should retry to root it?
UPDATE 3:
So, after the first setup (google account, samsung account, time, etc.) I turned the phone off to insert my SIM card.
But as soon as the smartphone turned off, it powered on itself again in Download mode, showing me this error:
Could not do normal boot.
ddi : mmc_read failed
I think that maybe, there's a problem with the eMMC
Hi there
Do you want to flash the firmware?
i have s6 edge and when i choose file(in odin) for (PA) it falis so i tried for (CSC) and it worked.
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
landerhazard said:
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
Click to expand...
Click to collapse
i had a simialar problem with odin but my problem was that the adb wasnt successful i had to do it twice before it said successful then when i ran odin it worked not sure if this will help but i was stuck for days with the odin fail it was frustrating but good luck hope you find a solution
Related
So my phone got ran over, and I shelled out $150 on the deductible for a replacement. I rooted and put TWRP on immediately. I did a full wipe: data, system, cache, and dalvik, and attempted to flash BeanStalk ROM only to get some error that said something like "can't install from the binary". I wanted to try some other ROM, but for some reason mounting USB storage didn't work. So I just ODINed back to stock...which also didn't work. I get the following every time I try to ODIN a ROM
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf9fullupgrade.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> SingleDownload.
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
After trying to use ODIN, booting normally or booting into recovery gives me a screen that says "firmware upgrade encountered and issue. Please select recovery mode in Kies and & try again" (I installed kies but the recovery mode doesn't find my device).
However, I CAN use ODIN to flash custom recoveries like TWRP or philz, so I'm not without hope. I just don't know what to do.
When I ODIN a recovery on and boot into it, the phone says "RECOVERY IS NOT SEANDROID ENFORCING" if that helps.
THINGS I'VE TRIED
Different USB ports
Different USB cables
Uninstalling/reinstalling drivers
Various ROMS
Different versions of ODIN (settled on 3.09)
Were you on 4.3/MJA or 4.2.2/MF9 when you attempted to install the ROM?
I'd try putting the stock MF9 recovery on and do a factory reset from there. Then Odin the firmware on.
It sounds like you have the 4.3 bootloader which means you also can not install any previous bootloader. This is why you get a fail when sending aboot.mbn. Though you should be able to flash philz recovery and install a different rom. (i'm on the 4.3 bootloader and running 4.2.2) but you loose the ability to run a stock kernel. Hope this helps
skippwhy said:
So my phone got ran over, and I shelled out $150 on the deductible for a replacement. I rooted and put TWRP on immediately. I did a full wipe: data, system, cache, and dalvik, and attempted to flash BeanStalk ROM only to get some error that said something like "can't install from the binary". I wanted to try some other ROM, but for some reason mounting USB storage didn't work. So I just ODINed back to stock...which also didn't work. I get the following every time I try to ODIN a ROM
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf9fullupgrade.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> SingleDownload.
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
After trying to use ODIN, booting normally or booting into recovery gives me a screen that says "firmware upgrade encountered and issue. Please select recovery mode in Kies and & try again" (I installed kies but the recovery mode doesn't find my device).
However, I CAN use ODIN to flash custom recoveries like TWRP or philz, so I'm not without hope. I just don't know what to do.
When I ODIN a recovery on and boot into it, the phone says "RECOVERY IS NOT SEANDROID ENFORCING" if that helps.
THINGS I'VE TRIED
Different USB ports
Different USB cables
Uninstalling/reinstalling drivers
Various ROMS
Different versions of ODIN (settled on 3.09)
Click to expand...
Click to collapse
wilsonwa said:
It sounds like you have the 4.3 bootloader which means you also can not install any previous bootloader. This is why you get a fail when sending aboot.mbn. Though you should be able to flash philz recovery and install a different rom. (i'm on the 4.3 bootloader and running 4.2.2) but you loose the ability to run a stock kernel. Hope this helps
Click to expand...
Click to collapse
Right before I left for class I started up the MJA full restore and I came back to a working phone! Thank god. I love the false sense of accomplishment that comes from fixing your own mistake.
Grab this tar (it's zipped, so unzip and use tar.md5..) and try it in Odin. It's the full MJA.
Also make sure to run Odin 'As administrator'
Hey everyone,
I got this problem, today i wanted to whipe my phone... But i failed and also whiped the OS... So i was stuck on samsung logo.. After i got into download mode i tried to flash the standard unbranded S4 called:I9505XXUFNC4_I9505PHNFNC1_PHN
After i tried to flash that as PDA with ODIN v3.04, it says it failed..
What to do now?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC4_I9505PHNFNC1_I9505XXUFNC4_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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.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> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I used the official cable ...
Any options?
EDIT:
Now when i boot the phone it only says:
Firmware upgrade encountered an issue.Please select recoverymode in Kies & try again.
Tunestwo said:
Hey everyone,
I got this problem, today i wanted to whipe my phone... But i failed and also whiped the OS... So i was stuck on samsung logo.. After i got into download mode i tried to flash the standard unbranded S4 called:I9505XXUFNC4_I9505PHNFNC1_PHN
After i tried to flash that as PDA with ODIN v3.04, it says it failed..
What to do now?
I used the official cable ...
Any options?
EDIT:
Now when i boot the phone it only says:
Firmware upgrade encountered an issue.Please select recoverymode in Kies & try again.
Click to expand...
Click to collapse
just repeat procedure, change odin version, change usb port, change usb cable....
samersh72 said:
just repeat procedure, change odin version, change usb port, change usb cable....
Click to expand...
Click to collapse
no effect so far.... T.T
Try it on another pc
Or
Download another firmware
I had the same issue yesterday phone stoipped working got andropid.phone errors and phone would not make or take calls when go to dialer kept crashing and black screen tried wiping/factory reset and still had same issue on djembey stock pre root
I decided to then download stock EE firmware latest 4.4.2 this then failed and phone after this would not even boot up only thing I could manage to do now was to put into download mode would no longer even go into recovery mode either
I tried flashing about 4times and ODIN kept on failing tried with Odin 1.85, 3.04 3.07
FED up I read somewhere to try diff cable ( like that will make a diff I thought)
YESSSSS it flashed and now I have a working phone
After using, diffrent pc's, diffrent cables, and diffrent usb ports...
it worked... Jezus i love you guys!
Hello...
Please if someone could help me and guide me to rescue my brand new S5 G900F :crying:
Starting to get desperate here... as I did not backup my EFS was going to do it after rooting
Here are the steps I did to get into trouble:
Upgraded to Stock Poland G900FXXU1BNL2 Loolipop to the phone everything was fine... except some app crashes as Facebook so decided to return to 4.4
So put the phone into recovery mode did a full wipe and loaded G900FXXU1ANJ1 from poland too with odin
The phone booted and looked all ok so turned it off after first boot withouth even touching the language settings.
Put again into dowload and decided to run CF-Auto to root the phone
Here everything started and Fail! message appeared at ODIN.
So turned of the phone and now the phone auto boots with message "Firmware upgrade encounter an issue. Please select recovery mode in Kies & try again."
So put the phone in download mode and try to put again stock 4.4 G900FXXU1ANJ1 again but got fail message during system.img.ext4 writting multiple times.
Then tryed to go back to Loolipop same issue multiple times...
Then finally try with lollipop after restarting computer, changing usb port, unziping again the firmware, etc...but from off state removed battery then putting back, then connecting the usb cable so from the "Firmware upgrade issue" screen hit the start and the firmware finally succedd the process.
The phone boot normally ....but I'm such and IDIOT that I said ok why not get back to 4.4 as it worked first time...
So put the phone back into download mode and try to load 4.4 stock rom G900FXXU1ANJ1 again but FAIL! appeared again and now I cant get pass it even after trying what solved the issue before...
Please help ideas etc ???
Now if I try to load 5.0 G900FXXU1ANJ1 it fail at the begining of system.img.ext4 writting...
If I try with 4.4 G900FXXU1ANJ1 from "Firmware Upgrade issue" screen the best I could get was half of the system.img.ext4 writting once before getting FAIL message again but most time it fails at the begining too.
These is what I'm getting from Odin now every test...
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL2_G900FXEO1BNL1_G900FXXU1BNL2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks a lot for your time in advance for helping me...
Let me know if you need more info or anything please.
SOLVED!
GREAT NEWS
Solved myself on the last try before heading to bed crying hehehe
What I did for the record to others...and dont actually as why it worked...but it did...
Leaved the phone without battery almost half hour, then shutdown computer, unziped the 5.0 stock rom once again to have one fresh copy, open odin loaded rom wait till md5 check, then change usb port once again, then put battery to phone, then connect cable as soon as odin recognized it hit start and pray.
WORKED...
So the phone restarted as normal etc but there was the app updating screen...after it the phone was like dumb and some poland message only displaying. So turn it of, put on recovery, did cache clear and then complete wipe and restarted, Now everything is back to normal...
Phone now on 5.0 and staying so at least I find a way to backup my efs folder and stop sacking from these time mistake. I will only downgrade if safer method available or teste or maybe updating to the new 5.0 G900FXXU1BNL7 that just get out and forgeting about the downgrade well what I wanted was to open LTE bands... maybe some day...also available on 5.0 LTE band opening
For know happy having it back working
Good that you solved it and even better that you explained how you solved it! :good:
Seems like your phone wants you to stay on 5.0, hehe.
Sent from my SM-G900F using Tapatalk
Looks like he wants 5.0 stock untouched really bad...
As today I had another episode with it... LOL
It got BNL7 over OTA yesterday after all everything went perfect... but today I try to root it using CF-Auto-Root-klte-kltexx-smg900f and Odin 3.09 after enabling USB debug, etc. just like instructions but at the end of process FAIL!
Had to put again stock BNL5 to recover it.
Don't know what to do or I should wait for update on the CF-Auto to use it. In the manual I found said it should work on BNL7 but looks like it does not.
Code:
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have spent the better part of two days searching for a solution with no avail so I thought I would post up what I see and determine if someone else has found a solution (I have found similar posts with either no answers or successful outcomes).
I was on OG5 and kept postponing the OTA update (phone was stock, not rooted as I received it with OE1 on it and eventually took the OG5 update since the bootloader was already locked). Last week I fell asleep and forgot to plug in my phone, and when I woke up the battery was dead. When I plugged it in I got the bootloop (without the RECOVERY BOOTING banner at the top). I have Odin 3.09, and have tried flashing different images including just the ROM, the ROM & recovery, etc, as well as the full factory image with the bootloader included. If I try to flash anything with a bootloader in it older than OG5 I get the error (as expected). However, all flashes end up in the blue "RECOVERY BOOTING...." loop. If I force it to recovery I get Maintenance Recovery and not the full factory recovery so that i could clear cache and Dalvik (as many have suggested). Basically, I'm trapped when trying to boot into regular recovery and cannot get there. Even tried repartitioning when flashing, all to no avail.
I saw a thread somewhere a couple days ago back on something with two phones (known good, another with issues) and a way to recover the dead one with the help of the other, but have not been able ot find it since.
Can someone hopefully provide me counsel on how to either fix what I am seeing or perhaps to the other thread as I have access to a working S5 with OE1 on it that I can use to make any custom image and/or something to help out? Below is my output from Odin - appears to work every time it flashes anything that doesn't contain a bootloader older than OG5:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU2BOG5_G900VVZW2BOG5_G900VVRU2BOG5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This is conjecture, based on what I've read recently.
I believe what you're asking about is the Unbrick image, but my understanding is that is only needed when you are not able to get Odin to recognize that your device is even a phone. In any case, you would need to use one that matches the firmware and bootloader version of your phone.
Your Odin output reports that it IS connecting to the phone, that factory image md5 is valid, and that it is flashing successfully.
You cannot downgrade below BOE, but you can always go up. Maybe try using Odin to flash the BOK3 image linked in this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Update 2/1/2016
Well, I was fed up last night and left the phone in the boot loop as I headed off to bed (watched it boot loop about 10 times). Woke up Sunday and it had booted up and was running with all the data intact, even after I had tried to do a Factory Reset from the Maintenance Recovery menu. Got curious, powered it down and it it boot looped a couple times (without the RECOVERY BOOTING banner) and then came up ... after that it seemed to be OK as later in the day I powered it down a couple times and it came up fine.
Thanks for the reference @painiac - I was able to flash either OK3 or OG5 with success from Odin (the full factory images) but behavior was the same.
I got curious and tried to boot into recovery this morning and now it's boot-looping again - sigh... Was going to let it run the battery out trying to boot and after about 12-15 loops it finally came back! Hopefully the patience theme seen above may help others who are in the same scenario as this phone never seems to boot into standard recovery even after flashing full factory images.
At this point, I am planning on (hopefully) getting it booted up one last time, copying all my data off of it, and then walk into Verizon and try to get an exchange as this is not normal behavior and smells to me a bit like a hardware issue but my searches have determined that I am not the only one with this issue - HTH someone...
I agree, it's probably a hardware issue because a fresh factory image should have wiped out any problems that would be causing a bootloop. That combined with the fact that the problem persists across different version flashes.
Hi Guys,
Ok this is my problem, the phone is a Samsung Galaxy S4 LTE SGH-I337 ATT Unlocked i bought a year ago here in Argentina, the phone came with the Android 5.0.1 "OC3" firmware. The phone is a refurbished one.
Arount six month ago, the phone started a weird problem, it cannot make o receive calls (it rings actually, but you cannot hear the caller and the caller cannot hear me).
This happend after i pass the phone turned on in the airport scanner (i always turned it off before), so initially i though of some kind of related problem with that.
After researching online, my conclusion was the problem is related to the common sim card tray problems stated in another post here.
So i got a new phone and i tought to flash another android version to change the modem, because i really need to sell the S4.
This is the steps i do
First i root the phone with the Wondershare mobile trial app. I seems to work fine.
Then i load Odin 3.09 (is not my first Samsung, i have flashed another friends Samsungs before) and i try the methods for rolling back to NB1 and go to OC4/OK2, but none works!
All flashes stops in recovery.img write failed. So i read some more and yes my bootloader is locked and now i have a softbricked phone.
I try with Kies, nothing. Now i just want it to came back to life again.
I know i shound read more, and its my fault.
Its there any way to unbrick my phone?
Please Help!
Thanks
This is the tl;dr
Samsung SGH-I337 ATT Unlocked Refurbished
Android 5.0.1 (USB Debugging On)
I337UCUGOC3
LRX22C.I337UCUGOC3
KNOX 2.3
Rooted with Wondershare Mobile Go Trial
Try to flash "NB1 Full Rootable", fails at recovery.img
Can go to Download, but doesnt go to Recovery
Doesnt boot, says recover with Kies
Kies doesnt allow to recover
Tried anothed methods, always says fails write o complete failed when write.
I use the back USBs from my PC, all USB 2.0, and its a "good" data cable.
I use Odin 3.09, and Odin 3.10.6
I use Kies 2 and Kies 3
I try to flash recovery-mj6.tar.md5 also (i found in another post here), always fails in write
I use 1.5.61 Samsung USB Drivers
I Use Windows 7 32 bits
Please Help!
Thanks
Sounds like you have a bad download of the NB1 firmware. Try downloading it again and flashing it again with Odin 3.09 or 3.07. I have used both versions of Odin on my i337 AT&T GS4 and I've had your exact problem before when I didn't get all the parts of the NB1 firmware in their places. I've never successfully flashed out of a soft brick with Kies, just Odin.
Hi, thanks for your response.
I have 2 NB1 tar.md5 files, both download from links i encounter here in this forum
Code:
07/03/2014 17:26 2.598.543.468 ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5
18/06/2014 11:04 2.598.676.551 I337UCUFNB1_TWRootable_Full_Odin.tar.md5
I just tryed again and now is stuck in system (i dont know why, yesterday always got stuck in recovery.img, maybe because i flash recovery_mj6.tar last night? idk)
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> persdata.img.ext4
<ID:0/007> system.img.ext4
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Still only boot to download mode.
I will to find other odin versions.
Thank you again
Succefully flashed NB1 !!!
I use the PC from work, Windows 7 64 bit Ultimate, USB 2.0 (as COM3) in the back, same data cable.
I use Odin 3.12.3 (found it here)
The phone is alive!
Thanks all.