how do you send this to the g1 using adb
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
can someone send step by step instructions of how to do this so i can bypss the activation screen without using wifi
HI, The latest version of stock firmware for galaxy mini is MJKT3, now how do I root it?
http://www.mediafire.com/?p0oh96olw9h2v72
hi
this will root all versions even the latest one? or like released by 1 minute? or new ones that has been released 1-10 seconds ago?
just try it if it worked just thank me and the Dev of the update package
if not do something else
I forgot to tell you that you will need to flash that package in stock recovery (in CWM it will not work)
It doesn't work.
it doesn't work for me too
super one click can't be used too
Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
i did flash it
---------- Post added at 06:42 AM ---------- Previous post was at 06:14 AM ----------
can
ashu.bigsmoke said:
Flash this zip in stock recovery. http://www.mediafire.com/?dg360wy61szduv3
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
Click to expand...
Click to collapse
can someone tell me if this one will work?
17thGwydion said:
can someone tell me if this one will work?
Click to expand...
Click to collapse
no
I did try another .zip but not succeeded, it just installed super user
you can flash cwm then with the help of adb you can remount system and can push su to /system
tut
dheeraj (dhlalit11) said:
you can flash cwm then with the help of adb you can remount system and can push su to /system
Click to expand...
Click to collapse
can u give me a tutorial on how to push SU to system? or remount system? or full tutorial.. thanks
full tut plz
still no good
still no good feedback, someone try it please
flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted
Can't set SetUID or SetGID bit.
adb shell chmod 06755 /system/xbin/su
"chmod: operation not permitted"
SuperOneClick doesn't work also.
/system partition is 100% full, you have to delete something to push su binary. (i deleted stock samsung apps, and wallpapers)
dheeraj (dhlalit11) said:
flash cwm with odin
boot into it
connect your mobile with pc
configure your adb connection correctly
open cmd cd to the folder where you are having adb.exe file
copy your su file in the folder where you have adb
type adb remount
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell
if you will get # you are rooted
Click to expand...
Click to collapse
you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that
Unfortunately permission change is a must. You must set setuid and setgid (06755), because upon the su binary execution it will pass the owner's (root) permissions.
Can't use aroma file manager to set permissions because /system/xbin/su owner is root and a plain user can't change permission on files that he doesn't own.
I don't know how to solve this issue.
edit:
I can mount the system partition as rfs:
mount -rw -t rfs /dev/block/stl12 /system
Then, i can set chmod 06755 su.
But after unmount or reboot, permission will be set back to 00755...
dheeraj (dhlalit11) said:
you were able to push su which means you have proper access
my be permission change is not needed
try type adb shell su
or use aroma file manager v1.80 and change su permission from that
Click to expand...
Click to collapse
it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same
Ok, it's solved!
I tried with ubuntu's adb. Unpacked the universal_gb_root_v25.zip. I mounted the system partition in adb. Then pushed all files with correct permissions to /system/xbin (the apks goes to /system/app).
First:
chown all files to root:shell
Second:
chmod 06755 /system/xbin/su
chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/sqlite3
chmod 04755 /system/xbin/ssh
now it looks like this:
-rwsr-xr-x 1 root shell 853044 Jun 22 2011 busybox
-rwxr-xr-x 1 root shell 60264 Dec 6 10:28 dexdump
-rwsr-xr-x 1 root shell 125024 Jun 22 2011 sqlite3
-rwsr-xr-x 1 root shell 146720 Jun 22 2011 ssh
-rwsr-sr-x 1 root shell 91980 Jun 22 2011 su
It works after unmount or reboot.
Finally i have root access.
dheeraj (dhlalit11) said:
it is too much weird
can you use linux
you may be able to change the permission of the su file in Linux desktop and then can push it to system with adb
in this way permissions would remain same
Click to expand...
Click to collapse
Has anybody worked out how to create a Genymotion Xposed testing device?
What I've already achieved:
- Grant Root access to Xposed
- Flash ARM zip
The problem is: Genymotion runs on x86, not ARM. So flashing the ARM zip just breaks the VM.
But flashing the x86 zip just gives the Error "Failed to flash file".
(Yes, I'm using Genyflash)
I also tried it with and without arm translation, no changes.
I simply have no idea what else I could try. Is it currently possible at all?
LM13 said:
Has anybody worked out how to create a Genymotion Xposed testing device?
What I've already achieved:
- Grant Root access to Xposed
- Flash ARM zip
The problem is: Genymotion runs on x86, not ARM. So flashing the ARM zip just breaks the VM.
But flashing the x86 zip just gives the Error "Failed to flash file".
(Yes, I'm using Genyflash)
I also tried it with and without arm translation, no changes.
I simply have no idea what else I could try. Is it currently possible at all?
Click to expand...
Click to collapse
I found that the flash-script.sh inside the xposed-v78-sdk23-x86.zip file is somehow not successfully executed by Genymotion. I've manually patched it.
getting root on Marshmallow
Hi,
How did You get root on Marshmallow?
Sergiusz
sbrzezin said:
Hi,
How did You get root on Marshmallow?
Sergiusz
Click to expand...
Click to collapse
Yes, the latest Genymotion version already come with rooted MM image
itandy said:
Yes, the latest Genymotion version already come with rooted MM image
Click to expand...
Click to collapse
I installed Custom Phone and Google Nexus 7 and none of them has root. Should I do any special setup or did I install wrong device? I use Genymotion 2.6.0 free version.
Sergiusz
sbrzezin said:
I installed Custom Phone and Google Nexus 7 and none of them has root. Should I do any special setup or did I install wrong device? I use Genymotion 2.6.0 free version.
Sergiusz
Click to expand...
Click to collapse
The ROM should be rooted already. su command is available and when you use ADB, it's already a rooted shell.
itandy said:
The ROM should be rooted already. su command is available and when you use ADB, it's already a rooted shell.
Click to expand...
Click to collapse
I got answer from Genymotion team:
"I just got an update from the Dev Team : it appears that in 6.0 the SuperUser Android App hasn't been yet implemented.
This feature will be implemented in the future, and I have linked your request to the task.
When it will be completed and released, you will be automatically notified."
Sergiusz
sbrzezin said:
I got answer from Genymotion team:
"I just got an update from the Dev Team : it appears that in 6.0 the SuperUser Android App hasn't been yet implemented.
This feature will be implemented in the future, and I have linked your request to the task.
When it will be completed and released, you will be automatically notified."
Sergiusz
Click to expand...
Click to collapse
So I managed to make some progress on this. I got the latest v84 xposed working in the newest Genymotion 2.6.0 with a Nexus 5X image by doing the following:
Code:
git clone https://github.com/rovo89/GenyFlash
cd GenyFlash && ./install.sh
adb push xposed-v84-sdk23-x86.zip /sdcard
adb shell flash-archive.sh /sdcard/xposed-v84-sdk23-x86.zip
Reboot Genymotion VM and then drag XposedInstaller_3.0_alpha4.apk to Genymotion vm...profit!
As stated above, the Genymotion images are rooted but a lot of root apps ask for permission and the prompt to grant/deny root wasn't working for me rendering the apps limited in use. I downloaded the newest SuperSU BETA, at the time of this post, BETA-SuperSU-v2.71-20160331103524. I extracted it and then issues the following commands from terminal:
Code:
adb shell mount -o remount,rw /system
adb install common/Superuser.apk
adb push x86/su /system/bin/su
adb shell chmod 0755 /system/bin/su
adb push x86/su /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell su --install
adb shell "su --daemon&"
adb shell setenforce 0
adb shell mount -o remount,ro /system
The problem was issuing the "su" commands resulted in: "error: only position independent executables (PIE) are supported." Countless time spent google searching didn't turn up any leads, but then I happened to notice in the x86/su directory a file called su.pie...pie = position independent executable derp. So I reran the following:
Code:
adb shell mount -o remount,rw /system
adb push x86/su.pie /system/bin/su
adb shell chmod 0755 /system/bin/su
adb push x86/su.pie /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell su --install
adb shell "su --daemon&"
adb shell setenforce 0
adb shell mount -o remount,ro /system
Rebooted my Genymotion vm and BAM root access prompts!!!!! Hope this helps others and good luck.
Worked for me
123SIT said:
So I managed to make some progress on this. I got the latest v84 xposed working in the newest Genymotion 2.6.0 with a Nexus 5X image by doing the following:
Code:
git clone https://github.com/rovo89/GenyFlash
cd GenyFlash && ./install.sh
adb push xposed-v84-sdk23-x86.zip /sdcard
adb shell flash-archive.sh /sdcard/xposed-v84-sdk23-x86.zip
Reboot Genymotion VM and then drag XposedInstaller_3.0_alpha4.apk to Genymotion vm...profit!
As stated above, the Genymotion images are rooted but a lot of root apps ask for permission and the prompt to grant/deny root wasn't working for me rendering the apps limited in use. I downloaded the newest SuperSU BETA, at the time of this post, BETA-SuperSU-v2.71-20160331103524. I extracted it and then issues the following commands from terminal:
Code:
adb shell mount -o remount,rw /system
adb install common/Superuser.apk
adb push x86/su /system/bin/su
adb shell chmod 0755 /system/bin/su
adb push x86/su /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell su --install
adb shell "su --daemon&"
adb shell setenforce 0
adb shell mount -o remount,ro /system
The problem was issuing the "su" commands resulted in: "error: only position independent executables (PIE) are supported." Countless time spent google searching didn't turn up any leads, but then I happened to notice in the x86/su directory a file called su.pie...pie = position independent executable derp. So I reran the following:
Code:
adb shell mount -o remount,rw /system
adb push x86/su.pie /system/bin/su
adb shell chmod 0755 /system/bin/su
adb push x86/su.pie /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell su --install
adb shell "su --daemon&"
adb shell setenforce 0
adb shell mount -o remount,ro /system
Rebooted my Genymotion vm and BAM root access prompts!!!!! Hope this helps others and good luck.
Click to expand...
Click to collapse
Worked for me on the Google Nexus 9 API 23
gamerkcw123 said:
Worked for me on the Google Nexus 9 API 23
Click to expand...
Click to collapse
Hell yeah! I was beginning to think I was the only one who wanted this...and then there were two lol
123SIT said:
Hell yeah! I was beginning to think I was the only one who wanted this...and then there were two lol
Click to expand...
Click to collapse
the Supersu.apk still won't update the su binary. Do you know of a way to get that to work? If not I don't care I have supersu granting root. LOL
gamerkcw123 said:
the Supersu.apk still won't update the su binary. Do you know of a way to get that to work? If not I don't care I have supersu granting root. LOL
Click to expand...
Click to collapse
If I remember correctly I have that same issue but if you use the newest supersu zip you should be able to update it manually via the provided steps.
I think GenyFlash shouldn't be needed anymore... just drag and drop the x86 zip and the installer APK on the Genymotion window and reboot. The only thing that isn't working are the reboot buttons in the installer.
123SIT said:
If I remember correctly I have that same issue but if you use the newest supersu zip you should be able to update it manually via the provided steps.
Click to expand...
Click to collapse
I got it to work. This is what I did. I fallowed your steps to get SuperSU working, and granting
apps permission. Then I removed the APK and installed the APK from the 2.46 update. Then I updated SuperSU.apk from the play store. Success the binary updated successfully.
Step 1: fallowed your steps with the Bata.
Step 2: once I confirmed superSU is working, I remove the APK.
Step 3: I use the SuperSU APK in the 2.46 update.
Step 4: I use adb to push the APK in the 2.46 update to /system/app, and chmod it to 755.
Step 5: I reboot and go to the play store and update SuperSU.
Success!!!!!!!
this was again on the Genymotion Google Nexus 9 6.0 API.
rovo89 said:
I think GenyFlash shouldn't be needed anymore... just drag and drop the x86 zip and the installer APK on the Genymotion window and reboot. The only thing that isn't working are the reboot buttons in the installer.
Click to expand...
Click to collapse
You know, I don't think I ever actually tried it without. May have saved me some time lol
123SIT said:
So I managed to make some progress on this. I got the latest v84 xposed working in the newest Genymotion 2.6.0 with a Nexus 5X image by doing the following:
Code:
git clone https://github.com/rovo89/GenyFlash
cd GenyFlash && ./install.sh
adb push xposed-v84-sdk23-x86.zip /sdcard
adb shell flash-archive.sh /sdcard/xposed-v84-sdk23-x86.zip
Reboot Genymotion VM and then drag XposedInstaller_3.0_alpha4.apk to Genymotion vm...profit!
As stated above, the Genymotion images are rooted but a lot of root apps ask for permission and the prompt to grant/deny root wasn't working for me rendering the apps limited in use. I downloaded the newest SuperSU BETA, at the time of this post, BETA-SuperSU-v2.71-20160331103524. I extracted it and then issues the following commands from terminal:
Code:
adb shell mount -o remount,rw /system
adb install common/Superuser.apk
adb push x86/su /system/bin/su
adb shell chmod 0755 /system/bin/su
adb push x86/su /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell su --install
adb shell "su --daemon&"
adb shell setenforce 0
adb shell mount -o remount,ro /system
The problem was issuing the "su" commands resulted in: "error: only position independent executables (PIE) are supported." Countless time spent google searching didn't turn up any leads, but then I happened to notice in the x86/su directory a file called su.pie...pie = position independent executable derp. So I reran the following:
Code:
adb shell mount -o remount,rw /system
adb push x86/su.pie /system/bin/su
adb shell chmod 0755 /system/bin/su
adb push x86/su.pie /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell su --install
adb shell "su --daemon&"
adb shell setenforce 0
adb shell mount -o remount,ro /system
Rebooted my Genymotion vm and BAM root access prompts!!!!! Hope this helps others and good luck.
Click to expand...
Click to collapse
It's worked on Galaxy S6 6.0.0 API23, Genymotion 2.7.2! Thanks you so much!
Please excuse my poor English
After HUAWEI mate10 brushes into supersu2.82 SR5,
Open supersu prompt without obtaining root permission
But use
ADB shell
$su
Stuck in here, does not appear #
If you uninstall supersu, then execute it
ADB shell
$su
#
There will be root
I'm sorry, I don't have permission to publish pictures
bbs.xxroot.com/data/download/1.jpg
bbs.xxroot.com/data/download/2.jpg
bbs.xxroot.com/data/download/3.jpg
Sorry, I can only send pictures to other forums, the above is the web site!
@Chainfire
@Chainfire
@Chainfire
Hi
I rooted my Nexus 5 with custom rom Paranoid androind 7.3.1(Nougat 7.1.2) using Magisk v18.0
When I run the su from adb shell, it says su: not found
Code:
C:\windows\system32>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
I looked in Magisk Manager -> SuperUser, to check if shell needs toggle to enable root, but didnt find the entry for shell. Please help
First make sure that adb shell is working as it should and then take a look at the "Superuser Access" setting in the Magisk Manager. It should be set to "ADB only" or "Apps and ADB".
Didgeridoohan said:
First make sure that adb shell is working as it should and then take a look at the "Superuser Access" setting in the Magisk Manager. It should be set to "ADB only" or "Apps and ADB".
Click to expand...
Click to collapse
"make sure that adb shell" - How do I do this?
Superuser Access is set to "Apps and ADB" in Magisk Manager