Database Users

[Q] How to root after the latest update ?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Soft Bricked S4 Checked all other threads

Hey guys this is my first post here and I am in need of some help. I have rooted several phones in the past with no trouble before my galaxy s4. I was trying to downgrade my s4 so I could root but managed to soft brick my phone in the process. Trying to turn on my phone I encounter and error saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I have tried various methods I have found on the forums. Trying to recover firmware in Kies I get an error saying "Firmware Update encountered an unexpected error". Whenever I try to flash anything in odin I get an error.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't really know what else I can try. My goal is to try to get back to stock.

Are you on mdb firmware? I'm guessing not. You need to flash the same firmware you were on in Odin. If you've taken any ota updates you're on something newer than mdb. There are Odin tar files in the general forum, look for those
Sent from my Nexus 5 using XDA Free mobile app

DrRodion said:
Hey guys this is my first post here and I am in need of some help. I have rooted several phones in the past with no trouble before my galaxy s4. I was trying to downgrade my s4 so I could root but managed to soft brick my phone in the process. Trying to turn on my phone I encounter and error saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I have tried various methods I have found on the forums. Trying to recover firmware in Kies I get an error saying "Firmware Update encountered an unexpected error". Whenever I try to flash anything in odin I get an error.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't really know what else I can try. My goal is to try to get back to stock.
Click to expand...
Click to collapse
As jd said, you need to flash the firmware you were on before. MDL and MF3 are other 4.2.2 firmwares, MK2 is the 4.3 firmware, and NB1 is the 4.4.2 firmware. Unless you've had your phone since around launch and never taken an update, you're probably at least on MF3.

going through the same thing
DeadlySin9 said:
As jd said, you need to flash the firmware you were on before. MDL and MF3 are other 4.2.2 firmwares, MK2 is the 4.3 firmware, and NB1 is the 4.4.2 firmware. Unless you've had your phone since around launch and never taken an update, you're probably at least on MF3.
Click to expand...
Click to collapse
although i am on "firmware upgrade encountered an issue screen". i was on nb1 build or somethign like that and mk2 build. i can flash a thing on odin. already tried kies firmware recovery thing cant seem to get that to work

Vega said:
although i am on "firmware upgrade encountered an issue screen". i was on nb1 build or somethign like that and mk2 build. i can flash a thing on odin. already tried kies firmware recovery thing cant seem to get that to work
Click to expand...
Click to collapse
Kies doesn't work for us, you'll need to use the NB1 full ODIN files in the general section.
Sent from my SGH-I337 running BlackBox 3.0

DeadlySin9 said:
Kies doesn't work for us, you'll need to use the NB1 full ODIN files in the general section.
Sent from my SGH-I337 running BlackBox 3.0
Click to expand...
Click to collapse
although i have noticed i have to downgrade to mk2 in a some threads.??? can i just get a stock nb1( 4.4.2) firmware and flash it though odin?

Vega said:
although i have noticed i have to downgrade to mk2 in a some threads.??? can i just get a stock nb1( 4.4.2) firmware and flash it though odin?
Click to expand...
Click to collapse
That's what I said, get the NB1 files and flash. You only have to downgrade to root.
Sent from my SGH-I337 running BlackBox 3.0

DeadlySin9 said:
That's what I said, get the NB1 files and flash. You only have to downgrade to root.
Sent from my SGH-I337 running BlackBox 3.0
Click to expand...
Click to collapse
THANKS SO MUCH . was afffriaid to go to kk since i am new to the gs4 and this whole sfe strap and knox buuisness. up and running . thanks again

[Q] N9005 Dubai Version bricked during update via Odin

Hi Everyone!
Can anyone helpe me with following trouble? I have a SM-9005 Dubai version.
I tried to flash lolipop 5.0 rom to my device via odin. but when installing system it said fails, even if i tried that several times the result is same. I used Odin 3.09 and then tried V1.85 after reading some suggestions for another guy in similiar situation. But unfortunately didn't help my case. on the device screen i see 3 lines of red messages saying :
UDC start
Volume size is too big 4620288<4718592
ODIN: Invalid ext4 image
and Odin messages:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know what to do. Please help.
BR
FIRAT

is it locked to carrier?

When it fails on NAND write that shouldn't brick your phone because nothing on the device has been written by Odin. Is your device still working or are you just wondering how to flash Lollipop?

fuel3100 said:
is it locked to carrier?
Click to expand...
Click to collapse
Hi, no, It was sim free. Any sim could use.

speedyjay said:
When it fails on NAND write that shouldn't brick your phone because nothing on the device has been written by Odin. Is your device still working or are you just wondering how to flash Lollipop?
Click to expand...
Click to collapse
But when i switch on the device i always use the same screen. I can't do anything. Recover mode doesn't work too.
Well, i would like to flasg lolipop but sure my priority is to save the phone first. Then i can think about rom version.
So, what do you think about it ?

Canadian sm-g920w8 firmware available for download.

Sammobile just added Telus and bell sm-g920w8 firmware on their site. Anyone know if this is good to go for Rogers or Fido S6?
http://www.sammobile.com/firmwares/database/SM-G920W8/
Edit: You can get the firmware directly from samsung using Smart Switch

neotekz said:
Sammobile just added Telus and bell sm-g920w8 firmware on their site. Anyone know if this is good to go for Rogers or Fido S6?
http://www.sammobile.com/firmwares/database/SM-G920W8/
Edit: You can get the firmware directly from samsung using Smart Switch
Click to expand...
Click to collapse
How do you get the firmware from smart switch?

mrapp said:
How do you get the firmware from smart switch?
Click to expand...
Click to collapse
In the menu on the top right side there is an option for emergency recovery.

Does anyone notice that they have an older version of Bell's firmware than what ships with their S6? They posted OCC and mine shipped with OCG.

MrKhozam said:
Does anyone notice that they have an older version of Bell's firmware than what ships with their S6? They posted OCC and mine shipped with OCG.
Click to expand...
Click to collapse
yea mine shows OCG as well.. this is confusing.
I am not sure which one I need to install OCC? or OCG?
Is OCC is older version of OCG?

Guys they show the build dates of the firmware, that with knowing your ABC's suggests OCG is newer

redpotatojae said:
yea mine shows OCG as well.. this is confusing.
I am not sure which one I need to install OCC? or OCG?
Is OCC is older version of OCG?
Click to expand...
Click to collapse
You can actually use the Telus firmware. It's identical.

Wouldn't it be problem if the device is locked or unlocked?
Sorry for a dump question.

The software is the same among all carriers, the bloat only gets installed upon first boot!
You can navigate to the CSC folder and see a folder for all the Canadian carriers in there!

neotekz said:
In the menu on the top right side there is an option for emergency recovery.
Click to expand...
Click to collapse
That didn't work for me. I went into the Emergency Software Recovery and Initialization menu. I can't do an emergency software recovery as I don't have a recovery code - my device didn't fail a software update. And when I do a device initialization, it is offering me the same software version.
I have a Fido/Rogers GS6 running 5.1.1.
How did you make it work for you?

Im Currently trying to flash my SG6 with 6.0.1 for Bell.
In odin i get this far and nothing. Been trying all day with NO luck:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920W8VLU3CPF2_G920W8OYA3CPF2_G920W8VLU3CPF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
what is going on?
This exact phone i flash jelly bean's newest firmware the same exact way and it went as smooth as a hot knife in butter.
but this one is making me,.... pull my hair out.
can anyone assist me on this please?

andyid said:
Im Currently trying to flash my SG6 with 6.0.1 for Bell.
In odin i get this far and nothing. Been trying all day with NO luck:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920W8VLU3CPF2_G920W8OYA3CPF2_G920W8VLU3CPF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
what is going on?
This exact phone i flash jelly bean's newest firmware the same exact way and it went as smooth as a hot knife in butter.
but this one is making me,.... pull my hair out.
can anyone assist me on this please?
Click to expand...
Click to collapse
what version of odin are you using ?

I was using 3.09. Updated to 3.10 and within 10 mins my phone was updated.

kgh00007 said:
That didn't work for me. I went into the Emergency Software Recovery and Initialization menu. I can't do an emergency software recovery as I don't have a recovery code - my device didn't fail a software update. And when I do a device initialization, it is offering me the same software version.
I have a Fido/Rogers GS6 running 5.1.1.
How did you make it work for you?
Click to expand...
Click to collapse
have you managed to get 6.x on a rogers one ?
guess we might have to wait for rogers .... or maybe use the at&t us version since at&t and rogers is the same corp
on rogers website the eta for the update is still at : comming soon
source: http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/OSUpgrades/thread-id/1

doditz said:
have you managed to get 6.x on a rogers one ?
guess we might have to wait for rogers .... or maybe use the at&t us version since at&t and rogers is the same corp
on rogers website the eta for the update is still at : comming soon
source: http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/OSUpgrades/thread-id/1
Click to expand...
Click to collapse
At&t and Rogers is not the same. Their phones have locked bootloaders. T-Mobile is the closest to the Canadian phones.
Sent from my iPhone using Tapatalk

Gs5 verizon soft bricked! Urgent!

Hi,
I have a SAMSUNG GALAXY S5 VERIZON and I treid to restore it to its stock rom using ODIN.
I have used every version of odin and I keep getting the same message:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANCG_G900VVZW1ANCG_G900VVRU1ANCG_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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried multiple PC's multiple cables and multiple STOCK MD5 files.
I am Able to get to download mode and recovery boot.
I have tried almost every troubleshoot posted online so far.
On download screen I get SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1
URGENTLY NEED HELP!
Thanks guys

Need to know what build you were on before you attempted all of this. If you were on BOE1 or BOG5, you cannot ODIN back to a previous build. You will have to ODIN the same build you were on when you started this.

Most likely I had one of the two. I'll try to odin to same build.
My phone was on Android 5.1.1 stock.

YES! It worked. Thank you so much! I really appreciate taking the time to help me. Good to know people are still willing to help out!

Hi I am having the same problem but I cannot find the stock file for 5.1 or 5.0.1. or whatever the newest version is if anyone could help out

Dark Karas said:
Hi I am having the same problem but I cannot find the stock file for 5.1 or 5.0.1. or whatever the newest version is if anyone could help out
Click to expand...
Click to collapse
Here you go. This is factory stock, it will locked your bootloader.
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527

I am having the same issue as the OP but mine is 5.0 and was BOG5. Can you please help me fix it or explain to me how I can? I am a noobie at all of this.

Hollieanne said:
I am having the same issue as the OP but mine is 5.0 and was BOG5. Can you please help me fix it or explain to me how I can? I am a noobie at all of this.
Click to expand...
Click to collapse
If you're having the same problem, the solution is the same: Use Odin to flash the BOG5 system restore image that was linked in the post above yours.