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?

Need help recovering Samsung S5 SM-G900A

Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the screen of the phone it says:
UDC START
SYS REV CHECK FAIL : Refer 3 > Binary 1
SECURE CHECK FAIL : system
Click to expand...
Click to collapse
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.

To flash the firmware using Odin you need to put the phone in Download mode (Power + home + volume down) and not recovery mode. Select PDA/AP in Odin, select the firmware and then click start.
DigitalBeating said:
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
On the screen of the phone it says:
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
Click to expand...
Click to collapse

Yes, I already have done that and the only thing that writes successfully is the [CP] file. It fails to write to the NAND and does a FAIL! (Auth). Not sure what else I can do.

Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.

DigitalBeating said:
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
Click to expand...
Click to collapse
I am currently in the same boat. Please tell me you found a fix for this and if so, what was it? Any help is greatly appreciated.

@DigitalBeating and @Theamazingcorey
Here is an AT&T lollipop firmware.....
https://www.androidfilehost.com/?fid=24591000424940454
G900AUCU4COI5_ATT4COI5_v5.1.1_Repair_Firmware
I found it (by chance) on a Russian hosting site. They say it's a 'repair' firmware which means it is more than likely going to be more than one file (it'll probably be bootloader, modem and OS) So you'll have to load each file into it's respective Odin 'slot'.
If I understand how repair firmwares work, it should wipe and format the data partitions (instead of simply overwriting them) as it flashes. This will give the best chance of a successful flash.....
http://i.imgur.com/rVnFwJM.jpg

I cannot thank you enough, that seems to have fixed my problem. I though I was going to be stuck with a paperweight, lol.
Would you happen to know if there is a way to root the the AT&T S5 with 5.1.1?

Glad it worked fella.....
With regards to rooting, everything I've read on XDA indicates AT&T Lollipop can't be rooted....and the possibility of downgrading to achieve root is non existent.......
But there's a LOT if information on XDA, and I'll be the first to admit that I haven't read it all........
http://i.imgur.com/rVnFwJM.jpg

@Theamazingcorey just out of interest, can you confirm what files were inside the zip?
http://i.imgur.com/rVnFwJM.jpg

Thanks for the info. Sorry I was not able to get back to you sooner, I've been slammed these last couple of days. Have family coming into town this evening and between work and getting ready for their visit, I haven't had time to think straight, lol.

Samsung Galaxy s4 gt-i9505 crushed after firmware update. can i throw it away now?.

Hey.
Hopefully someone can help me.
Ive a Samsung Galaxy s4 GT-I9505
Android version is (well im confused now but i think..) 4.4.2
Well what happened:
I wanted to unroot my phone. i clicked on unroot in SuperSU and wanted to flash the original firmware.
Well then my phone got stuck in "firmware upgrade encountered an issue."
WHAT I TRIED:
1. try
Flash 4.4.2 via odin (3.07 & 3.10) but it said: FAIL
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
2. flash 5.0.1 but: FAIL
3. try
flash stock recovery and Kernel but also FAIL.
3. try
Wanted to enter the recovery mode on the phone but its just bringing up "firmware upgrade encountered an issue." again.
4. try
went into KIES, KIES3 and Smart Switch to recover like it said but i just get:
"GT-I9505 doesnt allow initialization" or something like that.
5. try
flashing the original PIT file but it also failed at re-partiti
SO:
i can enter download mode but cant enter recovery or start the phone normally.
Additional info in odin mode:
ODIN MODE
GT-I9505
Samsung Official
kernel: 0x0
warranty: 0x1
LSB: 0x30
write protection: enabled
burst mode: enabled
(at flashin pit file also
start [224,1440]
start [224,1440]
secure check fail: pit
Im not really into switchin the motherboard or whatever i found...
Please can someone help.
If info is needed i give them if i can just need to know how.
I try to reply to this in between 5-20 minutes
Because i really want to get my phone fixed..
Its needed for work and i dont have any replacement.
Ive teamviewer also if needed
Already to for the fast answers and the help. i kiss everyone if my phone gets secured somehow.
greetings.

I think there is official 5.0.1 firmware you could try flashing that.

To resolve the "Firmware encountered an issue" error, plug a ROM into the BL (bootloader) slot in Odin and flash. Just be certain the ROM is Android 4.4.2 or later.

EDIT: The Solution of Strephon Alkhalikoi that i should plug the 5.0.1 original rom into Bootloader in Odin worked Like a CHARM.
Phone went on again. Booted 5.0.1. Updated everything.
I leave you a big thanks. you secured my day.
Not sure about how i can close this.
or leave it open for people who have the same problem.
Again thanks alot for the fast answer and the help.
greetings.

CF-AUTO-ROOT Samsung A5 2016 SM-5100 (HONG KONG)

Please,I 'm looking for the file for root this version samsung A5 SM-5100 (HONG KONG) but I can not find it that nodody can help me I took days and can not find the damn file,thanks for everything

salsero63 said:
Please,I 'm looking for the file for root this version samsung A5 SM-5100 (HONG KONG) but I can not find it that nodody can help me I took days and can not find the damn file,thanks for everything
Click to expand...
Click to collapse
I built this for the Chinese SM-A5100, but it should be compatible if your device is Qualcomm MSM8939.
This is as yet untested so ensure you have your stock firmware just in case.
Flash with ODIN in the AP slot.
CF-Auto-Root-a5xltechn
.

Thanks ashyx but this file is not compatible whit my firware a5100zhu1apg1 5.1.1 is sctock help me please from spain

salsero63 said:
Thanks ashyx but this file is not compatible whit my firware a5100zhu1apg1 5.1.1 is sctock help me please from spain
Click to expand...
Click to collapse
Tell me what happens in detail I may be able to fix it.
Depending on what fails is dependent on how it's fixed.
Videos of the root process is good as let's me see exactly what the issue is.
Does it flash?
Does it start the root process?
Does it fail to mount partitions?

when start the root process stop and the message falil and saw press button power for reboot

salsero63 said:
when start the root process stop and the message falil and saw press button power for reboot
Click to expand...
Click to collapse
Partitions mounting failure?

Same problem here, the root proces fails. But for a moment, before it fails root proces, there is a message on the phone display (while in download mode), that the phone is locked (I think because of a locked bootloader, but maybe I'm wrong).
My phone is Samsung Galaxy A5 SM-A5100 (Qualcomm MSM8939, Hong Kong ver).

dirtyprogg said:
Same problem here, the root proces fails. But for a moment, before it fails root proces, there is a message on the phone display (while in download mode), that the phone is locked (I think because of a locked bootloader, but maybe I'm wrong).
My phone is Samsung Galaxy A5 SM-A5100 (Qualcomm MSM8939, Hong Kong ver).
Click to expand...
Click to collapse
You need to unlock it with crom service apk first.
Go to Samsung store and download it.

ashyx said:
You need to unlock it with crom service apk first.
Go to Samsung store and download it.
Click to expand...
Click to collapse
I downloaded the crom service app, and unlocked my phone (thanks very much for that )
But, again I was not able to root the phone, this is the message from the odin (if this can help):
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> cache.img.ext4
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

dirtyprogg said:
I downloaded the crom service app, and unlocked my phone (thanks very much for that )
But, again I was not able to root the phone, this is the message from the odin (if this can help):
Added!!
Odin engine v(ID:3.1101)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
cache.img.ext4
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Ah right odin fails to flash the cache.img.
Nobody mentioned that.
Have you enabled OEM unlock in developer settings as its says 'auth' meaning unauthorized?

ashyx said:
Ah right odin fails to flash the cache.img.
Nobody mentioned that.
Have you enabled OEM unlock in developer settings as its says 'auth' meaning unauthorized?
Click to expand...
Click to collapse
Yes, I did that, and USB debugging also.
---------- Post added at 02:27 PM ---------- Previous post was at 02:19 PM ----------
dirtyprogg said:
Yes, I did that, and USB debugging also.
Click to expand...
Click to collapse
Update, I tried root process couple of times, I also changed all USB ports on my laptop. Finally I downloaded the older version of ODIN (ver 3.10), and I managed (with your help offkors) to root my phone. 1000 thanks for your root file.

dirtyprogg said:
Yes, I did that, and USB debugging also.
---------- Post added at 02:27 PM ---------- Previous post was at 02:19 PM ----------
Update, I tried root process couple of times, I also changed all USB ports on my laptop. Finally I downloaded the older version of ODIN (ver 3.10), and I managed (with your help offkors) to root my phone. 1000 thanks for your root file.
Click to expand...
Click to collapse
So you can confirm everything works OK with ODIN 3.10?
Which version of ODIN did not work?

ashyx said:
So you can confirm everything works OK with ODIN 3.10?
Which version of ODIN did not work?
Click to expand...
Click to collapse
Yes, so far, everything works just fine.
Just to mention, after the root was completed, the phone "bootlooped" for 3 or 4 times, before it started up android OS (maybe that's normal, I don't know).
I'm not shure if the problem was different version of ODIN or the USB port on my laptop, but first couple of times I tried this version "Odin engine v(ID:3.1101)", the last time, when root process was successful I was using "Odin3_v3.10.6".

salsero63 said:
when start the root process stop and the message falil and saw press button power for reboot
Click to expand...
Click to collapse
See post #13. Confirmed working.

Works for me too. ( I used Odin v3.10.6. )
Note : Because I removed the "auto-reboot" option, when the flash finished, I had to press Vol + , Vol - , home btn , power btn to reboot, so the rooting process started, and finally finished after 3 reboots.
BIG thanks ashyx ! Great job
My Phone :
Galaxy A5 (2016) - SM-A5100 (Hong-Kong) - A5100ZHU1APG1

ashyx said:
So you can confirm everything works OK with ODIN 3.10?
Which version of ODIN did not work?
Click to expand...
Click to collapse
Please ashy again you can send link the cf-auto root please my phone is crom servive:lock you are is the truth,and nowI am installing the firmware because the phone is blocked frp lock thanks for everything and forgive the inconvenience

Andorid a5 sm5000
ashyx said:
Ah right odin fails to flash the cache.img.
Nobody mentioned that.
Have you enabled OEM unlock in developer settings as its says 'auth' meaning unauthorized?
Click to expand...
Click to collapse
What i have to do if i'm can't acces to enable OEM unlock in my phone because i forgot my email..? My phone already reset..
Can i root using the odin...?
Thanks,

[Q] Cannot root SM-N910W8 (Canada) , 6.01 - Problems, already attempted ODIN

Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!

WarDerp said:
Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!
Click to expand...
Click to collapse
DISCLAIMER-_-Try on your own risk.
This is a universal method if you follow all steps correctly you will have permanent root and also custom recovery for flashing roms,zip files,backup roms etc.
1, download TWRP recovery img.tar.
2,download supersu.zip
3,open odin go to options and "uncheck" autoreboot.
4,choose AP tab in odin and upload TWRP recovery.
5,go to device download mode and connect to pc via usb cable.
6,HIT START in odin once odin shows pass remove battery from device.(DO NOT REBOOT YOUR DEVICE)
7,insert battery again and boot into TWRP recovery by pressing (volume up+home+power button)
8,go to install and flash supersu.zip and reboot.
Your device may reboot twice so dont worry its normal
Enjoy root.
TWRP RECOVERY LINK
https://dl.twrp.me/trltecan/twrp-3.0.2-0-trltecan.img.tar.html
SUPERSU.ZIP LATEST
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Thanks for the help! I tried that though and now it's just hanging at the Downloading screen again. Going to give it another five minutes but I really hope I'm not ruining it.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
Click to expand...
Click to collapse
EDIT: Nothing's happened. Trying with latest RV of ODIN
Tried with the latest version of ODIN. Nothing

can the w8 be rooted?

Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.

HappyPlato said:
Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.
Click to expand...
Click to collapse
Know any way to revive via sd card? I hear it's possible.
Sent from my Samsung SM-N900T using XDA Labs