Database Users

[Q] [HELP] - Undoing MH8 update

So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...

OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!

Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.

No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4

Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.

Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4

In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.

jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4

shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?

Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.

Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4

Note 3 is "not supported" by Kies 3

EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.

If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005

ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.

Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?

bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.

Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).

Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.

Possible not a genuine Note 3?

This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..

Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.

Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.

Flashed Rom zip. Note 3 back to health.

shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2

shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked

R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.

If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.

Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?

I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?

I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...

[Q] Odin FAIL - N910U / From Hong Kong 4.4.4 to Taiwan 5.0.1 ROM

Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?

gokhan04uk said:
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
Click to expand...
Click to collapse
I have identical problem. Same device, same stock firmware. Trying to update to BOD4

Dancing around:
I've installed last TWRP (https://twrp.me/devices/samsunggalaxynote4exynos.html) from Odin after multiple failed attempts with N910UXXU1BOD4
Device booted normally (long boot with "updating applications")
TA-DA!
it booted to 5.0.1
It's creepy magic, but it works.
BTW, sammobile has newer version (N910UXXU1BOE3_N910UZZT1BOE3_BRI.zip)

I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system

stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"

gokhan04uk said:
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
Click to expand...
Click to collapse
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox

I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse

stari4ek said:
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
Click to expand...
Click to collapse
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.

a_ballads said:
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
Click to expand...
Click to collapse
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
gokhan04uk said:
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
Click to expand...
Click to collapse
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk

stari4ek said:
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
Click to expand...
Click to collapse
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..

gokhan04uk said:
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
Click to expand...
Click to collapse
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)

stari4ek said:
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
Click to expand...
Click to collapse
Ok, Well if i do it the way you done it, will i get future ota updates or not ? i dont mind voiding warranty because the device is from hong kong, even if something goes wrong it will be a headache to send it back there and wait for it to come back. If I can get future updates wirelessly then i dont mind rooting it.

Nope. It rejects to check OTA. Manual update via Odin is still an option.
Probably, if flash original recovery and reset device, so it switches to new CSC - OTA will work. Probably.

@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered

Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
This sounds interesting, can you please expand on the inductions as I am I little confused about when to flash hidden.img.
Thanks[emoji1]

Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else

gokhan04uk said:
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
Click to expand...
Click to collapse
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user

Salim.Keady said:
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Click to expand...
Click to collapse
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?

gokhan04uk said:
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
Click to expand...
Click to collapse
Yes

How do you even flash the hidden.img,ext4 files through odin?

Galaxy S5 Unrooting (Odin Passes but still have my data WTF?!)

My Galaxy s5 Will not return to stock after Odin 3.10.6 passes.
Sorry Guys I will have to keep this short. My Galaxy S5 (model number irrelvant) will not return to stock. Prior it had a custom 5.0 firmware and worked perfectly, except whenver headphones were plugin it would turn itself off. I decied to go back to stock firmware using Odin 3.10 and firmware 5.0 based on my model number.
Odin passes with green light. But I STILL HAVE MY DATA WTF?! Music and photos are still there.
Please help me reset my phone back to stock
Recap:
Model : G900T (irrelvant for my problem, I know what firmware to download)
Problem: Soft-Brick - sometimes loads rom other times black screen and rom is in the background. All data is still there, and phone does not ask you to rename phone, login to google, etc... You know the first bookup screen after reset of Rom.
Tried: Odin 3.09 and 3.10 (default settings) Firmware 4.4.2 and 5.0 multiple times.
WTF?! is going on. I cannot for the life of me understand this.
Be my :angel: and help me out with this problem

You can go down one of two routes.....
1) go to settings >> backup & reset >> factory reset......
As far as i know this just destroys the file paths to your data.....it's still on the device, but not accessible with a file manager.....The possibility exists that it *could* be retrieved by specialist software.
2) odin flash a pit file and a firmware.
The pit file will erase and format and rebuild the data partitions on your device leaving absolutely no data behind including the firmware.....hence the need to flash the firmware again.....
If you choose option 2, make sure you are flashing the CORRECT pit file for your device variant......flashing the wrong pit will turn your phone into an unrecoverable paperweight
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

Help finding pit file
keithross39 said:
You can go down one of two routes.....
1) go to settings >> backup & reset >> factory reset......
As far as i know this just destroys the file paths to your data.....it's still on the device, but not accessible with a file manager.....The possibility exists that it *could* be retrieved by specialist software.
2) odin flash a pit file and a firmware.
The pit file will erase and format and rebuild the data partitions on your device leaving absolutely no data behind including the firmware.....hence the need to flash the firmware again.....
If you choose option 2, make sure you are flashing the CORRECT pit file for your device variant......flashing the wrong pit will turn your phone into an unrecoverable paperweight
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I never even tried to do it with a pit file. I will be googling it now and will report to you if it works out. In the meantime if anyone could direct me to the right way for the correct pit file for Android 5.0 G900t 16GB. I will edit as soon as I find it and it works out.
Crucial I get the correct Pit file, so I will not leave it up to my judgement, I really need the help here guys.
Found these pit files
http://forum.xda-developers.com/showthread.php?t=2737448
I am guessing the G900T_pit_16GB is for me, but I need confirmation

Provided that you have the 'T' variant and provided that it is a 16gb model, you should be good to go.....
Though I would check in that thread to find out if they're suitable for use with odin.....I always thought that odin packages had to have a .tar extension.....and none of those pit files do....i'm not sure.....
sorry fella.....
http://i.imgur.com/rVnFwJM.jpg

Flashing a stock ROM with ODIN will NOT wipe user data
To wipe user data, factory reset your phone from recovery (Volume up & Home & Power from a powered off state)
If you still want a more thorough wipe:
Flash this PIT file at the same time as your preferred stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2752477&d=1400519587
Extract the PIT file down to "SM-G900T_pit.pit" and add to ODIN PIT section
They have to be flashed simultaneously, PIT in PIT section, and ROM in AP/PDA section
Ensure ODIN is run as Admin
--
Let us know how that goes, any more issues and we'll try something else
TIP: S5 model is always important when troubleshooting, there are different methods for different models

Thanks *Detection* always good to get confirmation from experienced Odin users......
Cheers mate....
http://i.imgur.com/rVnFwJM.jpg

RE-Partition Failure
Odin is not re-partitioning my phone for some reason. The phone says secure check failed for the pit. I tried both 3.10.7 and 3.09 both give me the same error.
I was able to factory reset my phone through recovery but after the samsung logo it goes black often. I have to keep removing the battery and resetting it to finally get it to load normally. After couple of hours it goes black randomly when the phone is locked.
More Info
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ODIN MODE
PRODUCT NAME: SM-G900T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0x1 (2)
QUALCOM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
SECURE CHECK FAIL : PIT
Click to expand...
Click to collapse

Fixed Re-Partition Error
*Detection* said:
Flashing a stock ROM with ODIN will NOT wipe user data
To wipe user data, factory reset your phone from recovery (Volume up & Home & Power from a powered off state)
If you still want a more thorough wipe:
Flash this PIT file at the same time as your preferred stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2752477&d=1400519587
Extract the PIT file down to "SM-G900T_pit.pit" and add to ODIN PIT section
They have to be flashed simultaneously, PIT in PIT section, and ROM in AP/PDA section
Ensure ODIN is run as Admin
--
Let us know how that goes, any more issues and we'll try something else
TIP: S5 model is always important when troubleshooting, there are different methods for different models
Click to expand...
Click to collapse
OK I had to hex edit all the extra 00 00 00 00 from the end of the file you gave me to finally be able to flash. But I still have the same problem. As you can see below Odin flashed the following correctly: Re-partition.pit, AP, Bootloader, CP (Modem)
The only file I could not find is CSC file for my firmware (G900TTMB1DOB1).
More info:
Kernel Version 3.4.0-4033351
Build Number: LRX21T.G900TUVU1DOB1
SE For Andriod Device: SEPF_GM-G900T_5.0_0027
At this point I think the internal memory is physically damaged... But I find it weird that at times it just works for hours.
Any ideas anyone?

I cannot resolve brick...

I'm stucked into booting logo "Samsung" and i've only access to the download mode, where i tried everything i could find online: reinstall recovery, flash stock rom, and so on. From what i've find i suppose there is a problem about partitions so i even tried to flash .pit file, but Odin gets stucked at "SetupConnection" or "Initialzation" proccess. It takes forever, even for the recovery. I tried the emergency restore from Smart Switch but it cannot recognize my phone...
At the moment im writing (im trying another time to flash twrp), after 15 mins of initialzation now it's stucked on "Get PIT for mapping"...
Thanks in advace for any help.

Tick nand erase in odin and try again.

UsmaniMustafa said:
Tick nand erase in odin and try again.
Click to expand...
Click to collapse
I tried that already... I can try one more time but... But i'm hopeless to be honest. What should i flash while i tick nand erase?

Nekrux said:
I tried that already... I can try one more time but... But i'm hopeless to be honest. What should i flash while i tick nand erase?
Click to expand...
Click to collapse
Don't be hopeless. Bricking a phone tbh is not that easy.
Just find the latest firmware for your model on sammobile and then place the files in there respective slots. In the option check nand erase and re partition and flash. Hope this helps. https://forum.xda-developers.com/s7-edge/help/help-unbrick-s7edge-sm935w8-please-t3927240
This is a thread with someone having a similar problem.
Also try changing the cable your using and making sure on the latest odin or version 3.1. Also try different usb ports on your laptop.

UsmaniMustafa said:
Don't be hopeless. Bricking a phone tbh is not that easy.
Just find the latest firmware for your model on sammobile and then place the files in there respective slots. In the option check nand erase and re partition and flash. Hope this helps. https://forum.xda-developers.com/s7-edge/help/help-unbrick-s7edge-sm935w8-please-t3927240
This is a thread with someone having a similar problem.
Also try changing the cable your using and making sure on the latest odin or version 3.1. Also try different usb ports on your laptop.
Click to expand...
Click to collapse
This is the log...
Code:
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<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..
<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/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3993 M
<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> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)

Nekrux said:
This is the log...
Click to expand...
Click to collapse
Can't open the file. Maybe the download is corrupted. Re download and also try without pit file. One more thing you can try is just put AP in odin and leave everything else blank and try.
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Any error on the phone screen?

Your firmware has to be an exact match otherwise it won't work, my advice is to download Sam firm to find out the exact match of your firmware, download the files suggested by sam firm and flash with the latest Odin.

UsmaniMustafa said:
Can't open the file. Maybe the download is corrupted. Re download and also try without pit file. One more thing you can try is just put AP in odin and leave everything else blank and try.
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Any error on the phone screen?
Click to expand...
Click to collapse
Nope, on screen i have only classical logo and this on the left upper corner:
Odin mode
Download speed: fast
Product name: SM-G935F
Current binary: Custom
System status: Official
Fap lock: Off
Secure download: Enabled
Warranty void: 1 (0x030c)
Rp Swrev: B:5 K:3 S:4
Shauqeen said:
Your firmware has to be an exact match otherwise it won't work, my advice is to download Sam firm to find out the exact match of your firmware, download the files suggested by sam firm and flash with the latest Odin.
Click to expand...
Click to collapse
I'm sure enough i'm flashin last and exact firmware. My model is S7 Edge Italy no brand. Thats the file i've downloaded: G935FXXS5ESF6_G935FITV5ESF6_ITV.zip.

UsmaniMustafa said:
Can't open the file. Maybe the download is corrupted. Re download and also try without pit file. One more thing you can try is just put AP in odin and leave everything else blank and try.
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Any error on the phone screen?
Click to expand...
Click to collapse
I tried by setting only AP with nand erase and re-partition, after re-downloading firmware from SamMobile. No pit file at all [as well last time] and i get that error again:
Code:
<ID:0/003> 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/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3921 M
<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> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Now i'm trying to download the firmware also from Updato
Edit:
Updato keeps aborting the firmware download. I used SamFirm but files inside are the same of the Sammobile archive.
Anyway while trying to flash PIT file yesterday or two days ago i got this error tho:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 43 M
<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> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched a bit online but nothing works... I gonna buy new phone i guess. I'm sad cause i wanted a Pixel or a Xiaomi but i have to get a Samsung since my things are all backed up on their cloud.
A little vent: i'm not that expert at modding or coding or whatever, but i always liked to mod my old Nexus 5. It served me for years and i never had hard things to do, or dangerous situations or critical bricks/unsolvable problems. Now first time i put hands on my S7 Edge [i waited warranty's end]... This...

Nekrux said:
I tried by setting only AP with nand erase and re-partition, after re-downloading firmware from SamMobile. No pit file at all [as well last time] and i get that error again:
Now i'm trying to download the firmware also from Updato
Edit:
Updato keeps aborting the firmware download. I used SamFirm but files inside are the same of the Sammobile archive.
Anyway while trying to flash PIT file yesterday or two days ago i got this error tho:
I've searched a bit online but nothing works... I gonna buy new phone i guess. I'm sad cause i wanted a Pixel or a Xiaomi but i have to get a Samsung since my things are all backed up on their cloud.
A little vent: i'm not that expert at modding or coding or whatever, but i always liked to mod my old Nexus 5. It served me for years and i never had hard things to do, or dangerous situations or critical bricks/unsolvable problems. Now first time i put hands on my S7 Edge [i waited warranty's end]... This...
Click to expand...
Click to collapse
Before trying all this I'm assuming you enabled OEM Unlock in developer settings, if so try to flash twrp. Maybe that will give you access and from there ypu can flash a custom rom

UsmaniMustafa said:
Before trying all this I'm assuming you enabled OEM Unlock in developer settings, if so try to flash twrp. Maybe that will give you access and from there ypu can flash a custom rom
Click to expand...
Click to collapse
Twrp is flashed in recovery.img partition. I am afraid he will receive same error because Odin would try to open PIT file for recovery flashing. If there isn't any user error then the phone can only be fixed by AnyWay box.

Nisar Ahmed Nisar said:
Twrp is flashed in recovery.img partition. I am afraid he will receive same error because Odin would try to open PIT file for recovery flashing. If there isn't any user error then the phone can only be fixed by AnyWay box.
Click to expand...
Click to collapse
What is user error? I assume it's kinda errors should appear on phone screen like UsmaniMustafa asked me before. Also i suppose AnyWay Box is a tool that only Samsung customers service or some tricky people have.

Nekrux said:
I tried by setting only AP with nand erase and re-partition, after re-downloading firmware from SamMobile. No pit file at all [as well last time] and i get that error again:
Now i'm trying to download the firmware also from Updato
Edit:
Updato keeps aborting the firmware download. I used SamFirm but files inside are the same of the Sammobile archive.
Anyway while trying to flash PIT file yesterday or two days ago i got this error tho:
I've searched a bit online but nothing works... I gonna buy new phone i guess. I'm sad cause i wanted a Pixel or a Xiaomi but i have to get a Samsung since my things are all backed up on their cloud.
A little vent: i'm not that expert at modding or coding or whatever, but i always liked to mod my old Nexus 5. It served me for years and i never had hard things to do, or dangerous situations or critical bricks/unsolvable problems. Now first time i put hands on my S7 Edge [i waited warranty's end]... This...
Click to expand...
Click to collapse
A few things to check, Odin version and binary numbers of firmware you're trying to flash vs your current binary number. If trying to flash oreo software ensure you are using Odin 3.13.1.

Aimless Rambler said:
A few things to check, Odin version and binary numbers of firmware you're trying to flash vs your current binary number. If trying to flash oreo software ensure you are using Odin 3.13.1.
Click to expand...
Click to collapse
I started with Odin 3.13.1, later i even tried 3.12.7 since i've read something somewhere... I don't remember. How do i get my current binary number? I cannot access to anything but download mode...

Nekrux said:
I started with Odin 3.13.1, later i even tried 3.12.7 since i've read something somewhere... I don't remember. How do i get my current binary number? I cannot access to anything but download mode...
Click to expand...
Click to collapse
In a previous post you noted that you have this "Rp Swrev: B:5 K:3 S:4" in download mode. The B:5 = Binary 5, you would need to match the binary number against firmware you intend to flash in Odin. For example, for the following firmware G935XXXX9CSC2, counting from right to left the 5th number would be the binary number. In the example it is '9'. In your case you would need Binary 5 firmware. If you have downloaded the correct binary firmware and it has still failed to flash you may need to try a different version of Odin (if firmware is Android Oreo, Odin 3.13.1 is needed due to lz4 format). You may need to flash incrementally, please see the link below and follow suggestion as posted in my italicized text below.
In Odin v3.13 U must add all 4 files (BL,AP,CP,CSC)
And in PIT tab you must add pit file
In options you apply Re-Partition, Auto Reboot, F. Reset Time
Click Start
https://www.sammobile.com/forum/threads/40890-Odin-error-(can-t-open-the-specified-file-)-line-1892
Further suggestions:
If flash fails add USERDATA Home CSC in slot
If flash fail ... add all except CP
Forgot to mention the obvious ... make sure you are using OEM USB cable.

Redownload the firmware files, I think they are corrupt.
Redowmload odin 3.13.1 (only this version works with oreo firmwares)
Redownload italy's bootloader 5 firmware.
Don't use pit file.
Don't check repartition.
Don't check nand erase.
(All these options are useless and won't do any good (if not bad) on s7 edge)
To explain : pit file is already in csc md5, no need to extract and do pit mapping again..
Nand erase was a dangerous option only used for older samsung phones to repair hard bricked phones in samsung service centers. It erases all the nv data like imei / serial no. and even the download mode (accordingly on old samsung phones). This option is obsolete on latest samsung phones which are hard coded to not delete nv data and download mode etc so this option does nothing in new phones, also internal memory gets erased when csc.md5 is flashed !
Repartition option is useless too, as csc.md5 file repartitions automatically.
(Repartition option's only use is that when people want to upgrade from a previous android version WITHOUT losing data, they can select HOME_CSC.md5 while flashing the newer firmware and repartition box checked, I don't know if it works correctly..)
Just select auto reboot and F.reset timer in odin options.
If still it throws some error then phone's internal memory got some hardware problem.
Sent from my S7 Edge using XDA Labs

shah22 said:
To explain : pit file is already in csc md5, no need to extract and do pit mapping again..
Nand erase was a dangerous option only used for older samsung phones to repair hard bricked phones in samsung service centers. It erases all the nv data like imei / serial no. and even the download mode (accordingly on old samsung phones). This option is obsolete on latest samsung phones which are hard coded to not delete nv data and download mode etc so this option does nothing in new phones, also internal memory gets erased when csc.md5 is flashed !
Repartition option is useless too, as csc.md5 file repartitions automatically.
(Repartition option's only use is that when people want to upgrade from a previous android version WITHOUT using data, they can select HOME_CSC.md5 while flashing the newer firmware and repartition box checked, I don't know if it works correctly..)
Just select auto reboot and F.reset timer in odin options.
If still it throws some error then phone's internal memory got some hardware problem.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Good information, if OP isn't thanking you I will. I'm an old time Samsung fanboy but there's been a slight break in time for me and things seem to change.

Stuck in Samsung Logo Screen. Recovery Mode not loading. FRP Lock on
Suddenly My phone stopped working. Stuck in samsung logo screen . cannot enter recovery mode. I have only option is to use odin to install software. have downloaded files from sammobile site. Always stuck in initialisation for 30 min and then proceed and fails at re partition operation failed. tried to install twrp . download was halfway and stopped because of FRP Lock ON. How to proceed .. Pls help me..
---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------
Aimless Rambler said:
Good information, if OP isn't thanking you I will. I'm an old time Samsung fanboy but there's been a slight break in time for me and things seem to change.
Click to expand...
Click to collapse
Suddenly My phone stopped working. Stuck in samsung logo screen . cannot enter recovery mode. I have only option is to use odin to install software. have downloaded files from sammobile site. Always stuck in initialisation for 30 min and then proceed and fails at re partition operation failed. tried to install twrp . download was halfway and stopped because of FRP Lock ON. How to proceed .. Pls help me..

Use 7zip to extract the CSC file from the firmware you downloaded from sammobile. After extraction you'll find the PIT file in the folder.
Start Odin 3.14
Go to options tab and enable re-partition and nand erase
Go to pit tab
Click on pit and select the pit file you extracted from the firmware
Now preload the BL, AP, CP and CSC md5 files
Click start and wait
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
And for removing FRP lock the easiest way of doing this is by using a tool named FRP HiJacker by Hagard