Hello
I have Verizon Note 3 with version 4.3.
In the past I was able to root it with out tripping KNOX. Recently I tried to use ROM Recovery, but then found out that ROM recovery would not work on Verizon variant. In the process I soft bricked the phone. I used Odin to re-install OS. The phone works and I can get to Odin and recovery modes, however, it is not rooted. I tried rooting it again using Odin and Root Dela Vega method, but this time it would fail. I notice that Odin mode displays the following:
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
WRITE PROTECT: Enabled
It looks like I tripped the KNOX warranty.
I do not often do this kind of stuff, so I do not know exactly how do I root it in this situation. So my questions are:
1. Can the KNOX warranty be reversed back to 0x0? I think there was a post about it, but I could not find it.
2. How do I root the phone now?
Thanks
Knox cannot be reset for the time being.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Wicked Stunts said:
Knox cannot be reset for the time being.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any ideas about rooting?
suppafreak said:
Hello
I have Verizon Note 3 with version 4.3.
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-galaxy-note-3
And learn to use the Q/A/Help subforum (there and here).
Moved to Verizon Note 3 Q&A.
Would you please send us root de la vega sm-n900vvrsepl1 galaxy note 3. I can't root the phone
Try this....you will need to unzip it
SOLL365 said:
Would you please send us root de la vega sm-n900vvrsepl1 galaxy note 3. I can't root the phone
Click to expand...
Click to collapse
It is an older version of the Arabic Tool. Worked for me to root only.
https://www.dropbox.com/s/69ecfdtstta67ne/ArabicToolApp.zip?dl=0
Related
UPDATED POST:
Hello,
As @Dumbo53 has mentioned below posts, there is a root method by the developer @designgears and it seems that this root method does NOT trigger the knox flag.
Unfortunately, it is just for the AT&T Note 3 devices.
Maybe someone could port this root method for our international N900 and N9005 model devices?
Root de la Vega:
http://forum.xda-developers.com/showthread.php?t=2474422
----------------------------------------------------
Hello there,
I wanted to share something from Chainfire's Auto-Root thread.
Chainfire has mentioned:
Using this root method sets current binary and system status to custom. Additionally, it will also trigger the KNOX warranty void status.
This device store the traditional flash counter. Nor is is possible with Triangle Away to reset the current binary status. You will need to flash a stock kernel and stock recovery to reset the binary status.
The KNOX warranty status change is permanent, and a service center may deny warranty based on this flag - even if the other flags are reset correctly. The KNOX flag being tripped may also prevent certain Samsung KNOX features from working (enterprise security features).
If this is something you care about, use a root method not based on custom kernels or recoveries, like a modified system partition. These are possible, but I don't personally make them, so look around!
Click to expand...
Click to collapse
So my question is simple:
Is there any talented developer who can look at the system partition on the devices N900/9005 and somehow to look if he can modify it to root without triggering the knox counter. Iaw chainfire's post, it seems to be possible, but we need a talented developer to look for this
I would be really so happy, if it can be done this way...
No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4
BlueChris said:
No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4
Click to expand...
Click to collapse
I was talking according to Chainfire, dude. He just showed us that there could "may be" a way to root without knox would recognise this.
I think may be knox watches only the bootloader and recovery situation (if it is custom or official).
Chainfire's root method includes to flash first insecure recovery and after root flashes back the official recovery. During this process knox recognise the shortly time with the insecure recovery and the counter goes to 0x1. But iaw Chainfire's post, i think if someone could root without touching the recovery or kernel, it could be possible not to trigger the knox during the root process.
I don't think we will have a way to bypass it. I think once you get root it will still trigger it.
Funny how this is something from an Android device and not an iDevice.
Guess Samsung got tired of fixing devices after someone oc the hell out of it!
Sent from my SM-N9005 using XDA Premium 4 mobile app
There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
Thanks mate, i will also look to his thread and beg him for n900
Sounds promising. Don't really need a custom recovery thanks to xposed.
Sent from my SM-N9005 now Free
Knox problem thanks (lovelesss)
we are waiting for n900 please
n900 I want to wait for the Root de la Vega.
What about N9005?
vinokirk said:
What about N9005?
Click to expand...
Click to collapse
+1
Sent from my SM-N9005 using Tapatalk 4
vinokirk said:
What about N9005?
Click to expand...
Click to collapse
Yeah I can add N9005 also as request on this topic.
Changing the subject of this thread just a sec
I don't have any information showing Knox flag in Odin mode, Exynos SM-N900. Does this mean my phone doesn't have this flag?
Hi, im new here sorry if posted in wrong section
I tryed rooting my Samsung Galaxy Note
I followed every step and unfortunantly after 40 seconds of pressing start I recieved on Odin a red Fail box
Odin looked like it had finished what it was doing even though it failed, so I pressed exit and disconnected the phone.
when I switched the phone back on I got this message
"Firmware upgrade encountered an issue. Please select recovery mode in kies & try again"
So I connected to Kies but the phone wont connect. I tryed the recovery but ive never used Kies before so there was no files to recover.
I tryed firmware and initialisation by putting my model and seriel number in but there was nothing found for Samsung Galaxy Note 3.
I dont want to go any further as im not sure what im doing now and ive stopped researching as im nit sure what websites to trust or able to find a correct answer to my issue.
My phones a
Samsung Galaxy Note 3
SM N900
Android Jelly Bean 4.3
United kingdom
(Not sure of other details I cant get into phone to look)
I thought I would come her as my friend recommended the site. I need help on how to make my phone work again.
I can still boot in download mode but I cant connect to computer but I havent tryed to connect to Odin.
ive rooted 5 of my other phones and tablets in the past and never had an issue, so this is new to me
Any fix I am happy with weather its a root fix or back to normal fix I just want my phone working again.
I definantly wont be rooting again im worrying my phone wont work at all now
thank you for any help!
On my screen I have
ODIN MODE (in red)
PRODUCT NAME: SM-N9005
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
(In gray)
QUALCOMM SECUREBOOT ENABLE (CSB)
AP SWREV: S2, T2, A2, A2, P2
WRITE PROTECTION: Enable
then theres a pic of a phone, yellow triangle with an exclamation mark and a computer
then underneath the firmware upgrade error.
case elovmos
Im not 100% sure if I enabled USB debugging first. Will this cause me a problem?
Yes enable usb debug
To get away from this situation flash stock firmware
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
I havent fixed the problem but im doing research im one step closer
Mate. .. Get odin 3.09 and download firmware from sammobile.com. Try with the older firmware versions first like MI6 or something. ... If that don't work. .. Flash MJ7 latest firmware(can't go backwards once you Flash this firmware) and will definitely work
Sent from my SM-N9005 using Tapatalk
alom5 said:
Mate. .. Get odin 3.09 and download firmware from sammobile.com. Try with the older firmware versions first like MI6 or something. ... If that don't work. .. Flash MJ7 latest firmware(can't go backwards once you Flash this firmware) and will definitely work
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Ummm sammobile? Y know that hotfile is down and will never come back online due to DCMA complaints?
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Killberty said:
Ummm sammobile? Y know that hotfile is down and will never come back online due to DCMA complaints?
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Click to expand...
Click to collapse
They have a different server now. A lot slower though...
Hi XDA community,
I'm new to the Android community (Yeah, my previous phone was from Apple), and am currently enjoying trying new ROMs.
I have a international Note 3 SM-N9005 thatt was on 4.3 Android when I flash a CM11 nightly. (With TWRP, last version to date)
After, I tried to flash the Slim W03 v6 and it work very nice.
Here comes the problem.
I wanted to give a shot to other ROMs: X-note and Crash Rom. They installed, I reboot and I got stuck to the "Galaxy Note 3" Boot logo and nothing.
I can get back to my Nandroid Slim W03, but not to the CM11.
From what I read, it seems to be a bootloader version problem... I added up some picture to provide some background.
Is there a tutorial/thread to help me go through this situation?
Cheers to you and thanks for your help!
PAco
First try booting up to recovery and do a factory reset. If still stuck at the samsung splash screen ( give it a little time of at least 5 minutes to see if it's going to go through ), then you're still probably on 4.3 bootloader and you flashed a 4.4-based rom. If this is the case, you either have to update to stock 4.4 then flash custom recovery and root before you can flash 4.4-based roms or stay at 4.3 and you can flash 4.3 based roms.
Thanks. I'll try and see. Cheers mate.
Sent from my SM-N900T using XDA Premium 4 mobile app
Hi Joe, just for my personal knowledge, do you have a way to display your bootloader version / status (loi locked vs unlocked)? Thanks again
Sent from my SM-N900T using XDA Premium 4 mobile app
Don't really know how to display version if your phone doesn't boot up to system but if you put it in download mode, if you have 4.4 bootloader you will see " udc start " at the last line.
Sent from my SM-N900W8 using xda app-developers app
Hi, Here is what is displayed when in downloading mode:
Odin MOde
Product Name: SM-N9005
Current binary: Custom
System Satatus: Custom
Reactivation lock: OFF
Know Kernel Lock: 0x0
Know Warrantly void: 0x1
Qualcomm secureboot: enable (CSB)
AP swrev: s2, T2; R2, A2, P2
Write protection: Enable
**LOGO ANDROID**
Downloading...
Do not turn off target
So I guess I still have a 4.3 Bootloader.
Thanks Joe, you really helped!
Hi guys
I have a i337m from Tigo Colombia and I were looking for a way to install CM11 in it no matter if warranty was voided
In the process I found out that after installing CM11 my knox warranty void still is 0x0. I don't know if this is true for all i337m or I was lucky somehow, anyway here are the steps I made for having CM11:
1. Root with towel root
- Go to www.towelroot.com
- Click the lambda symbol
- Install the apk
- Click "Make it ra1n"
- Now you're rooted. Check looking for SuperSU app and update it
2. Install Recovery: I tried to install CWM from .img with heimdall in Linux and with proper file in Odin in Windows, both cases failed as you can see here [1], looking for answers I end up installing ROM Manager app.
- Install ROM Manager app from Google Play
- Run the app / give root permissions
- Click on install new recovery and select jfltecan (I first installed normal recovery, after donate for get the touch one and support the devs). I selected ClockWorkMod 3.x (the version of CWM installed is 6.0.4.7)
- Reboot to recovery from app and made a Nandroid to starting to mess with the device
Entering to recovery I see: RECOVERY IS NOT SEANDROID ENFORCING
After reboot I see a message in red that says: KERNERL IS NOT SEANDROID ENFORCING
And when I went to download mode I see this:
Code:
Product name: SGH-I227M
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: enabled
And attached you can find the pictures that probe it
I hope this can help anyone that wants to get custom ROMs on his/her i337M
[1] http://forum.xda-developers.com/galaxy-s4-att/help/s4-i337m-help-installing-custom-recovery-t2887774
Good guide.
I must admit I didn't read the m after your i337 and got slightly excited.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
kirbee213 said:
Good guide.
I must admit I didn't read the m after your i337 and got slightly excited.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for the false alarm, maybe this works for AT&T variation as well but I need more info from i337M owners to see if this can be considered as a guide or just my particular experience
Will this method work on a Candian Model? Our S4 model is also i337m, anyone from canada tried this? I don't want to trip my know counter cause i just got my phone
fatbuccha said:
Will this method work on a Candian Model? Our S4 model is also i337m, anyone from canada tried this? I don't want to trip my know counter cause i just got my phone
Click to expand...
Click to collapse
I think we import Canadian models so this should work. Anyway I'm wondering if I just have luck or really is a way to achieve flashing custom ROM's without trip the warranty void counter or if our model just don't trigger the counter at all
You can trigger it. I have i337m and my Knox flag is tripped. Custom Roms now tho
Sent from my SGH-I337M using XDA Free mobile app
Psykologikal said:
You can trigger it. I have i337m and my Knox flag is tripped. Custom Roms now tho
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
Then I was lucky or this can be a method to avoid trigger the counter. As you see in the pictures of OP, I have CWM, CM11 flashed and 0x0 (Official Samsung software appears there on download mode too).
Hello all
There is a lot of old threads about disabling KNOX on S5 but none disabling app dont work, I've tested a lot of them . Do we have hope for reset KNOX to 0x0? Are there any news about it? My phone is SM-G900F
You can't reset KNOX 0x1 to 0x0
Galaxy S5 Tapatalk
I think it's possible because lots of people were replying for disabling apps made by xda devs, it was working but usually for galaxy note users.
mitay said:
I think it's possible because lots of people were replying for disabling apps made by xda devs, it was working but usually for galaxy note users.
Click to expand...
Click to collapse
It's not
Sorry no I haven't heard of a way either
Sent from my SM-G900F using Tapatalk
as far as i know... you can't reset knox... but i think you can root g900F and still 0x0...
No, there's no way to reset the Knox Warranty Bit counter back to 0x0. The reason is that Samsung uses an eFuse that burns itself permanently when it detects that a unsigned kernel/bootloader/recovery is installed on the device. As a security measure, Knox is disabled forever on said device (and any data encrypted by it will not be any longer retrievable). That is to keep data secured from exploits and root.
Hope that explains everything!
Source: https://www2.samsungknox.com/en/faq/what-knox-warranty-bit-and-how-it-triggered
Actually it is still an ongoing debate whether it is software or an efuse just my 2 cents
No
How to reset knox 0x1 to 0x0 my phone model s5 sm g900f
Haslie said:
How to reset knox 0x1 to 0x0 my phone model s5 sm g900f
Click to expand...
Click to collapse
Did you read any of this thread at all before posting?
0x1 is PERMANENT