Related
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
theMaDHakkeR said:
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
Click to expand...
Click to collapse
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Haha! Thank you your a saint! I'm still learning everyday
Thanks again.
Sent from my X10a using XDA App
biktor_gj said:
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Click to expand...
Click to collapse
Simple, amazing solution. Thanks !
Hey guys,
I currently have LeoMar Revolution ROM installed, so phone is rooted, Superuser works fine etc.
Want to start playing around with adb (am new to this) and have the device showing up when running 'adb devices' but i cannot get adb root? Although the device is rooted ok?
So question is (yes i searched but cant find the answer) are phone root and adb root different things?
If so how do i go about getting adb root so i can push apps etc from cmd line?
Thanks in advance
kangfu84 said:
Hey guys,
I currently have LeoMar Revolution ROM installed, so phone is rooted, Superuser works fine etc.
Want to start playing around with adb (am new to this) and have the device showing up when running 'adb devices' but i cannot get adb root? Although the device is rooted ok?
So question is (yes i searched but cant find the answer) are phone root and adb root different things?
If so how do i go about getting adb root so i can push apps etc from cmd line?
Thanks in advance
Click to expand...
Click to collapse
When through cmd, you write su and press enter
If you get a $ sign, then you aren't adb rooted!
If you get a # sign, then you are adb rooted!
Umm, for adb root, I guess use superoneclick root and click shell root, you will get the # sign then!
Thanks for quick reply
I run abd shell and then su and i do get the #.
id=0 so i have root in an 'abd shell' but i cant get root when i just put 'adb root'
Tried to adb push the apks manually in adb shell but adb push doesnt exist in shell?
But i am trying to run a batch file that pushes some hidden apks and i get the error "cannot run as root in production builds" when i run the batch file?
Edit: I may have had a secure kernel installed, will try another kernel and re-try. Is it possible to have su rights when booted up with a secure kernel? That would explain things ..
kangfu84 said:
Thanks for quick reply
I run abd shell and then su and i do get the #.
id=0 so i have root in an 'abd shell' but i cant get root when i just put 'adb root'
But i am trying to run a batch file that pushes some hidden apks and i get the error "cannot run as root in production builds" when i run the batch file?
Edit: I may have had a secure kernel installed, will try another kernel and re-try. Is it possible to have su rights when booted up with a secure kernel? That would explain things ..
Click to expand...
Click to collapse
I have never tried doing pushing/pulling on stock/secure kernels ... so I can't tell you what's going wrong!
Will have a play with flashing other kernels and try again.
I have the yellow triangle show up on boot so i thought i had an insecure kernel. But maybe it is just there from when i installed a previous ROM/insecure kernel?
kangfu84 said:
Will have a play with flashing other kernels and try again.
I have the yellow triangle show up on boot so i thought i had an insecure kernel. But maybe it is just there from when i installed a previous ROM/insecure kernel?
Click to expand...
Click to collapse
Yellow triangle means you have a insecure kernel, maybe, Cf-root
"adb root" was only available on the original "Google dev phones" and requires special code somewhere on the phone (in the kernal?) to support it. When you root the phone it does not include the special code for "adb root" to work. I don't know what you need to do to get it working, but most people don't bother because there are other ways to do the same thing.
{Build:KI4, Version:1.3.4 (stock, rooted)}
LouisJB said:
"adb root" was only available on the original "Google dev phones" and requires special code somewhere on the phone (in the kernal?) to support it. When you root the phone it does not include the special code for "adb root" to work. I don't know what you need to do to get it working, but most people don't bother because there are other ways to do the same thing.
{Build:KI4, Version:1.3.4 (stock, rooted)}
Click to expand...
Click to collapse
Can i adb push apk's as su in an adb shell?
If so i guess i can push the apks i want to manually instead of using the batch file which is trying to get adb root.
kangfu84 said:
Can i adb push apk's as su in an adb shell?
Click to expand...
Click to collapse
1. If you use one of my insecure kernels, adb will be running as root, issue "adb root" and it will reply "adb is already running as root"
2. Yes you can adb push when using su root.
3. Why do you want to push APKs? If its to install them, then just use adb install <FILE NAME>
adb root can be used when ro.debuggable is set to 1 in /default.prop
and on every reboot ro.debuggable is replaced by the one in kernel you are using
Why did you bump a thread from November 2011 to post this gem? Is that what "Recognized Contributors" do? I did wonder.
Geez Oinky. I could really take that comment of yours (which is true on so many levels) & run with it ;-) But I can't be arsed these days (like more than a few people on here).
Probably one of the criteria for getting RC status; how many 8 mth old threads you bump over X period of time
oinkylicious said:
Why did you bump a thread from November 2011 to post this gem? Is that what "Recognized Contributors" do? I did wonder.
Click to expand...
Click to collapse
i was googling something related to this but not this and found this thread, readed it all and found that no one had answered this
then i thought many others can also look for this and i thought of answering for others who are googling for it not for the op, because i know op had got the answer many moths ago
and real xda member never offense but help others
G'day,
I've tried to root a 8" PendoPad 4.1.1, but hit a snag. I've root access when using "adb shell", but when running applications such as "ROM Toolbox Lite" on the tablet, they complain about not getting root access, although "Superuser" is installed.
What is the mechanism for applicatons running on Android to gaining root access? My understanding is that this is done by the "Superuser" application. What am I missing? My goal is to have this table dual boot Android/Linux.
I would appreciate any help and pointers to appropriate documentation to solve this riddle.
cheerio Berndt
Sysinfo:
======
8 PendoPad 4.1.1
Model MR18
Android Version 4.1.1
Kernel Version 3.0.8+ SMP PREEMPT
Build Number rk30sdk-eng 4.1.1 JR003H 20130108.130525 release-keys
Try to update the su binary for superuser. Also you can try re-rooting you device. The issue may be due to improper root also
anthonythangaraj said:
Try to update the su binary for superuser. Also you can try re-rooting you device. The issue may be due to improper root also
Click to expand...
Click to collapse
Checked that su is installed, see below
[email protected]:/ # ls -l /system/xbin/su*
-rwsr-sr-x root root 22364 2012-01-03 08:23 su
[email protected]:/ # su -v
3.0.3.2
Version of Superuser application is 3.1.3
barossa said:
Checked that su is installed, see below
[email protected]:/ # ls -l /system/xbin/su*
-rwsr-sr-x root root 22364 2012-01-03 08:23 su
[email protected]:/ # su -v
3.0.3.2
Version of Superuser application is 3.1.3
Click to expand...
Click to collapse
Ok, I believe to have progressed somewhat. It appears I can place the device into bootloader mode using
adb reboot-bootloader
The device reboots into what I presume bootloader mode, althought the screen stays dark, but
the device number changed from 2207:0010 to 2207:300a. I've added this ID to /etc/udev/rules.d/51_android.rules, but fastboot doesn't see the device. Any other ideas?
Solved the SuperUser issue by using "bin4ry" instead of SuperOneClick. I now have full SuperUser access on the PendoPad.
Ubuntu is running in an chrooted environment withing Android. Next step is to find a procedure that shows me how to install Ubuntu on this device.
Just purchased a Pendopad 8" PNDPP8MT8.
To get 'Root' access, bin4ry worked for me and I also have google play installed (ditched 1Mobile Market) and CWM Recovery 6.0.3.1 running. I don't cook ROMs so this is as far as I go.
pbezza said:
Just purchased a Pendopad 8" PNDPP8MT8.
To get 'Root' access, bin4ry worked for me and I also have google play installed (ditched 1Mobile Market) and CWM Recovery 6.0.3.1 running. I don't cook ROMs so this is as far as I go.
Click to expand...
Click to collapse
How did u do that. I've got root but can't get gapps installed.
Sent from my PNDPP42DG10BLK using xda app-developers app
re-install superuser flashable zip from recovery.
Hi guys,
I found a method to change System Status in Odin mode to 'Official/Samsung' that is very simple and only using the busybox application "devmem". Use this command in adb shell or terminal emulator. Just type it in, hit enter, and reboot. Bam.
Code:
devmem 0xF91CF8C 32 0xFF000000
This will change your status to Official and remove the padlock with 'Custom' on it. If you want 'Custom', replace FF with EE.
Immediately upon reboot, Odin mode and the device recognize the device as official.
The explanation is that this is from a small region of memory that stores what's known as DDI data. I don't know what that means yet, but some other information like the CC Mode flag and device name/product number are stored here. I'm still doing further research on what else resides here.
Enjoy.
Seem that "DDI" can be either:
A "MAC-e header parameter" as specified HERE.
Data Description Indicator (DDI):
The DDI field identifies the logical channel, MAC-d flow and size of the MAC-d
PDUs concatenated into the 3GPP associated MAC-es PDU. The mapping between the
DDI values and the logical channel ID, MAC-d flow and PDU size is provided by
higher layers. The length of the DDI field is 6 bits. When, due to the
quantization in the transport block sizes that can be supported, the size of the
data plus header is less than the TB size originally selected by the E-TFC
selection entity minus 6 bits, the DDI value [111111] shall be appended at the
end of the MAC-e header to indicate that there are no more MAC-es PDUs
concatenated into this MAC-e PDU. In any other case it will be understood that
another MAC-es PDU would not fit and it will therefore not be necessary to
reserve room in the transport block for this additional DDI field.
Click to expand...
Click to collapse
QVGA Display Driver IC (DDI) chip that incorporates QUALCOMM's Mobile Display Digital Interface (MDDI).
I'd vote its the second, as it also contain a good chunk of SRAM memory.
Couldn't get this to work. Anyone else have any luck?
coreydkoster said:
Couldn't get this to work. Anyone else have any luck?
Click to expand...
Click to collapse
What didn't work? Do you have busybox installed?
ryanbg said:
What didn't work? Do you have busybox installed?
Click to expand...
Click to collapse
I havent got it to work either. Though im guessing its only good til a reboot before it gets rewritten?
I thought I read in passing that syscope was the app that checked to see if the system was modified or not. I think it said if you get your phone to say official and freeze/uninstall syscope you won't have the padlock show up anymore.
Sent from my SM-N900V using XDA Premium HD app
Triangle away app gets rid of the padlock.
Sent from my SM-N900V using xda premium
Wanam Xposed module also can get rid of the custom status padlock also.
I get to here but not anywhere else. Am I on the right track.. If so what next?
Sent from my SM-N900V using XDA Free mobile app
---------- Post added at 06:52 AM ---------- Previous post was at 06:50 AM ----------
Sent from my SM-N900V using XDA Free mobile app
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Deansmithok said:
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Click to expand...
Click to collapse
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
donc113 said:
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Deansmithok said:
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Click to expand...
Click to collapse
This is what I get running devmem
[email protected]:/ $ devmem
BusyBox v1.24.2-Stericson (2016-04-23 13:23
:09 EDT) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/ $
To actually use it, you need to su first to get the # root prompt like this:
1|[email protected]:/ $ su
[email protected]:/ #
Then try the command /dev/mem isn't writeable by ordinary users
Sent from my SM-N900V using Tapatalk
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Deansmithok said:
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Click to expand...
Click to collapse
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
donc113 said:
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Deansmithok said:
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Click to expand...
Click to collapse
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
donc113 said:
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I don't have the play store because I don't have android.
The apps need android, but my phone won't even boot. I have "custom rom blocked by cc mode"
Download is blocked by it too.
All I have left is TWRP in recovery mode.
Regards
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Deansmithok said:
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Click to expand...
Click to collapse
You just need devmem and the address. Not busybox devmem and the address.
The only thing I can suggest is that you use ODIN to flash back to whatever the latest stock ROM you were on and go through the rooting process all over again.
The bootloader won't allow you to boot with a non stock recovery unless you unlock the bootloader.
Sent from my SM-N900V using Tapatalk
Hello community,
I'm new in the forum, It's 2 days I'm fighting with this problem: I want to root my BlackPhone 2 using TWRP and SuperSU (I think that this is the only method that works with BP2, since KingoRoot and others are patched for security)
I flashed the recovery TWRP, then I tried the following SuperSU versions:
SR3-SuperSU-v2.79-2017...zip
BETA-SuperSU-v2.74-2.zip
SuperSU-v2.79-2016...zip
UPDATE-SuperSU-v2.79-2016...zip
None of them works, in TWRP all goes OK, no errors and no warnings, but then when I open SuperSU apk it says "There is no SU binary installed... ...If you just upgraded to Android 5.0".
This is really crazy because I'm running on Android 6.0.1 (Silent OS 3.0.7) and using Total Commander I can see /su directory.
Using a root checker app it says that my device is not rooted, but the SU binary is present and also the busybox one.
The Silent Circle's Security Center in their "Privacy Meter" app warns me "Security alert, active root access detected! ...."
For install TWRP I had to switch these things on in Developer Options: "OEM unlocking", "USB debugging", then I enabled installs from unknown sources by ADB and SD card.
Any help will be great, Thanks guys
EDIT: sorry for the Thread title, I can't modify it, it should be SuperSU not sudo su (too much linux)
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
RAZERZDAHACKER said:
But did you try sudo su? Install a terminal emulator and cd to the xbin directory. FYI, the SU directory is there by default afaik.
Click to expand...
Click to collapse
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Unfortunately they are in the same situation. But I admit that I did not install the TWRP permanently due to a possible bootloop phone. Has anyone found a solution to the root?
i have same problem i want unlock bootloader .............need help plz!!!
Koskha said:
Oh I didn't knew that the /su dir was there by default sorry. I downloaded the terminal emulator and "sudo" is not a valid command, when I type "su" it says nothing, and "which su" tells "/su/bin/su", but it does nothing apparently.
If it's not rooted at all how can Silent OS say "root access active detected"?
I just installed SuperSU zip via TWRP, there are other things to do in order to maintain root privileges?
PS: another RootChecker app detects that busybox is installed in /system/xbin/busybox with version 1.13.3, I don't know how that happened, busybox is installed by SuperSU?
Click to expand...
Click to collapse
After you flashed the su zip, did you get the superuser app?
Blackphone 2 bootloader
RAZERZDAHACKER said:
After you flashed the su zip, did you get the superuser app
phone not flash with any file.....devices lock ....need to bootloader unlock.
Click to expand...
Click to collapse
A litle guide to increase bp2 performance
https://forum.xda-developers.com/an...e-make-bp2-t3735815/post75218344#post75218344