I have a danish P605 tablet and successfully rooted it with RDLV without triggering KNOX - the name of the rooted firmware is "P605XXUAMJ2_P605OXAAMI7_P605XXUAMJ1_HOME.tar.md5". There are further updates available, but due to rooting it, it does not want to update OTA any more - and this is in spite of having KNOX still at 0x0.
How can I get the latest firmware on my device without triggering KNOX? Can I repeat the RLDC process with the latest firmware from samsmobile, or can I even install that one without repeating the RLDC process? Can I get the OTA process to work somehow? I tried to temporarily disable SuperSU, but that didn't seem to help...
Please advise, thank you!
Related
So i have a Galaxy s4 mini with sprint as my carrier. I'm currently trying to root it via Kingo root app but the problem is that everytime i try, the end result is NeedRoot. I checked my phone and apparently the problem is that everytime I try to root, i get a little shield on my phone saying "Security notice" once it's clicked it states " An attempt to access a secure area on your phone without authorization has been blocked. Make sure your phone is protected by updating the security policy to the latest version from samsung". So how do I remove this policy problem? I just want to root my S4 Mini. Any help/advice is great help, thank you!
No one has an answer?
irvinavitia said:
No one has an answer?
Click to expand...
Click to collapse
If you took all the updates and are on NA7, no. As far as I know we need ODIN/Kies to root now. Ideally, we wouldn't have have taken the update that made Knox an issue. Someone would have dumped update, broken it apart and gave us a zip to flash everything but the bootloader so we wouldn't have these issues.
I believe you will find the answer to your question here ...
Rooting SPH-L520 Under KNOX?
http://forum.xda-developers.com/showthread.php?t=2676255
mdawdy said:
I believe you will find the answer to your question here ...
Rooting SPH-L520 Under KNOX?
http://forum.xda-developers.com/showthread.php?t=2676255
Click to expand...
Click to collapse
Did you notice who posted last on there?
Hi i have a s4 mini gti9195i with knox rooted by kingo root apk
how can i change from kingo's superuser to supersu from chainfire? The update of the binary fails.
Not fast but 100% good way:
1. Flash stock firmware with odin (remove kingoroot and all it's trash).
2. Use CF-Auto-root or (if you plan to use custom roms) flash custom recovery.
Notice:
CF-Auto-root probably will trip knox flag when trying to disable knox security.
Hello guys,
I'm sorry I created a new thread to ask some questions but nobody responded when I asked on an existing thread. Also, I think you should keep this thread for new users who what to know everything about rooting their LG G3.
So, my questions are the following:
I just bought the LG G3 (D855, runs Lollipop out of the box) and I want to root to it (I've rooted many devices before) but will I be able to receive OTA updates? Does LG has any security feature like Samsung's Knox that is triggered by the rooting process and marks my device? Is there any danger in general?
If later on I decide to flash TWRP and custom ROMs will I have to unlock the bootloader?
Thank you for your time, and again, sorry for the new tread.
I am not sure about the Lollipop version but when I was running KitKat I was notified of OTA updates but when I've tried to run it I got a pop up that update couldn't be applied because my phone was rooted. had to get rid of root than I could update it.
SpectralMeat said:
I am not sure about the Lollipop version but when I was running KitKat I was notified of OTA updates but when I've tried to run it I got a pop up that update couldn't be applied because my phone was rooted. had to get rid of root than I could update it.
Click to expand...
Click to collapse
From what I heard a simple unroot from SuperSu app was not even enough, because the stock fw has a counter that is incremented in case you root, and therefore even if you remove root the counter will still prevent you from applying the OTA.
tylerdurden83 said:
From what I heard a simple unroot from SuperSu app was not even enough, because the stock fw has a counter that is incremented in case you root, and therefore even if you remove root the counter will still prevent you from applying the OTA.
Click to expand...
Click to collapse
I've flashed a stock firmware and updated. There may have been a simpler way, but I am not an expert.
Again I am not sure if things got easier or harder with Lollipop but to be very honest in the last few firmware updates I did not see anything life changing from LG that would worth the hassle. I think being rooted is much more valuable than the latest firmware updates were.
For me personally anyways
tylerdurden83 said:
From what I heard a simple unroot from SuperSu app was not even enough, because the stock fw has a counter that is incremented in case you root, and therefore even if you remove root the counter will still prevent you from applying the OTA.
Click to expand...
Click to collapse
Thank you guys for the answers! :good:
So, LG indeed has a "security" feature that messes with your device. Can someone confirm it?
If the counter is software can't we alter/erase it? Or is it hw-based like Samsung's Knox Warranty Void? If it is hw-based we cannot do something.
I know we must suffer the perpetually locked bootloader provided by T-Mobile that should not be an issue; however the LP (OB6) bootloader will be able to load NK3, but for Towel Rooting, NE6 was the last Towel Root compatible version based on the research so far, and generally people are recommending to avoid NK3 if Towel Rooting is the goal, so is it possible using ODIN 3.07 to downgrade to NE6 without tripping KNOX on an unrooted OB6 N900T Note 3?
If it is possible to get the result we're looking for, we intend to follow the directions in the following links to root without tripping KNOX to also have the advantages of Lollipop in the end result:
1 - http://forum.xda-developers.com/not...-to-root-nf4-knox-0x0-effortless-nf4-t2846142 (Effortless Root for NK3 that begins with NE6)
2 - http://forum.xda-developers.com/not...icial-lollipop-n900tuvufob5-t-mobile-t3046295 (To go from NK3 to OB6 without rripping KNOX)
We're looking for input from those with experience downgrading from OB6 to NE6, and we've no desire to impose on our ability to use KNOX features by causing KNOX to become altered. We would appreciate the community's thoughts because the sharing of the results from those already having gone through this experience would be greatly appreciated.
Also, should we be using Heimdall to avoid tripping KNOX, or sticking with ODIN 3.07?
Thanks in advance.
I dunno if you still need the help or If this will help but, as long as it is a STOCK ROM FOR THE DEVICE IN QUESTION Odin shouldn't have any issues, but I recommend a backup of the device first (from recovery) just to be on the safe side
Hello, after a search on these forums I could not find any topic about my specific problem so here goes.
I purchased a secondhand P605.
When I checked the Knox trigger it said 0x1, which made me wonder if anyone tried to root it before. It is not rooted at the moment, and I am unable to root it because Knox prevents it. I did update it to Lollipop.
So, I took to the Web and tried to disable Knox. This seems impossible, due to the fact that I don't even have permission to enter the Knox container!
Does anyone have any idea how to disable Knox when one doesn't have access to Knox at all?
Thanks in advance.
Airethilien said:
Hello, after a search on these forums I could not find any topic about my specific problem so here goes.
I purchased a secondhand P605.
When I checked the Knox trigger it said 0x1, which made me wonder if anyone tried to root it before. It is not rooted at the moment, and I am unable to root it because Knox prevents it. I did update it to Lollipop.
So, I took to the Web and tried to disable Knox. This seems impossible, due to the fact that I don't even have permission to enter the Knox container!
Does anyone have any idea how to disable Knox when one doesn't have access to Knox at all?
Thanks in advance.
Click to expand...
Click to collapse
If you updated to 5.1.1 then you need a modded kernel to root. Install TWRP, then flash new kernel and then flash supersu.
Your P605has definitely been modified either with a kernel or recovery, that's why you have Knox trigger 0x1.
Will try that , thank you.
Hi,
I rooted a new A3 (2017) sm-a320fl device for a friend using CF-Auto-Root from firmware.mobi.
However, it turns out that after tripping KNOX and blowing the eFuse automatic OTA updates are now broken.
Is there any way to return to OTA updates?
My friend would prefer to not have root and return to a newly flashed stock ROM rather than not receive automatic system updates. However, I'm not sure if this will be possible at all, now that KNOX is already tripped and eFuse blown?
And if there is no way to return to OTA updates, then what is the easiest way to install updates from now on?
I missed the whole KNOX/eFuse development and went ahead too quickly and thoughtlessly without thorough research and now I'm dreading that there may be no way back to a newbie-friendly device for my friend...
Hope some of you can help us out.
Greetings,
shevtak
Flash the latest firmware available for your country on Odin and your friend will gets updates again without root
Thanks for the quick response - I will try that.
But I'm still curious in case I run into this myself one day: Can you also tell me if there is a known place to get the update files from and install these manually on the CF-auto-root'ed system (i.e. using FlashFire)? So far, I was only able to find complete stock firmware images, but not update files...
shevtak said:
Thanks for the quick response - I will try that.
But I'm still curious in case I run into this myself one day: Can you also tell me if there is a known place to get the update files from and install these manually on the CF-auto-root'ed system (i.e. using FlashFire)? So far, I was only able to find complete stock firmware images, but not update files...
Click to expand...
Click to collapse
I don't recommend using FlashFire for flashing updates or so. With an locked bootloader it's highly to hard brick your phone ?. And yeah the only way to get the OTA's back is to flash the official firmware via Odin. A good rooting method is Magisk, you should try it out!