Hi,
I'm completely new to the root world...
I tried to install towelroot V2 on my Galaxy Note 3 which runs the Kernel 3.4.0-636608.
I rooted it, root checker said all ok, but after installing SuperSU, updating binaries and rebooting the device, root checker says it's not rooted...
Now it's worst, Wifi is turning 100% even when turned off, and sometimes the screen of my phone stays black, even if I push the buttons, in that case I need to remove the battery and to reboot the phone...
Any solution ?
Again I'm a newbie, I don't even know how to restore the phone or to do a reset, so please help me...
Thanks in advance
RaphaelBEN said:
Hi,
I'm completely new to the root world...
I tried to install towelroot V2 on my Galaxy Note 3 which runs the Kernel 3.4.0-636608.
I rooted it, root checker said all ok, but after installing SuperSU, updating binaries and rebooting the device, root checker says it's not rooted...
Now it's worst, Wifi is turning 100% even when turned off, and sometimes the screen of my phone stays black, even if I push the buttons, in that case I need to remove the battery and to reboot the phone...
Any solution ?
Again I'm a newbie, I don't even know how to restore the phone or to do a reset, so please help me...
Thanks in advance
Click to expand...
Click to collapse
Hi.
To reset yr phone, turn off yr device first.
Then, press and hold power button, home button and volume up button at the same time.
In a few seconds, u will see a recovery options.
In there, scroll down using volume down button and click factory reset/wipe data using the power button.
Then, wipe cache partition and dalvik cache.
Once u done all that, reboot yr device.
U may need to towelroot yr device again if it lost root.
Hope this will help u..
Cheers..
maanz "L" said:
Hi.
To reset yr phone, turn off yr device first.
Then, press and hold power button, home button and volume up button at the same time.
In a few seconds, u will see a recovery options.
In there, scroll down using volume down button and click factory reset/wipe data using the power button.
Then, wipe cache partition and dalvik cache.
Once u done all that, reboot yr device.
U may need to towelroot yr device again if it lost root.
Hope this will help u..
Cheers..
Click to expand...
Click to collapse
Thank you very much for your answer.
Do you think there is any solution to avoid this freeze that happen instead of clear all the datas ? Because I didn't save my phone, and I don't even know how to save everything so that I just have to plug it back to my computer to restore everything (I am a former user of an iPhone...)
Thanks for your help !
RaphaelBEN said:
Thank you very much for your answer.
Do you think there is any solution to avoid this freeze that happen instead of clear all the datas ? Because I didn't save my phone, and I don't even know how to save everything so that I just have to plug it back to my computer to restore everything (I am a former user of an iPhone...)
Thanks for your help !
Click to expand...
Click to collapse
Since u are new to android, let's do the hard way...
Another thing is, after u installed SuperSU, have u allowed root checker to gain permission from SuperSU?
There are few members complained of wifi 100% in here: http://forum.xda-developers.com/showthread.php?t=2783954&page=23.
For me, I don't have this problem so far.
maanz "L" said:
Since u are new to android, let's do the hard way...
Another thing is, after u installed SuperSU, have u allowed root checker to gain permission from SuperSU?
There are few members complained of wifi 100% in here: http://forum.xda-developers.com/showthread.php?t=2783954&page=23.
For me, I don't have this problem so far.
Click to expand...
Click to collapse
Nope, any application never asked me for SuperSU permission, not even adblock...
But Root checker was saying that the check appeared to be very slow...
How about saving all the datas ?
u have to let SuperSU grant permission on all root apps, mate.
if not, the rooted apps will not work..
saving datas??
Sent from my SM-N9005 using Tapatalk
maanz "L" said:
u have to let SuperSU grant permission on all root apps, mate.
if not, the rooted apps will not work..
saving datas??
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
It's ok now, I just did a hard reset on my phone...
I know I had to grant SuperSU permission but it wasn't asking for...
Anyway, problem solved but I lost a few of my data...
Thanks for your help guys !
Unable to root
Hi~
I'm new to rooting too. SM-N9005 running on 4.4.2 & kernel 3.4.0-1703205 here. Tried to root my note 3 with towelroot V2 but failed. After pushing the "make it ra1n" button, it says "you should have root, no reboot required." However I checked with rootchecker app from playstore, and it says that I do not have root access. Therefore I have a few questions that I hope you guys can help me with.
1) Is rootchecker app from playstore reliable & accurate in telling whether or not a device has root access? Or are there other ways to check whether a device is rooted?
2) Does having root access means you can download any paid apps for free?
3) After rooting my note 3, can I update from 4.4.2 onwards? What will happen if I were to update my rooted device?
4) Does having Aptoide & apps downloaded through it hinder or affect the rooting process?
Please help and Thank you.
Mouzai said:
Hi~
I'm new to rooting too. SM-N9005 running on 4.4.2 & kernel 3.4.0-1703205 here. Tried to root my note 3 with towelroot V2 but failed. After pushing the "make it ra1n" button, it says "you should have root, no reboot required." However I checked with rootchecker app from playstore, and it says that I do not have root access. Therefore I have a few questions that I hope you guys can help me with.
1) Is rootchecker app from playstore reliable & accurate in telling whether or not a device has root access? Or are there other ways to check whether a device is rooted?
2) Does having root access means you can download any paid apps for free?
3) After rooting my note 3, can I update from 4.4.2 onwards? What will happen if I were to update my rooted device?
4) Does having Aptoide & apps downloaded through it hinder or affect the rooting process?
Please help and Thank you.
Click to expand...
Click to collapse
Hi.
are u using the newest and latest firmware update? I'm not sure whether it will work with towelroot v2. AFAIK, towelroot will work for firmwares before June release. need to read up here: http://forum.xda-developers.com/showthread.php?t=2783954&page=23
1) rootchecker app is reliable as lots of people used it. there should have other apps on playstore to check for root.
2) no, paid apps is paid apps. rooting yr device means u are able to "get inside or hack yr phone's system" and u can make adjustments or "mods" to system files (for developer level).
3) u can update new firmwares, but u will lose root and towelroot may not be able to support unless geohort (towelroot dev) updates it.
4) u can install any app u like, it will not hinder yr rooted device.
Cheers..
Hi~
Thanks a lot for your reply & helpful answers! Anyway after granting access of rootchecker from superSU, it says I do have root access. However I can't tell the difference... hahaha. So lets assume my device is rooted, may I know how can I delete all those useless & space consuming built-in apps of my note 3 during purchase?
Use titanium backup
Sent from my SM-N9005 using XDA Premium 4 mobile app
Related
Okay, so I have this phone and the info attached to the imei DCNO Prod Test phone. It has the following build listed N900VVREBMJ5 test-keys. I checked for root access with a app and it didn't have root access. I tried to root with odin3 root_de_la etc and it came up with an error and was basically soft bricked. Was able to reload the pit file and eventually get it working again. I clearly don't know what I'm doing and bought this phone online and have learned very little since last night. It loads up with the custom logo etc etc. I'm looking load a regular stock rom onto or just a custom one, but no matter what I do I get an error.. Can anybody help.. thanks
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
shiftr182 said:
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
2swizzle said:
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
Click to expand...
Click to collapse
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
topurdue said:
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
Click to expand...
Click to collapse
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
topurdue said:
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
Click to expand...
Click to collapse
Anyways, i wiped deleted restarted and now i have root access.. blah blah ill be back im sure.
I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
hhai2pth said:
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
DrShenanigan said:
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
Click to expand...
Click to collapse
You need to go on sammobile and download your stock firmware (you probably want to stay on 4.3 unless your particular phone and carrier have root capabilities on 4.4.2 which verizon and att do not yet have) then flash it through odin... just search your model # through sammobile and it will show all the available stock firmwares. That will at least get you running again then u will have to root it again from there
Posted from my beast of a VZW Note 3!!
I downloaded the firmware from that site and have tried to flash it.
I get an Error Meassage:
SW REV CHECK FAIL : [sb1]Fused 2 > Binary 1
DrShenanigan said:
I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Click to expand...
Click to collapse
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
antique_sonic said:
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
Click to expand...
Click to collapse
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
DrShenanigan said:
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
Click to expand...
Click to collapse
Try this, mate
http://forum.xda-developers.com/showthread.php?t=2466423
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
Hello everyone,
I've noticed that there hasn't been any threads about rooting the Xperia Z2 Tablet on lollipop. Most threads have discussed how to root the device on 4.4.4 and to create an update image to maintain your root whilst updating to 5.0+.
I've scoured the interwebs and found nothing so I'll make it easy for those whom don't know how to achieve root or don't want to do much work without creating images and such.
First off I'm not responsible for any inconvenience that may come with rooting your device and losing your warranty. I can and will be willing to help out in restoring or answering questions that you may have.
This method uses Kingroot... For those who have a problem with kingroot, it is only used to achieve root and this guide will also be showing you how to remove kingroot and install Supersu with ease. Using the link below download the necessary files: Kingroot V4, Supersume, XZDualRecovery 2.8.26. Place all these files on the root of your devices internal storage/SD card excluding Xdualrecovery as that needs a PC. (If you want to Xposed working I will also supply the files needed for that as well). https://www.mediafire.com/download/wrsajbgw2jr6czt
*Make sure you have unknown sources enabled under Settings>Security>Device administrators as well as Developer Options available and USB debugging enabled. (To enable Developer Options go to Settings>About Tablet>Build Number and click it 10 times).
1. Install NewKingroot.apk and run the application. It will notify you that a root method was found and to try it. It may take up to 2 minutes to achieve root. (If all you wanted was root and are content with kinguser then you're done! :good: if you want Supersu and/or a custom recovery then continue on to step 2!
2. Connect your Tablet to your PC via microUSB. On your PC open and extract the contents of TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip to your desktop. Now double click install.bat a screen will pop up providing you with options to install xdualrecovery. Choose option 2. Installation on ROM rooted with SuperUser by pressing 2 and enter. The script will run its course and tell you to grant permission on your tablet. Open up your tablet and a kinguser prompt will show asking you to grant or deny permission to ADB (Grant it!!!) afterwards your tablet will reboot on it's own to TWRP. (I advise you to either make a backup of the tablet now or after you install Supersu as insurance in case of any mishaps). Click reboot System.
3.Install Supersume, open the application and run it. It will of course ask to grant it permission (Grant it!!!) it will check the environment (making sure that there isn't any Pokemon nearby that you don't need... Sorry Pokemon Go reference) and it will begin removing kingroot and install Supersu. If you didn't have Supersu installed already great! It'll open up Supersu automatically. Supersu may ask you to update binaries (DO NOT click TWRP as it will reboot and you have to start the process over from step one!!! :crying: Just click Normal and once it says successful you're done! :victory: The next step is optional if you Want Xposed.
*Optional 4. Install XposedInstaller_3.0_alpha4.apk. Open your app drawer and open NDR Utils. It will ask for permission (Grant it!!!) now here you may choose your preferred recovery... Philz Touch Recovery,TWRP or Clockwork Mod Recovery. Click Reboot to Primary Recovery (fourth option) once it's rebooted you want to click install>SD>xposed-v85.1-sdk22-arm-by-romracer-20160620.zip and swipe to install. You should get a success when it's finished. Now simply reboot and your apps will be upgrading. Congratulations you now have root with SuperSU and xposed! :victory:
**if you wish to uninstall Xposed simply reboot to recovery and click install>SD>xposed-uninstaller-20151218-arm.zip uninstall the application once it's rebooted and you're good to go!
***if you have a problem with Supersume not working, reinstall Newkingroot.apk and run it again to get root. Then run supersume again (Grant permission!!!) and let it run its magic.
If anyone has issues, has questions or needs help PM and I will do my best to help and answer all your questions. Please don't be discouraged because I'm new here! I will be soon adding a link to a video tutorial on how all these steps can be done!
I have the Verizon 561, will this allow rom upgrade to marshmallow?
chin_bone said:
I have the Verizon 561, will this allow rom upgrade to marshmallow?
Click to expand...
Click to collapse
Hi there, I also have SGP561 as well for Verizon. Verizon didn't release Marshmallowfor the device yet unfortunately. ???? still waiting and more then willing to confirm when it does
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
creepingcreep said:
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
Click to expand...
Click to collapse
Glad it worked for you. Just wanted to help people out as I had invested time trying to figure out my own. I didn't like flashing files constantly so tried making easy.
Never had luck with kingoapp and today isnt any different
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Sent from my SM-G930V using XDA-Developers mobile app
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Sent from my SGP561 using XDA-Developers mobile app
ToneLa said:
Never had luck with kingoapp and today isnt any different
Click to expand...
Click to collapse
Sorry to hear what version are you using? Use the provided KingRoot in the download link provided
Daimonion1980 said:
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
Click to expand...
Click to collapse
No, in the link provided all necessary apps and folders/zips are included. Including KingRoot apk
Cammy253 said:
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Click to expand...
Click to collapse
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
JediDru said:
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Click to expand...
Click to collapse
That's great news to hear! I picked one up and wanted to root and I did on KitKat but when I upgraded to lollipop I lost root and rooted it the long way... Needed something simpler and couldn't find anything on here. So I wanted to make sure a guide was available to all. Enjoy and let me know how it went
reymund602 said:
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
Click to expand...
Click to collapse
Thank you working great
Sent from my SGP561 using XDA-Developers mobile app
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
ToneLa said:
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
Click to expand...
Click to collapse
Let me double check and if anything I'll post a link to the apk
Sorry that you're having issues though
bilestoad said:
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
Click to expand...
Click to collapse
Thanks for confirming! If you didn't see the KingRoot apk in drive I'll upload the current version!
ToneLa said:
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
Click to expand...
Click to collapse
What is the software version you are having problems with?
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.