Database Users

Unable to Root Note 3 900W8

Hey guys
I have a Canadian Note 3 model 900W8
Yesterday I had to flash back to the stock firmware due to a bootloop issue I had...
Today I tried to re-root my Note 3...and when I press start in Odin, it fails.
I'm doing the exact same method I did the first time I rooted it, and it fails. In dowlnoad mode, the tiniest bit of progress is made and it just stops.
I believe it says recovery failed in download mode.
I've tried to do this on two different computers using various USB ports.
I have developer mode enabled, and usb debugger is also enabled.
Anyone have any ideas?
Thanks

Were you able to root using the same setup before?
Sent from my SM-N900W8 using xda app-developers app
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
What firmware are you on 4.3 or 4.4?
Sent from my SM-N900W8 using xda app-developers app

I'm currently on 4.3
and yes it worked the exact same way last time...I'm not sure what I'm doing wrong this time...
I'm not able to post the url to the site that I used last time to root my phone....maybe if I space it out lol
www . android . gs / root-install-twrp-recovery-canada-galaxy-note-3-n900w8/
but yeah it worked perfectly fine when I did it last month

Try using cf auto root which you can find in the original android Dev section ( make sure you download the one for 4.3 ). If you're not successful in using Twrp, try Cwm as custom recovery ( although I'm using Twrp on 4.4 right now ).

alright so I tried again
in ODIN mode this is what I see
ODIN MODE
PRODUCT NAME: SM-N900W8
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
REACTIVATION LOCK: ON
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWERV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
and this appears after the flash fails
SECURE CHECK FAIL: recovery

HulkSmash316 said:
alright so I tried again
in ODIN mode this is what I see
ODIN MODE
PRODUCT NAME: SM-N900W8
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
REACTIVATION LOCK: ON
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWERV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
and this appears after the flash fails
SECURE CHECK FAIL: recovery
Click to expand...
Click to collapse
Ouch, you tripped your KNOX. Okay no worries. You're currently on 4.3 bootloader, and if you're trying to flash the 4.4.2 firmware - http://forum.xda-developers.com/showthread.php?t=2614772
I suggest you do that first.

Yeah I rooted my phone a month ago and tripped knox
I'm not upset about it or anything...
Thanks for the help, I'll give what you suggested a shot right now and will reply with the results

HulkSmash316 said:
Yeah I rooted my phone a month ago and tripped knox
I'm not upset about it or anything...
Thanks for the help, I'll give what you suggested a shot right now and will reply with the results
Click to expand...
Click to collapse
You have to turn off reactivation lock then flash again. It can be found in the security settings.

hey_joe said:
You have to turn off reactivation lock then flash again. It can be found in the security settings.
Click to expand...
Click to collapse
I have to turn off reactivation lock and flash again?
I already did step 1 of what nicholaschum suggested I do, and I have 4.4.2 installed now.
Before going through the setup process of setting up my phone, I went to root it immediately, but I got hte same failure I've been getting...
I assumed it's because I have to enable USB debugging...so I setup my phone...has me enter my login/password for my phone becuase of reactivation lock...confirm 4.4.2 is installed....enable dev mode.....check usb debugging....
So before I do anything further I just want to get confirmation....after checking reactivation lock in security settings (for some reason it wasn't checked just now when I looked even though I had to login with the info when I first booted the phone after flashing to 4.4.2)
do I flash 4.4.2 again and continue with what nicholaschum said to do?

HulkSmash316 said:
I have to turn off reactivation lock and flash again?
I already did step 1 of what nicholaschum suggested I do, and I have 4.4.2 installed now.
Before going through the setup process of setting up my phone, I went to root it immediately, but I got hte same failure I've been getting...
I assumed it's because I have to enable USB debugging...so I setup my phone...has me enter my login/password for my phone becuase of reactivation lock...confirm 4.4.2 is installed....enable dev mode.....check usb debugging....
So before I do anything further I just want to get confirmation....after checking reactivation lock in security settings (for some reason it wasn't checked just now when I looked even though I had to login with the info when I first booted the phone after flashing to 4.4.2)
do I flash 4.4.2 again and continue with what nicholaschum said to do?
Click to expand...
Click to collapse
You can continue what you are doing just make sure it says off when you are in download mode.
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
I think as long as reactivation lock is on in download mode you won't get root or flash custom recovery.

Hey guys
I now have a rooted Note 3 running Kitkat 4.4.2
Huge thank you to you both of you who helped me this evening.
Now my biggest problem is trying to figure out what rom I want to install.
What would you guys recommend? The only ones I know are Jedi......xnote and wicked.
Basically don't want an bloatware that comes stock with Samsung devices lol

I personally use vision x n3 from the tmobile section as it comes stock and just add my own customization courtesy of xposed installer. Having said that, each of us has their own preferences so read the features that appeal to you and take that rim for a spin. Some roms though need a fix for bt, wifi and nfc along with a kernel that supports them in order to function especially those based on n9005.

hey_joe said:
I personally use vision x n3 from the tmobile section as it comes stock and just add my own customization courtesy of xposed installer. Having said that, each of us has their own preferences so read the features that appeal to you and take that rim for a spin. Some roms though need a fix for bt, wifi and nfc along with a kernel that supports them in order to function especially those based on n9005.
Click to expand...
Click to collapse
So the roms that are compatible for our N900W8 are for the n9005?

HulkSmash316 said:
So the roms that are compatible for our N900W8 are for the n9005?
Click to expand...
Click to collapse
I think every rom made for a note 3 snapdragon ( N9005, N900T, N900A, etc..) will work on our N900W8 except as i mentioned, the wifi,bt and nfc which will need a fix. I found that only AT&T and Tmobile roms don't need a fix for wifi,bt and nfc, They work right off the bat. Problem is there's not many 4.4 based rom from them because of their locked bootloader. If you're still looking for a good rom to try, give Knoxraid 3.5 a spin.

HulkSmash316 said:
Hey guys
I now have a rooted Note 3 running Kitkat 4.4.2
Huge thank you to you both of you who helped me this evening.
Now my biggest problem is trying to figure out what rom I want to install.
What would you guys recommend? The only ones I know are Jedi......xnote and wicked.
Basically don't want an bloatware that comes stock with Samsung devices lol
Click to expand...
Click to collapse
Check out the Canadian Galaxy Note 3 Users thread: http://forum.xda-developers.com/showthread.php?t=2464292
I personally use X-Note 10. But you can use ANY N9005 ROM provided you DON'T INSTALL KERNEL AND BOOT WITH IT. Follow this guide here to run custom ROMs on 4.4.2. Skip to Part Three. http://forum.xda-developers.com/showthread.php?t=2614772

[Q] Is UDC Start line in Download more a warranty voider?

Hi, fellow geeks and mastermands :laugh:
I have flashed one of the latest Netherlands KK 4.4.2 firmwares on my Note 3 (N9005) because I was too impatient to wait another forever for my carrier's Bulgaria Vivacom (VVT) to appear on OTA. I realized that I cannot flash any carrier's ROM, I don't really know why, so I have chosen the Netherlands latest NB4 ROM. Everything went fine but I noticed the famous red line UDC Start appearing on the bottom of Download Mode.
I have read that it is not a problem and that it is something coming together with KitKat anyway BUT - my wife's Galaxy S4 (I9505) got its OTA update last week and I see that it does NOT show UDC Start in Download mode although her S4 is definitely running 4.4.2 now.
So I was worried if this difference is only because she's got S4 and I have Note 3, or because she got her update OTA and I force flashed mine via ODIN?
Does anyone know if this UDC Start status will void my device's warranty in case it needs a visit to the service?
Do you know if UDC Start will disappear if I flash the official, i.e. my device carrier's VVT ROM when it comes out?
Thank you

boboev said:
Hi, fellow geeks and mastermands :laugh:
I have flashed one of the latest Netherlands KK 4.4.2 firmwares on my Note 3 (N9005) because I was too impatient to wait another forever for my carrier's Bulgaria Vivacom (VVT) to appear on OTA. I realized that I cannot flash any carrier's ROM, I don't really know why, so I have chosen the Netherlands latest NB4 ROM. Everything went fine but I noticed the famous red line UDC Start appearing on the bottom of Download Mode.
I have read that it is not a problem and that it is something coming together with KitKat anyway BUT - my wife's Galaxy S4 (I9505) got its OTA update last week and I see that it does NOT show UDC Start in Download mode although her S4 is definitely running 4.4.2 now.
So I was worried if this difference is only because she's got S4 and I have Note 3, or because she got her update OTA and I force flashed mine via ODIN?
Does anyone know if this UDC Start status will void my device's warranty in case it needs a visit to the service?
Do you know if UDC Start will disappear if I flash the official, i.e. my device carrier's VVT ROM when it comes out?
Thank you
Click to expand...
Click to collapse
no. Just 4.4.2 NB1 bootloader

Thank you for replying, hhai2pth, but I am not sure which of my questions the reply refers to? What about the NB1 bootloader?
Sent from my SM-N9005 using Tapatalk

Strange that nobody knows about that. So, let's asknit another way - is it possible to remove the UDC Start line?
Sent from my SM-N9005 using Tapatalk

boboev said:
Strange that nobody knows about that. So, let's asknit another way - is it possible to remove the UDC Start line?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Why would you want to remove the "UDC Start" line?
It's meaningless to you. Or to anyone else that matters as well.
The absolute ONLY thing that will void your warranty is the "Knox" flag. Is it at 0x0 or 0x1 currently?
0x0 means your warranty is fine, 0x1 means you do not have a warranty anymore.
Who told you about this UDC Start flag? Why are you even asking about it?
ARE you working for the cops?

that line does't void your warranty. it's Knox. you go to download mod and see if knox is 0x1 you void warranty

nexxusty said:
Why would you want to remove the "UDC Start" line?
It's meaningless to you. Or to anyone else that matters as well.
The absolute ONLY thing that will void your warranty is the "Knox" flag. Is it at 0x0 or 0x1 currently?
0x0 means your warranty is fine, 0x1 means you do not have a warranty anymore.
Who told you about this UDC Start flag? Why are you even asking about it?
ARE you working for the cops?
Click to expand...
Click to collapse
No, I am not working for the cops. Tripping Knox is a federal crime, so it's FBI :laugh:
OK, seriously. I am no WORRIED. I am just INTERESTED. XDA dev forum is maybe the only place where there are enough people who really know some things. I just started doubting the validity of the widely repeated statement that UDC Start is something that comes automatically in the bootloader with the KitKat. I just saw that in the instance of Galaxy S4 the device got OTA updated to KitKat and UDC Start did not show up in the bootloader screen.
Therefore the statement that everybody repeats lately - UDC Start is just something that goes with 4.4.2 - is simply not always true. And I am a curious person, that's why I started looking for the REAL ANSWER....and yes, I promised to turn in some of the people who have replied to the Federals

UDC START - problem
UDC START - doesn't allow to root Your device. The Ondine, seems to be working properly, the process always pass, but IT DOESNT CHANGE ANYTHING !
regards
AD

Pretty sure the UDC Start line is simply stating "usb download connection start" doesn't affect anything at all.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T

[Q] About kernel and ChainFire auto root

Hello
i have the SM-N910C running the official lollipop firmware,
days ago i've rooted it using CF auto root through the odin,
And it was successful, but the question is the CF auto root
replacing the stock Kernel to another one while flashing ?
cause when i reset flash counter using triangle away even without restarting the phone it still shows in triangle away:
counter: 1
Binary: custom
system: official
but in bootloader it says:
current binary: samsung official
system status: official
secure download : enabled
knox warranty void: 1
rp swrev: 1
and the reactivation lock is off in the settings and the bootloader
i just need the software updates after root
and resetting the flash counter to Zero
and to know the kernel is it stock or custom
anyone could help ?
and sorry for any bad english, thanks.

Mr.3bood said:
Hello
i have the SM-N910C running the official lollipop firmware,
days ago i've rooted it using CF auto root through the odin,
And it was successful, but the question is the CF auto root
replacing the stock Kernel to another one while flashing ?
cause when i reset flash counter using triangle away even without restarting the phone it still shows in triangle away:
counter: 1
Binary: custom
system: official
but in bootloader it says:
current binary: samsung official
system status: official
secure download : enabled
knox warranty void: 1
rp swrev: 1
and the reactivation lock is off in the settings and the bootloader
i just need the software updates after root
and resetting the flash counter to Zero
and to know the kernel is it stock or custom
anyone could help ?
and sorry for any bad english, thanks.
Click to expand...
Click to collapse
Hi, cf autoroot doesnt replace your kernel, so u should still have stock kernel.
and also as far as i know, triangle away doesnt work on note 4 ... so right now there is no way to reset the counter to zero.
and 1 more thing is you may have posted this question in the wrong thread, you should have posted it in the Q&A thread. ^^

randykzc said:
Hi, cf autoroot doesnt replace your kernel, so u should still have stock kernel.
and also as far as i know, triangle away doesnt work on note 4 ... so right now there is no way to reset the counter to zero.
and 1 more thing is you may have posted this question in the wrong thread, you should have posted it in the Q&A thread. ^^
Click to expand...
Click to collapse
Thanks a lot , i'll try different ways to reset it, if i succeed i'll wrrite a thread about it

Mr.3bood said:
Thanks a lot , i'll try different ways to reset it, if i succeed i'll wrrite a thread about it
Click to expand...
Click to collapse
Good luck trying to figure out how to reset that counter permanently - so far no one managed to find a way to do that since the introduction of KNOX back in 2013.

Got confused about Note 3 and Knox current situation

So guys, i got a little bit confused about knox 0x0 - 0x1 - root - custom roms etc.
I own a note 3, when it was with kitkat i've installed twrp through odin and got "knox 0x1 (1)" then i went with official lollipop firmware, and now i've reflashed twrp for installing cm12.1 getting knox 0x1 (2). From what i understand, there is no way to revert knox to 0x0, isn't it?
If i had a brand new note 3 with lollipop and knox 0x0 could I install custom roms without tripping it? or even get root permissions on the stock rom?
what also keep me confused is: why there are so many alert in the note 3 section on xda about tripping knox while in the s5/s6/note4 sections everything seems to be much easier? can you please explain me?
PS: execuse me if i've had not been so clear but english is not my first language

Nope, the device's virginity is lost, that baby is done, unless you have the Exynos version, where KNOX status could be reset

Thanks for answering. So i got a friend that would like to install the cm12.1 on his knox 0x0 N9005. will he trip it?

Not much idea mate. But I think there is a possibility that he might not trip it, at least I have seen something like that. Obviously the standard method of flashing a ROM via Odin or or from custom recovery will trip it, but I think there's a way to avoid that, not the usual way of course. You might ask to those who have already done it, or in the CM topic itself, if there is one.

Verizon Galaxy S5 bricked?? PLEASE HELP!!!

Verizon Galaxy S5 (SMG900vzkw), I bought the phone already rooted from a friend and it was running KitKat (4.4.4). Tried to update it to Lollipop and now I'm not sure what I've actually done. Can someone please walk me through how to get this phone back to its stock configuration? My plan is to just revert back to stock, use OTA updates and then root it back afterwards. I've always had Motorola phones prior to this galaxy and as I've just found out, the entire update/root process is completely different on a Samsung. I tried to flash the stock firmware using Odin last night but without success. I did find these on this thread:
http://forum.xda-developers.com/showthread.php?t=2519544&page=3
I downloaded them but I'm not sure if this is what I need or not. Currently when I plug my phone up to my PC the screen reads:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK (KK): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
UDC START
Firmware upgrade encountered an issue. Please use Software Repair Assistant and try again.
I am brand new to this Odin software/process so if could please be very specific on instructions I would really appreciate it. I really hope I haven't ruined this phone. Thanks in advance for any help.

i have the same problem. to get out of Please use Software Repair Assistant download the NK2 kernel and flash it in odin. Still looking for a solution to get it out of softbrike...............

Assuming you haven't already screwed it up already, DON'T DO THIS. You will lock your bootloader on PB1, which is unrecoverable. Go download the latest NCG firmware from SamMobile and use FlashFire to flash a pre-rooted Lollipop ROM. Or CyanogenMod, if you have a 15 chip.