Related
I was concerned about Security with Kingroot so decided to try this. I'm on a RETAIL Verizon Note 4 running 4.4.4.
I did a factory restore then after setup, I DISABLED SDM, THEN I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot on the "Personal" side.
It worked. Root is, On Demand, temporary, And I think it is safer than using Kingroot without Knox.
I went into recovery to check but no Knox trip. I win!. I have two environments. One rooted the other as secure as you can get.
This is like having a dual boot on the fly. With this root you can at least use Adaway. You can get a lot done with it. This is the best root solution for the Retail Verizon Note 4. I am hoping to get developers interested.
O.K.,This is where I'm at. If someone could look at the pictures and tell me what I should add to the OP description, I'll do it. Look at the last two pictures, Knox would not let me take the screen shots because of security.
Check Out MOST ASKED QUESTIONS and Fixes in the next post.
MOST ASKED QUESTIONS
1. What phone is this for? Retail Verizon Note 4. This may also work on other un-rooted phones
2. What ROM are you on? 4.4.4 found HERE http://forum.xda-developers.com/not...w-to-roll-to-kk-4-4-4-lollipop-5-0-1-t3097054
3. How did you set up your google account? I set my personal side up with a "burner" email and the Knox side with the email I use every day.
4. How do you disable SDM? I used this: http://forum.xda-developers.com/and...---------------------------------------------
5.Where do you get My Knox" The Play Store.
6. Where did you get Kingroot? http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
7. What order do you install the software? Restore 4.4.4/Set up Google account./disable SDM/setup My Knox/Kingroot on personal side/=enjoy..... .......Note: this is not for use with SuperSUME.
8. Is root permanent? Some of the modification made when rooted are permanent but this Root is On Demand, temporary And I think this root method is safer than using Kingroot without Knox.
9. What about reboots. If a App ask to reboot first try not rebooting some changes will take effect without a reboot. If you have to reboot use a soft-reboot like SimpleReboot. You will almost always lose root with a hard reboot.
10. For an added security measure I am going to use the "Personal" root side as a playground and reboot before I open the My Knox Security side. Just to throw off any would be hackers.
Fixes
1. I found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select allow and then on the first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
The same procedure may work for other apps. For some reason Adaway starts working without a reboot. You will need to clear and restart your browser.
Calm down, these things take time. First when you reboot allow your phone to settle down, a minute or two. Don't open anything. FIRST, Open and run kingroot. Once root is established run Adaway like I said. It probably will work the first time but if it fails just try again. It seem that once Kingroot gets to the point where it is not asked for permission, the reboots go away and it becomes more stable.
2. O.K., KNOX disables USB debugging, but I was able to uninstall Knox at the Playstore /Re-enable USB debugging/ then use gatesjunior's debolater app to remove SDM/ then install Knox /then root with Kingroot and it is working great again. I did try to put Super-Sume Pro on top but it would NOT work. I think Super-Sume Pro removes Knox. So I had to start over but I got it working great. If you need to use USB debugging for anything now we have to uninstall Knox. I'm still testing now.
-----------------------------------------------------------------------------------------
Check Back to post # 1 & 2 for updates.
Having some guys look into this.
doctor-cool said:
I was concerned about Kingroot and security so decided to try this.
I'm on a retail Verizon Note 4 running Gatesjunior's Safe 4.4.4.
I did a factory restore then after setup, I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot . It worked. Now sometime when I reboot I get the Unlock logo with the words Custom on the boot screen just like the DE Note 4 . I went into recovery to check but no Knox trip. I win the Root Price. I have two environments. One rooted the other as secure as you can get.
Click to expand...
Click to collapse
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
warriorpluto said:
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
Click to expand...
Click to collapse
did you test it?
Extreme Syndicate L
This is like having a dual boot on the fly
gatesjunior said:
Having some guys look into this.
Click to expand...
Click to collapse
I have two separate Google play store account on two separate partitions .
Can you get it to work with SuperSuMe Pro.
All this time we have been disabling Knox and actually My Knox is your friend.
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Wetzel402 said:
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Click to expand...
Click to collapse
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
doctor-cool said:
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
Click to expand...
Click to collapse
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
gatesjunior said:
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
Click to expand...
Click to collapse
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
doctor-cool said:
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
Click to expand...
Click to collapse
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
elliwigy said:
did you test it?
Extreme Syndicate L
Click to expand...
Click to collapse
No. I havemt backed up my phone yet to try. Ill do it when I get home and try
Sent from my SM-N915V using XDA Free mobile app
not random
elliwigy said:
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
Click to expand...
Click to collapse
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
doctor-cool said:
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
Click to expand...
Click to collapse
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
elliwigy said:
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
Click to expand...
Click to collapse
I meant when AdAway disables the commercials it is worth the trouble. But yes most of the time the root results are temporary . But once you get it set up your good to go and it is worth the trouble until your battery dies
-----------------------------------------------------
Edit: I may have found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select alow and on first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Hotdizzle said:
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Click to expand...
Click to collapse
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
doctor-cool said:
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
Click to expand...
Click to collapse
I have the retail note 4
Hotdizzle said:
I have the retail note 4
Click to expand...
Click to collapse
Then...l don't know. I'm on safe 4.4.4, how about you?
-----------------------------------------------------
I just read your post 16 . Your on LP I'm on KK
LOL this works?!? how did nobody ever try this until now.. I'm speechless
ok, so there are some things i've found out by doing some research and combining what i found on here with the issues that some people were having with the Cricket version of the LG Stylo, and would like to share with you guys. while i was rooting my phone with kingroot, i noticed a threat that discussed that using supersu me and supersu wasn't an option without soft bricking your phone with a boot loop, after some research and trial i figured out how to get around the problem. The issue was the uninstallation of kinguser app form the phone, this is because using supersu me uninstalls kingroot and replaced it with the superuser binaries, but it leaves some core files of kinguser behind which causes errors, an if you keep your phone on, you'll notice that you'll start getting error messages for an about kingroot permission and all types of errors until your phone starts to freeze and act up. there is an easy fix for it all that worked for me, and would like to share this information and help people having this issue.....
I'm posting this as a hint for those who needed the help with installing xposed on cricket model LG STYLO only running 5.1.1
so to begin, download system repair 2016 and apps2sd from play store, kinguser directly from their site so it will be the latest version,,,root your phone,,,,,don't delete the kinguser apk you downloaded you'll need it for later,,,,now install supersu me from the play store and open and run it, it'll uninstall kinguser and replace the binaries for superuser, this is where its gonna become tricky,,,,,,download supersu and run which will ask for update of binaries also let it finish updating and uninstall the supersu me control,,,,,now open apps2sd and clear the davik cache and other caches without restarting,,,,then run system repair 2016, it'll show that you had a few errors because kinguser hates the fact that supersu me uninstalled it and left messed up configurations on your phone, then clear the davik cache again, now you have to use the same kinguser apk you get at the start of the process and reinstall it to your phone, or else you will be getting a boot loop issue......for some reason even though all the caches are cleared and the system has been checked for errors, the kinguser app installs itself as a system app, a dependency if you will, like a basic LG/Cricket app that if you uninstall will cause errors, so but reinstalling it we stop that problem, you can run it but don't need to activate the root option of kinguser......this will cause the kinguser permission errors to stop also from this point only you can restart your phone,,,,,now you're able to install flashfire and xposed frameworks, and even restart your phone without worry of boot looping since there isn't much support for the LG-H634 stylo model.........:angel::angel:
hope this was helpful for you guys that was in need of replacing kinguser, and installing xposed framework, i've not tried anything further with the twrp install but keep a look out for the names "vegito6" "vegito69" ....and wish me luck on twrp
#humbleprogrammer
seems i've got to post at least 10 times in order to post outside pics
So I rooted my same phone via kingroot and it has the purify apo along with it. Also having problems with errors and stuff. I'm gonna follow your method see what happens. This being #2 stylo after bricked the first one and couldn't find kdz. Anyway I'll get back to ya let me know if you have anymore info thanks for the help man.
orphan tear maker
Help Please
Drumdestroyed said:
So I rooted my same phone via kingroot and it has the purify apo along with it. Also having problems with errors and stuff. I'm gonna follow your method see what happens. This being #2 stylo after bricked the first one and couldn't find kdz. Anyway I'll get back to ya let me know if you have anymore info thanks for the help man.
orphan tear maker
Click to expand...
Click to collapse
got bricked today, anyone any luck with something??
markos638 said:
got bricked today, anyone any luck with something??
Click to expand...
Click to collapse
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
vegito69 said:
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
Click to expand...
Click to collapse
I got bricked, trying to change from kingroot to SU, I´ll really appreciate when you find solution give us instructions on how you did it!!
Have you guys any luck with a recovery method? And think you for helping I'll do my best with what I have. Also idk if I mentioned it earlier but when I reboot lg symbol appears but (authentication failed #9) appears below it. It was roted via king root and didn't o anything but remove some bloatware. Idk God be with you man cuz this is a bummer
vegito69 said:
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
Click to expand...
Click to collapse
I'm pretty sure that you ended up with brick because you didn't unlock your bootloader before backing up. My girlfriend did the same thing. As of right now I'm trying to figure out If there's a way past the bootloader or at least a way to do everything the bootloader can do without unlocking it.
Original Firmware
Can we not flash the original firmware via download mode ? I had this phone (bought from a friend, cricket sim unlocked, phone bricked while i was playing around. )
I'm not super familiar with LG phones, but i keep hearing about a KDZ , is that some kind of official image format ?
If we can flash it for stock via download mode, can someone direct me as to where I might find instructions for our variant of the device, please ?
I was able to replace Kingroot with SuperSu using a guide I found on a website called w0lfdroid, I think. I just Google 'replace Kingroot with SuperSu and it was the second one down (I'm a new user so I can't post the link). I think it worked pretty well, but I'm still not able to flash TWRP or start the process to get xposed. If I can't get it, I might unroot and try the process again with this method.
as anyone with brick try this http://lg-firmware-rom.com/downloads/lg-g-stylo-h634-stock-tot-firmware-v10g/ , they offer files for unbricking, $40 bucks
what do you guys think
markos638 said:
as anyone with brick try this http://lg-firmware-rom.com/downloads/lg-g-stylo-h634-stock-tot-firmware-v10g/ , they offer files for unbricking, $40 bucks
what do you guys think
Click to expand...
Click to collapse
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
vegito6 said:
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
Click to expand...
Click to collapse
works just fine!!!! lg stylo is back!!! thanks vegito ,....
vegito6 said:
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
Click to expand...
Click to collapse
Great job man. It is people like you who keep the community going.
Su binary installation failed!
Mooose-Nuckle said:
I'm pretty sure that you ended up with brick because you didn't unlock your bootloader before backing up. My girlfriend did the same thing. As of right now I'm trying to figure out If there's a way past the bootloader or at least a way to do everything the bootloader can do without unlocking it.
Click to expand...
Click to collapse
well not really, because if you go into the developer options there is the oem bootloader unlock you can select, not sure but i've got a cricket and boost version i've been working on it for a while, for some reason the phone doesn't like the way SU gets injected into the phone, and writes things to the wrong areas, i've been playing with some scripts for superuser installers from zip, hopefully i get a hit.
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
jxs714 said:
Great job man. It is people like you who keep the community going.
Click to expand...
Click to collapse
thats the life of us programmers and developers thats trying to get better lol, we just share the knowledge passed down lol
vegito6 said:
well not really, because if you go into the developer options there is the oem bootloader unlock you can select, not sure but i've got a cricket and boost version i've been working on it for a while, for some reason the phone doesn't like the way SU gets injected into the phone, and writes things to the wrong areas, i've been playing with some scripts for superuser installers from zip, hopefully i get a hit.
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
thats the life of us programmers and developers thats trying to get better lol, we just share the knowledge passed down lol
Click to expand...
Click to collapse
I noticed there is no solution posted. I recently bricked my phone and fixed it, thanks to you. I was simply wondering of there has been progress with getting the framework installed. Your help is much appreciated.
So I'm sort of confused... I cannot install xposed, and can't seem to find a work around. I am rooted but not with kingroot. I used a one click root tool on pc, and works great... Using su that is suggested using in this guide, so no trace of king root. Idk, could someone give me a quick run down on how to install xposed?
So no luck with installing xposed yet
So far I am rooted with Super SU and have exposed installer I'm just having a hard time getting the framework installed. I do not have custom recovery installed. Is there any way to flash the framework zip file with like flashify or another app like that?
Hi,
i need to get this phone rooted please, no root apps works, @Chainfire maybe can help?
Any one be able to help if this can be rooted?
xxmcvapourxx said:
Any one be able to help if this can be rooted?
Click to expand...
Click to collapse
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
KNOX should remain 0x0
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
ashyx said:
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
Click to expand...
Click to collapse
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
xxmcvapourxx said:
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
Click to expand...
Click to collapse
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
when trying to root
By Kin9Root Won Chu chu in a few ROot failure 'not yet suitable ˉ a - condolence ˉ ˉ a ˉ a "` ` One by one - one 'one one '- one - the
i get i've tried the pc version and the apk a few tries i keep getting notifications in the settings it is set to permissive
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
figured it out -- it was the pin we just trying super me
xxmcvapourxx said:
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
ok I tried 3 different cords, various lengths, and now no matter what I get this screen only
Click to expand...
Click to collapse
You're using the desktop version, please download and use the android English apk:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
.
Is there an update on this, did anyone achieve root?
.
ashyx said:
Is there an update on this, did anyone achieve root?
.
Click to expand...
Click to collapse
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
xxmcvapourxx said:
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
Click to expand...
Click to collapse
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
Yes as soon as super su me installs ask to install binaries ans ask to reboot it will lose root.
I will try the script without flashing firmware
Thank you ill let you know how i get on
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
xxmcvapourxx said:
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
Click to expand...
Click to collapse
It's not related to the bootloader, the bootloader is still locked, it's simply an incomplete installation of SuperSU. Probably due to permissions.
Follow the guide posted above and you should be good. I'd also suggest using root package disabler to disable knox.
Hit search in the app and type knox. Disable all knox related files.
https://play.google.com/store/apps/details?id=com.kunkunsoft.rootpackagedisablerfree
.
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
ashyx said:
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
Click to expand...
Click to collapse
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
xxmcvapourxx said:
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
Click to expand...
Click to collapse
So even when flashing root with Flashfire still losing root? Did you try using the script posted above?
Also could you post a screenshot of Root validator after losing root?
I would also suggest flashing the stock firmware with FLASHFIRE.
Ensure to Uncheck the boot partition and disable EverRoot.
Add the system supersu zip to the install.
It may be remnants of Kingroot causing the issue. Flashing this way will ensure a clean system with just supersu.
Having the same problem
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
stanfox said:
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
Click to expand...
Click to collapse
Why can't you enable OEM unlock? Remove any pin/password from the device first.
ashyx said:
Why can't you enable OEM unlock? Remove any pin/password from the device first.
Click to expand...
Click to collapse
I was surprised at first when you directed me to this thread ashyx, the first word I saw was Kingroot and I was sure a dev such as yourself wouldn't use that.
I write against Kingroot all the time. It is information stealing malware that doesn't even give true root, packs PUPs, and sends IMEI and other info to China upon install (check the logcat).
And it's nortoriously hard to get rid of and replace with a different SU. From what I read above, true root hasnt' been achieved yet. Ive used KR a few times in the past, but never again. It used to be easier to replace KingUser w SuperSU. Not so much anymore.
Please folks, Kingroot IS NOT actual root ; please quit posting about it in a true professional developer site.
Ahyx, PM me if you wish. I'd like to work on any methods other than this. I can get the bootloader unlocked from Net 10. But not until having it hooked up w/ lthem for a year. I've already chosen to disconnect this device anyhow because I can't stand using a non-rooted phone. Too bad, it's a good machine. I got a great buy on it. $50US brand new. Same store today $99. WalMart = $120
I just bought an LG G3 for $45. Verizon model, interesting root. I had to downgrade firmware to achieve root. It's TWRPd, and running Dirty Unicorns 10.6, a nice rom, better once I mod it.
Tried the latest RR rom for it. Nougat was cool, but too early, too many bugs.
Has anyone received Google Assistant on their phones yet? Just curious.
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
I'm surprised to hear some people still don't have GA natively. I'm a long time HTC user, but I just bought my 10 last Fri. it's pretty sweet. although, I must say, I still REALLY like my One M8.
SilverZero said:
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
Click to expand...
Click to collapse
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
SilverZero said:
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
Click to expand...
Click to collapse
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
"OK Google" Always on!!??
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
misfiremind said:
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
Click to expand...
Click to collapse
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
this is from my Bolt, so it may be different, but I can disable just fine...
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
misfiremind said:
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
Click to expand...
Click to collapse
Ill try that but I flashed N using the RUU and then clean installed OMJ's badboys rom so no app data would have been there during M to N
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
OMJ said:
this is from my Bolt, so it may be different, but I can disable just fine...
Click to expand...
Click to collapse
Thats strange, i dont have all those menu entries... could be cause I have work email on my phone via activesync which restricts certain security and lockscreen options.
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
Click to expand...
Click to collapse
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
SilverZero said:
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
Click to expand...
Click to collapse
yes, merely having the bootloader unlocked even w/ 100% stock ROM, safetynet will fail....the beauty of magisk is that it hides it
I think at this point I'd rather relock my bootloader and go back to using my Galaxy S4 while I try to sell my HTC 10 and then put that money towards a Pixel. Anybody wanna buy a phone? ?
It's here! I literally just this minute got Google Assistant!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I think I am going to give this a shot. I am running your stock rooted with TWRP while S-on. Can I just install your Magisk Full Rom and go from there or is that too easy to believe? Thanks OMJ!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
Is magisk a ROM or more of a mod? And what is magisk su? I'm going to try and get my phone rooted this weekend but I can't find a tutorial thread, it seems to be scattered everywhere. It seems like I fastboot TWRP, flash SuperSU, flash magisk then install magisk manager from Google Play?
misfiremind said:
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
Click to expand...
Click to collapse
im running viper due to lack of cm/aosp st the moment.. so i have magisk but i have no idea what it is or how to use it. very little instruction out there.
Has anyone been successful in editing their build.prop file to activate (or deactivate) Google Assistant? I actually want to deactivate Google Assistant but I can't seem save changes to my build.prop file.
I have root on stock ROM.
Set SE Linux to permissive.
Tried using Root Explorer and build.prop Editor. Both give me an error message stating it can't save the build.prop file.
Suggestions?
Hi everyone, I just want to share this tutorial for someone like me (NEWBIE, NOOB, BEGINNER, ZERO KNOWLEDGE).
ALL CREDITS TO THE RIGHTFUL OWNER.
PRE-REQUISITES
- Laptop
- Applications, .img files (https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc)
- Your Nubia Phone
ENSURE THAT:
- You installed the application and driver (Minimal ADB and Fastboot & the driver from your Nubia phone).
- You updated your OS in the latest version.
- You UNLOCK the developer option (setting>>about phone>>tap 7x the build number) and you switch ON the OEM unlocking & USB Debugging.
- You approved the RSA request in your RM5G
NUBIA RED MAGIC 5G UNLOCK BOOTLOADER
1. Connect your Nubia in laptop, in your laptop, open Minimal ADB and Fastboot and type the following:
a. adb reboot bootloader
b. fastboot oem nubia_unlock NUBIA_NX659J
c. fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
d. fastboot flash vbmeta vbmeta_BL_skip.img
e. fastboot flash modem NON-HLOS.bin
f. fastboot flash parameter parameter.img
2. Go to your RM5G, select reboot to recovery
3. It will reboot in TWRP twice, in the 2nd reboot it will stay in TWRP, change the language to English and select the keep read only.
4. Go to WIPE option, then select FORMAT DATA, type yes
5. Press home button, then go to REBOOT, select REBOOT to RECOVERY
NUBIA RED MAGIC 5G ROOTING PROCEDURE
6. Go to ADVANCED, below there are list, select INSTALL ROOT.
7. Reboot your RM5G.
At first, my RM5G restart twice, I was afraid that it was bootloop, the 3rd boots, it booted up and its rooted already.
Also, when I first registered my Finger Print, it’s malfunctioning, so I just deleted the OLD FP , register NEW FP and it works like a charm.
Now, I managed to flash the wonderful kernel of @mslezak.
Credits:
@mslezak - for his tutorial,
files we used in this thread https://forum.xda-developers.com/nu...how-to-unlock-bootloader-redmagic-5g-t4081743
And kernel in this thread: https://forum.xda-developers.com/nu...od-kernel-red-magic-5g-simply-source-t4112811
Ibr ALnaQbi - for his video tutorial
And to all who made it successful.
Great job bro !
Note for those that don't know how to enable developer options - go to settings, about phone, click build number 7x. It should take you right to the Developer Options menu. Nice clear concise guide by the way! Glad someone wrote a simpler one than the one I wrote initially, only so many hours in the day.
mslezak said:
Note for those that don't know how to enable developer options - go to settings, about phone, click build number 7x. It should take you right to the Developer Options menu. Nice clear concise guide by the way! Glad someone wrote a simpler one than the one I wrote initially, only so many hours in the day.
Click to expand...
Click to collapse
Thanks for mentioning the dev. option. All credit to all of you guys who made this possible.
I've been trying for days to download the MEGA zip, but no matter what I do it always stays on 0% and gives me an error. I tried on different browsers, on different computers, and using the desktop app, I even tried with the mobile app with no luck. Could someone please share a mirror or another link, please?
Nevermind, I was finally able to download the file, my solution was to use chrome instead of firefox and close every window except the mega one... I left it like that for a couple of hours and it finally downloaded it.
Possibly a stupid question, but are there any downsides to this other than the risk of bricking?
samussamus1 said:
Possibly a stupid question, but are there any downsides to this other than the risk of bricking?
Click to expand...
Click to collapse
If you follow the tutorial, there will be no problem even soft brick.
luis7654 said:
Nevermind, I was finally able to download the file, my solution was to use chrome instead of firefox and close every window except the mega one... I left it like that for a couple of hours and it finally downloaded it.
Click to expand...
Click to collapse
Its a normal troubleshooting, if its not working to other browser, try another one, great to hear that you managed, happy rooting.
CaLix25 said:
If you follow the tutorial, there will be no problem even soft brick.
Click to expand...
Click to collapse
Thanks but this isn't what I meant, I was thinking more so of apps not working due to root detection. Banking apps or others?
-
Sam
samussamus1 said:
Thanks but this isn't what I meant, I was thinking more so of apps not working due to root detection. Banking apps or others?
-
Sam
Click to expand...
Click to collapse
You can hide the Magisk (setting/select the apps/then hide magisk) so it will not detect that you are rooted.
CaLix25 said:
You can hide the Magisk (setting/select the apps/then hide magisk) so it will not detect that you are rooted.
Click to expand...
Click to collapse
Brilliant, thank you!
-
Sam
Hi,
2 questions. First of all, does this method work for all of the 5G phones? As in the European version etc. And second of all, will the phone brick if you update it via OTA, or do we need to do this method every time?
Noahesbjerg said:
Hi,
2 questions. First of all, does this method work for all of the 5G phones? As in the European version etc. And second of all, will the phone brick if you update it via OTA, or do we need to do this method every time?
Click to expand...
Click to collapse
Hi,
1. Yes its applicable for all version.
2. Yes it will brick your phone when updating via OTA
you can take a screen for hide magisk for app (Root) because I can't find it.
and still no solution to recover the fingerprint reader? thank you
cyberpunkfw1983 said:
you can take a screen for hide magisk for app (Root) because I can't find it.
and still no solution to recover the fingerprint reader? thank you
Click to expand...
Click to collapse
Hi, see attached. You have to rename the Magisk after selecting in pic. # 1.
You can find the FP calibration procedure here in XDA.
Ty ?
Hi Guys, first of all thanks for awesome tutorial. Got it rooted and enjoying the perks. However, some issues do exist. 1. The phone has detected a new update v4.09. Will the root be deactivated if I update the system? Second question, my banking app is detecting the root and does not want to start. I did set magisk manager to hide it from the app and restarted the phone even, but no luck the app still sees the root. Any solution for it? Thanks all
hello I would like to know how to put it back original? bootloader, Root ... thank you
Zigi86 said:
Hi Guys, first of all thanks for awesome tutorial. Got it rooted and enjoying the perks. However, some issues do exist. 1. The phone has detected a new update v4.09. Will the root be deactivated if I update the system? Second question, my banking app is detecting the root and does not want to start. I did set magisk manager to hide it from the app and restarted the phone even, but no luck the app still sees the root. Any solution for it? Thanks all
Click to expand...
Click to collapse
1. If you updated your RM5G before rooting, its bug, ignore it.
2. Mine is working as i showed in the photo above (ANB)