Database Users

GT-I9101 Stuck on yellow triangle saying "Firmware upgrade encountered"

After I tried to use odin for root I am not able to start my phone. It can't go to recovery or download it's stuck on an yellow exclamation mark with "Firmware upgrade encountered" below it. Any solutions for this? I've tried all the instructions here already but same thing.
On odin when I try to flash a PDA file this is the prompt.,
Fail
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> boot.bin
<ID:0/014> NAND Write Start!!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help please. Is my sII totally bricked?

well I believe it has something to do with nand-write....pretty sure you shouldn't be doing that....what 'boxes' did you tick ?
if you can't get in to download mode, that generally isn't a good sign
Sent from my GT-I9100 using Tapatalk

If you havent done so already try pulling the battery then putting it back into download mode and try flashing a stock rom if this fails i suggest you look for a Samsung jig to force it into download mode (samsung jig is just a 300k resistor on a micro usb connector that plugs into your phone and forces it into download mode)

Will it be a problem if i use firmwares of i9100 to i9101 unit? Because I have i9101 and I can't really find any firmware for this. And btw, the boxes tick are just "auto reboot" and "F. Reset time". I cant really go to recovery , the yellow exclamation pops up right away after doing the Vol. down+home+power.

florexus said:
Will it be a problem if i use firmwares of i9100 to i9101 unit? Because I have i9101 and I can't really find any firmware for this. And btw, the boxes tick are just "auto reboot" and "F. Reset time". I cant really go to recovery , the yellow exclamation pops up right away after doing the Vol. down+home+power.
Click to expand...
Click to collapse
Yes it is a problem. The I9101 supposedly has different hardware to the I9100, so I wouldn't try to flash the firmware if it wasn't for the specific phone.

Do you guys have any link for a firmware of this kind of phone? Galaxy S II I9101 Made in Korea. thank you

Hi. I have the same unit, i9101, and in the same condition. I'm also waiting for a rom to be available. Samfirmware has no i9101 firmware at this time.

florexus said:
Do you guys have any link for a firmware of this kind of phone? Galaxy S II I9101 Made in Korea. thank you
Click to expand...
Click to collapse
Try searching the Android General or the Android Hacking thread and if not found then make a thread yourself and gather supporters!
Then possibly something will start!
And never flash a different firmware on a different phone!
Like u did with i9010 with i9100 firmware!!!

xwkf1
Hi,
I also have an i9101 galaxy s2. I found a working firmware for our phone in samfirmware.
Use the xwkf1 firmware. Make sure you get the south east asia release
Worked for me. Should work for you

Im gonna try it out thank you.... Any steps? Because I am stuck on the "Firmware upgrade encountered"

monchinglopez said:
Hi,
I also have an i9101 galaxy s2. I found a working firmware for our phone in samfirmware.
Use the xwkf1 firmware. Make sure you get the south east asia release
Worked for me. Should work for you
Click to expand...
Click to collapse
Hi. I get 4 files in that package. Where did you put the "KERNEL" file in Odin? Did you put it in the Bootloader option? Thanks.

marsomadness said:
Hi. I get 4 files in that package. Where did you put the "KERNEL" file in Odin? Did you put it in the Bootloader option? Thanks.
Click to expand...
Click to collapse
Are you able to go to download mode? Because I am just stuck on the yellow triangle. Thanks.

florexus said:
Are you able to go to download mode? Because I am just stuck on the yellow triangle. Thanks.
Click to expand...
Click to collapse
Someone, who is very experienced in flashing, told me that you can use Odin while the phone is in the "Phone--!--PC" state.
I just don't know where to put the "KERNEL" file from the downloaded files from samfirmware. I want to be sure before I try to flash this.

marsomadness said:
Someone, who is very experienced in flashing, told me that you can use Odin while the phone is in the "Phone--!--PC" state.
I just don't know where to put the "KERNEL" file from the downloaded files from samfirmware. I want to be sure before I try to flash this.
Click to expand...
Click to collapse
Yah. I'm not sure as well where to put the "Kernel". Right now I am just trying the PDA file

Tried using just the PDA. I got this:
<ID:0/015> Added!!
<ID:0/015> Removed!!
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XWKF1_CL265340_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.bin
<ID:0/015> NAND Write Start!!
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I got a the Galaxy S II GT-19100G Prompt right now after I used just the kernel on the bootloader. I am not stuck anymore on Phone--!--PC.. Interesting!

florexus said:
I got a the Galaxy S II GT-19100G Prompt right now after I used just the kernel on the bootloader. I am not stuck anymore on Phone--!--PC.. Interesting!
Click to expand...
Click to collapse
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KERNEL_I9100XWKF1_CL265340_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> zImage
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/015> Removed!!

xwkf1 is not working.

Did you put kernel in Csc? Tar file should go to PDA and modem file to phone.
Don't put anything on pit
If you did it wrong, flash in Odin again

monchinglopez said:
Did you put kernel in Csc? Tar file should go to PDA and modem file to phone.
Don't put anything on pit
If you did it wrong, flash in Odin again
Click to expand...
Click to collapse
I put kernel in the bootloader. And the result is i was able to get to download mode
By the way. What tar file are you talking about? All of them are tar files...
If you could clarify what to use and where to put it that would be awesome!

[Q] How to root after the latest update ?

Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html

frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.

Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.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> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...

frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.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> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )

Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.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> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)

Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?

yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.

Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.

)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country

frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**

hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...

Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem

It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.

Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration

problem with A300f flash firmware

hi
i wanted to update my phone from 4.4.4 to 5.0.2 but odin stuck on aboot.mbn then i downloaded 4 files firmware include bl ap cp csc but odin said aboot,mbn fail and then i flashed just ap file but i saw an error on writing system.img and now my phone dosnt boot and auto goes to download mode.
please help
here odin log :
Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> A300FXXU1BOD5_A300FOXY1BOD5_A300FXXU1BOD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/037> Added!!
<ID:0/037> Odin engine v(ID:3.1005)..
<ID:0/037> File analysis..
<ID:0/037> SetupConnection..
<ID:0/037> Initialzation..
<ID:0/037> Get PIT for mapping..
<ID:0/037> Firmware update start..
<ID:0/037> SingleDownload.
<ID:0/037> aboot.mbn
<ID:0/037> NAND Write Start!!
<ID:0/037> FAIL! (Auth)
<ID:0/037>
<ID:0/037> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i have downloaded 10 different files but problem still doesnt solve. also i have tried recover phone with Kies but it doesnt know phone

you may have reactivation lock ticked under the security settings.

PlutoDelic said:
you may have reactivation lock ticked under the security settings.
Click to expand...
Click to collapse
now phone doesnt boot
can you do me favor ?

If it boot to download mode, try flashing a 4 file package stock rom. You can get it with SamFirm.
Sounds like a soft brick, but if the reactivation lock is on, you wont be able to flash anything through odin.

i have tried with 4 part firmware but that error apears.
i dont acces to disable reactivation lock . so what shoud i do now? do you have any idea?

try using the pit file as well, it's included on the CSC package of the 4 part files. Load it on the PIT tab.
If that wont make a difference, your eMMC (internal storage) is either locked or done.

Galaxy Prime Bricked?

So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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/004> 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/004> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?

jhonatann989 said:
So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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/004> 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/004> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?
Click to expand...
Click to collapse
Download odin from this thread:- https://forum.xda-developers.com/grand-prime/general/tut-how-to-install-xposed-framework-t3508071
And download stock recovery for your device model and add open odin add the stock recovery to pda and flash it.
Note: make sure u have samsung drivers installled and do not add pit file

Owen007 said:
Download odin from this thread:- https://forum.xda-developers.com/grand-prime/general/tut-how-to-install-xposed-framework-t3508071
And download stock recovery for your device model and add open odin add the stock recovery to pda and flash it.
Note: make sure u have samsung drivers installled and do not add pit file
Click to expand...
Click to collapse
Did it, but still have the problem that i described earlier. Odin3 from the thread that you suggested, gives me the above text:
<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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I didn't test with the pit file that i found for the 531F variation
->EDIT: tried to flash the pit file and it didn't work. It says Repartition Failed

jhonatann989 said:
So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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/004> 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/004> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?
Click to expand...
Click to collapse
odin only works with the correct version is on the device

tran nam hoang said:
odin only works with the correct version is on the device
Click to expand...
Click to collapse
i wrote this:
The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M
Click to expand...
Click to collapse
then i asked for this:
- is there a chance that some of you could helpme to find a correct pit file?
Click to expand...
Click to collapse
If you have a PIT partition for the SM-G531M i will be gratefull if you share it with me
PD: BTW I HAVE the Correct firmware, my problem is PIT partition as i can conclude

Help needed.

So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Anybody???
I'm sure you're tired of walking noobs through this crap, but I'm sure you can sympathize the idea of suddenly losing access to your smart phone. Does anyone have any ideas on what to try next? I've read for hours and tried dozens of tutorials and I'm just not getting anywhere. FRUSTRATING AS HELL!!! I can stop a heart attack or a tension pneumothorax in my sleep, but trying to program a damn smart phone correctly... you might as well tell me to try to fly.

ERDOC76 said:
So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I finally figured it out. Thanks for all your help!

:good: but what was your solution?
edit: I think you didn't get much attention because your title likely turned people off -- it's kind of petty to call attention to someone's background if it's not part of the discussion. I saw you had another post where you didn't do that, and got help, so :good:
chill,
Procrastinatron

What's with the title of your post? We don't need that BS on these forums.

ERDOC76 said:
So I tried to root using an old youtube tutorial
Click to expand...
Click to collapse
You'll be fine man go to sammobile look up your G930V in firmware. You can get your current or update to oreo (no root method for oreo yet) unzip
Make sure you have all samsung drivers and adb uninstall kies maybe reboot your computer and make sure your cable is mtp compatible not just a charging cable. Reboot into download mode flash the BL, AP, CP, and CSC .md5 files in their respective Odin slots. Let recovery do its thing first boot will take some time.
Rooting is even quicker and easier so if you're still confident in yourself look up the methods here on here xda. G930V, G930A, G930T, G930U and G930P pretty much use the same root methods as far as nougat goes.
this is probably the biggest thread all credit to those guys that developed it and shared the files, this is probably the best place to start before you discover safestrap and what mods you can actually do (dual speaker ect.). Rooting, like everything else in life is always at your own risk
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502