Database Users

[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?

[Q] Disabling Reactivation lock

Hello all,
Problem: my S5 SM-G900F has ''Reactivation Lock'' enabled.
ROM: XtreStoLite 2.2 (touchwiz based)
I tried to get into my recovery and it gave me Custom binary blocked by Reactivation Lock instead. It seems Reactivation Lock is enabled. This happened to me after (not directly) I had flashed XtreStoLite 2.2 ROM. The thing is that I don't remember enabling anything, and I can't find the option to disable it in this ROM either. Also I never made a Samsung account in order to enable this lock. And it looks like I need a Samsung account to disable it again. So how can I disable it if I don't have a Samsung account in the first place?
I tried to flash recovery via Odin, but that just failed. I also tried to do a factory reset from the settings menu but then settings app just crashed and nothing happens.
I really hope someone can help me... Thanks in advance!

Flash a stock Kitkat ROM with ODIN from sammobile dot com, instructions under the download
Log into all accounts you have, disable reactivation lock
--
Can a mod make these instructions a MASSIVE red sticky? The number of people not reading threads and asking the same question day after day is ridiculous

Flash a stock Kitkat ROM with ODIN from sammobile dot com, instructions under the download
Log into all accounts you have, disable reactivation lock
Click to expand...
Click to collapse
Thanks for your reply!
I had already flashed a lollipop version via the same way. But I see you say KitKat, and probably for a reason...
Now with the Stock Lollipop ROM which I flashed:
-In download mode I can see Reactivation Lock is ON.
-It shows a Samsung icon to add an account in account settings. But selecting it results in nothing.
-Factory reset doesn't work. Results in endless loop <next> <next>....
-In settings>security Reactivation Lock can't be disabled. It just turns itself on automatically.
I'm downloading a KitKat version now. Hope that solves the problem.

Lollipop doesn't work, needs to be KitKat

*Detection* said:
Lollipop doesn't work, needs to be KitKat
Click to expand...
Click to collapse
Downloading took forever (200kb/s)... But I've the file now. Tried to flash it via Odin. All great, but near the end it fails to complete...
I tried twice. This phone is from Germany, but I live in the Netherlands. I bought it with Lollipop on it, didn't need to update from KitKat first. Is there any problem in that when going to a KitKat firmware? The firmware I downloaded is one for the Netherlands, not Germany.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANH6_G900FPHN1ANH1_G900FXXU1ANG8_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
-edit-
Seems I need a PIT file or something (for re-partitioning phone). Will try finding one...

All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.

Disabling reactivation lock - another solution
Darkmond said:
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Click to expand...
Click to collapse
I encountered the same problem with the reactivation lock after flashing xtresolite (lollipop) onto my g900f. I followed the steps to download the stock KK rom, flash from Odin and reboot. At this point I got stuck on the boot screen (not boot-loop) indefinitely (until 2% battery). After flashing KK, removing battery and reinserting it I was then able to boot into the stock recovery. I did a factory reset and wiped the cache and rebooted. The phone now boots normally into stock KK rom and I was able to deactivate the reactivation lock using my samsung account. Hope this helps anyone with a similar issue.

please help me with my s6 g920a, I can't find any kitkat firmware.
/
Darkmond said:
All good now. Thanks for your help
For the ones that might have same problem as I had:
Download KitKat firmware and flash it using Odin. If you get an error (because downgrade from L to KK) get yourself the right .PIT file for re-partitioning your phone. I got mine from here : http://forum.xda-developers.com/showthread.php?t=2737448 and flasht it after the fail. Then did a factory reset via stock recovery and booted phone. On some point got the Samsung lock thing which wanted me to log in. Just made a Samsung account and logged in. Now it's all working fine and Reactivation Lock is disabled via the settings.
Click to expand...
Click to collapse

Another easy solution can be found here:
[Guide] Unlock FRP / Deactivate Reactivation lock, Root and recovery for Samsung

Please help me i tried rooting and now my phone won't work

I tried rooting my phone using Odin from this tutorial:
https:// theunlockr(dot)com/2016/02/04/root-samsung-galaxy-s6-edge-plus/
It failed and now my phone reads "Kernel is not seandroid enforcing" and will not enter recovery mode.
I tried installing the proper firmware but when I try using that it fails and my phone then reads "SW REV CHECK FAIL DEVICE 3 BINARY 2"
This is what Odin says:
<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> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I don't know what to do, and any help would be greatly appreciated!
Also, the firmware I used is G928TUVU2COI5_G928TTMB2COI5_TMB and my model is SM-G928T

Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477

kdogguk said:
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
Click to expand...
Click to collapse
I'm on the most updated software, that's entirely possible. I can get on download mode, I will try to use the link you gave me and give you an update, thank you very much

kdogguk said:
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
Click to expand...
Click to collapse
Okay so I tried it but since my phone doesn't turn on I cant put in the files from that link, I tried using oden and it failed again. On Odin it says Pass but my phone continues to say Kernel is Not seandroid enforcing, I've been at this for so long and I can't find a fix :'(

Where did you get your stock firmware from to flash with odin?
Is it a 3 file flash or a single large file which you place in the AP slot?
I find the 3 file ones are better as it contains the firmware, bootloader and correct files all for the same version/model.
Try sammobile, the download is slow if you don't have premium access to the download site.
You can also try the program kies or whatever the recovery program is these days, I remember with my note having exhausted all possibilities using it and it actually worked. It's slow but might bring your phone back to life.
Looks like the recovery program lies is now called smart switch...
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176

kdogguk said:
Where did you get your stock firmware from to flash with odin?
Is it a 3 file flash or a single large file which you place in the AP slot?
I find the 3 file ones are better as it contains the firmware, bootloader and correct files all for the same version/model.
Try sammobile, the download is slow if you don't have premium access to the download site.
You can also try the program kies or whatever the recovery program is these days, I remember with my note having exhausted all possibilities using it and it actually worked. It's slow but might bring your phone back to life.
Looks like the recovery program lies is now called smart switch...
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
Click to expand...
Click to collapse
It's a three file flash I believe, I've just been putting one huge file in the AP, I haven't heard of the three file thing, I've tried the Sammobile firmware stock too and it hasn't worked. It fails on Odin. Do you know anything else I could try?

You could try grabbing TWRP recovery and flashing that with odin. That could give you access to a recovery to wipe and factory wipe. You could grab a custom rom and use TWRP to install that.
If you could find the 3 file flash it might help because it will have the right bootloader/firmware/csc for your phone.
Just a quick thought... Have you tried running odin with administration rights in Windows? And is it the latest version of odin?
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
Found these links for you to have a look at...
http://forum.xda-developers.com/tmo...sources-tmobile-g928t-galaxy-s6-edge-t3204478
http://forum.xda-developers.com/tmo...rmware-g928t-complete-untouched-boh6-t3198387

kdogguk said:
You could try grabbing TWRP recovery and flashing that with odin. That could give you access to a recovery to wipe and factory wipe. You could grab a custom rom and use TWRP to install that.
If you could find the 3 file flash it might help because it will have the right bootloader/firmware/csc for your phone.
Just a quick thought... Have you tried running odin with administration rights in Windows? And is it the latest version of odin?
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
Found these links for you to have a look at...
http://forum.xda-developers.com/tmo...sources-tmobile-g928t-galaxy-s6-edge-t3204478
http://forum.xda-developers.com/tmo...rmware-g928t-complete-untouched-boh6-t3198387
Click to expand...
Click to collapse
Sorry this is really late, apparently nothing worked, I took it to the uBreakiFix and they apparently had to install the firmware by it's build number which took like a week cause I had to go through every single build number. But thank you very much for your help

There is No PIT Partition

Hey!
I kinda screwed up, horribly.
I initially had a Verizon S7 Edge, but I was on T-Mobile service so I decided to follow this guide: http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145 and it worked! Then I thought, maybe if I flash the T-Mobile firmware, it would work even better, and it did! Then recently I decided that I wanted to go back to unlocked firmware, so I tried flashing it again. Thats when everything went to ****. It failed, and said something about "sw rev check fail fused 3 binary 2", and so I tried again and it failed. I rebooted thinking that maybe the old os would be intact but it booted to recovery mode saying that it couldn't mount any of the partitions. So I tried to reflash the T-Mobile firmware again and now its giving an error about how there is no PIT partition. From googling online, I think I need to flash a .pit file or something. I could only find PIT files for the international unlocked s7 edge. Does anyone have the PIT files for the AT&T/Verizon/Unlocked S7 Edge (preferred, because I can then flash the U firmware), or even the T-Mobile PIT file?
Any help would be greatly appreciated.
Thanks.
EDIT: I rebooted the device and it took me to recovery and complained about not being able to mount /cache and /system. I fixed the /cache issue by using the "wipe cache partition" option, but now it is saying "dm-verity verification failed. E: failed to mount /system (Invalid argument)"

I tried flashing a PIT/ROM combo for tmobile that I found online but now im getting this error:
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Please help!
EDIT: It gave that same weird binary thing.

Pit file zipped on the original csc.zip... Unpack csc zip, and copy pit...

DenyDeBeyle said:
Pit file zipped on the original csc.zip... Unpack csc zip, and copy pit...
Click to expand...
Click to collapse
Thank you, but I just figured out how to solve the issue. I found the latest firmware from TMOBILE and flashed that. Apparently I had updated my phone so the bootloader was version 3 instead of version 2 or something and you can downgrade. Im not sure if thats the right explanation, but my phone works now, so thats good.
Thank you.

Download G935 U 4files firmware (qualcomm edition, no verison-tmobile-sprint-att bloatware).
My g935a phone is g935u firmware, and work perfectly.

DenyDeBeyle said:
Download G935 U 4files firmware (qualcomm edition, no verison-tmobile-sprint-att bloatware).
My g935a phone is g935u firmware, and work perfectly.
Click to expand...
Click to collapse
I have already tried that and failed. I think the TMOBILE bootloader is more updated or something and so you cant flash to a previous version of the bootloader. IDK, maybe someone can explain it better?

Nahtnam, do you solve that problem, just now I have exactly the same

emavas said:
Nahtnam, do you solve that problem, just now I have exactly the same
Click to expand...
Click to collapse
The issue was that I was I was on bootloader version 4, and I tried to flash a firmware with bootloader version 3. I ended up finding the firmware with bootloader version 4 and flashed that.

hi I messed up too I went to install a new rom but I had to flash a new twrp recovery and I flashed the wrong one and I cant boot in to recovery no more and then I tried to put the right twrp recovery back on there and it gave me a odin error {no pit partition} so I downloaded the sm-g935f pit file and tried to use the pit tab and got a new odin error {Complete(Write) operation failed} iv tried different usb ports 2.0 and 3.0 and tried different cables I need help someone please save me phone
---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------
hi I messed up too I went to install a new rom but I had to flash a new twrp recovery and I flashed the wrong one and I cant boot in to recovery no more and then I tried to put the right twrp recovery back on there and it gave me a odin error {no pit partition} so I downloaded the sm-g935f pit file and tried to use the pit tab and got a new odin error {Complete(Write) operation failed} iv tried different usb ports 2.0 and 3.0 and tried different cables I need help someone please save me phone

Samsung G935F (Soft Bricked & FRP Locked and Bootloader Locked)

Hello everyone,
I have a customer that managed to forget his account. He came to me to bypass the frp. He said he has the latest update of Nougat so I knew the only bypass I could posssibly use was probably the bluetooth headset one (if lucky). So I tried to revert the phone to an earlier Nougat version so I can use an easy bypass (hence I don't have any bluetooth headset). I've used Odin to flash one of the earliest Marshmallow versions for G935F (a vodafone, Uk one as the user said he bought the phone from there). Problem is Odin failed to flash the BL file and I've read somewhere on this forum a user said just uncheck that and I'll be fine. Well I've done that and the phone remained soft bricked (probably because the BL the phone still had was made for Nougat). Then I've downloaded a Nougat rom for the phone and the same problem (SW_RW verification for the BL file) so I bypassed the BL again and I've flashed the other files via Odin. All good, now the phone boots, installs the apps but it doesn't see the Sim anymore (I know that because the customer had a sim pin lock, wich the phone doesn't ask for anymore). Well, also the phone of course is still FRP locked but now I have two problems: It doesn't detect the Sim card anymore and it's still FRP locked. I am planning to flash the latest Oreo Rom as I am thinking that the bootloader will accept it and this way the phone will detect the sim again and at least I will be able to return it to my cutsomer in the same state as it was before.. but I am afraid I will not be able to bypass the FRP at all afterwards if I flash to the latest security patch. What should I do, is there any possiblity to fix both of my problems ? If yes can anyone here help me ?
EDIT:
First of all, the title is wrong - the phone ain't soft bricked anymore., it just doesn't detect the sim anymore and it's frp locked. And regarding to what I've wrote, I've also tried to flash like 3 Nougat versions for the G935F and same result everytime: BL check failed. Two of the roms were taken from threads from here, one of them had "untouched in its name" so I thought the bootloader will accept it but it didn't. Maybe the client thought he had Nougat on the phone when he had Oreo and maybe that's why the Bootloader won't accept to be flashed with any bootloader from Nougat roms. I must specify at least, I didn't try flashing the latest Nougat version yet. I can access download mode and recovery mode and I can turn on the phone but it won't let me pass the frp of course. I am waiting for some answers in here before trying to flash latest Nougat version and latest Oreo versionl.
Any help would be greatly apreciated, thank you very much!
Edit 2: Managed to flash the latest Nougat patch with succes (the Bootloader passed the verification, the Rom I flashed it's called: "G935FXXS2DRDI_Germany.zip".
Now the problem with the sim is solved, but I still have the FRP lock activated. If anyone knows how can I bypass it please help! Maybe I can dowgrade the phone somehow or anything else.
Edit 3: Planning to use a combination method shown in this video: youtube.com/watch?v=5v1oN4WFuqA
Edit 4: The combination ROM used in that tutorial won't get past the verification in Odin, wich results in a SW_RW flash fail. Trying a newer one from May, 2018 (COMBINATION_FA60_G935FXXU2ARA1).
Edit 5: This one failed as well..
=====================================================
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
===================================
EDIT 6: The second combination ROM actually worked! I forgot to switch to my other folder in odin so I thought it's not working. Now I am in the rom, on developer settings but I only see the usb debugging option. I can't see anything about OEM unlock. Could I directly flash the 6.0.1 Marshmallow now ? Hmm I will try exacly that!
Edit 7: Looks like the verification in Odin still fails if I try flashing the 6.0.1. I'm out of ideas.
EDIT 8: FInal Edit - I managed to unlock it by making an update and a downgrade from a specific x version to a specific y version. But.. I am afraid it is forbidden to give the exact details here so I guess that's it. SOLVED!

We don't allow discussion of FRP bypassing here because it could be used by thieves. The main purpose of FRP locks is to prevent that.
BrainwashedUser said:
Hello everyone,
I have a customer that managed to forget his account. He came to me to bypass the frp. He said he has the latest update of Nougat so I knew the only bypass I could posssibly use was probably the bluetooth headset one (if lucky). So I tried to revert the phone to an earlier Nougat version so I can use an easy bypass (hence I don't have any bluetooth headset). I've used Odin to flash one of the earliest Marshmallow versions for G935F (a vodafone, Uk one as the user said he bought the phone from there). Problem is Odin failed to flash the BL file and I've read somewhere on this forum a user said just uncheck that and I'll be fine. Well I've done that and the phone remained soft bricked (probably because the BL the phone still had was made for Nougat). Then I've downloaded a Nougat rom for the phone and the same problem (SW_RW verification for the BL file) so I bypassed the BL again and I've flashed the other files via Odin. All good, now the phone boots, installs the apps but it doesn't see the Sim anymore (I know that because the customer had a sim pin lock, wich the phone doesn't ask for anymore). Well, also the phone of course is still FRP locked but now I have two problems: It doesn't detect the Sim card anymore and it's still FRP locked. I am planning to flash the latest Oreo Rom as I am thinking that the bootloader will accept it and this way the phone will detect the sim again and at least I will be able to return it to my cutsomer in the same state as it was before.. but I am afraid I will not be able to bypass the FRP at all afterwards if I flash to the latest security patch. What should I do, is there any possiblity to fix both of my problems ? If yes can anyone here help me ?
EDIT:
First of all, the title is wrong - the phone ain't soft bricked anymore., it just doesn't detect the sim anymore and it's frp locked. And regarding to what I've wrote, I've also tried to flash like 3 Nougat versions for the G935F and same result everytime: BL check failed. Two of the roms were taken from threads from here, one of them had "untouched in its name" so I thought the bootloader will accept it but it didn't. Maybe the client thought he had Nougat on the phone when he had Oreo and maybe that's why the Bootloader won't accept to be flashed with any bootloader from Nougat roms. I must specify at least, I didn't try flashing the latest Nougat version yet. I can access download mode and recovery mode and I can turn on the phone but it won't let me pass the frp of course. I am waiting for some answers in here before trying to flash latest Nougat version and latest Oreo versionl.
Any help would be greatly apreciated, thank you very much!
Edit 2: Managed to flash the latest Nougat patch with succes (the Bootloader passed the verification, the Rom I flashed it's called: "G935FXXS2DRDI_Germany.zip".
Now the problem with the sim is solved, but I still have the FRP lock activated. If anyone knows how can I bypass it please help! Maybe I can dowgrade the phone somehow or anything else.
Edit 3: Planning to use a combination method shown in this video: youtube.com/watch?v=5v1oN4WFuqA
Edit 4: The combination ROM used in that tutorial won't get past the verification in Odin, wich results in a SW_RW flash fail. Trying a newer one from May, 2018 (COMBINATION_FA60_G935FXXU2ARA1).
Edit 5: This one failed as well..
=====================================================
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
===================================
EDIT 6: The second combination ROM actually worked! I forgot to switch to my other folder in odin so I thought it's not working. Now I am in the rom, on developer settings but I only see the usb debugging option. I can't see anything about OEM unlock. Could I directly flash the 6.0.1 Marshmallow now ? Hmm I will try exacly that!
Edit 7: Looks like the verification in Odin still fails if I try flashing the 6.0.1. I'm out of ideas.
Click to expand...
Click to collapse
Sent from my GT-I9300 using Tapatalk