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
Related
Hi,
I just got my Note 3 and was annoyed by the hole knox issue so i started to read back & forward after a few hours i found this program called kingo which i liked cause i only had to install it and start the program and the rest was done for me by the program.
Here are the easy steps to rooting.
1. Install the Note 3 drivers on the PC "all i did was plug-in the phone and it was installed for me".
2. Install Kingo (LINKS REMOVED)
3. Open the program and follow the simple instructions on you monitor.
When it's done you are rooted and your knox will still be 0x0.
After this i used Odin to flash the TWRP 2.6.3.7 and the knox was still 0x0.
I then shut off the phone to reboot into TWRP and did a backup of the stock rom rooted. Once done backing up the rom i rebooted into download mode and noticed that it knox was changed to 0x1.
So if you want root on stock rom then this is the easiest solution but you wont get custom recovery nor custom roms without tripping the knox counter for now.
Great does it work with latest stock firmware mj7
Sent from my SM-N9005 using Tapatalk
Doesn't work with MJ7, as posted on their Facebook page.
I did this with MJ2
Zionator said:
I did this with MJ2
Click to expand...
Click to collapse
If you did not absolutely need a custom recovery/kernel you should have gone with URDLV and you could have kept knox 0x0
xclub_101 said:
If you did not absolutely need a custom recovery/kernel you should have gone with URDLV and you could have kept knox 0x0
Click to expand...
Click to collapse
I have no idea what you are talking about.
Zionator said:
Hi,
I just got my Note 3 and was annoyed by the hole knox issue so i started to read back & forward after a few hours i found this program called kingo which i liked cause i only had to install it and start the program and the rest was done for me by the program.
Here are the easy steps to rooting.
1. Install the Note 3 drivers on the PC "all i did was plug-in the phone and it was installed for me".
2. Install Kingo from here.
3. Open the program and follow the simple instructions on you monitor.
When it's done you are rooted and your knox will still be 0x0.
After this i used Odin to flash the TWRP 2.6.3.7 and the knox was still 0x0.
I then shut off the phone to reboot into TWRP and did a backup of the stock rom rooted. Once done backing up the rom i rebooted into download mode and noticed that it knox was changed to 0x1.
So if you want root on stock rom then this is the easiest solution but you wont get custom recovery nor custom roms without tripping the knox counter for now.
Click to expand...
Click to collapse
As far as I know Kingo is banned on XDA forums until further notice, unless they finally got approved? Not to get you paranoid or anything, but suspicious communications with a chinese server were part of the rooting method you just used.
blumsen said:
As far as I know Kingo is banned on XDA forums until further notice, unless they finally got approved? Not to get you paranoid or anything, but suspicious communications with a chinese server were part of the rooting method you just used.
Click to expand...
Click to collapse
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Zionator said:
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Click to expand...
Click to collapse
It was suspected of sending your IMEI #. Don't know the details.....
Zionator said:
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Click to expand...
Click to collapse
1. It is suspicious because nobody knows who Kingo are. It is suspicious because the process is not transparent and it was not known what kind of information is collected from your device (or why) and what information is received (and possibly installed on your PC/ device). The exploit that they use for rooting is also kept secret. The server's IP they use is chinese. Some of the information they collect is arguably not necessary (for example your device's IMEI). The communication with Kingo is over a facebook page. Hmm.. can't think of more suspicious things right now, but that is plenty I think
2. "It is most likely just.." yes that is true. and for 99% of users that is good enough. Myself, I will lose my job if my clients/ employers find such a huge security hole which I am aware of and ignore. But then again they also expect me to never get near the WWW with my work phone or computer, I am not allowed to have a wifi module in my work laptop! You can see why a "probably just a harmless connection to China" is just not good enough in some situations.
3. If you do a search on XDA for Kingo, you will see that all threads were closed by admins.
4. Time for you to get a new firewall, or tinker with the settings!
Zionator said:
I have no idea what you are talking about.
Click to expand...
Click to collapse
With firmware before MJ3 there is a separate method called Universal Root De La Vega (URDLV) which is a lot more transparent and which (as long as you keep updating with Mobile Odin Pro and you do not change stock kernel and stock recovery) is giving you full root while keeping your Knox 0x0 (if you had it 0x0 before URDLV).
xclub_101 said:
With firmware before MJ3 there is a separate method called Universal Root De La Vega (URDLV) which is a lot more transparent and which (as long as you keep updating with Mobile Odin Pro and you do not change stock kernel and stock recovery) is giving you full root while keeping your Knox 0x0 (if you had it 0x0 before URDLV).
Click to expand...
Click to collapse
Oh ok but i have already flashed a custom recovery and rom. To hell with the warranty. I have never liked any stock roms and i like my freedom so my knox will most likely look like 0x2 now.
Kingo : Well if it's that bad then i am sure the moderators will close this and had i known this was the issue then i wouldn't have made this thread. However i would still have used this method if i knew this before as i never stay on stock rom and after finding out about the stupid chip that cant be recoded i didn't wanna wait for someone to come with a solution in one years time so i flashed the rom and recovery and now enjoying the phone
So if the Kingo really is that bad it has been wiped from my phone when i flashed a new rom.
Does not belong in Original Development, you did not create Kingo.
Moved to General
Use at your own risk. Rooting process has been known to collect and transmit IMEI and Serial numbers to China
FNSM
Before I even read the posts and start asking questions, I would like to know one thing. That is what does that United Arab Emirates mean in the pic below, its my screen after entering "About"
and can I root my device without any sort of issues?
iTTi said:
Before I even read the posts and start asking questions, I would like to know one thing. That is what does that United Arab Emirates mean in the pic below, its my screen after entering "About"
and can I root my device without any sort of issues?
Click to expand...
Click to collapse
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
kennyglass123 said:
Does not belong in Original Development, you did not create Kingo.
Moved to General
Use at your own risk. Rooting process has been known to collect and transmit IMEI and Serial numbers to China
FNSM
Click to expand...
Click to collapse
Just FYI - but Kingo stopped collecting the IMEI numbers a few versions ago.
mvansomeren said:
Just FYI - but Kingo stopped collecting the IMEI numbers a few versions ago.
Click to expand...
Click to collapse
That is great news! Our security expert has not been available to confirm this and Kingo has not sent us any correspondence to notify us of that. Has anyone confirmed this by recording data traffic while rooting?
Ok i have been reading around the net and all the reported security issues comes back to XDA.
wmshua.com is the site the connection is sent out to but is it possible that the app connects to their servers only in order to download the appropriate phone/device drivers.
On there web site under F.A.Q's
Q. Why don't you publish your source code?
A1. We kind of hope, in the future, Kingo Android Root could generate revenue to support our staff (STILL FREE FOR USERS). We all know that, in the long run, interest alone cannot make a living. To develop better software, we need to be financially motivated aside from being driven by passion.
A2. We manage to obtain root privilege of Android by exploiting certain undisclosed vulnerabilities, which we believe would be patched in no time once made public. And that would dysfunction this software that we've worked so hard for.
Click to expand...
Click to collapse
However it pushes Chainfires SuperSU to the device's and apparently they didn't ask him for his permission to use his work.
All in all i don't think isn't a matter of security issue anymore but more likely a matter of hard fellings that they stole Chainfires SuperSU to use in there app without asking him.
Correct me if i am wrong ?
xclub_101 said:
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
Click to expand...
Click to collapse
Knox 0x0 is the warranty thingy right? I have no warranty. So whats next?
xclub_101 said:
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
Click to expand...
Click to collapse
Is it not possible to root MJ7 using knigo! or rooting MJ7 using kingo will trigger knox ?
Temp Root on LG G Stylo LS770 M 6.0 ( Boost / Sprint )
Attention if you decide to try this and end up with a BRICK / Expensive paperweight or your device decides to transform and destroys your home town that's on you. You have been warned . So just read all of this instructions (and read the O.P more then once)
I can confirm temp root on the LG G Stylo LS770 M 6.0 ( Boost / Sprint ) . Perm root will work with Android OS 2.1 - 5.1 & TEMP Root for Android OS 6.0 - ?
Downloads
Download King root ( Suggest from their website and not the Play store ) http://www.kingroot.net/
Download BusyBox from the Play store ( I suggest BusyBox from Jrummy ) https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=en
Download a Root Cheaker to verify root , I suggest https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Instructions
Download all the necessary APP's and Files .
Run KingRoot and just follow the in app instructions ( Normally you will get to around 23% and the app will say failed to root device but it hasn't yet for me )
Run whatever Root checker you decided to download and verify root ( if you didn't obtain root just run KingRoot again )
Run and install BusyBox
PROFIT
Now you are able to use Apps and Mods until you re-boot your phone.
-Permanent root is reversible, open the app and there will be a button to unroot
-Temporary root will be removed after a reboot
Temporary root
These are usually one-step apps that you install on your phone, and they give you root access until the next time your phone is restarted. They are a great way to get your feet wet,and you can do a lot with them -- both good and bad. The ease of use makes temporary rooting pretty popular, and it's a fine choice if your reasons for rooting are to use root-enabled apps from the Market.
That being said, some apps just aren't going to work unless you go all out and permanently root your phone. This depends a lot on which phone you're using, as manufacturers have an endless supply of dirty tricks to keep the hardware you paid for under lock and key. You'll either have to ask users with the same model as you're using, or use trial and error. The good news is that the popular root-enabled apps, and the ones you're most likely to want to use should work without a problem. Titanium Backup, Wireless Tether, Root Explorer and the like should do just fine.
The last thing to keep in mind, is that not all changes will be permanent. For example -- using a utility to "freeze" bloatware (applications from your carrier that you don't want or need) may not keep them frozen and hidden after a reboot. Also some of the newer HTC phones have an evil little bug a feature that reverts any changes you have made to the system, bringing it back to the way it was before you started hacking away at it. In those cases, the only fix is to perma-root your phone.
Permanent root
This is where things get a bit hairy. Some phones, like the Nexus One, don't need to be rooted -- they can be unlocked via the Android SDK and modified at will. Other phones, like the OG Droid, are really easy to root, and will only take a few minutes. Finally, some phones, like the T-Mobile MyTouch 4G force you to jump through flaming hoops and follow often cryptic instructions, laden with warnings about bricking your phone. That's a whole 'nother rant for a different venue, but it does need said so that you know what you may be getting yourself into. You'll need to do your homework, ask any questions you feel are unanswered or are unsure of, and weigh all this into your decision. Everyone who says "It's easy!" (including me) really means they found it easy -- that doesn't necessarily mean you will.
Now that I've sufficiently scared you, it's time to talk about why anyone in their right mind would go through this. Besides the advantages of keeping changes persistent between reboots, and those few Market apps that won't work with a temp-rooted phone, you have what many consider the best part of owning an Android phone -- custom ROMs.
To flash any custom recovery, kernel, or ROM, you're going to need to have permanent root access to your phone. Flashing new firmware is very low level stuff, and you need read and write access to everything. The good news is that usually the rooting is the most difficult part, and a custom recovery gives you access to a tool that can take a snapshot of your system, and save it as a restore point. That's a good thing, because once you start flashing, you're hooked -- and a single command restore is priceless.
Hopefully I've helped a little in your decision making, and remember -- there is always help in the XDA forums. Find the specific area for your model of Android phone, and look for the link at the top to the hacking section. Those guys live for this stuff, and will steer you in the right direction.
LG G Stylo LS770 MM Restore Files
Due to the overwhelming private messages about kingroot and other rooting apps softbricking phones i have posted a fix for the Boost Mobile LG G Stylo LS770 on MM (6.0) . Here are all the files needed to restore a bricked LS770 on MM .
Needed Files:
https://mega.nz/#F!SM9iQILQ!vr9cFE8wxGnqUxvJ0Pr-Og
instructions:
http://forum.xda-developers.com/showpost.php?p=64624324&postcount=2
(Most users can skip step 8)
Somehow after freezing few apps most Google one, rebooted and got code: 1003 system been modified and stuck in boot loop at initial boot, just reboots after LG logo. Tried to factory reset and LG tool, already running 6.0 latest OS. Had root, busy box easy install and rebooted it, stuck. Soft brick?
I'm sorry to hear that , I've personally never had a problem uninstalling apps on the LG G Stylo but i only really uninstall the bloat from my carrier . There is a Safe To Debloat Guide for our phone but I haven't personally tried it out yet .
Sadly we don't have the KDZ file for our phone so you cant just simply re-flash your phone . But hopefully that doesn't mean we cant get your phone back up and running . There are a few different things we can try .
Can you give me all the information about your phone as you can like carrier, model number , software version and so on .
Linux215 said:
I'm sorry to hear that , I've personally never had a problem uninstalling apps on the LG G Stylo but i only really uninstall the bloat from my carrier . There is a Safe To Debloat Guide for our phone but I haven't personally tried it out yet .
Sadly we don't have the KDZ file for our phone so you cant just simply re-flash your phone . But hopefully that doesn't mean we cant get your phone back up and running . There are a few different things we can try .
Can you give me all the information about your phone as you can like carrier, model number , software version and so on .
Click to expand...
Click to collapse
Boost Mobile
LG LS770 / ZNFLS770
6.0 ROM
KingRoot
Rom Toolbox Pro
Busybox
Froze All google bloatware and bloatware and backed it up before freezing and re-booting
and
[650] or [640] 7 lines straight down
----------------------------------------------
Secure booting Error!
Error Code : 1003
MODIFIED !!
----------------------------------------------
Thank you for the information.
Lets start by seeing if just flashing the latest Update zip for M 6.0 will get your phone back up and running. It should take you back to stock and update the system file . it's a untouched update zip .
You can find all the necessary files, downloads and instructions here.
https://mega.nz/#F!PksQAaoA!tgopiux4KU849_yta4zHlg
Thank you for the file
What extSD partition should be in and what size should it be? It's in FAT32 64GB right now
Re-sizing it into 8GB FAT32 then will try exFAT and then NTFS still in 8GB
Recovery displaying failed to mount extSD, failed update from External SD
Will update after changes for the next 30-60 minutes
=========================================================
[LGE][RECOVERY] first_status is 6
Supported API: 3
E:failed to mount /sdcard (Unknown error 150)
-- Couldn't mount /sdcard.
Installation aborted.
==========================================================
Got into ADB bootloader and after # I get
Hello, I am LAF, Nice to meet you. #
---------
I can list folder contents in device #ls
as soon as I try to open any folder I get Hello, I am LAF, Nice to meet you. #
You got LAF ..... Ive only ran into her a couple times and i still dont understand if she's mocking us .
But don't partition anything quit yet , we might be able to just flash the system img with a command line . Do you have adb and everything set up ?
I'll be able to help more when i get home from work .
Here's a helpful video from YouTube that might help https://youtu.be/Za9H7TgeZ50
, i will be leaving all the LG files in my cloud just in case you need the original zip
I just went out and got me another one. I tried ADB and it was all LAF constantly.
Will wait till stable root available and possibly unlocked bootloader, 6.0 got it locked pretty complicated.
Ya they did a number on locking this device . How were you able to get a replacement so fast ?
I'm just hoping we can get fastboot working so we don't have these types of problems.
Linux215 said:
Ya they did a number on locking this device . How were you able to get a replacement so fast ?
I'm just hoping we can get fastboot working so we don't have these types of problems.
Click to expand...
Click to collapse
PM'd you
Any way to root boost mobile only to edit hosts file and then un-root to prevent LAF lock-down?
I'll actually test if editing the build prop with temp root will allow the change to stick after a reboot .
Ive been spending all my free time trying to get fastboot running to tinker with temp root to much .
STAY AWAY FROM KING ROOT! I used King Root last night to obtain root on Marshmallow for my LGMS631 running the official T-Mobile update. Root was successful however the system became very unstable to the point which I decided to unroot and uninstall King Root completely. After restarting my phone I was prompted with Secure Boot Error and MODIFIED. If I didn't have access to a stock KDZ my phone would have been a complete paperweight with no other choice but to send it in to LG for repair. My suggestion to all LG G Stylo users that are not with T-Mobile or MetroPCS will be that you avoid King Root at all costs. Without a KDZ and the LG Flash Tool you will nit be able to recover from a soft brick.
No KDZ available for Boost/Sprint
Anyone got a way to edit hosts file?
Do not root 6.0 boost until bootloader has been unlocked.
it will need to be rooted
it will need to be rooted
as stock marshmallow 6.0 uses too much memory upto 886 mb
only 65 mb free
As of right now we haven't been able to pull the system.img
Sent from my LG-ls990 using XDA-Developers mobile app
Doesnt look like any root for us virgin, boost or sprint stylo owners, shame. Glad its just my sons phone.
HD-man said:
Any way to root boost mobile only to edit hosts file and then un-root to prevent LAF lock-down?
Click to expand...
Click to collapse
Yes. I did replace the hosts file with using kingroot. I rebooted and was fine. I later bricked it doing something else and sent it to LG for free repair. I haven't rooted since. Isn't there the tot files posted to recover from a brick on Boost?
Now I'm using NetGuard (here on XDA) that uses a VPN instead of root to implement a hosts list. I also have my DPI set to 270 but that can be done via ADB without root. :]
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
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Nightcatfisher said:
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Click to expand...
Click to collapse
You need to edit the build.prop
Look for ro.config.tima and change the "1" to a "0".
You can either use a app like root explorer or BuildProp Editor.
You will have to root to fix this as it is using Knox to detect the past root/recovery flash.
Once you trip knox with twrp / root you can undo that.
Rooting alone shouldnt be giving you any trouble?
What problems were you having that made you want to go stock with no root?
DeeXii said:
You need to edit the build.prop
Look for ro.config.tima and change the "1" to a "0".
You can either use a app like root explorer or BuildProp Editor.
Click to expand...
Click to collapse
I wonder where you got this little tidbit of advice from...
https://forum.xda-developers.com/showthread.php?p=71995091
Nightcatfisher said:
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Click to expand...
Click to collapse
just downgrade to 6.0.1 with odin, start s health and let the phone upgrade it`s self to 7. Worked for me
Hi everyone !
For noob user like me : root S7 = risk to no more working knox samsung app : mainly samsung pass / secure folder. Sad i've didn't seen that before rooting -_-
For others : I prefer to open a new thread, because i've read many post about knox problem or only pass or only secure folder after root... people saying yes, no, work, don't work, update, offical stock rom, snapdragon, magisk, or nothing :/
I got a S7 G930F from France (exynos?), now model version show g930fxx4esc5, i've try root, pass, [...] and no more knox app.
- I've seen index-samsung-galaxy-s7 thread, put oem unlock, followed CF-Auto Root link http://autoroot.chainfire.eu/
> alert : KNOX WARRANTY : If you have a KNOX-enabled device, using CF-Auto-Root will trip the KNOX WARRANTY VOID status ! (but didnt know what it mean XD)
> site didn't looked noob friendly to me so i looked for another one......
- Then I've followed a french link : https://www.androidpit.fr/comment-rooter-samsung-galaxy-s7-et-s7-edge
> So i took files on this page, without using more my brain -_- (didn't seen page is dated 2016... and dunno if the auto root file must be a strict model version...)
- odin said pass ! Samsung pass and secure folder dont work... T-T (i've noted my model version g930fxx4esc5 dunno if it was same before)
> with the message error I got the bad idea to remove oem unlock (perhaps it was bugging the app XD)
- then.... verification problem at boot... reinitialise dont work, useless, wipe...
> So i put my brain finally on, xda, i tried to get back official stock rom version g930fxx4esc5
- from samfirm depreciated thread i've found this site : https://updato.com/firmware-archive...=XEF,BOG,FTM,SFR&v=Oreo(Android+8.0.0)&rpp=15
- update all 4 files in ODIN BL / AP / CP / CSC, phone work but knox is 0x0500 and still no Spass no Secured Folder. Here i am :/
Général questions :
1- These knox problems are only for s7 exynos ?
2- Root and samsung pass never work ? still have someone who say yes
3- Rooted and now unrouted and samsung pass don't work ? still someone who say yes
4- unrooted + full wipe + stock rom and samsung pass don't work ? must i have to try several official rom perhaps ? trying will fail my knox more ? still someone who say an official rom will work
5- Other root method could have work with knox ? but too late if already rooted ?
For me, S7 exynos, R16NW.G930FXXS4ESC5, knox 0x0500 :
6- How did i mistake ? Like i'm not in knox 0x1 but 0x0500 do i have a try ? or if i try i'll have 0x1 and no more try ?
7- Can i have back knox related apps or almost same apps (mainly samsung pass and secure folder) ?
8- Can i go back to initial stock rom ? a real samsung official rom ?
9- Can i try again following from http://autoroot.chainfire.eu/ then this link https://desktop.firmware.mobi/ look for G930F, take the R16NW.G930FXXS4ESC5 version who has the same than my phone ?
10- Must i follow post like : https://forum.xda-developers.com/s7-edge/how-to/samsung-pay-knox-warranty-void-t3549449 or it will be worst hard to get back to normallity ?
11- What is Magisk ? before rooting ? after rooting ? for rooting ? Can i try magisk solution ? or it will be worst hard to get back to normallity
12- On french support samsung-forum just say go in samsung store they got tool to repair with a real official rom for 40€ . i dont believe.
edited : 13- Like that can i still have samsung android updates ?
If no solution to get back samsung pass and secure folder, i'll re try to root phone at least i'll have that, even if knox go to 0x1 it won't be worst ? others problem with app on a rooted phone ?
Yotitchy said:
Hi everyone !
For noob user like me : root S7 = risk to no more working knox samsung app : mainly samsung pass / secure folder. Sad i've didn't seen that before rooting -_-
For others : I prefer to open a new thread, because i've read many post about knox problem or only pass or only secure folder after root... people saying yes, no, work, don't work, update, offical stock rom, snapdragon, magisk, or nothing :/
I got a S7 G930F from France (exynos?), now model version show g930fxx4esc5, i've try root, pass, [...] and no more knox app.
- I've seen index-samsung-galaxy-s7 thread, put oem unlock, followed CF-Auto Root link http://autoroot.chainfire.eu/
> alert : KNOX WARRANTY : If you have a KNOX-enabled device, using CF-Auto-Root will trip the KNOX WARRANTY VOID status ! (but didnt know what it mean XD)
> site didn't looked noob friendly to me so i looked for another one......
- Then I've followed a french link : https://www.androidpit.fr/comment-rooter-samsung-galaxy-s7-et-s7-edge
> So i took files on this page, without using more my brain -_- (didn't seen page is dated 2016... and dunno if the auto root file must be a strict model version...)
- odin said pass ! Samsung pass and secure folder dont work... T-T (i've noted my model version g930fxx4esc5 dunno if it was same before)
> with the message error I got the bad idea to remove oem unlock (perhaps it was bugging the app XD)
- then.... verification problem at boot... reinitialise dont work, useless, wipe...
> So i put my brain finally on, xda, i tried to get back official stock rom version g930fxx4esc5
- from samfirm depreciated thread i've found this site : https://updato.com/firmware-archive...=XEF,BOG,FTM,SFR&v=Oreo(Android+8.0.0)&rpp=15
- update all 4 files in ODIN BL / AP / CP / CSC, phone work but knox is 0x0500 and still no Spass no Secured Folder. Here i am :/
Général questions :
1- These knox problems are only for s7 exynos ?
2- Root and samsung pass never work ? still have someone who say yes
3- Rooted and now unrouted and samsung pass don't work ? still someone who say yes
4- unrooted + full wipe + stock rom and samsung pass don't work ? must i have to try several official rom perhaps ? trying will fail my knox more ? still someone who say an official rom will work
5- Other root method could have work with knox ? but too late if already rooted ?
For me, S7 exynos, R16NW.G930FXXS4ESC5, knox 0x0500 :
6- How did i mistake ? Like i'm not in knox 0x1 but 0x0500 do i have a try ? or if i try i'll have 0x1 and no more try ?
7- Can i have back knox related apps or almost same apps (mainly samsung pass and secure folder) ?
8- Can i go back to initial stock rom ? a real samsung official rom ?
9- Can i try again following from http://autoroot.chainfire.eu/ then this link https://desktop.firmware.mobi/ look for G930F, take the R16NW.G930FXXS4ESC5 version who has the same than my phone ?
10- Must i follow post like : https://forum.xda-developers.com/s7-edge/how-to/samsung-pay-knox-warranty-void-t3549449 or it will be worst hard to get back to normallity ?
11- What is Magisk ? before rooting ? after rooting ? for rooting ? Can i try magisk solution ? or it will be worst hard to get back to normallity
12- On french support samsung-forum just say go in samsung store they got tool to repair with a real official rom for 40€ . i dont believe.
If no solution to get back samsung pass and secure folder, i'll re try to root phone at least i'll have that, even if knox go to 0x1 it won't be worst ? others problem with app on a rooted phone ?
Click to expand...
Click to collapse
In europe rooting your phone and knox 0x1 is not hardware damage and will be covered by samsung
kpwnApps said:
In europe rooting your phone and knox 0x1 is not hardware damage and will be covered by samsung
Click to expand...
Click to collapse
what you mean by covered ? i bought it since more than 2 years, no more warranty:/
so i'll have to pay, and pay for what ? they will change mother board and ask me to pay ? they will install an official rom who work ?
edit : just phone them, i don't have to flash my phone, i have to go in a store they will check my phone, and see what they can do and tell me the price for it.
i prefer to see what people on xda have to say before
Yotitchy said:
what you mean by covered ? i bought it since more than 2 years, no more warranty:/
so i'll have to pay, and pay for what ? they will change mother board and ask me to pay ? they will install an official rom who work ?
edit : just phone them, i don't have to flash my phone, i have to go in a store they will check my phone, and see what they can do and tell me the price for it.
i prefer to see what people on xda have to say before
Click to expand...
Click to collapse
You dont need to call them.
If you rooted once you can never use samsung pass , secure folder samsung pay again
For updates just flash back to stock
no one can confirm / answer to some of the questions ? :/
Yotitchy said:
no one can confirm / answer to some of the questions ? :/
Click to expand...
Click to collapse
Read my comment above
kpwnApps said:
Read my comment above
Click to expand...
Click to collapse
thanks for your comment of 2-3 lines to answer 12 questions, i've listened to you :
"In europe rooting your phone and knox 0x1 is not hardware damage and will be covered by samsung" >> covered by samsung so i call them, they said no.
"You dont need to call them." >> i dont need to call them ok so dont say me it will be covered by samsung
"If you rooted once you can never use samsung pass , secure folder samsung pay again. For updates just flash back to stock" >> answer to ask 7 and 8
Now i dont won't to be unfriendly with you but i don't think you are alone on this forum, and i don't think you answered to the other questions.
I would like to know more about this, and why some people dont say the same things on many topics, btw it could greatly help other users to not make the same mistake than me just thinking it will be ok for them.
thanks
Yotitchy said:
thanks for your comment of 2-3 lines to answer 12 questions, i've listened to you :
"In europe rooting your phone and knox 0x1 is not hardware damage and will be covered by samsung" >> covered by samsung so i call them, they said no.
"You dont need to call them." >> i dont need to call them ok so dont say me it will be covered by samsung
"If you rooted once you can never use samsung pass , secure folder samsung pay again. For updates just flash back to stock" >> answer to ask 7 and 8
Now i dont won't to be unfriendly with you but i don't think you are alone on this forum, and i don't think you answered to the other questions.
I would like to know more about this, and why some people dont say the same things on many topics, btw it could greatly help other users to not make the same mistake than me just thinking it will be ok for them.
thanks
Click to expand...
Click to collapse
Well you dont understand.
Ive already answered all your questions.
Knox cant be reset even flashing a newer firmware
And magisk doesnt let u use samsung apps either so.
kpwnApps said:
Well you dont understand.
Ive already answered all your questions.
Knox cant be reset even flashing a newer firmware
And magisk doesnt let u use samsung apps either so.
Click to expand...
Click to collapse
well ok... for me its total fail according to only you (but like i said other say no) but then i answer to you, again..
if i made a long post with questions instead of just, "can i resolve my problem" its cause i think xda is a place where people can learn things with "clever" peoples.
1 - i cant resolve my problem thanks, but rooting s7 snapdragon would have been the same ? you didn't answer to this i think
2 - i cant resolve my problem thanks, but is there someone who have been able to root s7 and to still use samsung pass or secure folder ? you won't answer to this cause it's a no for you. but others ?
3 - i cant resolve my problem thanks, but some people said unrooted flash worked ? you won't answer to this cause it's a no for you. but others ?
4 - same
5 - i cant resolve my problem thanks, but does other root methods could have work ? you didn't answer to this i think...
6 - i cant resolve my problem thanks, but so i havn't mistake my root ? all methods would have get me to the same result ? what's the difference between 0x1 and 0x0500 ? you didn't answer to this i think
7 - i cant resolve my problem thanks, but there is no other app who work like secure folder ? you didn't answer to this i think
8 - i cant resolve my problem thanks, even with a real samsung rom in a samsung center so.
9 - i cant resolve my problem thanks, then no need to test to flash again
10 - i cant resolve my problem thanks, so if in futur there is a trick, i won't try cause you said me no.
11 - i cant resolve my problem thanks, and thanks to explained me magisk, it was really helpfull. But this one is for me, i can find info on magisk on the forum somewhere else.
12 - you just say me no, so like the french forum for me :/
For exemple here, a thread where you have post, it seems to be reasonnable to try to make S health work on a rooted phone
https://forum.xda-developers.com/ga...riped-knox-t3921869/post79346431#post79346431
ou answer : Flash twrp then connect to pc with adb and pull build.prop .
Then edit ro.config.tima="1" to "0"
After that push the edited buildprop back to your device and flash original recovery back
so you say me no, fail is fail, but now i can try to make S health work.
Samsung Health on rooted link : https://tinyurl.com/yy37gnwv
you can answer me again and again and again, but its quite useless if its just to troll me with "no you can't" or "yes i answered all" in 2 lines to my ****ing boring long post.
i'll look boring, but you don't look smart to act like this :/ no answer would be smarter from you. So please don't answer anymore. Right now i won't be able to give any interest in your posts.
Yotitchy said:
well ok... for me its total fail according to only you (but like i said other say no) but then i answer to you, again..
if i made a long post with questions instead of just, "can i resolve my problem" its cause i think xda is a place where people can learn things with "clever" peoples.
1 - i cant resolve my problem thanks, but rooting s7 snapdragon would have been the same ? you didn't answer to this i think
2 - i cant resolve my problem thanks, but is there someone who have been able to root s7 and to still use samsung pass or secure folder ? you won't answer to this cause it's a no for you. but others ?
3 - i cant resolve my problem thanks, but some people said unrooted flash worked ? you won't answer to this cause it's a no for you. but others ?
4 - same
5 - i cant resolve my problem thanks, but does other root methods could have work ? you didn't answer to this i think...
6 - i cant resolve my problem thanks, but so i havn't mistake my root ? all methods would have get me to the same result ? what's the difference between 0x1 and 0x0500 ? you didn't answer to this i think
7 - i cant resolve my problem thanks, but there is no other app who work like secure folder ? you didn't answer to this i think
8 - i cant resolve my problem thanks, even with a real samsung rom in a samsung center so.
9 - i cant resolve my problem thanks, then no need to test to flash again
10 - i cant resolve my problem thanks, so if in futur there is a trick, i won't try cause you said me no.
11 - i cant resolve my problem thanks, and thanks to explained me magisk, it was really helpfull. But this one is for me, i can find info on magisk on the forum somewhere else.
12 - you just say me no, so like the french forum for me :/
For exemple here, a thread where you have post, it seems to be reasonnable to try to make S health work on a rooted phone
https://forum.xda-developers.com/ga...riped-knox-t3921869/post79346431#post79346431
ou answer : Flash twrp then connect to pc with adb and pull build.prop .
Then edit ro.config.tima="1" to "0"
After that push the edited buildprop back to your device and flash original recovery back
so you say me no, fail is fail, but now i can try to make S health work.
Samsung Health on rooted link : https://tinyurl.com/yy37gnwv
you can answer me again and again and again, but its quite useless if its just to troll me with "no you can't" or "yes i answered all" in 2 lines to my ****ing boring long post.
i'll look boring, but you don't look smart to act like this :/ no answer would be smarter from you. So please don't answer anymore. Right now i won't be able to give any interest in your posts.
Click to expand...
Click to collapse
I have no idea what youre talking about. Anyway , my other thread refers to the use of shealth without root as the op wanted to do it with no root acces,compared to yours with root. And to your thread your thread is complete bull**** since its unclear to read and understand your questions. So do me a favor and elaborate your questions next time.
Thanks
Ok thanks bye !
Back to my first "elaborate" post then
"elaborate", but i accord it certainly unclear (cause i'm not a pro english, and not a dev or a pro root user )
so here is a simplified version since i've understood more thingies (on this forum not on this thread)
Général questions :
1- Knox 0x1 problems are only for S7 exynos ?
2-3-4- Samsung Pass, Samsung Pay, Secure Folder, Health, etc.. can't never work on rooted / no-more rooted / wiped stock rom phone cause of knox ?
5- Other root method could have work without breaking knox ?
For me, S7 exynos, R16NW.G930FXXS4ESC5, knox 0x0500 :
6- Like i'm not in knox 0x1 but 0x0500 do i have a try ?
7- Can i have back knox related apps editing something ? or almost same knox-apps (mainly secured folder) ?
8- If it's usefull, can i go back to initial stock rom ? A real samsung official install from myself or samsung center ?
Click to expand...
Click to collapse
Yotitchy said:
Général questions :
1- These knox problems are only for s7 exynos ?
2- Root and samsung pass never work ? still have someone who say yes
3- Rooted and now unrouted and samsung pass don't work ? still someone who say yes
4- unrooted + full wipe + stock rom and samsung pass don't work ? must i have to try several official rom perhaps ? trying will fail my knox more ? still someone who say an official rom will work
5- Other root method could have work with knox ? but too late if already rooted ?
For me, S7 exynos, R16NW.G930FXXS4ESC5, knox 0x0500 :
6- How did i mistake ? Like i'm not in knox 0x1 but 0x0500 do i have a try ? or if i try i'll have 0x1 and no more try ?
7- Can i have back knox related apps or almost same apps (mainly samsung pass and secure folder) ?
8- Can i go back to initial stock rom ? a real samsung official rom ?
9- Can i try again following from http://autoroot.chainfire.eu/ then this link https://desktop.firmware.mobi/ look for G930F, take the R16NW.G930FXXS4ESC5 version who has the same than my phone ?
10- Must i follow post like : https://forum.xda-developers.com/s7-edge/how-to/samsung-pay-knox-warranty-void-t3549449 or it will be worst hard to get back to normallity ?
11- What is Magisk ? before rooting ? after rooting ? for rooting ? Can i try magisk solution ? or it will be worst hard to get back to normallity
12- On french support samsung-forum just say go in samsung store they got tool to repair with a real official rom for 40€ . i dont believe.
edited : 13- Like that can i still have samsung android updates ?
Click to expand...
Click to collapse
Hellooo
1. No, the KNOX Warranty Void stuff is already an "issue" ever since the Samsung Galaxy S4 came out. And ever since that, every new Samsung Device launches with that Knox counter. BTW, the KNOX Counter is an one-time programmable chip that once it detects any sort of modifications to the Device (Root, Custom Recovery like TWRP etc.) sets the counter from 0x0 to either 0x1 or 0x500.
2. That's right, All of Samsung's Security / Pay apps immediately will stop working once the Device was rooted.
3. See Answer 2 xD Since the KNOX Counter is more like a Hardware-based thing, it won't change even after a complete Stock ROM flash process.
4. Whatever those guys say, don't believe them. See Answer 3. xD
5. There are pretty much no methods to root the Device without screwing up with KNOX. The Samsung S6 / S6 Edge once had such a way of rooting tho where you were able to root while still having the KNOX at 0x0, but only on the Lollipop firmware though.
6. "Triggering" the KNOX Counter, whether it shows 0x1 or 0x500 is a one-time thing, like voiding the Warranty with rooting countless times won't make the Counter go crazy between 0x1 and 0x500 xD
7. Maybe. You'd be better to look for alternatives though, but maybe after a while tho some Dev might be able to patch it to work with rooted / Knox 0x1 Devices.
8. Yes sure. Flashing the for the Device latest available Stock ROM will return the Device to factory condition... Except the KNOX thingy tho xD
11. Magisk is like SuperSU a tool/program/software whatever you wanna name it, a Program to gain root access.
12. Nice joke, damn. xD I once asked at a Samsung Store to repair the Dead Motherboard of the S7 from my Mom, they said it'll be between 200-300€ JUST FOR THE MOBO, means you'll also have to consider the actual repair costs and so on. 40€ is a joke.
13. See 8. Yes, after returning to full stock you should still get OTA Updates.
Okaaaayyy soo I hope I was able to help you at least a little bit
Fatal_Scythe said:
Hellooo
[...]
Okaaaayyy soo I hope I was able to help you at least a little bit
Click to expand...
Click to collapse
hi !
Yes thanks a lot for these answers
Its should be in capitals red letters thtat knox broken = samsung app broken in notices threads :/
Even if rooting look easy, noob people like me should take really care before, wost that i did it mainly for fun testing
Finally i got a rooted phone but not really usefull for me, and no more secure folder who was really usefull for me XD
If someone got a method to get an app like secure folder (who emulate another system, don't care security) he is welcome
thanks again Fatal
Yotitchy said:
hi !
Yes thanks a lot for these answers
If someone got a method to get an app like secure folder (who emulate another system, don't care security) he is welcome
thanks again Fatal
Click to expand...
Click to collapse
Your welcome.
I made a quick google search and came across that thread on Reddit, maybe one of these apps is gonna work for you? ^^
Fatal_Scythe said:
Your welcome.
I made a quick google search and came across that thread on Reddit, maybe one of these apps is gonna work for you? ^^
Click to expand...
Click to collapse
thx i've found it too
exactly what i need, I tried normal install who dont work XD
island FAQ said manual install with ADB : https://island.oasisfeng.com/setup.html
but i block at begin with “Error: couldn’t create User” even if I execute setprop fw.max_users 10, i'm looking about it