Related
I searched around several threads and saw a few people with the same issue but no fixes.
I rooted my phone using this and it worked great.
I then installed clockwork manager from here and then installed the clockwork recovery and made my nandroid.
So far so good.
I booted up and then checked the terminal emulator app i had installed and did:
Code:
$su
and got
Code:
#
So, all good.
I then went to remove some of the bloatware by using adb.
When I do adb shell I get the $ prompt.
I type in "su" without quotes and after a few seconds i get "Permission denied".
Seems like i fudged something somewhere but I am not sure what.
Anyone able to offer some constructive help?
Make sure your phone is unlocked when you type su in adb shell, and a superuser permission should pop up.
many thanks for that!
i have been on a rooted G1 with CM for so long that i forgot to even look at my phone when i "adb shell...su" into it =)
did it just now and looked at the phone and the superuser permissions window came up. all set.
thanks again!
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
You may have to run visionary and reboot a few more times to make root privileges stick.
My MyGlacier 4G MINE!!!
Try this:
: adb shell (this should give $)
:$ su (next line type su, this should give you prompt on Super user to allow permission)
:# ( once you get this your good)
Sent from my HTC Glacier using Tapatalk
Try to install visionary and then re install open click temp root then permoot super user should ask to approve click yes. After that restart
Sent from my HTC Glacier using XDA App
Please post questions in Q&A forum. Thank you
ok everytime i try adb shell in terminal emulator it says the permission denied, im gonna try the first reply again and then see....any other ideas?
also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.
mrpanic7 said:
also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.
Click to expand...
Click to collapse
Ok, go into adb shell and type su + enter. Watch your phone when you do this. Superuser should ask if you want to allow "unknown" root privileges. "unknown" is adb. Click allow and your problems should go away.
My MyGlacier 4G MINE!!!
So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G
Whats a test command I could try?
Sent via MyTouch 4G
mrpanic7 said:
So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G
Click to expand...
Click to collapse
I ran into this same issue and it drove me crazy. I would not get prompted by the phone to allow su permissions when going through ADB- kept getting "permission denied"
I did finally get SU permissions through ADB, but I dont recall exactly what I did to get prompted to allow access.
I will try to retrace what I did... believe I had ADB shell running (without su permissions "$"), but I also had terminal emulator running on my phone. I entered the su command on my phone, then I did the same from ADB shell.
Finally the phone prompted me to allow access - accepted - and no problems from that point.
Basically, I just had to keep f'n with it.
Yeah thats my problem exactly. Yeah I appreciate any assistance you can provide. I mean my pc reads my device when I adb devices command, but it wont allow nothing past that. Please keep me informed on anything I can try, also im not thag most fluent with using sdk/adb stuff so any additional info with using that is much appreciated thanks again fellow enthusiasts!
Sent via MyTouch 4G
Have you tried to bacup su, then uninstall su. Reinstall su, Then try it again. MIGHT work
Sent from my HTC Glacier using XDA App
yeah i re-installed su and didnt help, @dbiggs-what can i do thru adb to initiate the su permissions to the device like you did?
I wish I could help more specifically, but I dont remember exactly what I did that allowed me access- just kept trying
Maybe try this...(dont be offended if any of these steps are ones that you already know or have tried, I am just trying to be as thorough as I can from memory)
Open up super user, then go back to the terminal emulator and enter the "su" command to gain superuser permissions.
Plug the phone into the computer, select charge only, enter ADB through tools (probably "C:\Android\tools" if your Android folder is in the root of your harddrive).
from the prompt C:\Android\Tools, enter:
adb shell
then you will get the "$" that you mentioned.
enter the "su" command, and hopefully you will get prompted to allow superuser permissions for ADB.
I am pretty sure these are the steps that I took, just had to keep trying.
Lemme know how it works out.
I see some people here asking about getting su privileges in adb, however I do have SU and I can run su in adb shell. My problem is that I am trying to push some files and use Android Commander. I can't run "adb remount" (remount failed: Operation not permitted), I can't copy files in Android Commander (it's says that I do not have ROOT)
How can I get Read-Write in ADB ??
Edit: Oh, now I got it, I don't have root in ADB, when i type "adb root" it says "adbd cannot run as root in production builds"
Did anyone figure this out? I'm being denied on TE and PC also.
I have managed to be able to get around this issue by going into recovery mode on my phone.
If the end result that you are looking for is to adb push files, then the easier way to do this is to flash clockwork recovery to your phone, then start your phone into recovery mode, mount system and you should be able to push files no problem.
Lemke know if this helps.
Sent from my HTC Glacier using XDA App
mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
I'm pretty sure your issue has nothing to do with SU access. Most likely, your phone is simply mounting as r/o (read only) when it boots up, so ADB is unable to change anything to the system folder. The easiest way to mount as r/w (Read/Write) is to go into Root Explorer and click the r/w button in the top right corner, and then go to ADB and see if it will allow you to do the same commands that it previously denied.
I have the same issue with my phone mounting as r/o by default, but I haven't been able to figure out how to automount as r/w on the MT4G. If anyone knows how, please share.
I had this same issue, on several android phones including MT4G. Here is how I fixed it.
1. Connect phone via usb (I was in "charge only" mode, not disk drive mode)
2. Open command prompt and navigate to the android tools folder
3. type "adb shell"
4. MAKE SURE YOUR PHONE SCREEN IS ON AND UNLOCKED
- The above step is very important otherwise you will not get the SU prompt
5. At the "$" prompt type "su"
6. Your phone should now display the SU screen asking you to allow the connection root access.
7. Once you allow it, you are golden.
I did this on a windows pc. Hope it helps.
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.
you know, I've had the same problem lately. --curious to know what's causing it.
decalex said:
you know, I've had the same problem lately. --curious to know what's causing it.
Click to expand...
Click to collapse
Its good to know I am not the only one out there with this issue maybe someone can chime in with a fix. or some insight at least to what the problem may be.
Still no response.... Bump?
watermoore said:
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.
Click to expand...
Click to collapse
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
DevinXtreme said:
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
Click to expand...
Click to collapse
Hey man thanks for your input, I really appreciate it. That didnt work either, on ADB or on Terminal Emulator. It responds correctly from both sources with:
Code:
remount rw
Remounting /system </dev/st19> in read/write mode
I am wondering if it has anything to do with the fact that the 64bit drivers dont install totally. this module called the "Abstract Control Module" hangs forever and doesn't install. However I ran over to my wifes 32 bit vista laptop where the drivers will install totally with no success either.
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.
DevinXtreme said:
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.
Click to expand...
Click to collapse
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
Bump again
Sent from my Epic
Okay since I'm not getting much love from the forum I'm guessing this is an uncommon occurance, in which case I am going to try one more thing before I send it back for a replacement. I am planning on going back to DI18 via odin then one click rooting. Then flashing the modem and other nessecary files to run 2.2 epic experience. Its the only possible thing I can think of that I haven't tried to address my problem. Thanks for the feedback I have gotten thus far.
Sent from my Epic
This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2
The e0pic and hero are way differentwhen it comes to adb
I was the same way lol I don't think adb works
Like I think the only way is to cp things
Sent from my SPH-D700 using XDA App
watermoore said:
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
Click to expand...
Click to collapse
That last one appears to have worked. Check and see if movetest.txt is in /system/fonts. If so, then you're in business. Just copy stuff across as root instead of pushing.
Well now I can use ADB fully. I odined back to stock then used the one click clockwork 3.0.0.05 ext4 batch then flashed Truley Epic Rebirth 1.2 and was able to remount correctly, push and pull all the way down to the root dir. I am not sure what changed but it just all of the sudden started working.... I'll take that lol
mirth18 said:
This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2
Click to expand...
Click to collapse
Well my issue was a bit different. I could get it show up with the "devices" command. When I tried to "adb remount" it would deny me. It would reply with "device not found". Which is really wierd because I could ADB shell with root access any day of the week. I just had to change my process to accommodate the limitation.
I would just ADB push files to the sdcard, mount into shell to gain full root permissions then finish my work.
Kind of a strange round about way of going about it but I learned quite a bit more linux commands that way lol
Fyi.. I am using ubuntu 11.04
Sent from my SPH-D700 using XDA App
Hey gius Im trying to reboot via terminal but I cant seem to get it to work. Keep getting "Nor premited!" error.
I tried with both commands and am using a rooted G2 with stock rom.
su reboot - same error
su reboot now- same error.
any ideas? I know there are apps to do it but why is it not working via terminal?
Any reason why you can't just hold the button in and press reboot?
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
ohgood said:
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
Click to expand...
Click to collapse
Hmm Tried that right now and it says shutdown: not found.
I'm getting the same error! I only tried terminal when Gscript Lite gave me a "not permited". Don't know if it's related, but terminal always starts with $ rather than #. The weirdest part is that it DID work through ADB.
I'm S-OFF, root verified. Has anyone else seen this? I've been searching the forums for a while now...
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
I get busybox: not found, but since I initially thought it was a busybox issue, I have already updated busybox. Per Titanium Backup, I have version 1.18.4-Titanium. Could it be the titanium busybox?
PanCubano said:
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Having a similar problem with rebooting from terminal "not permitted", I am using Virtuous Unity,and my phone is rooted etc,anybody having any joy getting reboot from terminal working?double checked busybox permissions and are RWX so whats going on???????????????????
Ok restored my nandroid backup of CM7 and reboot from terminal works so for the problem is connected to Virtuous Unity.
got it ! command is:
$su
#reboot -f
hay presto!!!!!!!
EDIT BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
I dont get it,what is the problem !!!!!!!!!!!!!!!!
xsteven77x said:
Any reason why you can't just hold the button in and press reboot?
Click to expand...
Click to collapse
This.
Sent from Space using Tapatalk Pro
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
bombadier said:
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
Click to expand...
Click to collapse
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
mjasmin said:
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
Click to expand...
Click to collapse
I can get reboot -f which works but I have to use busybox killall_server to get it work from a script,have tried a few things but literature on the subject is pretty sparse,its not so important but would still like to understand the whole process, but I seem to be in the minority trying to solve this.......
Why I have to use reboot -f on Unity where reboot will do on CM is a mystery,have found a file that seems to define functions on Unity(virtuous-functions.sh), have tried adding REBOOT="$BUSYBOX reboot" to this but doesn't help.
reboot -f it is then!
I have moved this from here https://forum.xda-developers.com/pixel-2-xl/how-to/zero-day-vzw-pixel-2-xl-root-t3977851/
Hey everyone!
I am here to post some good news. I have made a set of scripts that can give you temporary root through Magisk. It persists until the next reboot, but setting it up after the initial setup is a lot easier.
The script requires that it be run as root, which means that you need to run the temproot binary provided earlier.
Big thank you to Elliwigy for walking me through the initial process and for providing the commands.
Source code for the "exploit" binary can be found here, and compiled from source if you so desire.
This script is provided with no warranty whatsoever. This script may brick your phone. YOU ARE RUNNING THIS AT YOUR OWN RISK. I ACCEPT NO RESPONSIBILITY FOR WHAT THIS SCRIPT DOES TO YOUR PHONE.
Click to expand...
Click to collapse
IF YOU DO NOT WANT TO RISK YOUR PHONE BEING BRICKED, DO NOT CONTINUE!
Requirements:
A Verizon Pixel 2 (XL) on the September 2019 Security Patch
A computer with ADB If you need ADB, it can be found here
A USB cable
Appropriate USB drivers USB drivers can be found here if needed
Some knowledge of how to use the terminal
The taimentempmagisk.zip file (attached)
The APK for Magisk Manager (included in the zip)
Hope
Magisk and MagiskManager can also be downloaded from here if you wish.
If Magisk Manager prompts you to perform additional setup, DO NOT ACCEPT. (unless you like having a bricked phone)
Install the Magisk Manager APK onto your phone
Use ADB to push the attached ZIP file (taimentempmagisk.zip) to /data/local/tmp
Open an ADB shell and navigate to /data/local/tmp
Extract the ZIP file with the unzip command
Navigate into the scripts folder
Run ./exploit (If this step fails, repeat until you have a root shell)
Run ./installtemproot.sh magiskinit64
After you have done this, you now have root!
If you reboot and want root back, just run /data/local/tmp/scripts/exploit in an adb shell, then run /data/local/tmp/scripts/temproot.sh
Enjoy your root!
Does not work
Hexlay said:
Does not work
Click to expand...
Click to collapse
I'm currently working on a solution, it seems some terminal emulators error out on the mount command.
EDIT: Instructions updated.
logan2611 said:
I'm currently working on a solution, it seems some terminal emulators error out on the mount command.
EDIT: Instructions updated.
Click to expand...
Click to collapse
I'v tried, everything went fine, however magisk still does not detect root
Hexlay said:
I'v tried, everything went fine, however magisk still does not detect root
Click to expand...
Click to collapse
did u install magisk manager? if u dont have it installed then u womt b able to grant su permissions.. it does work as we spent hours testing and ensuring it works before he posted it.. id triple check each instruction and make sure u have magisk apk installed.. if not then reboot and try again from the beginning
elliwigy said:
did u install magisk manager? if u dont have it installed then u womt b able to grant su permissions.. it does work as we spent hours testing and ensuring it works before he posted it.. id triple check each instruction and make sure u have magisk apk installed.. if not then reboot and try again from the beginning
Click to expand...
Click to collapse
Yep, i have it pre-installed, i did follow every step provided, but prompt is not showing up and afterwards it does not detect root... Well, i'v done it several times, i tried ./temproot.sh after install script, but still same...
Well, i guess i have to reboot
Edit: tried reboot, still same.... i'll write down what i have done exactly.
Rebooted dvice
Went into terminal emulator and executed ./taimen
After that went one step back with cd .. and executed chmod -R 777 scripts
Then went to pc and entered ADB shell and executed ./taimen there too, because otherwise i was getting This script must be run as root. Exiting. on install script
Then ran install script. Process did complete successfully, however no magisk prompt was fired and afterwards root was not detected
I'v tried chmod -R 777 . even from adb shell, tried opening magisk app and then doing these whole process... no luck
First, thanks for your supporting and your instruction
I just install October(6/10) update so any risk if i follow your instruction
Anyone know how to delete the update? I've downloaded and refuse to restart my device in the wake of these new development
enigma2446 said:
Anyone know how to delete the update? I've downloaded and refuse to restart my device in the wake of these new development
Click to expand...
Click to collapse
I also want to know this. I need to reboot but I don't want to move to the October patch.
Hexlay said:
Yep, i have it pre-installed, i did follow every step provided, but prompt is not showing up and afterwards it does not detect root... Well, i'v done it several times, i tried ./temproot.sh after install script, but still same...
Well, i guess i have to reboot
Edit: tried reboot, still same.... i'll write down what i have done exactly.
Rebooted dvice
Went into terminal emulator and executed ./taimen
After that went one step back with cd .. and executed chmod -R 777 scripts
Then went to pc and entered ADB shell and executed ./taimen there too, because otherwise i was getting This script must be run as root. Exiting. on install script
Then ran install script. Process did complete successfully, however no magisk prompt was fired and afterwards root was not detected
I'v tried chmod -R 777 . even from adb shell, tried opening magisk app and then doing these whole process... no luck
Click to expand...
Click to collapse
Can you post the output of the script?
logan2611 said:
Can you post the output of the script?
Click to expand...
Click to collapse
That's output every time, it finishes script successfully
Hexlay said:
That's output every time, it finishes script successfully
Click to expand...
Click to collapse
Sorry, screenshot didn't load the first time. Looks like all the files are already in place, try rebooting and running temproot.sh
running ./taimen just gives a "permission denied" error
Some1CP said:
running ./taimen just gives a "permission denied" error
Click to expand...
Click to collapse
If you are getting this on the phone, you need to use a terminal emulator with access to a directory in /data. I used Termux in my example.
If you want to use Termux, here is how to get taimen running:
Install Termux
Open Termux and let it install
Run termux-setup-storage
Push the ZIP to /sdcard/Download
On the phone, move the ZIP file from ~/storage/downloads to ~
Continue from step 4 in OP
logan2611 said:
If you are getting this on the phone, you need to use a terminal emulator with access to a directory in /data. I used Termux in my example.
If you want to use Termux, here is how to get taimen running:
Install Termux
Open Termux and let it install
Run termux-setup-storage
Push the ZIP to /sdcard/Download
On the phone, move the ZIP file from ~/storage/downloads to ~
Continue from step 4 in OP
Click to expand...
Click to collapse
How would I move it to ~ without root?
Edit: nevermind, got it to run.
Just need to figure out how to make the temproot work.
Some1CP said:
How would I move it to ~ without root?
Click to expand...
Click to collapse
In Linux ~ is a shortcut for the home directory, which is always owned by the current user. Root is not required to move the ZIP from ~/storage/downloads to ~ on Termux.
Ok I can't run installtemproot.sh in adb, and neither on the phone itself through termux. Is there something I'm missing? su can't be find on the phone.
Edit: It works if you use Jack Pal's terminal emulator and you cd into its directory on adb. Sadly magisk doesn't recognize it's installed.
I'm on October 5 2018 security update and should flash September 5 2019 try temp root?I know stay away October's 2019 that's patch,sean
logan2611 said:
Sorry, screenshot didn't load the first time. Looks like all the files are already in place, try rebooting and running temproot.sh
Click to expand...
Click to collapse
Sorry for wait time, literally had to wait for type-c to type-c connection -_- it's pain....
Anyway i did reboot and tried again with just temproot.sh, without repeating previous stuff. No prompt is fired, but output is success
Hexlay said:
Sorry for wait time, literally had to wait for type-c to type-c connection -_- it's pain....
Anyway i did reboot and tried again with just temproot.sh, without repeating previous stuff. No prompt is fired, but output is success
Click to expand...
Click to collapse
client: launching new main daemon process
Click to expand...
Click to collapse
The output suggests that Magisk started successfully. What does Magisk Manager look like after running that script?