Related
Posting this here because I think it will be of more interest to the tinkerers/devs than general users, if not, feel free to move it. I cobbled all of this together from various places on the web, but I think the credit for the binaries goes to Paul @ MoDaCo.
Nandroid before going any further!
Files you'll need:
For WiFi and CDMA SSH access - QuickSSHD (Download this from the Market. $1.50). I'm just going to assume if you're still reading, you know what this is for and how to use it. It's braindead simple. I think dropbear can be installed and configured manually, but for the $1.50...meh.
adb for tethered access.
The rest are zipped up here: terminfo, nano, bash, profile**
Unzip bashnano.zip onto your SDCard.
adb remount
From adb shell:
Install Terminfo:
cp -r /sdcard/terminfo /system/etc
Setup Bash:
cp /sdcard/bash /system/bin/bash_new
mv /system/bin/sh /system/bin/sh.old
ln -s /system/bin/bash_new /system/bin/sh
mv /sdcard/profile /sdcard/bash_profile (Thanks to jjvcuyler for finding adb bash profile location.)
Setup Nano:
cp /sdcard/nano /system/bin
I'm not sure if this setup will have any impact on sh scripts being used in the various ROMs, so use this at your own risk. I think it would kick ass to see this type of bash functionality baked into the custom ROMs.
If anybody would like to make this a flashable.zip, please do. I don't know how to do that yet.
Anyway, hope y'all find it useful.
**profile reflects a few personal choices for aliases and colors, but you can edit to your personal taste.
So I just did this. Is there any way to get this functionality into a local terminal?
Also I was able to do everything from a local terminal without adb. Just do the following first:
su
remount rw
Click to expand...
Click to collapse
adb shell fires off bash, but it doesn't read profile from /etc. It's going to be a simple matter of figuring out where bash is looking for it. I just haven't found that out yet.
How do you like having full bash capabilities on EVO? Arrows/tab completion/color prompts, etc...
J
jmxp69 said:
adb shell fires off bash, but it doesn't read profile from /etc. It's going to be a simple matter of figuring out where bash is looking for it. I just haven't found that out yet.
How do you like having full bash capabilities on EVO? Arrows/tab completion/color prompts, etc...
J
Click to expand...
Click to collapse
Copy profile to /sdcard/bash_profile
jjvcuyler said:
Copy profile to /sdcard/bash_profile
Click to expand...
Click to collapse
WooT! There it is. I'll update the OP. Thanks jjvcuyler.
Edit: /sdcard/bash_profile works for ssh and adb. OP updated to reflect the change.
jmxp69 said:
Posting this here because I think it will be of more interest to the tinkerers/devs than general users, if not, feel free to move it. I cobbled all of this together from various places on the web, but I think the credit for the binaries goes to Paul @ MoDaCo.
Nandroid before going any further!
Files you'll need:
For WiFi and CDMA SSH access - QuickSSHD (Download this from the Market. $1.50). I'm just going to assume if you're still reading, you know what this is for and how to use it. It's braindead simple. I think dropbear can be installed and configured manually, but for the $1.50...meh.
adb for tethered access.
The rest are zipped up here[/URL]: terminfo.zip, nano, bash, profile**
Unzip bashnano.zip onto your SDCard.
Unzip terminfo.zip (from inside bashnano.zip) onto your SDCard.
adb remount
From adb shell:
Install Terminfo:
cp -r /sdcard/terminfo /system/etc
Setup Bash:
cp /sdcard/bash /system/bin/bash_new
mv /system/bin/sh /system/bin/sh.old
ln -s /system/bin/bash_new /system/bin/sh
mv /sdcard/profile /sdcard/bash_profile (Thanks to jjvcuyler for finding adb bash profile location.)
Setup Nano:
cp /sdcard/nano /system/bin
I'm not sure if this setup will have any impact on sh scripts being used in the various ROMs, so use this at your own risk. I think it would kick ass to see this type of bash functionality baked into the custom ROMs.
If anybody would like to make this a flashable.zip, please do. I don't know how to do that yet.
Anyway, hope y'all find it useful.
**profile reflects a few personal choices for aliases and colors, but you can edit to your personal taste.
Click to expand...
Click to collapse
there is no terminfo.zip and there is nothing in terminfo directory from within the original zip... help?
Sorry, I missed the recurse flag zipping the terminfo directory. It's fixed now. Go ahead and re-download.
Here's a link for just terminfo.zip
J
I modified the bash_profile to get rid of the colors since the window's cmd.exe doesnt support ansi colors. probably a better way to do this but it works for me.
also found this useful for setting PS1 to my liking http://www.cyberciti.biz/tips/howto-linux-unix-bash-shell-setup-prompt.html
jmxp69 said:
adb shell fires off bash, but it doesn't read profile from /etc. It's going to be a simple matter of figuring out where bash is looking for it. I just haven't found that out yet.
How do you like having full bash capabilities on EVO? Arrows/tab completion/color prompts, etc...
J
Click to expand...
Click to collapse
is there a way to get tab completion through adb shell?
Yes. This works with adb shell. Just follow the directions in the OP.
jmxp69 said:
Yes. This works with adb shell. Just follow the directions in the OP.
Click to expand...
Click to collapse
i have and i do have everything done as stated in the OP, when i try tab completion via adb shell (phone tethered with usb) from my pc, it just puts in a tab, it doesn't complete.
Hmm....could be a dos thing with cmd.exe. I haven't tried on a PC, I'm on a Mac. adb shell via OSX works fine with tab completion. Try ssh'ing in instead with something like putty? Once you get ssh going, you don't need a cable.
Edit: Confirmed...tab completion doesn't work over Win cmd.exe and adb shell.
jmxp69 said:
Hmm....could be a dos thing with cmd.exe. I haven't tried on a PC, I'm on a Mac. adb shell via OSX works fine with tab completion. Try ssh'ing in instead with something like putty? Once you get ssh going, you don't need a cable.
Edit: Confirmed...tab completion doesn't work over Win cmd.exe and adb shell.
Click to expand...
Click to collapse
Thanks for looking into it... I'll try getting it to work via linux instead. I guess ssh would be a solution, but i never turn wifi on.
Is anyone able to do a NAND backup/restore after doing this? With Amon Ra's recovery I was unable to NAND backup.
EDIT:
I think this is a big negatory. I was just able to do a NAND backup, so maybe the error I got was a coincidence after applying these changes.
Anyone else noticing that the time is always displayed as GMT in the prompt? The date command gives the correct time for my timezone but the bash prompt always shows GMT
Vinny75 said:
Anyone else noticing that the time is always displayed as GMT in the prompt? The date command gives the correct time for my timezone but the bash prompt always shows GMT
Click to expand...
Click to collapse
Change PS1 line: \A to `date +%H:%M`
jmxp69 said:
Posting this here because I think it will be of more interest to the tinkerers/devs than general users, if not, feel free to move it. I cobbled all of this together from various places on the web, but I think the credit for the binaries goes to Paul @ MoDaCo.
Nandroid before going any further!
Files you'll need:
For WiFi and CDMA SSH access - QuickSSHD (Download this from the Market. $1.50). I'm just going to assume if you're still reading, you know what this is for and how to use it. It's braindead simple. I think dropbear can be installed and configured manually, but for the $1.50...meh.
adb for tethered access.
The rest are zipped up here: terminfo, nano, bash, profile**
Unzip bashnano.zip onto your SDCard.
adb remount
From adb shell:
Install Terminfo:
cp -r /sdcard/terminfo /system/etc
Setup Bash:
cp /sdcard/bash /system/bin/bash_new
mv /system/bin/sh /system/bin/sh.old
ln -s /system/bin/bash_new /system/bin/sh
mv /sdcard/profile /sdcard/bash_profile (Thanks to jjvcuyler for finding adb bash profile location.)
Setup Nano:
cp /sdcard/nano /system/bin
I'm not sure if this setup will have any impact on sh scripts being used in the various ROMs, so use this at your own risk. I think it would kick ass to see this type of bash functionality baked into the custom ROMs.
If anybody would like to make this a flashable.zip, please do. I don't know how to do that yet.
Anyway, hope y'all find it useful.
**profile reflects a few personal choices for aliases and colors, but you can edit to your personal taste.
Click to expand...
Click to collapse
I followed the steps exactly, but end up with "- exec '/system/bin/sh' failed: Permission denied (13) -" while typing "adb shell" in a windows or linux terminal. I cannot recover the original sh because the root is lost, and I cant root my phone anymore probably because something wrong with the new sh. Any idea how to fix this?
EDIT: Acutally nevermind. adb shell works in recovery mode. but still, not sure why the modified sh doest work for me
The Downloadlink is dead!
So the thread is useless.
francwalter said:
The Downloadlink is dead!
So the thread is useless.
Click to expand...
Click to collapse
Yeah.....no.
A simple google search would have shown you that the files are here: http://66.197.42.222/bashnano.zip
or here http://androidforums.com/attachment...ide-installing-bash-nano-android-bashnano.zip.
EDIT: I've also attached it in case the links above ever die, there will still be one which does not.
ya this is great and all but any decent busybox installer will setup bash for you.
Hi all!
Was about to purchase a Nexus 7 when I saw a huge discount on the Asus TF101 and decided to take it. How I have a it in front of me proudly informing it has the firmware revision IML74K.WW_epad-9.2.1.27-20120615. BTW, the s/n starts with B50 if it matters.
And now what? Wait for the official JB or root it right now? I usually root all my devices at least to have nandroid + TiBu, even if I don't plan to install any alternative FW.
The problem is it's an ICS 4.0.3 with the problem to enter into recovery mode and I have only a Mac computer, no Windows and no Linux machines around. I read the threads and see every time the Windows tools, nothing for Mac. No root from SD card neither.
Any advice how to root using the Transformer itself or my Mac? And any advice regarding best JB ROM or at least best kernel for stock 4.0.3 ROM with exFAT support? I don't use NTFS because my Macs can't write on and old FAT16 has the famous 4 Gb limit, not good for the movies.
Many thanks in advance.
You could try and install Windows on your Mac to essentially have a dual boot of both OS's. Or you could use something like VMWare (I think that's what it is but I'm like 5% sure) which allows you to run windows without necessarily installing it. Anyway, I suggest, if you can, to go ahead and root your device and install a JB ROM like EOS or CM10 or something.
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Hi all,
Shmi117 said:
You could try and install Windows on your Mac to essentially have a dual boot of both OS's.
Click to expand...
Click to collapse
No chance! I don't like to spend hours installing Windows and all this stuff again !!! :crying:
WCL1990 said:
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Click to expand...
Click to collapse
Basically what Linux can to Mac OS X can do. At least regarding adb and the command line use. The problem is I have found tons of good information about how to do it using Windows, but nothing for Linux nor Mac.
OK, here is the answer. One can root the Asus Eee Pad Transformer TF101 using Mac OS X only!
Developing in next message...
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Thanks a lot friend. I used the same procedure to root my TF101 using Ubuntu Are you using any Customised ROM ? I am using CM10 based ROM built by RaymanFX and it is simply awesome
iLearner said:
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Click to expand...
Click to collapse
Thanks, that worked nicely for me!
One thing I can't figure out yet, though, is how to do a backup - the microsd card doesn't mount at /sdcard/ and backing up to internal storage is not recommended...
Wheelie
Hi!
A linux only solution for B70(+) devices can be found here:
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
It is what I used twice so far. Works as it should.
I do not claim credit for anything! I just stumbled upon the solution.
Problem rooting
Hi,
this is my first post on XDA.
After a lot of readings here, I think I have tried everything I could, but my knowledge in rooting is too limited to understand these bugs:
At first, when I tried running these lines on the terminal, I couldn't push the files to /data/local: permission denied.
Then, I tried pushing to /sdcard/ and it worked.
But the next error I get is when linking:
"link failed Function not implemented"
Can you help me please?
My computer is a Mac, so I have tried you method first. I also tried on my Parallel Desktop with Windows 8 and on the PC with Windows 8.1 of my girlfriend, with RootDebugFs.
Here is the description of my Infinity pad:
model: ASUS Transformer Pad TF700T
Android: 4.2.1
Kernel: 3.1.10-g9827b9a, [email protected] #1
Build: JOP40D.WW_epad-10.6.1.14.8
I had the build 14.10 but I found that I should downgrade to 14.8, so I did, but nothing changed.
I also unlocked my tablet by mistake, thinking it would help rooting.
Thanks for your help.
Best,
Yohan.
Just did this!!! Still works!!! Followed your steps. Now the recovery is TWRP 2.5!!! As the peri version changed I checked if the .bat was still doing the same things, and it is!!
Thanks for your tuto! Saved me some time installing W**** ...
Currently on a Nexus 5X with marshmallow and am looking to change the location mode [High Accuracy, Battery Saving, GPS] through the shell. I've found numerous threads on this topic simulating essentially what Secure Settings does for the Tasker plugin.
http://android.stackexchange.com/qu...ossible-to-enable-location-services-via-shell
http://android.stackexchange.com/questions/115011/toggle-location-services-via-adb-in-android-5
Also this alternative method: http://forum.xda-developers.com/nexus-6/general/how-to-restore-change-android-id-t3219345
Tried these too:
Code:
INSERT
adb shell content insert --uri content://settings/secure --bind name:s:location_providers_allowed --bind value:s:wifi,network
UPDATE
adb shell content update --uri content://settings/secure --bind value:s:wifi,network --where "name=\'location_providers_allowed\'"
However, it refuses to change on my Nexus 5X. I've tried numerous different ways whether just calling it from ADB shell or just as a root user in the shell directly. Nothing seems to change the "location_provders_allowed" key manually.
Anyone have any leads on this? I've wanted to use Secure Settings, but it doesn't support systemless root as well as even if it did I think this is the method they use in the app.
I'd like the answer to that too!
Ok so i got a zte quest 5 (z3351s) though qlink. Not the phone i wanted but it was one i could afford. And it works very well just can't run amazon music and other apps at the same time.
But the bloatware is unreal. Used to in my galaxy s3&s4 days i could root and delete all apps i didn't need. I know i can disable them but i want them gone completely.
Majisk didnt work
Kingoroot same even used pc.
I am hoping someone knows of a way i can root this phone or at least delete all the un needed apps for example i have Google maps go (came stock) i put the org google maps which is better plus offers sat view.
Edit i did some math and converting and the useless apps 11 out of 58 come out to 349.72mb which is a lot if your phone only has 16gb of space. Also note i don't have hardly anything.
Worst case i can Hotspot to my note10+ for multitasking but not sure of data limit.
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
I heard about adb methods but i haven't messed with it in forever since apk/ios apps came out
jwoegerbauer said:
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
Click to expand...
Click to collapse
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
vp1117 said:
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
Click to expand...
Click to collapse
I spoke of SU-binary and NOT of SuperSU installer package
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
TexasPride, sorry I stepped in your thread.
jwoegerbauer said:
I spoke of SU-binary and NOT of SuperSU installer package
Click to expand...
Click to collapse
I see. It is often mixed in numerous materials one can find in the net. Subject is SU-binary update, but the ultimate goal is to install supersu.
jwoegerbauer said:
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Click to expand...
Click to collapse
What should be result of running this code? SU-binary located in Downloads with 777 permission? What is the practical sense/use of it?
What software/application would use SU in that location?
Sorry for my questions. I'm not arguing. I try to understand the idea.
jwoegerbauer said:
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
Click to expand...
Click to collapse
Somehow, with my almost zero knowledge of edify and linux command line I got the same conclusion: SuperSU zip has to be modified in order to install it via adb on devices that do not have TWRP for sideload. I failed to find any examples of SuperSU modding...
@vp1117
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
jwoegerbauer said:
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
Click to expand...
Click to collapse
OK. I guess, I can repack zip to tar.
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
jwoegerbauer said:
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
Click to expand...
Click to collapse
Interestingly, I can execute all commands I need without having su-binary (~100 KB) uploaded to my phone. It is strange but I see #-prompt after I ran <adb shell>. This happens on my UNrooted phone, running stock ROM. I guess, it's a specifics of my phone, no need to try explain it.
I done failed trying to read i dont really understand linux all that well. But if anyone has any links so i can download it and try it
vp1117 said:
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
Click to expand...
Click to collapse
Of course it's your decision how you transfer the SuperSU package onto phone: many ways lead to Rome.
My decision was to push SuperSU package repacked as TAR-file onto phone, extract it there, and finally run the modified update-binary.sh when phone is booted into recovery mode:
Code:
adb shell "$(cat < %supersu_dir%/update-binary.sh); echo $?"
So I rebooted to stock recovery and then uploaded following from UPDATE-SuperSU-v2.82-20170528234214.zip package to my phone's folder /tmp:
/arm64
/common
/META-INF
update-binary.sh
Here is what I got:
Z:\android\adb>adb shell "$(cat < /tmp/update-binary.sh); echo $?"
127
/system/bin/sh: #!/sbin/sh: not found
And here's what I got running same command from # command line:
# $(cat < /tmp/update-binary.sh); echo $?
/system/bin/sh: #!/sbin/sh: not found
127
In response to # ls -al /sbin I get lots of lines one of them is as follows:
lrwxrwxrwx 1 root root 7 1970-01-01 00:00 sh -> busybox
I feel that I'm doing something wrong, but what exactly?
In attached txt-file I put some more details I got in command line.
jwoegerbauer said:
... and finally run the modified update-binary.sh when phone is booted into recovery mode:
Click to expand...
Click to collapse
Am I right the only modification needed is to rename update-binary to update-binary.sh ?
@vp1117
NO.
When I said modified then I didn't mean simply rename it: The contents of original update-binary file must be rewritten / deleted in some parts. Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above. Take also note that, if device's Android isn't rooted yet, the location for unpacked SuperSU mandatory must be /data/local/tmp.
BTW:
I can see BusyBox is installed on your device's Android. Take note that BusyBox by default comes with the SU-binary. Hence your device's Android is rooted! Wondering why you waste your time with trying to completely install SuperSU from scratch?
jwoegerbauer said:
Wondering why you waste your time with trying to completely install SuperSU from scratch?
Click to expand...
Click to collapse
Good question.
Probably, because I see this when phone restarts from recovery to normal android:
jwoegerbauer said:
Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above.
Click to expand...
Click to collapse
OK, no problem, I can re-pack zip into tar.
However, what you demonstrated above was a screenshot showing update-binary.sh being inside the tar. At the same time you don't tell how update-binary.sh must be amended. Is it OK?
TexasPride
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
vp1117 said:
TexasPride
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
Click to expand...
Click to collapse
Its ok, i dont mind at all.
@TexasPride
FYI: I no longer participate this hijacked thread.
Hello Friends~!
Today I bring to you the Latest version of Nox, made portable, with a Cleaner Script to remove all the junk on your Main Machine as well as for Clones
DOWNLOAD BARENOX:
BareNox.zip (200M)
If you would rather build your own, I will now provide a written guide for how BareNox was built.
"BareNox" went through a lot of testing and a script was made to automate much of what is written below
Spoiler: WRITTEN GUIDE
Made using the latest version of Nox, which can be downloaded off the right side of this page:
System Requirements of Nox App Player – NoxPlayer
Open Nox's Multi Drive Manager and select "Add Emulator" and "Android 9" or whatever you prefer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When it is done building the machine you need to click on settings and enable root.
Spoiler: HOW TO CLEAN THE PREINSTALLED MACHINE WITH AN APP (NOT RECOMMENDED)
This method is advised against, due to the amount of time it takes to physically remove each directory within the gui, when we could remove all of these directories with a simple script. The knowledge will still be provided to show what the adb method is doing for us.
Open Nox and install a launcher app like nova, and a root explorer by selecting the apk button on the right side panel.
Spoiler: PIC
If you need the apps:
Nova
nova.apk
drive.google.com
Root Explorer
RootExplorer.apk
drive.google.com
Now open Nox's settings by clicking on the gear icon at the top right.
We need to go into General, and then put a check on root.
Spoiler: PIC
Next click on the Gaming tab and enable high fps and rendering cache. This is to allow you to be able to play higher end mobile games
Spoiler: PIC
Save settings and restart the machine
Select Nova as the Launcher app always
Spoiler: PIC
Open root explorer. Grant Superuser access forever
Delete all the items highlighted in the pictures below and close the machine.
Spoiler: PIC
Spoiler: HOW TO CLEAN THE PREINSTALLED MACHINE WITH ADB (RECOMMENDED)
This comment explains it
Spoiler: HOW TO USE THE SCRIPT AND NOVA ON ANY VERSION OF NOX
Make a new machine and enable root in settings
Make a text file and call it run.bat
Paste in this code.
Code:
adb root
adb shell rm -r /system/app/AmazeFileManager
adb shell rm -r /system/app/AppStore
adb shell rm -r /system/app/BuiltInPrintService
adb shell rm -r /system/app/CarrierDefaultApp
adb shell rm -r /system/app/CompanionDeviceManager
adb shell rm -r /system/app/CtsShimPrebuilt
adb shell rm -r /system/app/EasterEgg
adb shell rm -r /system/app/Facebook
adb shell rm -r /system/app/Helper
adb shell rm -r /system/app/LiveWallpapersPicker
adb shell rm -r /system/app/PrintRecommendationService
adb shell rm -r /system/app/PrintSpooler
adb shell rm -r /system/app/Traceur
adb shell rm -r /system/app/WallpaperBackup
adb shell rm -r /system/app/newAppNameEn
adb install nova.apk
adb reboot
Paste run.bat into the bin folder of Nox
Paste nova.apk (10M) into the bin folder of Nox
Now Run run.bat
Spoiler: VERIFIED WORKING GAMES
If there is a game you want me to test, leave a comment below.
Spoiler: BEAT PARTY
at the end of the video
Spoiler: DIABLO IMMORTAL
at the end of the video. guide is outdated
Spoiler: EPISODE STORY APP
Spoiler: MKX ONLINE
There's more that can be finessed here, have fun!
VT-Error fix
For rooted WSA (Android 12 or 13) see this guide
How To Build and Root Your Desired Flavor of WSA and install the Playstore Using LSPosed & Magisk. Plus a Premade
Hello Friends, Today I wanted to write a guide about how to use the LSPosed Github Repo on a linux machine to build your desired flavor of WSA with GAPPS and Root. If you do not already have a Linux machine or WSL, I have a fully built and...
forum.xda-developers.com
Works pretty well for me, except for trying open the multiple instances. I've wiped things clean a couple times and even tried on my other pc. Luckily the app I was trying to install had an x86 version so it'll do for now. I'll have to look into it when I have a bit more time.
Thanks for the post!
Twistt said:
Works pretty well for me, except for trying open the multiple instances. I've wiped things clean a couple times and even tried on my other pc. Luckily the app I was trying to install had an x86 version so it'll do for now. I'll have to look into it when I have a bit more time.
Thanks for the post!
Click to expand...
Click to collapse
Thank you for testing it!
Note that this issue has now been corrected
-
--
--
NotNox has had a Proper Update and is now at V2 "BareNox"
Includes the cleaning script commented on earlier.
Spoiler: HOW TO USE BARENOX
UPDATED 08/04/2022
BareNox.zip
drive.google.com
(196.2 MB ZIPPED)
Open BareNox and then bin, run MultiplayerManager.exe and add new emulator of choice
The first time you make a machine, nox will have to dl the "base" of the android version you selected from nox's servers. You only have to do this the first time you try to create an android 9 or 7 machine. You will then be able to create clones quickly as the BareNox folder will now contain the base disk and data folder.
Make sure to click on the gear icon and enable Root in system settings before running the machine
Run the remove.bat script when this lady appears on your new machine (this is when you have full read write access)
This will go through and remove the crap apps and install nova launcher for us
Spoiler: HOW TO CLEAN THE PREINSTALLED MACHINE (OR CLONES) WITH ADB
Spoiler: WRITTEN GUIDE
Go into the Binary folder of Nox or Not Nox and add a new text file called remove, paste NOVA.APK into this folder as well
Paste the contents of the script into the remove file
change the file extension from txt to .bat by renaming the file
add a new emulator and wait for it to make it to this screen, you need to hit Login later in order to get full Root, otherwise our batch will fail.
Run the remove.bat file after hitting Login Later and waiting for the garena lady to appear
this is what will be shown as the batch runs, don't do anything the machine will reset itself
select nova always and you're all set!
Spoiler: THE SCRIPT AND NOVA DL LINK
Spoiler: FILE EXPLORER OPTIONS PREREQ
View attachment 5669749
You need to have hide extensions for known file types unchecked, in order to be able to change a file from text to batch
nova.apk
drive.google.com
adb shell rm -r /system/app/AmazeFileManager
adb shell rm -r /system/app/AppStore
adb shell rm -r /system/app/BuiltInPrintService
adb shell rm -r /system/app/CarrierDefaultApp
adb shell rm -r /system/app/CompanionDeviceManager
adb shell rm -r /system/app/CtsShimPrebuilt
adb shell rm -r /system/app/EasterEgg
adb shell rm -r /system/app/Facebook
adb shell rm -r /system/app/Helper
adb shell rm -r /system/app/LiveWallpapersPicker
adb shell rm -r /system/app/PrintRecommendationService
adb shell rm -r /system/app/PrintSpooler
adb shell rm -r /system/app/Traceur
adb shell rm -r /system/app/WallpaperBackup
adb shell rm -r /system/app/newAppNameEn
adb install nova.apk
adb reboot
Spoiler: HOW THE NOX ADB SCRIPT WAS MADE
Hello Friends! I have created a guide on how to make your own Script to clean up your Nox machines (pre-installed and clones)~! Please note there is much much more that you can do here, this is just to teach you the basics to help you come up with interesting ideas!!
This video is Nerd Knowledge, and unneeded for folks that just want to quickly clean up their clones. Check out the next comment for the quick cleaning method
"BareNox" has this batch file pre-installed for your convenience
jenneh said:
NotNox has had a Proper Update and is now at V2 "BareNox"
BareNox.zip
drive.google.com
100 mb zipped!
Includes the cleaning script commented on earlier. Watch the video to see how to use it.
Note that:
THIS IS NOT A PREINSTALLED MACHINE, like "NotNox".
You will have to use multiplayermanager and add a new emulator with your choice of android version.
The first time you make a machine, nox will have to dl the "base" of the android version you selected from nox's servers. You only have to do this the first time you try to create an android 9 or 7 machine. You will then be able to create clones quickly as the BareNox folder will now contain the base disk and data folder.
Run the remove.bat script when this lady appears on your new machine (this is when you have full read write access)
This will go through and remove the crap apps and install nova launcher for us
View attachment 5669963
Click to expand...
Click to collapse
i got this error
HoangNK said:
i got this error
Click to expand...
Click to collapse
edit I am working on a fix
This issue has now been fixed
@HoangNK I apologize, I didn't mean to dismiss your VT error, I sincerely thought it was due to that mode not being enabled on the user end.
I now realize, after reinstalling windows on my laptop which has vt enabled, that I did indeed create this error. I didn't realize it at the time due to sharding, as I had nox installed in the main directory as well as the portable, so I didn't notice the problem.
I have rebuilt and verified BareNox, here's the new dl link:
BareNox.zip
drive.google.com
(196.2 mb ZIPPED)
For anyone Still experiencing the "VT Error" check your Windows Features settings. I unintentionally caused this error to myself while playing with WSL. Open up windows Features and uncheck these options, then reset
Spoiler: show
Something to consider about Emulators, they can be used to program virtual machines that have windows preinstalled faster usually than on your android device. Then you could pull your machine from the emulator and port over to any android device. I'm working on a detailed guide but it will take some time as I work to make the virtual machine's parameters more feasable for work use, i.e. a 10gb max hdd is not gonna suffice~!
To Do List: get win 10 working
Proof of Windows 7 Working in Nox:
How To Guide:
How To Install Windows Or Linux ISOs on your Android Devices - Windows 10 Nox Lab + Working Arm Distros for your phone using Termux
Update: A new thread is created to house "premade" linux distros. The first premade environment is an Ubuntu distro, installed using proot-distro in termux, Takes only a few minutes to restore the backup, else instructions are provided to build...
forum.xda-developers.com
A note to anyone checking this out from this date forward, Nox has had an update since I wrote the script. So when barenox downloads the android image from nox's server, they are different than before. Meaning that Even though one selects ROOT on startup, the ADB will not recognize the READ WRITE status thus rendering the .REMOVE.bat script useless for the time being. The adb root command does not help, I didn't bother to su into the shell bc the time factor, I could just delete in root explorer
A TLDR use the manual removal method with root explorer and manually install nova as the original thread shows how to do if you want to remove the crapware.
I'm not going to update the script, instead I am going to stop being lazy and just make my own emulators in android studio and share some builds in another thread. I'll leave a comment below whenever that happens.
Listen Linda.
I found an Amazing OS that I am trying to work out a few kinks for. It runs in vmware, has root, can play the games, has a traditional desktop feel, can run multiple apps in separate windows.
It's called prime os! I am not a creator. Just a testing a producto~!
I will make a new thread with prebuilt images of this and like 5 other prebuilt android x86_64/ chrome os forked os's that I played with this week. Putting out the word about prime in case anyone has any ideas how to get openvmtools or vmware tools to work on here. I am trying to build a stack in termux to accomplish this myself, key word trying. Maybe someone knows how.
other os's tested and built -- may add more if I find them
google chrome os - cloudready version
bliss os
android x86_64 9.0
flint os
fyde os
Spoiler: notes
as an Edit ---I am well aware that the tools are not "officially supported" so lets make them work anyway ok
This is 12 years old but still relevant
'As an update, I was able to locate the vmware tools iso for pre glibc linux distros (like our android vms) It comes with vmware workstation 17
had to pkg install tsu then run this command and am a step closer
I went through and pointed the script to the requested binary's location /system/bin/more and the others all for the most part in bin with depmod being in xbin. the program seemed to have an error at the end. going to take all the requested binaries out from system now and add them to the vmtools folder
using root explorer can copy the binaries from bin into the vmtools folder
So here's my notes on getting vmware tools to work in the android emulator.
In vmware tools on your windows pc there are isos that contain the tools.
Inside the iso is a file like this. extract it and extract the file it makes
So here is what I did, You can see the tools have an etc folder and a bin folder. and in pictures in the notes comment above, we know that the tools need certain binaries to run, or access to.
It is not just enough to point the tools to the /system/bin/binaryname because the stock binaries aren't executable.
So I obtained all the binaries the code calls for and put them into the bin folder of the tools.
I also built the missing directories such as /var/log
i changed the name of install-vmwaretools.pl to run.pl and added mkdir codes for the needed folders
Now running perl run.pl gives this interesting error
Anyone have any ideas?
It also really Did create that many folders, haha
hey there.. is there still possible to use your script to use older version of noxplayer and make that work? i get it that no more noxplayer updates will be compatible. but, that is just perfect for me.
i used noxplayer every day since 2016 and run 12 instances. it was and still is Ver. 3.8.3.1
but google as of last month has now removed games that is no longer supported by the google play.. so no more game updates for me. so i have no other choice to upgrade too.. i had off course followed guides and hacked it.. so no adds what so ever.. so hoping that you can still your very useful software to get rid of ads and malwares that they usually bring to free version.
thank you
@noxlar2 anything is possible, however i would need a copy of the version you want to fix to be able to advise better. as far as the current version i will for sure look at fixing the script for it tomorrow. kinda got super carried away on other projects and should take the time
@jenneh
wow.. fast reply back. well, just buildt me a new pc.. so, it will be with a fresh win11 and fresh noxplayer.. so i have no idea what version i must choose.. i will have my old pc system untouched in case of fall back on nox.p.. reason i always used the version i did was because of superior stability vs recent (back then + few years forwards)
also i did test latest free version on my minipc.. and it worked great as well. but, i have not done extensive testing so i don't know.
@noxlar2 Hey Congratulations on your new PC! That's always an amazing feeling. Thank you for clarifying which version. I was able to successfully get the script working again on the Latest nox and Lol it was silly, all the script needed was "adb root" added to the top.
i had to do the VT-Error fix bc of playing with WSA
got the original barenox updated -- link in the op and HERE Just remember to select root in settings before running the machine or the script wont work