Related
Hello,
When I run adb shell, it reports back with a "$,"even though I do have root. I'm running JoeyKrim Stock With Root ROM. Odexed...
I do have superuser installed with the latest binary, and latest official busybox. Terminal emulator even detects that I have root.
Basically everything works as it should, except adb. Anybody know what's going on?
Rydah805 said:
Hello,
When I run adb shell, it reports back with a "$,"even though I do have root. I'm running JoeyKrim Stock With Root ROM. Odexed...
I do have superuser installed with the latest binary, and latest official busybox. Terminal emulator even detects that I have root.
Basically everything works as it should, except adb. Anybody know what's going on?
Click to expand...
Click to collapse
When you type adb shell, does it immediately report back with a $, or does it pause for a few and then report back with a $? If it pauses for a few seconds, look down at your phone during that time. You may be being prompted with the super user request prompt, where you need to hit allow. I'm not sure why you need to do this sometimes, but I've had it happen before. If you don't look at the phone and hit 'allow', then it times out and doesn't give you root access. So type 'adb shell', check out your phone and see if your prompted, if so allow it, and you should be good. If that is not the case, then I'm unsure what could be causing it.
k2buckley said:
When you type adb shell, does it immediately report back with a $, or does it pause for a few and then report back with a $? If it pauses for a few seconds, look down at your phone during that time. You may be being prompted with the super user request prompt, where you need to hit allow. I'm not sure why you need to do this sometimes, but I've had it happen before. If you don't look at the phone and hit 'allow', then it times out and doesn't give you root access. So type 'adb shell', check out your phone and see if your prompted, if so allow it, and you should be good. If that is not the case, then I'm unsure what could be causing it.
Click to expand...
Click to collapse
Thanks, I'll test that out. I have a pin set on superuser. Maybe that's the issue.
Just checked, and it does it right away, and does not prompt... Sigh...
Rydah805 said:
Just checked, and it does it right away, and does not prompt... Sigh...
Click to expand...
Click to collapse
Very strange. I'm not sure. Has it happened on all roms, or just the one you're currently on?
Sent from my PG86100 using Tapatalk
Rydah805 said:
Just checked, and it does it right away, and does not prompt... Sigh...
Click to expand...
Click to collapse
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Another option, inside the Superuser app, on the Settings tab, at the very bottom there is an option, update su binary. Sometimes using this update feature will resolve permission/installation issues with the su binary.
If you wanted to verify the installation of both Superuser and root as having been done properly, my free app Root Check from the market works well. Advanced Mode should provide all the details we'd need to troubleshoot further.
Hope that helps and appreciate your support!
joeykrim said:
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Another option, inside the Superuser app, on the Settings tab, at the very bottom there is an option, update su binary. Sometimes using this update feature will resolve permission/installation issues with the su binary.
If you wanted to verify the installation of both Superuser and root as having been done properly, my free app Root Check from the market works well. Advanced Mode should provide all the details we'd need to troubleshoot further.
Hope that helps and appreciate your support!
Click to expand...
Click to collapse
Yep that does work on his rom the "type su" thing and thanks for your root check app Joey it's been super useful in trying to figure out stuff lately on the photon.... really appreciate all your contributions
joeykrim said:
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Hope that helps and appreciate your support!
Click to expand...
Click to collapse
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Rydah805 said:
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Click to expand...
Click to collapse
Short answer: Since Superuser.apk is another developer's software, I didn't include it in my ROM as I didn't have his permission. I provide the superuser apk market link in my ROM OP for users. Instead of packaging Superuser apk, I used the su binary provided in AOSP as its source code is public and publically available for android usage.
Long answer: There is a free version of Superuser available thru the market and figured that would be the best way to load the Superuser apk. From personal experience as an android developer, when an app is provided with a ROM, it doesn't appear in the developer's market statistics and essentially is "off the radar". Which makes it more difficult to track which devices have loaded the software, which versions of android, etc and makes it more difficult to prioritize software upgrades to the application.
Hope I was able to explain and it helps!
joeykrim said:
Short answer: Since Superuser.apk is another developer's software, I didn't include it in my ROM as I didn't have his permission. I provide the superuser apk market link in my ROM OP for users. Instead of packaging Superuser apk, I used the su binary provided in AOSP as its source code is public and publically available for android usage.
Long answer: There is a free version of Superuser available thru the market and figured that would be the best way to load the Superuser apk. From personal experience as an android developer, when an app is provided with a ROM, it doesn't appear in the developer's market statistics and essentially is "off the radar". Which makes it more difficult to track which devices have loaded the software, which versions of android, etc and makes it more difficult to prioritize software upgrades to the application.
Hope I was able to explain and it helps!
Click to expand...
Click to collapse
Gotcha, I'm not complaining, just wondering why. I've always loved your roms over any others. Any way I can easily set it to use the superuser app binary over aosp binary?
ADB starting with root depends on the ro.secure property; if you type "getprop ro.secure" it should show either 0 meaning ADB keeps root or 1 meaning you have to use su for root. Just about all custom kernels/ROMs use unsecured boot.imgs but you can always change it yourself by modifying the default.prop file packed in the boot.img.
This is also what people are referring to when they say the kernel/boot.img/rom is secured or unsecured.
Rydah805 said:
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Click to expand...
Click to collapse
xHausx said:
ADB starting with root depends on the ro.secure property; if you type "getprop ro.secure" it should show either 0 meaning ADB keeps root or 1 meaning you have to use su for root. Just about all custom kernels/ROMs use unsecured boot.imgs but you can always change it yourself by modifying the default.prop file packed in the boot.img.
This is also what people are referring to when they say the kernel/boot.img/rom is secured or unsecured.
Click to expand...
Click to collapse
Rydah805 said:
Gotcha, I'm not complaining, just wondering why. I've always loved your roms over any others. Any way I can easily set it to use the superuser app binary over aosp binary?
Click to expand...
Click to collapse
Ah! Your question in the first quote above could be intrepreted two different ways. I provided one answer for one intrepretation and Haus provided the other answer for a different intrepretation!
I'll try and bring both together. There are two primary ways to access the shell interface on an android device.
1) Via adb shell. When typing adb shell and it opens the connection to the device, by android standard, it drops you to a shell with non root access reflected with the $ prompt. As Haus articulated above, this can be modified in the /default.prop file inside the ramdisk of the boot.img file. There are two options, have adb shell drop to root access or have adb shell drop to non root access. Many custom kernels modify this option so the user drops to root access.
In my kernel I'm using a non-modified stock kernel so it drops to non root access. I prefer to have to type su, once in the shell, to elevate to root access. Mainly because most functions I perform in adb shell I don't want root access for.
2) Via terminal emulator/connectbot. When accessing the shell directly on the device thru one of the common android applications, these generally open up a standard "sh" or non root shell. Then by typing "su" the user can elevate to root access (if the device has the su binary, etc.).
There are two main options for how to handle the "su" command inside a shell on the android device.
1) Superuser.apk - this application provides its own su binary, which hooks into the android application. Whenever su is called, the Superuser application is therefore called and allows the user to accept/deny root access requests.
2) su binary - from aosp or busybox. this is a version of the su binary more common to android developers in aosp, or the busybox version is more common to a generic linux version. the aosp version of su will grant any user/application root access. the busybox version will grant any user/application root access but does rely on an /etc/passwd and /etc/group file for permissions.
To answer your previous question, why you haven't had to type su on other custom ROMs, as Haus explained, they probably modified adb shell access in the /defult.prop file to automatically elevate adb shell to root priviledges.
To answer your last question regarding Superuser.apk and aosp su. Once you install the Superuser.apk file and it properly installs its own version of the su binary, it has now overwrite the previous aosp su binary. Superuser will now control all root access requests. Once you grant an application, adb shell, titantium backup, root explorer, or whatever application root access with Superuser, it will not prompt again and will handle every future request with the default action (grant/deny) provided.
Hope the extra details help!
Thanks, wasn't trying to be a pest. Just curious. The info in this thread is a nice thing to know.
Hi all!
This question may seem a little dumb.. But I'm trying to understand what configuration file (if it's that kind of thing used) gives the "shell" uid on my phone but a root uid on the emulator when I type "adb shell" command.
If someone could point out the process used, that would be great.
Thanks!
Nobody can give me a hint on my question?
Nerver mind, found the answer with the ps command..
All depends on the uid running adbd. On the emulator the uid is root and ion my phone it's shell.
I also believe in build.prop or default.prop or something. That ro.secure controls whether adb is root.
Thanks, I'll try to dig that.
in the ramdisk of your boot image you have a file called default.prop
if the setting in that file have:
persist.service.adb.enable=1
you get a root shell, if it has
persist.service.adb.enable=0
You do not get a root shell, basicly that is what you change when you root a phone or tablet, and then normally also add su and busybox to /system/xbin, and add the Superuser apk.
Per
If you type su on the prompt, you get root, nothing tricky.
yareally said:
If you type su on the prompt, you get root, nothing tricky.
Click to expand...
Click to collapse
Nothing tricky indeed, but you need a rooted phone to do this..
foxl3y said:
Nothing tricky indeed, but you need a rooted phone to do this..
Click to expand...
Click to collapse
True. I was just under the notion they had root.
whatever ICS rom i use my phone never locks/sleeps.i set faceunlock pattern pin evrything different times and never it goes to sleep or locks whether i press lock button or not like gingerbread roms... :S anyone got any solution... cant lock my phone.. or get it into sleep mode anyway :S
Try the latest release or go back to GB and wait for Samsung to release ICS is about all or even post in one of the many ICS threads .
jje
i have the same problem
flash it with [ROM][IML74K][4.0.3] CyanogenMod 9 experimental Build
this 1 works
JJEgan said:
Try the latest release or go back to GB and wait for Samsung to release ICS is about all or even post in one of the many ICS threads .
jje
Click to expand...
Click to collapse
i tried all official ics roms and a few custom 1s and on no roms screen lock or any kind of lock never works...
victorbd said:
i tried all official ics roms and a few custom 1s and on no roms screen lock or any kind of lock never works...
Click to expand...
Click to collapse
There are no "official" ICS ROMs because there is no official ICS for the SGS2.
Odia said:
# echo -n ON > /efs/imei/keystr
# reboot
Click to expand...
Click to collapse
There's plenty of other information in the threads dealing with these ROMs too. If only people would ask/read there, rather than making new threads for every issue they encounter.
(potential original source in T989 forums http://forum.xda-developers.com/showthread.php?t=1438451)
problem solfd!!
just do:
- Download "Terminal Emulator" app from market
- open it
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
reboot
- go in recovery mode : clear both cache and Dalvik and factory reset!!
you wil have your screenlock bak
State at least whom and from where you quoted
tonyblazze said:
problem solfd!!
just do:
- Download "Terminal Emulator" app from market
- open it
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
reboot
- go in recovery mode : clear both cache and Dalvik and factory reset!!
you wil have your screenlock bak
Click to expand...
Click to collapse
problem!
Guys,
I have a same problem. I install the app "Android Terminal Emulator", but when use this:
# echo -n ON > /efs/imei/keystr
# reboot
the terminal show the message "permission denied"
Please help me!
antifakie said:
Guys,
I have a same problem. I install the app "Android Terminal Emulator", but when use this:
# echo -n ON > /efs/imei/keystr
# reboot
the terminal show the message "permission denied"
Please help me!
Click to expand...
Click to collapse
You need root to apply this. The "#" prompt at the beginning of the lines indicates that you have su permissions. If you have an "$" prompt instead, and are getting a message "permission denied", then you likely do not have root. If you DO have root, you may have to run "su" before the first line.
still problem
[/COLOR]
ctomgee said:
You need root to apply this. The "#" prompt at the beginning of the lines indicates that you have su permissions. If you have an "$" prompt instead, and are getting a message "permission denied", then you likely do not have root. If you DO have root, you may have to run "su" before the first line.
Click to expand...
Click to collapse
Thanks for the answer, but when i type the command "su", the terminal show message: /system/bin/sh: su: not found"
I don't know what happen
antifakie said:
[/COLOR]
Thanks for the answer, but when i type the command "su", the terminal show message: /system/bin/sh: su: not found"
I don't know what happen
Click to expand...
Click to collapse
Dude. The very first sentence of my post said "you need root to apply this". If you are not rooted, you will not have the su binary, thus you cannot do this.
Root your phone first.
Though, if you can't understand what I'm saying, maybe you shouldn't.
ctomgee said:
Dude. The very first sentence of my post said "you need root to apply this". If you are not rooted, you will not have the su binary, thus you cannot do this.
Root your phone first.
Though, if you can't understand what I'm saying, maybe you shouldn't.
Click to expand...
Click to collapse
I understand, but i use a stock rom of ICS. Should be rooted my phone with a kernel that have a root or exist other form to root the phone?
Thanks a lot!
antifakie said:
I understand, but i use a stock rom of ICS. Should be rooted my phone with a kernel that have a root or exist other form to root the phone?
Thanks a lot!
Click to expand...
Click to collapse
Sorry, I don't really understand what you are asking.
Bottom line; you need root to apply the fix. However you are able to accomplish this doesn't matter.
ctomgee said:
Sorry, I don't really understand what you are asking.
Bottom line; you need root to apply the fix. However you are able to accomplish this doesn't matter.
Click to expand...
Click to collapse
OK, thanks!
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..
Prerequisites:
Dirty Santa
ADB
HOW TO: (UPDATE COMING SOON...)
Follow DirtySanta all the way through step 3.5
Step 1: On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux,
./RUNMEFIRST.sh
Step 2: Open a Separate Terminal, then run
./Step1.sh
Step 3: Wait for shell prompt then.
run-as con
chmod 0777 /storage/emulated/0/*
This will not give you full root access!
Please comment if you're willing to help me out in getting root.
Just so everyone knows I am not taking credit for writing any of the code, none of it was me, I just was fiddling try to create root and found this worked to get root over ADB.
when does this wear off?
tommy7115 said:
when does this wear off?
Click to expand...
Click to collapse
I have not done enough to know for sure, but all the changes you made are going to reset most likely be on a reboot.
abine45 said:
Prerequisites:
Dirty Santa
ADB
HOW TO:
Follow DirtySanta all the way through step 3.5
That should give you a temporary root. I am on android 6.0, not sure if this will work on five but I don't see why it wouldn't. from there i'm going to try to make root.
Just so everyone knows I am not taking credit for writing any of the code, none of it was me, I just was fiddling try to create root and found this worked to get root over ADB.
Click to expand...
Click to collapse
Would you please write a guide for doing root step by step?THX
alexanderzhang said:
Would you please write a guide for doing root step by step?THX
Click to expand...
Click to collapse
I will either tonight or tomorrow. I'm in the process to actually getting a full root, I think i'm on to something and may be able to get this to work. This is just a temporary thing for people to try.
abine45 said:
I will either tonight or tomorrow. I'm in the process to actually getting a full root, I think i'm on to something and may be able to get this to work. This is just a temporary thing for people to try.
Click to expand...
Click to collapse
OK, My mother language isn't Eng, so I can't understand the meaning of "Follow DirtySanta all the way through step 3.5".
Is your meaning that flollow the guide from step 1 to step 3.5?
Im not getting root access, root check is not recognizing it and neither is an app like freedom
Testing it right now. @alvislee[email protected]
---------- Post added at 11:00 PM ---------- Previous post was at 10:28 PM ----------
I got a tmp root shell. Now working on installing su and changing selinux status with chainfires tools.
alvinator94 said:
Testing it right now. @alvislee[email protected]
---------- Post added at 11:00 PM ---------- Previous post was at 10:28 PM ----------
I got a tmp root shell. Now working on installing su and changing selinux status with chainfires tools.
Click to expand...
Click to collapse
How did you achieve the root shell, I can't get it working.
tommy7115 said:
How did you achieve the root shell, I can't get it working.
Click to expand...
Click to collapse
Download v20.zip
extract it
run "RUNMEFIRST.bat"
give it a second and then run STEP1.bat
wait and itll show up as a normal shell "$"
then type in "run-as con" without the quotes
then you will see "#"
alvinator94 said:
Download v20.zip
extract it
run "RUNMEFIRST.bat"
give it a second and then run STEP1.bat
wait and itll show up as a normal shell "$"
then type in "run-as con" without the quotes
then you will see "#"
Click to expand...
Click to collapse
Yeah but then the next line does nothing, by that I mean chmod 0777 /storage/emulated/0/*
Plus even if that works how do I get root?
tommy7115 said:
Yeah but then the next line does nothing, by that I mean chmod 0777 /storage/emulated/0/*
Plus even if that works how do I get root?
Click to expand...
Click to collapse
Do you see the # symbol after you type run-as con
if so then i believe you have a temporary root shell.
by the way, the line after that is just giving elevated permissions to your entire internal storage, this part of the code does not apply to us as we do not need to give more permissions to anything on our internal storage as we will not be using them unlike the other several steps on that dirty santa post.
the problem is, even though we have a sort of root shell selinux is stopping us from being able to modify any of the other files.
alvinator94 said:
Do you see the # symbol after you type run-as con
if so then i believe you have a temporary root shell.
by the way, the line after that is just giving elevated permissions to your entire internal storage, this part of the code does not apply to us as we do not need to give more permissions to anything on our internal storage as we will not be using them unlike the other several steps on that dirty santa post.
the problem is, even though we have a sort of root shell selinux is stopping us from being able to modify any of the other files.
Click to expand...
Click to collapse
Thanks for clarifying that:good:
alvinator94 said:
Do you see the # symbol after you type run-as con
if so then i believe you have a temporary root shell.
by the way, the line after that is just giving elevated permissions to your entire internal storage, this part of the code does not apply to us as we do not need to give more permissions to anything on our internal storage as we will not be using them unlike the other several steps on that dirty santa post.
the problem is, even though we have a sort of root shell selinux is stopping us from being able to modify any of the other files.
Click to expand...
Click to collapse
What are you thinking to get full root from here?
Flash a modified boot img somehow that still let's the phone boot but gives us root even with the SElinux still set to enforcing. Go reading on the dirty cow thread and get caught up
Is this an option if I wanted to change my font or do something that required root? Would it survive past a reboot?
JRM_3 said:
Is this an option if I wanted to change my font or do something that required root? Would it survive past a reboot?
Click to expand...
Click to collapse
This is still exactly what you see when reading through the post. Please follow the main ROOT thread from Albine45 (patiently wait for Albine's frequent updates on progress) and when full root is achieved, you'll know and a guide will show up to walk you through. For now, you can change system fonts in your settings menu on Android. There are a few free built in fonts and others you can purchase. Just look through your settings menu.
snapz54 said:
This is still exactly what you see when reading through the post. Please follow the main ROOT thread from Albine45 (patiently wait for Albine's frequent updates on progress) and when full root is achieved, you'll know and a guide will show up to walk you through. For now, you can change system fonts in your settings menu on Android. There are a few free built in fonts and others you can purchase. Just look through your settings menu.
Click to expand...
Click to collapse
Thank you so much. I'll definitely be watching for full root?
After I run "run-as con" package 'con' is unknown
Any solutions?
I only need to delete or rename /system/bin/logd it's giving me some troubles, battery drain and over heating.
Enviado desde mi VS990 mediante Tapatalk
windows 7 supported???