Related
Hey,
even though (literally) NOBODY answered my simple questions when I was desperate to figure out how to get my Note 3 rooted while keeping Knox 0x0 after I updated to MJ3 through odin to get rid of branding, here it is:
(what a long sentence lol)
I could not use Root de la Vega I was told, because I took the update to MJ3 with a different bootloader, so I had to find something else. (phone is just 3 days old lol, didnt want to trip knox yet - even if it won't matter for warranty here in europe)
WARNING: I'm not taking resposibility if you brick your phone or if things do not work as I described here, I just wanted to share the info and my experience with others. What you do with it is your own thing! I was worried that this tool is fake so I would have been glad about more infos before trying it myself..
Working for Snapdragon only afaik!
(This isnt my work and I'm not related in any way - so give those guys credit and like em on facebook etc..)
With this app I could root my German N3 with the latest stock firmware, and knox stayed 0x0.
There could still be problems - but so far it seems to work as root is supposed to work with full write access to system partition.
(adb remount did not work for me, but system was actually mounted writable to root already, and remounting system in shell did work as well).
---
Steps to get your Note rooted without having to touch odin and risking Knox flag to trip:
1. Download the android_root.exe from kingoapp.com (I'm still a bit suspicious since the thing does not have that much reputation, but who would program a working root tool just to distribute viruses etc? and its definitely working!)
2. Turn off OTA-Updates, Reactivation-Lock, Security-Updates (just to make sure - dont know if these are really necessary, but it wont hurt either)
3. Turn on USB-Debugging.
4. Install and start the android_root.exe from kingoapp.com and connect the phone when asked to.
5. Most likely it will install drivers (again... even though I had all drivers installed it downloaded the samsung drivers again, but in snail speed - so it takes a while to finish..) and ask you to disconnect/reconnect the phone.
6. It will then give you a nice big and red "Root" button, in addition to some infos.
7. Click root, and if I remember correctly there is one final step - to allow adb shell root access in su.
8. After that reboot the damn thing and enjoy root with knox still at 0x0.
9. Thank the guys who created this app (and like on facebook/twitter)!
10. (if you feel like). Click the thanks button below =)
No need to "risk it" by flashing modified odin files! (absolute noob-friendly and probably also noob-proof™ tool)
(during the whole process knox was "freaking out" a few times, the usualy prevention notification, but it seems that the kingo root tries different approaches and once it succeeded my phone did a soft reboot - screen black for a second and then booting again)
----
ADDff course your system-status will show "custom" when using this, but knox and binary counter/flag stay 0x0. I heard from some other guy that you can restore to full stock with kies 3 by just flashing the firmware you are on again. This also keeps knox 0x0 I heard, but I cannot confirm yet since who wants a non-rooted phone here anyway? =) Only useful incase you need warranty repair - then I would give it a try.
I, too, successfully rooted my MJ3 Note with this tool.
I guess the reason why most, but not all apps get succesfull root or are not able to alter some files despite obtaining root permissions from SuperSU (which itself works but can't be updated) lies with SELinux. It remains on "Enforcing".
But better than nothing and hassle free so far, :good:
saintsimon said:
I, too, successfully rooted my MJ3 Note with this tool.
I guess the reason why most, but not all apps get succesfull root or are not able to alter some files despite obtaining root permissions from SuperSU (which itself works but can't be updated) lies with SELinux. It remains on "Enforcing".
But better than nothing and hassle free so far, :good:
Click to expand...
Click to collapse
Yea its this SELinux enforcing BS apparently.
Does anyone without custom kernel have it on permissive and knox still at 0x0?
"setenforce 0" does not work (permission denied) and i cannot enter the selinux directory although its set as owned by root...
I found a few lines in init.rc which give "system" access to the enforce files, maybe if we could change this to root ..? =)
Will this work on exynos?
Sent from Note 3 (The beauty & beast)
sohebq said:
Will this work on exynos?
Sent from Note 3 (The beauty & beast)
Click to expand...
Click to collapse
No clue sorry, good you ask though. Officially the app only supports N9005 and N9006
Look what I found in the init.rc:
HTML:
# Allow system UID to setenforce and set booleans.
chown system system /selinux/enforce
chown system system /sys/fs/selinux/enforce
chown -R system system /selinux/booleans
chown -R system system /sys/fs/selinux/booleans
chown system system /selinux/commit_pending_bools
chown system system /sys/fs/selinux/commit_pending_bools
I made a version where this is all commented out, but knox that lil mofo doesnt let me write to init.rc - prevention BS again.
But how are the these things circumvented in the first place to aquire "root"? In the same way you could replace init.rc and turn that crap off that way or not?
ADD: Just a lil warning - I apparently did something that ****ed up the supersu app so it only shows a blank screen and su requests arent shown anymore. I tried reapplying the kingo root, but it wants me to allow adb shell again in superuser but i cant and then it gets stuck lol.. cant tell it to just do the root process again it seems. So I will have to go back to stock and reroot, but I'm trying all sorts of other stuff first to avoid having to do that. Not sure what caused it probably "pm enable com.sec.knox.selinux" .. after i first disabled it (probably already was disabled..and i stupidly turned it on... but not 100% sure yet that is the cause because I still had root afterwards.. but at some point it stopped working)
ADD2: Loading the firmware over kies right now, goes quite fast and when it succeeds ill report if i still got 0x0 (which I expect since someone said it works like this). If so then this would be a safe method to return to stock from rooted phone. (odin always dangerous - efs or knox..)
ADD3: OMG this kies! 100% cpu load while downloading the firmware lol? At the end it kept stalling for ages at 100% even after decompress was complete - killed it and restarted pc now i have to download everything again - and it keeps utilizing 100% cpu load (on one core, and like 50% on 2nd)
AAAAAND its gone!
I mean its there again. (the root!)
Full cycle went through without any problems or knox triggering:
1. Unbranding with stock odin file for my region from sammobile.com
2. Rooting with Kingo Root
3. (optional) Messing up root somehow... (still not sure how exactly)
4. Goin back to official status (and removing the non-working root) with Kies 3
5. Rooting again with Kingo Root
and everything with knox warranty still intact
While I still wont take responsibility what you do with your phone incase something goes wrong - I can do nothing but recommend this Kingo Root to everyone worried about the knox warranty flag - it seems completely safe (as long as nothing interrupt the process at least). With RDLV (which is also good I'm sure, but I couldnt use it since I had updated too early) you run the risk of tripping knox. At least you did with the old version where you had to find the right files yourself.
Has anyone confirmed that this root method works on Verizon Galaxy Note 3?
Sent from my SM-N900V using Tapatalk
I posted this in Sprint general section tonight. Works for Sprint version for sure L900p. I actually rooted and unrooted using app.
Link to the devs facebook fan page to like his page and ask questions.
https://www.facebook.com/kingoapp
Very few feedbacks considering the tool is compatible with Note 3 since 23rd of october...
Is it for real or not ?
Have you been able to update su binary?
Yes it works. A Mod closed my sprint thread. He stated we can't link to work outside of XDA. Weird since I been a member since 2006 I never heard of that rule. Most of the development comes from outside xda. Anyways yes it does work perfectly.
Sent from my SM-N900P using Tapatalk
CSC change !
I managed to change the CSC code to CYO >> XEF (France) without triggering Knox and with MJ3 ! :good:
Root with Kingoapp (download program, switch off reactivation lock OTA upgrades etc and activate USB debug, lunch the program, connect the phone, click root, allow debuging on the phone, wait, ignore message at screen, phone reboot, done !)
Use a root file explorer (Root explorer works for me) go to system/csc and search your actual CSC, normally there is 2 folder inside "csc_contents system and" move these folders to a safe location ( ex, PC )
Again in system/csc, look the code you want to apply, enter the folder, copy the two folders "and csc_contents system" and paste in the folder of your current code.
Make a full wipe with restore save menu, the phone reboot, after restart, switch off the phone and reboot in recovery, look at the bottom line "Applied the CSC code :" if your code is here, win !
Note : Root survive after full wipe.
jerem52 said:
I managed to change the CSC code to CYO >> XEF (France) without triggering Knox and with MJ3 ! :good:
Root with Kingoapp (download program, switch off reactivation lock OTA upgrades etc and activate USB debug, lunch the program, connect the phone, click root, wait, ignore message at screen, phone reboot, done !)
Use a root file explorer (Root explorer works for me) go to system/csc and search your actual CSC, normally there is 2 folder inside "csc_contents system and" move these folders to a safe location ( ex, PC )
Again in system/csc, look the code you want to apply, enter the folder, copy the two folders "and csc_contents system" and paste in the folder of your current code.
Make a full wipe with restore save menu, the phone reboot, after restart, switch off the phone and reboot in recovery, look at the bottom line "Applied the CSC code :" if your code is here, win !
Note : Root survive after full wipe.
Click to expand...
Click to collapse
I thought it was not possible to get a recovery mode, without triggering the Knox flag ?...
Dit you got the recovery mode during the Kingo Root procedure ?
HokutoNoFred said:
I thought it was not possible to get a recovery mode, without triggering the Knox flag ?...
Dit you got the recovery mode during the Kingo Root procedure ?
Click to expand...
Click to collapse
No need recovery for kingo, just download and install the program on PC, on the phone, turn on usb debugging, turn off reactivation lock and automatic upgrade (it may not necessary, it's to avoid surprise with upgrade ) connect the phone, wait on kingo, click Root, Wait, some message pop on the phone, ignore it, phone reboot and root is okay, after you can do the steps for CSC, but when i said Recovery it's the stock recovery.
Edit : I forget one thing, when you connect the phone in usb debug,the phone show a pop up to allow or not debugging, the one must be yes, if not kingo can do nothing
Why are you changing the csc code? Your updates should work without changing the csc. If you decide to unroot everything is restored as well.
Sent from Heaven.
dallastx said:
Why are you changing the csc code? Your updates should work without changing the csc. If you decide to unroot everything is restored as well.
Sent from Heaven.
Click to expand...
Click to collapse
I also think it is not necessary, it is to be certain that there was no conflict or problem with other applications or network settings.
jerem52 said:
No need recovery for kingo, just download and install the program on PC, on the phone, turn on usb debugging, turn off reactivation lock and automatic upgrade (it may not necessary, it's to avoid surprise with upgrade ) connect the phone, wait on kingo, click Root, Wait, some message pop on the phone, ignore it, phone reboot and root is okay, after you can do the steps for CSC, but when i said Recovery it's the stock recovery.
Edit : I forget one thing, when you connect the phone in usb debug,the phone show a pop up to allow or not debugging, the one must be yes, if not kingo can do nothing
Click to expand...
Click to collapse
OK, I didn't know there was a stock recovery.
I thought recovery was always something related to root or smartphone tuning.
So if I understand well, I just have to :
- upgrade my Note 3 with the last official ROM (N9005XXUBMJ3_N9005OXXBMJ3_N9005XXUBMJ2_HOME.tar.md5)
- download and execute Kingo
And then my Note 3 should be BMJ3 with root access and knox still to 0x0.
PS: regarding your CSC issue, what was your ROM version before the BMJ3 ?
(maybe your CYO status was due to the BMJ1 ROM from SamMobile)
And how does it work with the updates? Unroot via superSU app, then enable OTA, update and after that again Kingo Tool to root again?
HokutoNoFred said:
OK, I didn't know there was a stock recovery.
I thought recovery was always something related to root or smartphone tuning.
So if I understand well, I just have to :
- upgrade my Note 3 with the last official ROM (N9005XXUBMJ3_N9005OXXBMJ3_N9005XXUBMJ2_HOME.tar.md5)
- download and execute Kingo
And then my Note 3 should be BMJ3 with root access and knox still to 0x0.
PS: regarding your CSC issue, what was your ROM version before the BMJ3 ?
(maybe your CYO status was due to the BMJ1 ROM from SamMobile)
Click to expand...
Click to collapse
Before it's branded with operator rom (BOG code > french Bouygues telecom, i dont remember version) i install latest version with kies recovery ( with french youtube video of unboxing, spot a S/N from a unlocked version and kies download the last unbranded version and install it :good: , but after, CSC code is CYO )
I use kingoo root because the MJ3 has a new bootloader and its nots possible for me to root with dela vega method, but it's not a "full root" some applications does not work, ( ex root unistaller ) maybe it's better fo you to root with de la vega, you have the root and the MJ3 but not the problematic last bootloader.
@ korny10 I dont try unroot, in download sytem is "Custom", i think a flash with stock rom and and everything was back to normal
Hi,
after reading some information about the FRP, a perhaps possible way to bypass it on Samsung devices came into my mind:
After all, the only thing one has to do is somehow managing to open the settings app. From there, one can do a factory reset which will erase the FRP partition. There are already lots of ways to do so, mostly by exploiting "holes" in the UI.
And of course, the FRP is never really secure; as it relies on the inaccessibility of the phone's internal storage. So if one is able to write the flash by some means (for example JTAG), getting rid of the FRP is pretty much straightforward.
This to be said, just to assure you that I don't plan anything malicious. I'm just curious about Samsung's and Android's security measures, and I don't own any recent Samsung device (with FRP) to try it myself.
But now my thoughts: If FRP is active, from what I read one could not boot unsigned binaries flashed by Odin. But Odin seems to flash these images; it appears that it just blocks the boot.
The next point that flashing+booting modified firmware without triggering the Knox flag is possible. From what I read, the kernel and recovery must stay stock. Apps can change. So I assume that it behaves similar with FRP.
This brought me to an idea: Maybe one could modify a stock image so that one could get to a settings screen, flash it via Odin, boot it, open settings, do the factory reset, and do whatever you want form there.
As a modification, I would suggest just deleting the Gapps from the image; then the phone will never ask for a google account. Or put in one of the apps commonly used to bypass FRP by USB OTG.
The key question is: Will the device boot the modified image, or will one get the "Custom binary blocked by FRP" error?
Hi,
I've one (big) problem that I can't fix.
I've been using Android 5.0.1 for more than 1 year as I didn't want to upgrade (it worked pretty well) and because I had the S6 rooted with PingPong root.
However, one month ago it started to run slowly, crashing apps, ... so I decided that, as I wanted to wipe the device, why not upgrade to MM (6.0.1)??, so I did.
I did a backup of all my data and EFS folder and downloaded a 6.0.1 ROM to flash it with ODIN. Everything went OK and finished flashing the rom, but when the S6 restarted it showed this in the recovery:
'dm-verity verificztion failed...
Need to check DRK first...'
And I cant boot.
I've tried some tips that are here and in other websites:
- I've flashed stock rom again
- I've flashed a stock rom without cache.img file.
- I Can't flash some files as I've R/L ON. (I've been trying to disable it for many months but I couldn't).
But the S6 doesn't boot...
Thank you!
What worked for me.
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Critical_DoubleShot said:
So this is my current issue, but i was able to resolve the issue you are having. so what i did was get the 5.1X OK7 (My phone is Verizon) firmware and flashed through ODIN 3.12.5, this flashed stock 5.1.1 in my phone and it worked good. however i have issue with my phone random restarts and power button not working in recovery or in rom. however i can go in and out of downloading mode or maintenance mode.
Click to expand...
Click to collapse
Thanks for your reply!
I tried to downgrade to 5.1.1 or 5.0.1 but I get an error.
(SW REV CHECK FAIL DEVICE 2 BINARY 1)
That happens when you don't have the right firmware you have.
You CANNOT downgrade to 5.1 or 5.0 since you are on 6.0. The bootloaders refuses to be overwritten.
Critical_DoubleShot said:
That happens when you don't have the right firmware you have.
Click to expand...
Click to collapse
I'm trying to flash another 6.0.1 ROM (a bit older), but I get 'CHECK FAIL. DEVICE: 4, BINARY:3'
I've read that DRK problems are related with EFS files, so... Can I restore EFS folder (I've a backup from Android 5.0.1) to solve?? I don't know how to restore it without booting into the sistem (and without custom recovery)
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thank you for your reply!!
I had the device rooted, but with PingPong root, so Knox is still 0. However it shows that the system is "custom".
I'll try the warranty, they may not notice the "custom", just the knox.
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
orbgel10 said:
I'm with the same problem when trying to flash stock BTU QA7..and only if i flashing cf_root my phone is booting.
Any idea? I don't care about the Knox..
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
If you are talking about DRK, the only way to fix it that I know of, other than hw replacement, is via 3rd party professional repair tool. (Octopus/Octoplus box)
If DRK is ok, phone boots normaly, if it is messed up, the only way of booting is with custom kernel which bypass DRK check.
You can check it in recovery, if messed up it will say DM verity failed on bottom of the screen.
Ok, i send my phone to fix, i will tell you what happened.
Sent from my Redmi 3S using Tapatalk
brenner650 said:
I am afraid that downgrade to 5.0.1 is not possible, at least I dont know anyone who succedeed in doing that.
If you were on systemless root, probably your Knox is still 0, check it in DL mode, if it is and you have the phone less that 3 yrs (1 yr warranty+2yrs factory warranty) best solution would be to ask in Samsung repair center if the factory warranty would be accepted (ofcourse dont mention flashing, just say you tried official update, and play dumb).
If not you can try custom kernel wich will bypass DRK, and prolly make the phone bootable, but there is no guarantee everything will work well (maybe it will, but mostly it doesnt, forget using Samsung pay, and KNOX tripped)
As for EFS, maybe I am wrong, but I think EFS contains IMEI and sn info, and DRK is something else.
Click to expand...
Click to collapse
Thanks for your reply!!.
I took my S6 (925F) to a Samsung service center as you said. However, they told me that my S/N was incorrect (I bought a second-hand S6 edge, I think someone changed it) so they couldn't fix it.
Now I'm trying to use SmartSwitch to do a factory reset but it asks me for the S/N and I don't have the original one, just a S/N from a non edge S6 (920F). How can I do the factory reset without my S/N??? Can I use the serial number from another 925F??
Now I'm trying to find an engineering bootloader, to bypass the R/L and flash CF-AutoRoot, custom recovery.... but I only find it for 5.0.1 or... for galaxy S6 G925T, not F.
Finally, I managed to fix my S6 by myself!! (not really, but at least it boots...)
This is what I did:
- I found a factory binary for my S6 so I flashed it via ODIN
- I flashed a 6.0.1 ROM without hidden and without cache
Then it boots without any problems. However, now I can't get into recovery
I hope this will help someone
Hi,
1- I was asked by the family to help unlock the phone of a tragically and untimely deceased person.
I do NOT want to reset !!!!!!!!, must recover photos, whatsapp and more
2- Phone is pattern lock, SM-G930F
3- phone is active and can receive calls
4- FRP lock: ON
5 - USB debugging: OFF
6 - I have access to google account, but it says "cant locate active phones"
7 - phone is registered in "Google Play"
I would appreciate and assistance, the family is really heart broken and waiting or this.
Thanks, Harris
The phone must be connected to a network, in order to find it using android device manager. Or else you need a custom recovery to remove the lock screen key. Or ADB, I don't know the exact method but try searching for removing lockscreen security using ADB.
Most services will provide access to an account if you provide a valid death certificate, that may be an option in getting the google account credentials to unlock FRP.
I would like to help you if you still having this problem
Is it a bit 1 or a bit 2 G930F check this is download mode will be under AP SWREV: B:1=BIT 1 AP SWREV: :B:2=BIT 2 if bit 1 just find a full version of the bit 1 combination file it will have FXXU1 as part of the file name or FXXU2 for bit 2 REMOVE THE .PIT FILE from combination though first of there is one this will wipe the device,
flash in the AP tab of odin let it boot, once booted in the top left tap the menu icon now look for an app with a folder icon all personal data is stored here, this works for S8 with combination file but im not sure as i havent tested on S7 before with it also DO NOT flash a bit 2 binary to a bit 1 device you will never be able to use bit 1 firmware of any kind again after flashing with a bit 2 firmware and also if the knox counter is tripped the comhination files will not boot on the device for some reason i have confirmed this with a knox tripped and non knox tripped device so it cannot have knox 0×1 - 0x50c - 0x500 for some examples
If the app isnt there with personal data then just flash the device with stock firmware again but DO NOT use the CSC you MUST USE the HOME_CSC as this will keep all data and apps in place and will take you straight back to the lock screen again,
If adb were enabled i would of been able to help you out but theres no way to enable adb without the risk of losing the personal data on the device
Good Morning Everyone
As the title suggests, i am looking to return my S22 Ultra back to stock.
i was on beyond rom for a bit, but too many apps complaining that my device was rooted has forced my hand to return my device back to stock once again.
I flashed the stock rom via odin, then locked my bootloader and wiped all data.
However i am still getting messages that my device is modifed.
Anyone got any ideas how to can truely return to full stock?
Thanks in advanced.
And yes i did do a search on the internet before asking, but i have been unable to find any advice outside of what i have already done.
happend to me, too. But only on the latest firmware. When I flash an older firmware, it won't appear. But after updating again to the latest ROM the message appears
Cheers mate. I'll give that a go.
Also note that if the device was rooted then you triggered the Knox flag and that one CANNOT BE RESET, it's an "efuse" (a hardware component that once changed it's state can only be reset by replacing it, i believe you need to replace the entire motherboard for that).
So, if the application checks the Knox status it will fail.
Here are a few apps that i know that will not work anymore :
- Knox itself (and any app that uses the Knox library/API )
- Samsung Pay
- Samsung Health
- Secure Folder
A few years ago I also had a banking app that failed to worked with a Knox flag triggered (on a Note 8), but after an update it allowed me to use the phone as long as i didn't have it rooted.