Related
So the other day I rooted my Inspire 4g, and it is now Unlocked. Now when it boots up and everything else, I see no superuser, so I just download it and some other apps that require a root access. And when I try to use it, says I have no root access, so I go into superuser, slide to the left and see that no Su Binary is there or found? And I used EasyUnlockTool to root my Inspire. I've been looking around for answers to solve how to fix this, but come to no luck or I am just plain dumb. I've been having some trouble with this, help would much appreciated. I need some help as to what I need to do? :\
You have only unlocked your bootloader, you have not rooted your phone. Those are two separate things.
Well think you could direct me to a way that I will be able to root it? I've been having a stressful time trying to. I've been trying everything on how I saw it.
Installing the app doesn't provide the su binary, but flashing the zip does. You could flash a superuser zip from recovery (I know SuperSU has one somewhere on XDA), or you could flash a rooted ROM. Or, you could use the Easy Ace Root Tool.
This is all documented in the Ace Think Tank thread, in multiple stickies in the Desire HD forums, or in various other threads concerning the same question. Details can be found there.
Do you know how long it takes when you go into the bootloader and Vol- to and press the power button on recovery, as when I did, it just stayed on the load up screen, with the white background and green HTC in the middle? Just wondering if you knew. But I will do what you just told me, thank you.
Nizun said:
Do you know how long it takes when you go into the bootloader and Vol- to and press the power button on recovery, as when I did, it just stayed on the load up screen, with the white background and green HTC in the middle? Just wondering if you knew. But I will do what you just told me, thank you.
Click to expand...
Click to collapse
Have you flashed a custom recovery from fastboot?
Yea, I used GooManager, hopefully I didn't do anything wrong?
Nizun said:
Yea, I used GooManager, hopefully I didn't do anything wrong?
Click to expand...
Click to collapse
No idea then. You could try flashing a custom recovery.img from fastboot.
Alright, I'll be trying that then. Thank you.
I was messing with a bunch of stuff like supersu me, trying to replace kingroot with supersu in terminal emulator, but I don't think that had anything to do with it. I re-ran kingroot today, and now, even if I power it off all the way, or reboot, it still holds root! Permanent root is a big step, but I always want more. lol. I'm hoping there will be a way to replace it with supersu soon, and get flashfire working. On 5.1.1 BOH4 Good luck everyone!
Edit: I have no idea how I was able to keep a permanent root, but alas, I had to go messing with $#!+, and end result was having to flash stock firmware and not be able to get permanent root again. I'm not sure if things I was messing with played a strange part, or if somehow kingroot magically went through that one time, but it sucks to have lost it. I can replace kingroot with supersu using a Replace_Kinguser_with_SuperSU-v2.4 zip file, flashing it in terminal emulator, then using a power menu for root app to soft reboot before kingroot fail errors start to pop up. Sadly, if hard reboot or power off and on are done, root with supersu are wiped. If you do this, don't update the su binary or you'll hang at at&t logo in a softbrick.
whats wrong with twrp?
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
the bootloader is locked
xjimmy said:
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
Click to expand...
Click to collapse
if i remember right theres some files thst you need to delete to prevent "unroot" in boot...... similar to stock recovery flashing back on some devices after installing twrp or cwm
My rooting experience with kingroot has been temp root, with reboots causing soft brick, an update to kingroot making reboots possible without bricking, but causing unroot, and the latest update where it retains root after reboot. So whatever they did, it's working now. It is limited, however, as I doubt cwm or twrp is flashable, and flashfire doesn't work with kingroot.
What I don't want is for people to doubt me. It's easy to download the latest kingroot and try it. The lp fix boot.tar is still available, but you'll see, you won't need it. And the stock firmware .tar is available so you really have nothing to lose. What I'm hoping is, more people do it so we can move forward. I'd like to see a new version of supersu me, and flash fire working. Get to a point where we see some custom roms.
Which version of KingRoot did you use? 5.0.0 or 5.0.1?
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
KGB7 said:
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
Click to expand...
Click to collapse
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
xjimmy said:
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
Click to expand...
Click to collapse
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
KGB7 said:
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
Click to expand...
Click to collapse
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
xjimmy said:
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
Click to expand...
Click to collapse
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
KGB7 said:
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
Click to expand...
Click to collapse
I replied to this comment a while ago, so I thought. lol. You ever reply to something, hit submit, and come back later to find it not posted? grrr. Thank you for at least trying again. It wouldn't seem likely that by simply clearing the cache, root would get wiped. I almost want to try it myself. What I wrote was that I would, if possible, love to do a system dump, or whatever they call it, so a developer could take a look at how and why I have permanent root. That would be to say that a developer would be interested at all. Supersu just froze in the process, and I read it's because kingroot now patched it so it wouldn't remove their root. Would be cool to get supersu on it and maybe get a custom rom or two.
Get bootloader unlocked
toolhas4degrees said:
the bootloader is locked
Click to expand...
Click to collapse
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
nd4400 said:
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
Click to expand...
Click to collapse
Ask at&t nicely.
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
bbc581 said:
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
Click to expand...
Click to collapse
I read that too, but you know what, it still doesn't work. I've found a zip file called Replace_Kinguser_with_SuperSU-v2.4 that works. What you do is install a power menu for root users first, then root with kingroot. Next, you install the replace kinguser zip using terminal emulator, which there are instructions online and on youtube on how to do it. Once you've replaced kingroot with supersu, quickly use the power menu app to do a soft reboot, as to avoid kingroot failure errors. DO NOT update the su binary. Only problem is, if you do regular reboot, or power off the tab, then power it back on, root is lost again. I have no idea how I got permanent root with kingroot, but I've lost it now while messing with things. I wish I would've tried to replace it with supersu this way when I had it just to see if it woul've still retained permanent root as well. Now what?!?! lol
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.[/QUOTE]
Hey man, old stuff, I know, but I thought this was interesting:
http://androidforums.com/threads/tutorial-how-to-root-the-sm-t337a-lollipop-with-kingroot.1100261/:
I'm not sure if he's saying to keep rebooting, and re-rooting until root sticks permanently, or to leave kingroot running without rebooting for a long time, and permanent root will sink in eventually. I think he means the second one, too leave it running without rebooting. On a sidenote, I have been able to use a replace kingroot with superuser 2.74 via terminal emulator with success, even after rooting with latest version kingroot. Updating supersu binary results in softbrick on reboot though. If you don't update user binary, and you reboot, you just lose root, is all. And sometimes the zip doesn't work, and it takes reboot, re-root with kingroot, then re-run terminal emulator. Flashfire doesn't like kingroot, but it opens up with supersu after this method. Not sure if it can actually flash zips though. Just thought I'd share my latest findings.
xjimmy said:
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
Thanks for the info. An interesting discovery! After going back and reading that guy's article again, I noticed that he posted a link to download kingroot. I was curious what version he used. It was 4.8.1 . When I tried downloading 4.8.1 from the xda link you gave me, it kept popping up with a network error. This time I downloaded 4.8.1 somewhere else and tried it. After root, I kept closing kingroot, swiping it clear in task manager, and re-opening it until it gave me the notice that it deployed itself as a system app. I then rebooted (not soft reboot) and it partially kept a permanent root this time. If I went into root checker, it would tell me no root, but other apps were popping up the grant permission tab. I'm sure I'll get root to stick permanently again, then I'll try to install supersu over it again, see if I can't get that as a permanent root. It's not the end of the world to me either, but it just drove me nuts not knowing how the hell I got it. Also, it's just fun to mess with stuff. lol. So in the chain of updates, 4.8.1 is right before 4.9.2, so I'm guessing that I probably got permanent root from 4.8.1 and then updated it, or possibly that I ran 4.8.1, updated, and maybe optimizing or running root again with 4.9.2 finished the job. Anyway, thanks for writing back!
Click to expand...
Click to collapse
hello i have a samsung galaxy express 3 j120a ud i have fallowed the instructions here to root my device and it worked up until i tried to install super su or super sume i tried super sume and it crashes and says it closed unexpectedly i have knox frozen btw with link2sd and i do have root from oden and king root so whatever but i found a recovery here but i dont understand how to flash this since i dont have a custom recovery i also found a "moded" recovery for the galaxy express 3 on a mexican website i cant find the website but i still have the moded recovery img and i flashed it but when i tryed to boot into recovery it told me to go to an AT&T store for help because software had been found that is not allowed etc... anyway is there twrp or cwm or a custom rom for this model phone specifically i have root heres a link to the exact phone i have thanks any help is appropriated thanks. NOTE: i cant post links cause noob status.
NOTE: i just got su binary updated and super su to install sucessfully so yea. thanks
I got viper4android working with samsung galaxy express 3 sm-j120a read more down.
Could you possibly share how you finally got SuperSU to install properly so other folks could know? I'm looking for the process myself.
Chuck
digitalchaos1980 said:
Could you possibly share how you finally got SuperSU to install properly so other folks could know? I'm looking for the process myself.
Chuck
Click to expand...
Click to collapse
ok so i used this link to root my phone with king root http://techbeasts.com/root-galaxy-express-3-j120a/
Required downloads:
Download and install Samsung USB drivers
Download and extract Odin 3.11.1 on your computer’s desktop
Download boot image for your phone: ENG_BOOT_J120A_PG1
Download KingRoot and Super SUME APK files. Extract the folder and copy the APKs to your phone’s internal storage.
How to flash boot image to make the phone root-able
Open Odin.exe from the extracted Odin files you downloaded on your computer’s desktop.
In Odin, click the “AP” tab in Odin and select the ENG_BOOT_J120A_PC1.tar for your device that you just downloaded above.
The only options checked in Odin should be Auto Reboot and F.Reset Time. No other options should be ticked.
Now put your phone in download mode. Turn it off first. Now press and hold Volume Down + Home + Power buttons. As soon as it boots up, leave the keys. Once it shows warning, press Volume Up to continue.
Connect your phone to your PC while Odin is open.
Once your the ID:COM box turns blue in Odin after the successful connection, click the Start button.
It will flash the boot image file and reboot the phone now.
Install Kingroot
Now on your phone, go to settings > security > allow unknown sources.
Open a file manager and locate the copied Kingroot APK file.
Tap the Kingroot APK file and install it.
Once installed, open Kingroot from the app drawer.
Tap the Android Icon on the screen shown in Kingroot or if it’s already processing, let it do that.
Kingroot will start finding an exploit to root your device now. As soon as it finds an exploit, it will root and reboot your device.
Replace King User with SuperSU
Install Super SUME APK just the way you installed Kingroot.
Open Super SUME from the App Drawer now.
Follow the instructions on-screen to finish the Super SUME procedure.
Super SUME will begin to uninstall Kingroot in favour of SuperSU now.
After uninstalling KingRoot it will install SuperSU.
SuperSU will appear in app drawer after installion. That’s all.
NOTE: sometimes when u flash the ENG_BOOT_J120A_PG1 file to get root with king root it wont work try rebooting trying again or flashing file again with odin i had to flash 3 times in some cases.
READ ALL BEFORE TRYING ROOT IMPORTANT!
and after i got king root to root my phone through this method i had to downlaod a different copy of supersu me pro from i think this link https://apkpure.com/super-sume/darkslide.com.supersume if its not the right one then just google a pro copy apk but yea so once super user is done with king root and u have a copy of supersu me pro that works just run it u may have to do it a few times and it may act funny or seem to pause half way through the root process but if it dose (like it did on mine) just have supersu app installed and run it while supersu me pro is running and it should install sucessfully keep trying till it dose thats what i did oh btw when u get super user with king root download link to sd and freeze all these apps ok (scrole down)
bbcagent
com.sec.enterprise.knox.attestation
device protection manager
diagmonagent
easy setup
elm agent
galaxy apps
klms agent
knox
knox setup wizard client
knox apps update agent
knox folder container
lookout security
new registration
personal data managnmment
rcpcomponents
remote controles
rootpa
samsungdlp services
security policy updates
security log agent
setup & transfer
spftware update
usage manager
att adress book sync
at&t locker
at&t navigator
at&t protect plus
at&t smart wifi
at&t software update
callername id
and keep runing supersu me pro and supersu me untill it installes root succesfully that worked for me
also i JUST got viper4android to work with samsung galaxy express 3 btw fallow the guide in this video https://www.youtube.com/watch?v=nFqbz8Ytjx0 and download the files from the mega link in description of video.
and now i have supersu and viper4android NOTE: be sure to have installed bussybox before trying to install viper its needed i got my bussybox from fdroid.
also if u want to get xposed modules working download an app called flashfire i think 0.53 is the latest once u have root with supersu and download and install xposed framework wanam 20161128 and flash the zip with flash fire and a side note the newest copy of gltools also works with driver support i havent had a single problem with gltools. if ur system ui crashes after boot eather keep rebooting untill it stops crashing or unsinstall an app u may think caused the issue or unfreeze an app that may be causeing it dont freeze apps unless u think its safe do it at ur own risk and freeze only apps i have found to be frozen with little to no problems. as far as xposed modules go lucky patcher installs but dosent work right due to not being on a custom rom and device id changer free works fine and xinternal sd works great and xprivacy works great and android n ify works great also gravity box for 6.0 marshmallow works fine but i only used it to make volume buttons switch tracks and for a battery bar i recomend not useing it for anything else as it has caused my phone to freeze and crash and bootloop so if u want a battery bar and to change tracks on lock screen use gravity box if u dont need those things then dont use it at all or at ur own risk.
so now u have viper and xposed and supersu enjoy it has been a pain in my ass for a long time so have fun. NOTE: there is no custom recovery for this phone sometimes when u flash these files the phone will bootloop but TRUST ME if it boot loops take the battery out and turn it back on untill it turns on sometimes doing this will force the phone to clear dalvic catch i think because it upgrades all the android apps again so keep removing the battery if it dosent work after about 20 tries the reflash ur stock rom with odin just download a stock rom from google for this device and flash all files ap=ap etc... hope this all helps
Thanks for the reply back! I had originally followed those directions from that site and it didn't work the first time. I kept trying different versions of Kingroot and Super SU ME with no luck, then I decided to try Kingroot 4.1 and a zip file that when extracted and ran from terminal is supposed to replace Kingroot with Super SU. It only partially worked that being when an app asked for root it was Super SU asking the permissions. I thought I was in the clear then so I tried to let the Super SU app update the binary, but it failed. So I downloaded Flashfire and flashed Super SU zip and it worked and I thought I was hot sh*t until it rebooted lol. When it rebooted it gave me the "Unauthorized software found on this device. Please take it to an ATT dealer blah blah blah". So I downloaded factory firmware and tried again only this time before I used Flashfire to flash the Super SU zip I went and deleted all the Knox crap and most of the other stuff in your list above and it worked that time lol. I already have Xposed and a bunch of other root apps on there working pretty well so far. It's a neat little phone for a cheapy. I have an S6 as a daily driver but I like toying with the Galaxy Express 3 when I can. My driving reason behind wanting to root it is because the Wi-Fi chip inside is a brcm43438 which supports monitor mode, sorta. The Raspberry Pi 3 has the same chip and can be used with pentesting tools and since it runs on android also, I hoped to find a way to port the patched firmware to this phone. But for now it gives me something else to tinker with lol. Thanks again for the long reply, I know someone out there can maybe use our methods or a combination thereof to get this phone rooted when it wants to be difficult!
Chuck
---------- Post added at 10:21 AM ---------- Previous post was at 09:57 AM ----------
Oh and if anyone has to end up flashing factory firmware, don't get the firmware ending in PJ2, it didn't allow the special bootloader file to flash. I had to download the firmware ending in PC2 for it to work. Just an fyi!
Chuck
ur very welcom thanks for ur help as well
Yea man, no problem! God knows I've gotten enough help thru this site by either reading til my eyes bled or just asking a question lol. It's nice to give back every now and then
Chuck
digitalchaos1980 said:
Yea man, no problem! God knows I've gotten enough help thru this site by either reading til my eyes bled or just asking a question lol. It's nice to give back every now and then
Chuck
Click to expand...
Click to collapse
its nice to help but i think the thing that bothers me the most is when i ask for help on here and people eather complain that i havent googled it (even though i have) and even if i havent big deal, or they r rude and tell me im "crying" because i put to many Z's ont he word plzzzz its ridicules and its like look eather help me or not dont put me down for asking for help or make fun of me jeez ya know?
anubis2497 said:
its nice to help but i think the thing that bothers me the most is when i ask for help on here and people eather complain that i havent googled it (even though i have) and even if i havent big deal, or they r rude and tell me im "crying" because i put to many Z's ont he word plzzzz its ridicules and its like look eather help me or not dont put me down for asking for help or make fun of me jeez ya know?
Click to expand...
Click to collapse
Yea, you're going to find people like that anywhere you go. Don't let it discourage you from this place. Yes, searching first is one of the rules, but sometimes you just can't find what you are looking for! There are a lot of great and very knowledgeable folks on this site. It's where I come to look up pretty much anything I can't figure out on my own. And I come to contribute when I can.
Chuck
digitalchaos1980 said:
Yea, you're going to find people like that anywhere you go. Don't let it discourage you from this place. Yes, searching first is one of the rules, but sometimes you just can't find what you are looking for! There are a lot of great and very knowledgeable folks on this site. It's where I come to look up pretty much anything I can't figure out on my own. And I come to contribute when I can.
Chuck
Click to expand...
Click to collapse
yea i compleatly agree with you and yea thanks i wont get discouraged its just kinda of a bother thats all but yea im just glad someone appricates my posts thanks :good:
digitalchaos1980 said:
Thanks for the reply back! I had originally followed those directions from that site and it didn't work the first time. I kept trying different versions of Kingroot and Super SU ME with no luck, then I decided to try Kingroot 4.1 and a zip file that when extracted and ran from terminal is supposed to replace Kingroot with Super SU. It only partially worked that being when an app asked for root it was Super SU asking the permissions. I thought I was in the clear then so I tried to let the Super SU app update the binary, but it failed. So I downloaded Flashfire and flashed Super SU zip and it worked and I thought I was hot sh*t until it rebooted lol. When it rebooted it gave me the "Unauthorized software found on this device. Please take it to an ATT dealer blah blah blah". So I downloaded factory firmware and tried again only this time before I used Flashfire to flash the Super SU zip I went and deleted all the Knox crap and most of the other stuff in your list above and it worked that time lol. I already have Xposed and a bunch of other root apps on there working pretty well so far. It's a neat little phone for a cheapy. I have an S6 as a daily driver but I like toying with the Galaxy Express 3 when I can. My driving reason behind wanting to root it is because the Wi-Fi chip inside is a brcm43438 which supports monitor mode, sorta. The Raspberry Pi 3 has the same chip and can be used with pentesting tools and since it runs on android also, I hoped to find a way to port the patched firmware to this phone. But for now it gives me something else to tinker with lol. Thanks again for the long reply, I know someone out there can maybe use our methods or a combination thereof to get this phone rooted when it wants to be difficult!
Chuck
---------- Post added at 10:21 AM ---------- Previous post was at 09:57 AM ----------
Oh and if anyone has to end up flashing factory firmware, don't get the firmware ending in PJ2, it didn't allow the special bootloader file to flash. I had to download the firmware ending in PC2 for it to work. Just an fyi!
Chuck
Click to expand...
Click to collapse
could you provide a link to the pc2 one, or maybe even email it to me? i cant find it anywhere. all i can find is ones ending in pj1 or pc1. id appreciate it very much
yea this is the files i used heres a link https://docs.google.com/uc?id=0B62nWP8Yfdegck5wRnZyYkRqR0k or http://www.allphonefiles.com/2017/01/samsung-galaxy-express-3-sm-j120a-stock.html make sure to flash all files in .zip with odin ap file flashes to ap etc...
hope that helps
Firmware
digitalchaos1980 said:
Thanks for the reply back! I had originally followed those directions from that site and it didn't work the first time. I kept trying different versions of Kingroot and Super SU ME with no luck, then I decided to try Kingroot 4.1 and a zip file that when extracted and ran from terminal is supposed to replace Kingroot with Super SU. It only partially worked that being when an app asked for root it was Super SU asking the permissions. I thought I was in the clear then so I tried to let the Super SU app update the binary, but it failed. So I downloaded Flashfire and flashed Super SU zip and it worked and I thought I was hot sh*t until it rebooted lol. When it rebooted it gave me the "Unauthorized software found on this device. Please take it to an ATT dealer blah blah blah". So I downloaded factory firmware and tried again only this time before I used Flashfire to flash the Super SU zip I went and deleted all the Knox crap and most of the other stuff in your list above and it worked that time lol. I already have Xposed and a bunch of other root apps on there working pretty well so far. It's a neat little phone for a cheapy. I have an S6 as a daily driver but I like toying with the Galaxy Express 3 when I can. My driving reason behind wanting to root it is because the Wi-Fi chip inside is a brcm43438 which supports monitor mode, sorta. The Raspberry Pi 3 has the same chip and can be used with pentesting tools and since it runs on android also, I hoped to find a way to port the patched firmware to this phone. But for now it gives me something else to tinker with lol. Thanks again for the long reply, I know someone out there can maybe use our methods or a combination thereof to get this phone rooted when it wants to be difficult!
Chuck
---------- Post added at 10:21 AM ---------- Previous post was at 09:57 AM ----------
Oh and if anyone has to end up flashing factory firmware, don't get the firmware ending in PJ2, it didn't allow the special bootloader file to flash. I had to download the firmware ending in PC2 for it to work. Just an fyi!
Chuck
Click to expand...
Click to collapse
Need link to PC2 can't find it at all and can't get. BL file to flash in Odin special boot loader file did flash but can't find PC2. OR HELP WHY BL WILL NOT FLASH
Have root kingroot v5.0
wmhaganjr1013 said:
Need link to PC2 can't find it at all and can't get. BL file to flash in Odin special boot loader file did flash but can't find PC2. OR HELP WHY BL WILL NOT FLASH
Click to expand...
Click to collapse
Ok have root with kingroot but now can't seem to switch kinder to supersu Super Sume does not work gets stuck processing. Tried manual way and looks like everything is good til supersu goes to update binary and does not work so I need help please.
Ps flashed APJ2 IN ODIN BUT (BL) NEVER LOADED ALWAYS FAILED SO I DID THE REMAINING AND EVERYTHING WORKS .
NEED HELP WITH SUPERSU SWAP PLEASE
Ok kingroot swap to superuser
wmhaganjr1013 said:
Ok have root with kingroot but now can't seem to switch kinder to supersu Super Sume does not work gets stuck processing. Tried manual way and looks like everything is good til supersu goes to update binary and does not work so I need help please.
Ps flashed APJ2 IN ODIN BUT (BL) NEVER LOADED ALWAYS FAILED SO I DID THE REMAINING AND EVERYTHING WORKS .
NEED HELP WITH SUPERSU SWAP PLEASE
Click to expand...
Click to collapse
Ok I followed link in above posts but after I ran terminal I let kingroot force close as was said above I used uninstaller pro (root) to freeze kingroot so now I have temporary root with super su now I flashed SuperSu v2
.82 -Sr3 from Chainfire with Flashfire and that updated binary re installed SuperSu app in app drawer then unfroze kingroot and uninstalled it . That's it root with SuperSu All the credit to XDA AND ITS MEMBERS POSTS AND CHAINFIRE. LOOKING AT RECOVERY NEXT???? HMMM .PS NEVER DID GET BL FILE TO FLASH WITH APJ2 all links to other firmware r broken .
---------- Post added at 01:26 AM ---------- Previous post was at 01:24 AM ----------
anubis2497 said:
yea this is the files i used heres a link https://docs.google.com/uc?id=0B62nWP8Yfdegck5wRnZyYkRqR0k or http://www.allphonefiles.com/2017/01/samsung-galaxy-express-3-sm-j120a-stock.html make sure to flash all files in .zip with odin ap file flashes to ap etc...
Click to expand...
Click to collapse
Dead links
Great write up! dead links and a ? about J120AUCS3AQE1
Hi and thanks for the great write up, very clear. My device is a SM-J120A that sports the AT&T logo upon boot.
Have you or any one tried this method with the OTA update that [I think AT&T] pushed on May 1, '17 labeled J120AUCS3AQE1. I have soft bricked device several times trying to use PJ2 and cant find PC2 [above posted links do not work]. One other thing about the AQE1 update I was only able to get it to install by 25%, my Baseband version changed to J120AUCS3AQE1, but the security patch level has remained at Oct. 1 '16 anf the Build number is at MMB29K.J120AUCU2APJ2. Not sure what is up w/that! If any one has a link to the full "4 file" zip of J120AUCS3AQE1 I would greatly appreciate it.
Root successful...........but
I was able to root with firmware version J120AUCS3AQE1 but because mine is an AT&T phone the bootloader is "locked and signed" meaning it's never going to unlock........? I have the latest version of firmware that came out in may 2017 and it will be available to you as soon as I can post an outside web address............ Every Recovery image that I flashed caused everything to fail and a big triangle that said AT&T detected software on your device that is not allowed on our device so I guess this one is never really your own........ but you can Root with Kingroot and supersume pro to get rid of bloatware and such but other than that no custom stuff on this one.
If Kingroot keeps freezing just restart phone and keep trying it took me a long while to obtain root.
Thanks for the Rooting Guide. I found an img file online for a TWRP Recovery for Samsung Galaxy J1, but with the same Build Number (SM - J120A).
1. Should I trust it?
2. If not, is there an exploit for it already?
Really hope someone can help me. Also, Is anyone else loosing wifi connection constantly after rooting?
Cheers,
Express 3 user
Anybody can you please send stock TouchWiz here???
I really need this APK....
NEED HELP!! i made a lot of progress but simple mistakes have me stuck..
I need some help from youi guys, idk igf im just missing something or thinking too much but im stuck somewhere simple because of a silly mistake.... lol -- heres the bkgrnd story: after using the ENG_BOOT and kingroot, i was unable to get supersume to work. in my quest to do so, I ended up with xposed framework installed and working as well as some more apps n tools... well anyway==here's the curveball (#1 - lol) - i edited some fields in buildprop and applied some tweaks - i did an original backup but was unable to find it.. due to the words and windows on my screen being resized (smaller windows larger text, unable to see entire text field and unable to move within individual framed windows li(ke on microsofts launcher homescreen) - so i edited buildprop one more time.... i changed the density and it zoomed in further - double bad move. heres the next one lol - upon reboot into custom android recovery from eng boot - i accidentally wiped/reset phone instead of the dang cache partition. so - now - it reboots, to the WELCOME! ^(language select, accessibility select) START screeb for first time setup. i cannot for the life of me get it to move a window or hope to select AGREE since its "rendered offscreen" on the terms and conditions. unable to use adb, unable to update from ext storage per recovery's settings apparently..
i am however able to use serial com connection and terminal (on bbqlinux) to do a few things and even remotely open shell - idk what i did to buildprop to fubar my screen render, and even after mounting system in recovery i have not been able to push/pull buildprop or edit again, nor usual adb - im frustrated and stopped finally because i know im missing something simple as hell.. #2 ready for the knuckleball? i was able to get TWRP to flash successfully to my phone with ODIN by clicking AP and using nand erase all, repartition and f, reset time - rebooted phone into recovery and its still the eng_boot one. so i cleared cache part mounted system rebooted, then off and reboot to recovery --still no TWRP either.
i would love a copy of a good buildprop file compatible with the engboot and a little help with the buildprop replacement in the given situation lol, TWRP would be a plus - i greatly appreciate your time and help guys and i apologize if i have posted in the wrong thread or something else that is uncooth - its my very first post but im a long time reader and follower as well as an intermediate developer., thank you for your time everyone. this thread is regarding sansung sm-j120a ud with the engboot build. att go phone, no frp lock, secure download is enabled in download mode tho.. -- usb connection to win 8.1 with android studio poison kitchen etc etc - also have bbq linux
Just goot this device rooted! Just gonna test the script a few times so there isent any bugs and i will upload it!
EDIT: Systemless Root methods like Magisk resets after root(I Think SuperSu works if u tweak dm-verity in the kernel). But using system-root both breaks saftynet and is boring
So im gonna try to edit the boot img to work with magisk or SuperSU even if the bootloader is locked.
If none of theese things works there is a way to Re-root after each reboot but its ofc much easyer just to edit the boot.img or unlock the BL
EDIT 2: I will also try to reverse engineer the bootloader to try to find a weak point where we can unlock it, for easyer rooting and creating custom roms
EDIT 3: Also forgot to mention xposed works because you dont "need" root. If anyone want xposed just reply in the thread and il upload the script "as is" even though it resets after each reboot, but root works perfect have tested multiple apps.
And as i said before, before i release the root method publicly i want to check if its the BL who "resets" the kernel like on some HTC devices or if its a simple dm-verity problem , if it is the dm-verity thing its easy to fix.
More info:
Flashing kernel,system,recovery works because the only partitions that are protected are the BL and FRP partions but not for long
So far:
Magisk: Works
Bootloader: Locked
Saftynet: Passes
Proof:
https://i.imgur.com/8uABTSl.jpg
Download:
Code:
Comming in an hour! Just gotta check the updatescript for errors before posting :)
j wait for your script to root my Z500 m thanks to you.
Wow, finally there's a method to root. I own the device since august and I really want to get it rooted due to all bloatware I want to uninstall and to install 3rd party apps.:good:
super thanks to you me too and thanks to you I could root the tablet with all s is unnecessary thank you for your work:good::good::good:
Cant wait
Wow.... time is ticking to bring root to the P027
I can't wait for an update on this.
There must be another way to get a rooted ASUS P027. I tried much but don't have any success. I think that there is a way to push some files manually to /data/local/tmp. Setting right permissions using adb. Finally executing a root-shell-script from one of many should do the rest. Problem is not to get the files inside the system, you have to do it again after each reboot.
I'm a bit nervous to modify bootloaders and flash them on the go with no oem support. If some support for this device comes available from ASUS it should be a lot easyer to do.
I cant upload photo's till i'm no longer seem like a robot. I also got some kind of root on my P027. only for a moment. After reboot it is gone.
I can't wait for that!
Will it come out soon..... so excited ^_^
BigThanh said:
Will it come out soon..... so excited ^_^
Click to expand...
Click to collapse
here too...the hour is over
That would be great
hey, very good news!! I am waiting a long time for this. It would also be nice, if you can give us your xposed script. Thnkas!!
Is p207 the model number? I'm only finding it listed as Z500M.
joshnat said:
Is p207 the model number? I'm only finding it listed as Z500M.
Click to expand...
Click to collapse
Yes
Ok guy's where do we stand on root as of 5pm Wednesday 10.04.2017 ??
I bought the ASUS Zenpad 3S 10 [P027] off Amazon on Saturday on a flash sale for $265, knowing it didn't have root, and that's a shame because it's a beautiful & buttery smooth tablet.
Today, as I was pondering boxing it up for a return, I figured I'd look for myself once more for the hell-of-it, AND BOOM! I found this thread!
So where are we guys? I'll test it for ya or whatever! So friggin' pumped ROOT has been established! Dare I say -Vanilla Oreo ROM with onscreen softkeys??? YEAH!
Really looking forward to this! I don't mind getting my hands dirty, but just waiting for the script I'm very happy to have stumbled upon this thread, can't wait to have root on this tablet!!
Fortunately we will get to see the script. I own the P027 since auust 17. A very good hardware. But without root its only worth half. So, me too is awaiting the script but so far I guess we still have to wait. Til now, no root app works (iRoot, Kingo, e.g.) Very sad because I think that once we rooted it and get rid of all the OEM bloatware, this tab may rocks a lot more.
Prinz069 said:
Fortunately we will get to see the script. I own the P027 since auust 17. A very good hardware. But without root its only worth half. So, me too is awaiting the script but so far I guess we still have to wait. Til now, no root app works (iRoot, Kingo, e.g.) Very sad because I think that once we rooted it and get rid of all the OEM bloatware, this tab may rocks a lot more.
Click to expand...
Click to collapse
to remove bloatware, i followed this guide. I can confirm ist works.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Can you go ahead and upload the script for those of us brave enough to try it? Thank you for all your hard work!
I got root and xposed. But I don't have a way to get it in that device
At my next post will I upload a photo or link of my own (semi) rooted P027. The Magic of rooting a device which is unsupported is far away from easy as flashing chainfire's zips or something possible using Odin or what. Most likely if there was a custom recovery for the P027 root would be easy because of all possibilities you have.
I've tried a lot of other ways to get in to try modify something in that locked system. It is hard to get there without losing patients! I also lose social networks I belong to. Even if days counts 48 hour instead of 24, root wasn't there with the success I had hope to. Sometimes only after manually redirecting some files with adb and manually setting right permissions to every file. It becomes possible to get accessing "su" in terminal app. Only sometimes, after each modifying something, you're device needs to reboot for applying that modification. At that point you lose everything before you can use it.
If someone can post latest boot.img I will try to patch it with Magisk. If that is possible it will get easier to activate systemless xposed. A few weeks ago on note 8 launch day... It took at least 1 hell of a day before root came available on xda. Also twrp and custom roms are available.
Hope soon to make it happening for real.
hi I would buy this tablet but wanted to understand root situation. can you run the root on this device? you can install Rom?
toineh said:
At my next post will I upload a photo or link of my own (semi) rooted P027. The Magic of rooting a device which is unsupported is far away from easy as flashing chainfire's zips or something possible using Odin or what. Most likely if there was a custom recovery for the P027 root would be easy because of all possibilities you have.
I've tried a lot of other ways to get in to try modify something in that locked system. It is hard to get there without losing patients! I also lose social networks I belong to. Even if days counts 48 hour instead of 24, root wasn't there with the success I had hope to. Sometimes only after manually redirecting some files with adb and manually setting right permissions to every file. It becomes possible to get accessing "su" in terminal app. Only sometimes, after each modifying something, you're device needs to reboot for applying that modification. At that point you lose everything before you can use it.
If someone can post latest boot.img I will try to patch it with Magisk. If that is possible it will get easier to activate systemless xposed. A few weeks ago on note 8 launch day... It took at least 1 hell of a day before root came available on xda. Also twrp and custom roms are available.
Hope soon to make it happening for real.
Click to expand...
Click to collapse
Here is the boot.img from WW_V14.0210.1709.27: https://mega.nz/#!4bQExBTB!5fyivXxvP4aYAxCDjsYRJ1X7o1wMXYGBLf1TO0ns-z4
I downloaded the WW_V14.0210.1709.27 firmware from ASUS Support then unzip the package to get this file.
Hope it will be helpful to you. I am really looking forward to root this device!
Thank you for your hard work!
Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!
DampDeceiver said:
Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!
Click to expand...
Click to collapse
Look in the forums of how to unlock, root and install TWRP recovery. I actually enjoy system wide black themes so this is what I would recommend.
You need to unlock your bootloader if you had not done so already. In the forum I suggested, under the rooting section, you need to grab the bootable Magisk file. You will have to put your OP6 into fastboot mode and open up a command prompt and type- fastboot boot "name of img file" to boot using that img file.
All these instructions are in the forum regarding unlocking and rooting the device. If you are only interested in obtaining a system wide black theme while also keeping everything in good shape, you need to unlock your bootloader and root with Magisk. Do not worry about installing TWRP as you do not need this for your certain needs. After you root with Magisk, you can use an app call Adaway to block ads. To obtain a system wide black/dark theme, you need to go to the Google Play Store and download an app called "Substratum" after you obtain root. It will only work with root. Also download an app called "Swift Black". This is the theme you will be applying.
I would look at the forums again, the one I am talking about is up there at the top of the page when you look at the OP6 forums. It is clearly labeled for unlocking, rooting and installing TWRP recovery. You are only interested in unlocking your bootloader and installing Magisk, that's it. It has all the instructions you need. Once you are there, install the apps above from the Google Play Store and apply the theme using Substratum. Hope this helps!
DampDeceiver said:
Hello all,
I got my Oneplus6 recently, for the first time using android. I've had an old iPhone for forever.
I like the phone but I'm so far not really happy with the android version (Oreo).
For example: I pick the dark theme from the settings, and my notification tray will stay bright white. I really don't like this. Then I went ahead to try a couple of apps to dim the screen more than the default will allow (it's too bright for my taste). They worked fine, untill I pulled down the notification tray. The contrast feels like staring directly into the sun!
After learning that google now apparently blocks overlays on the notification tray, I figured my only option is to root. Also I would like to use a systemwide adblock and YT Vanced, and maybe some other cool (beginner friendly) things that require a root. However, I would very much like to keep basic functionality, mobile signal, using banking apps, and so on. I don't watch netflix or amazon, only youtube and sometimes twitch, so the L1 and L3 things are not something I worry about.
For the past 5 days or so I've been reading these forums, reddit, and researching the web for information about unlocking,rooting and so on. But I still have a couple of questions, hopefully you experienced users can help a noobie out! I really want to learn.
Currently on these forums, as far as I can see, there are ways of rooting with Magisk and (unofficial) TWRP, the latter also making a custom recovery.
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
If I go with the Magisk root ( https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 ), do I still need a custom recovery? I think that is what TWRP is for. Say I want to remove my root and go back to factory default. Can I do that with the stock recovery?
Is it good to go with the guide I linked, or is it better to use the TWRP method described here: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
What are the major differences between them?
Should I wait until an official TWRP is released and unlock/root then?
I'm sorry if these are very silly things to ask. Keep in mind I've only been using an android device for the first time, ever, since a couple of days. I'm okay with tinkering with it while following a guide to make sure I don't brick or anything. Also I've been looking for a complete beginner guide to unlocking and rooting, but all I can seem to find are very outdated guides.
Thank you for taking the time to read!
Click to expand...
Click to collapse
you should totally root it!
This is how I did it!
Note u will break warranty, and unlocking bootloader will completely wipe ur phone(even the storage memory)
Download the following:
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3791316 (install this on computer)
and https://drive.google.com/open?id=15mXZz4OrwRGXz5JCKeYjwukQf0raWnOb
in your phone go to settings> about phone>Select "Build number" 4 times.
Then in Settings>Developer Options> turn on "OEM unlocking", "USB debugging" and for convenience "Advanced rooting".
Click reboot and Select "Bootloader"
Plug your phone to your computer and open the software you installed and click "check device" Then unlock, on your phone you will have to use volume buttons to go up and down and then the power button to select.
(Note, never relock with custom firmware or root on it, recommend u only lock it when 100% stock or u can permanently brick if something happens when ur rooted.)
Now on that software, you had click advanced options and click "Open a free terminal with adb and fastboot privileges".
Extract that zip file and move it to your desktop.
Type: cd "C:\Users\Bradley Gregory\Desktop" or if its in the folder: cd "C:\Users\Bradley Gregory\Desktop\All files for TWRP"
Then type: fastboot flash boot_a twrp.img , (Your using the same twrp.img)
Then again: fastboot flash boot_b twrp.img
After this look at your phone and use the volume buttons till it says recovery and press power button.
If it asks for a password type ur pin in from phone, and change language before pressing checkmark.
Then copy everything from that zip onto ur phone(when ur in the temporary recovery)
Then click install, find file location of where u put your stuff on. bottom right button click (img file) then click "boot.img" then select boot.
Now click the bottom right button to change back to zips.
Flash zips in this order
1. Flash TWRPWorkingInstaller.zip
2. Flash TWRP-BLUE-FIX.zip
3. Flash Root.zip or you will bootloop
after you can reboot your phone. Open magdisk app >settings and under update settings change update channel to beta. then you can go to the app home and install directly the new update.
(optional) in magisk select download and search busybox and click install
Hope this helps!
PM me for any questions!
(don't factory reset with custom boot. also in recovery, u can now make backups of your entire phone if error happens)
I recommend u download this file:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
if u ever hard brick this will wipe ur phone and make it normal again(wipes internal memory)
Personally, I would hold off on doing anything until we have an official twrp and more development. Right now, the solutions we've got are unforgiving. People are bricking their phones right and left because they missed a step, and the unbricking process is more involved than other android phones at the moment.
Also, before you do anything, I would take a moment to assess your computer literacy and comfort with mucking around in the system files of your devices. If you're used to things that "just work" like on iOS, you may not like what you find once you cross over into modding. If you do enjoy that kind of stuff, good, but the tradeoff for greater freedom is more work in keeping your phone updated and operational.
Don't do it!! Hold off,. I am an old hat, since 2005, and I spent the whole day yesterday fixing the brick that I turned my OnePlus 6 into. It's a pain and very easy to do.
Just wait two weeks.
Sent from my ONEPLUS A6003 using Tapatalk
Personally, I would hold off on doing anything until we have an official twrp and more development. Right now, the solutions we've got are unforgiving. People are bricking their phones right and left because they missed a step, and the unbricking process is more involved than other android phones at the moment.
Click to expand...
Click to collapse
Agree. I've been rooting and modding devices (mostly Oneplus) the last couple of years, but with the OP6 things have changed. A/B partitioning have made it somehow more complicated, at least compared to what I'm used to.
Personally I pulled the trigger anyway, i.e. not waiting for an official version of TWRP. I got TWRP and root with the method described in post 70 here: https://forum.xda-developers.com/showpost.php?p=76633618&postcount=70
If and when you do that too I recommend you to install:
* Adaway (from XDA forum) to get rid of ads
* Substratum theme engine (from Play Store)
And then some Substratum themes:
* Ozone (from Play store) to theme Oneplus OS and apps
* Swift Black (from Play store) to theme other apps
And finally some Magisk modules:
* Youtube Vanced Magisk black themed (from Magisk repo) to get themed You tube, adfree and with picture-in-picture
* Viper4Android FX (from Magisk repo) to get much better audio
* OP_AlwaysOnDisplay_enabler (from OP5T XDA forum) to enable settings for Always On Display (if you want that)
https://www.xda-developers.com/enable-always-on-display-oneplus-6-oneplus-5-5t/
Is this TWRP custom recovery something I need, when I want to keep using OxygenOS? Keep in mind I'm only really looking to apply a black theme on it all, including that blasted notification tray.
Click to expand...
Click to collapse
I strongly recommend you to use a custom recovery (TWRP) if you root and install rooted apps. If you don't it will be difficult or impossible to recover if you get in trouble. For example, it is easy to uninstall Magisk modules or Substratum themes from the recovery in case they cause bootloops. And additionaly you can make full backups of your system in TWRP. A small hint for backups is to copy them to a safe place (computer or USB stick) in case you get into trouble with the internal storage on your phone.
The A/B partitioning has definitely made things more complicated, especially with respect to flashing. I've been rooting and modding here for 5+ years, and I'm taking it very slowly so far. Right now, you can't just fix things with a quick reflash of your rom. Even factory resets can brick you. This is not a phone for noobs at the moment.
iElvis said:
The A/B partitioning has definitely made things more complicated, especially with respect to flashing. I've been rooting and modding here for 5+ years, and I'm taking it very slowly so far. Right now, you can't just fix things with a quick reflash of your rom. Even factory resets can brick you. This is not a phone for noobs at the moment.
Click to expand...
Click to collapse
There is an unbrick tool and fastboot ROMs to recover, but u r right, u just can't screw around with things like we used to due to u need a computer avail even if u bootloop
That, and there are some conflicting instructions flying around and some disagreements amongst the devs about how to do things. I would not want to be starting out with rooting on this phone tbh.
I agree with most posts here.
I've been flashing ever since the HD2 back in the days. I've really spend alot of nights fixing my phones from hard/soft bricks, never actually really broke one though.
But untill there are some stable recovery/root methods, I wouldn't want to start my android rooting experience with this phone right now. As some said, wait a couple of weeks.
Thank you everyone for replying! You've been a great help.
I figure I will wait for the official TWRP and a guide to install it by that time.
Until then I'll keep a close eye on these forums to keep learning. Cheers!
All of these guys are spot on with advice. I too have been doing this for awhile, however this is my first A/B partition phone. You definitely want TWRP. I can't count how many times I've installed a root program or tweaked a system file and messed up my device. Recovery is your friend! Make backups often!! (Once you get TWRP installed of course)
I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!
DampDeceiver said:
I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!
Click to expand...
Click to collapse
This is what I did. Unlock the bootloader to save from data loss later, but no recovery or root until things are a little more understood.
DampDeceiver said:
I will wait for TWRP official for sure now, but one last question.
It is possible to unlock the bootloader (that wipes all my data) right now, and not root, right? So I will just unlock it for the future when TWRP official is released and I can root w/o losing all my data?
It's safe to follow a guide to just unlock the bootloader as of right now?
Thanks again! Very much appreciated!!
Click to expand...
Click to collapse
Yes, you can unlock your bootloader and not root. You're correct that it will erase your data, but once it's unlocked you will be ready to root once official twrp and magisk root comes out.
You'll want to use Magisk because it keeps you compatible with Safety net, has root hide and really good modules as well to add stuff.
If you want a dark theme for now you can download Andromeda from the Play store, and hen substratum. It doesn't need root just some commands from your pc and adb. However it is a few dollars, so if you don't want to pay for that then you can just wait to root. The theme you'll want is swift black, but I use ozone as well. Swift black for some apps to be black theme, but ozone to get a custom accent color and dark theme for OOS quick settings, settings app, etc.
NateDev said:
Yes, you can unlock your bootloader and not root. You're correct that it will erase your data, but once it's unlocked you will be ready to root once official twrp and magisk root comes out.
You'll want to use Magisk because it keeps you compatible with Safety net, has root hide and really good modules as well to add stuff.
If you want a dark theme for now you can download Andromeda from the Play store, and hen substratum. It doesn't need root just some commands from your pc and adb. However it is a few dollars, so if you don't want to pay for that then you can just wait to root. The theme you'll want is swift black, but I use ozone as well. Swift black for some apps to be black theme, but ozone to get a custom accent color and dark theme for OOS quick settings, settings app, etc.
Click to expand...
Click to collapse
That is what i was about to type, use andromeda from play store and use substratum to theme whatever you like.
Unlocking the bootloader is required if you want root and/or custom recovery(TWRP).
Custom recovery is optional and root does not depend on it, nor does custom recovery depend on root either. What custom recovery gives you are mainly two things:
1. More features than a stock recovery.
2. Able to flash unsigned zip.
So if neither of these two really means something to you then you can stay with stock recovery.
The root procedure could be a bit different depends on whether you use a customer recovery or not.
If you do, then the root procedure usually is just as simple as flash a Magisk installation zip.
If you do not use a custom recovery, stay on the stock recovery, then the root procedure is different because the stock recovery does not allow you to flash an unsigned zip. The procedure is:
1. Obtain the stock boot image.
2. Install Magisk Manager and use it to patch the boot image.
3. Boot the phone with the patched boot image(fastboot boot patched_boot.img command), thus you get a temporarily rooted phone. Temporarily means you lost root after reboot because the patched boot image is not actually written to the ROM of your phone.
4. Now on the (temporarily) rooted phone, you have all the power to install the root permanently, by Magisk Manager.