Hi, I tried a million times to root my note 3(900N) after I install a bootloader(from note 4 modded for note 3), a modem and a modded kernel.
I tried to flash a rom, didnt worked(Error flashing zip). After a while, i got problem from that kernel. Now I installed stock lollipop (via odin), I installed a recovery(TWCM) but I cant flash anything. I even tried to flash the SuperSu.zip, it act like a crash.
Before I install that files(bootloader, modem, kernel) I rooted, flashed, etc.
Please help me to root the phone.
May be a problem from kernel or bootloader? Can I install the stock of this files? If I can, where I can get them?
Thank you.
L.E: "I searched and I find this: "Some facts about KNOX status:
It isn’t possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package). By downgrading from KNOX-enabled to KNOX-disabled firmware, your devices will be locked to installation of newer firmwares."
I Have KNOX 0x1. I don`t know how I did this. But I can fix this problem?
Related
Hi,
after reading a lot of thread here, or in android developement, about galaxy note 3, I am wondering if there is any way to know if a rom is knox free or not.
a lot of time, it is not clearly listed in the thread.
I saw some post saying that if you use odin mobile, or odin on PC, or rom without kernel, or rom without boot loader etc...
but I find easily some information which says the opposite (specially odin mobile, which I bought, and tell clearly when I launch it that it can trip knox counter)
my galaxy note 3 N9905 is under 4.4.2, xxxUGNG1.
I rooted it without modifying knox (I checked it, it is not set to 01, it is still = 0)
I would like to undertsand what I can flash without "any" risk, and whant method to use :
odin on PC ? custome recovery ? original recovery (renaming the rom by update.zip is working, no ?)
no kernel ? with kernel ? no bootloader ???
thanks for any help to understand.
Olivier
ROM has nothing to do with KNOX trigger. You strike the flag only if you flash custom recovery or custom kernel.
You need custom recovery to install custom ROM. Or Mobile Odin Pro. The only way to install custom ROM without affecting the KNOX flag is by installing via Mobile ODIN Pro and NOT installing custom kernel, should the ROM installation include one.
Hi,
thanks for the feedback.
I try to have more information please.
let me sumarize your answer, and add more question :
I have a N9005, under stock rom, 4.4.2, xxxUGNG1.
note : I never launched knox in the device. I don't know if it change things or not...
I can flash a rom, using mobile odin pro, and not set knox flag to 01 if the rom do not contain any kernel.
I cannot flag any recovery at all : if I do it, knox flag will be set to 01.
if the rom I want to flash contain a kernel, I have to remove it from the package (or may be mobile odin pro has a setting to load the package, and not flash the kernel) ?
I cannot change the modem, for the same reason than for the recovery, right ?
if I want to flahs CM11, I will set the knox flag to 01, in all case, because the kernel need to be changed. right ?
so, the result is :
if I want to play with my note3 (play for me is testing CM, or all rom not starting from a samsung rom), I will set the knox flag to 01... right ?
thanks for any feedback
Olivier
It is no guaranty that custom rom will work with the stock kernel.
Hello,
I'm using a SGS4 rooted since more than one year and a half (odin, flash a small root bin file if I remember well, flash counter set to 1, no custom recovery and no nandroid backup)
Since I want to implement NFC card emulation now avaliable in android 4.4 in one of my apps, I'd like to update.
I've seen few threads on the subject, and most of them date from a long time (am I late ? ). I'd like to know how I could update normally my actual rom (provided by Orange, precisely I9505XXUAME2), or move to another slightly modified rom like the base rom provided by samsung without all these apps that you can only remove with root.
I don't want to have any data issue I've read about, I don't want to lose my actual apps and their data. (Nandroid backup then restoring apps and their data through nandroid manager?)
Also, if possible i'd like to update without losing my start screen, my parameters, etc... (in the worst case I'd re-set them manually). And finally of course I want to have it rooted at the end of the process.
In fact I want it to be just like if I had done an OTA update, then rooted it.
Also, How to update without setting the Knox counter to 1 ? (My flash counter is set to 1, should I use Triangle Away?)
Is there any simpler way than flashing the new firmware and then importing everything from my old data to the new and reinstalling the changes I made to the system (like avast & such) ?
Also, maybe there exists newest versions of the firmware, but without the new bootloader that has the knox counter ?
Thanks in advance!
tboss1995 said:
Thanks in advance!
Click to expand...
Click to collapse
1. You can't receive OTA updates if you have rooted your device. You have to flash the firmwares via ODIN.
2. You don't need wipe nothing if you flash new stock firmware. Instructions: Flash new firmware (if you don't have wifi flash it one time more), root it again then and you're done. Your data don't have to be affected (maybe you only have to reinstall some app if the data/cache was moved to the SDCARD).
3. Flashing one new stock firmware don't modify KNOX. You actived KNOX rooting your device or flashing one custom recovery. Knox: 0x1 can't be reset. Triangle away only reset the flash counter.
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
tboss1995 said:
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
Click to expand...
Click to collapse
1. Updating via ODIN or Kies don't set the KNOX counter. Downgrading YES.
2. Root dissapear if you flash new update via ODIN.
3. You can flash latest firmware and root them without KNOX. Take a look for the method: HERE.
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
tboss1995 said:
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
Click to expand...
Click to collapse
1. Take a look: HERE.
2. Nobody know it.
3. - KNOX free: This therm is used for the custom ROMS normally. This mean that flashing this ROM dont touch the KNOX counter.
- KNOX counter: You still having your device in warranty if you have KNOX:0x0. You void your warranty if you have KNOX:0x1 in DOWNLOAD MODE.
So it means I'll still have the new bootloader ?
For those who may come to read this article and don't want to watch a video, I've found an article explaining what kernels are. http://m.androidcentral.com/android-z-what-kernel
Hi, I accidently rooted and installed cwm on my galaxy s4 gt i9-505, without disabling knox, and now I want to go back to the orginal samsung bootloader, (I don't not want to know how to get the stock firmware), I want to unroot and restore the bootloader, really need help asap, would be apperiated thanks.
Update: I'm on Android L 5.0.1, and installed cwm before rooting which was a silly mistake, because knox then countered that, and it's conflicting root problems when I tryed to root afterwards, but now I just want to go back to the Samsung bootloader, root issue fix but still don't know how to fix bootloader.
Not sure what is there to fix - if phone boots correctly it is good.
If you try to revert back to knox 0x0 I'm afraid it is not possible.
Flashing root and cwm doesn't replace your bootloader
How do you accidentally flash root and a customised recovery?
Imtigerclaw said:
Update: I'm on Android L 5.0.1, and installed cwm before rooting which was a silly mistake, because knox then countered that, and it's conflicting root problems when I tryed to root afterwards, but now I just want to go back to the Samsung bootloader, root issue fix but still don't know how to fix bootloader.
Click to expand...
Click to collapse
You are really mixing things up.
A custom recovery has nothing to do with Knox. A custom recovery gives no problems with Knox. It's impossible.
You are on the samsung bootloader. You cannot change it to a custom (there isn't even any).
If you want root just flash cf auto root and then delete knox. That's all.
Hi all,
I want to install ROM by _alexndr on a new G900F. I want to keep KNOX 0x0, so I need root to flash this ROM using flashfire.
However, the device came with android 5 when I bought it, so towelroot does not work. If I understood correctly, I have to flash stock 4.4.2 firmware (where do I get it? which tool to use for flashing? Just flash, or other things to take care of?), then I can use towelroot and flash ROM by _alexndr with flashfire. Did I miss anything important?
Get the ROM and ODIN the flashing tool from sammobile .com firmware section
Instructions under the download (Free account might be needed to download the ROM)
Can I just flash the old 4.4.2 firmware over the current 5.0 firmware, or do I have to consider something else?
I've flashed KK over LP before, and first boot didn't boot, flashed it again the same way, and it booted fine
Might need to factory reset before/after flashing if you have problems
Hello to all ..
is there any chance to root my S4 with the i9505XXUPPI1 version installed on it Or is there any other Way to Downgrade it to an earlier version and root it thereafter?
greetingz from Germany
HouseMeischda
You could try cfautoroot or flash TWRP and then flash supersu from TWRP.
CF-Auto-Root is your best option.
Thanks for your help.
For all i9505 Users with the same Problem ..
First i've flashed the original I9505XXUHOJ2 Firmware who listed on chainfire's Page, to be on the safe way =). Then i've flashed the cf-root Kernel from Chainfire. After that i installed the newest TWRP recovery and then the Resurrection Remix Rom 5.5.9.
Now i will test everything but seems to be nice till this moment =)
Thread can be closed .. Thanx
BTW, rooting is not required to install TWRP with Odin.
audit13 said:
BTW, rooting is not required to install TWRP with Odin.
Click to expand...
Click to collapse
True. But some people (including me) have had problems getting TWRP to stick with the Odin install.
I had to use an app to flash it when I took to the custom software world.
A user had the same problem few days ago. Also solved it with the app method.
I've never had a problem with getting TWRP or CWM to stick on the s2, s3, s4, note 1, note 2, or note 3 by unchecking auto reboot in Odin before flashing recovery. Once recovery has been flashed, I remove the battery and immediately boot into recovery. I found that not booting into recovery right after flashing will cause the stock recovery to overwrite the custom recovery when the phone boots normally.
Thats right. But in my case and first of all i wanted to test the stock rom with only root Access. But then i decided to install a custom one very quickly =)
After all i installed latest twrp via twrp-app, backed up everything, perform a full wipe and flashed ResurrectionRemix 5.5.9. Now i went to dirty unicorn rom on Android 6.0 base. Very nice performance, very clear Design and absolutely stable.
One more word to overriding the Recovery. In many other Posts, this Problem seems to be normal, if the S4 was already updatet to an official lollipop rom(with the new knox Bootloader, that verifies signatures of recovery and kernel) in the past. I think this issue was not present with kitkat and oder versions.
But with my little detour, i also was not effected from that override
Hope this can help others with similiar reservations who i had before. Not the fear of loosing warranty(because phone is anyway too old) but fear of tripping the bad eFuse and thus hardbricking the phone. BUT WELL DONE !!!
Many thanks for the support .. And greetingz to all =)
There is no eFuse that will hard-brick the S4.
It only has an eFuse for Knox, which simply prevents you from resetting the Knox counter back to 0x0, but it won't hard-brick anything.