What's up! I successfully rooted my Nexus S i9020T 2.3.4 Thanks to the many links in these forums! THANKS! Now, I downloaded the BT5 ARM img , got everything pushed to the phone. Then in Terminal emulator -
Code:
cd /sdcard/BT5
sh bootbt
Returns
Code:
mkdir failed for -p, File exists
Loop device exists
ioctl LOOP_SET_FD failed:
Bad file number
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt: cannot create /data/local/mnt etc.....
I can post the rest if needed.
I seen the other threads where the bootbt had to be modified but I haven't seen anything specific for the Nexus S. Perhaps I should use the modified BT5 ARM img? Any help is appreciated thanks in advance.
Update! BT5 ARM Nexus S
So I used the modified BT5 img and followed the instructions here.
http://forum.xda-developers.com/showthread.php?t=1074169 (not allowed to post there yet!)
I run sh installbt.sh and that seems to go ok.
I get errors at this step.
Code:
to use your BackTrack you can use following commands.
startbt <- mounts and prepares the system for usage.
stopbt <- unmounts and free up all resources.
bt <- a command line version of BT chroot.
When I run startbt I get this
Code:
mknod: /dev/block/loop: File exists
moun: mounting /dev/block/loop254 on /data/local/bt
failed: Device or resource busy
mount: I/O error
mount: I/O error
mount: I/O error
startbt: cannot create /data/local/bt/etc/resolv.conf: I/O error
startbt: cannot create /data/local/bt/etc/resolv.conf: I/O error
startbt: cannot create /data/local/bt/etc/hosts: I/O error
chroot: can't execute '/bin/bash': Input/output error
Any help is appreciated!
Did you check your ROM for EXT2 support?
sounds like you are trying to run Linux as the OS in the phone?
have you tried the guide on how to install ubuntu into your phone?
http://forum.xda-developers.com/showthread.php?t=907760&highlight=ubuntu
the original image you flashed is wrong it's for the wrong phone
this is a Nexus S not a Sony Xperia
Waiting for *how to*...
just founded that http://mayaseven.blogspot.com/2011/05/backtrack-5-on-my-android-phone-nexus-s.html
its posible.
Thanks! I'll keep an eye out for it.
Working
Using this link http://forum.xda-developers.com/showthread.php?t=1085863
{
"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"
}
Screens Added
added a few screens.
Working fine here on my nexus s. got the ui up in my vnc viewer no problem.
ext2 support
what roms are the two of you running?
my rom doesn't have support for mounting ext2 file systems so i can't use this until i find one that does.
Related
Introduction
As I like to stay connected via Putty to my Android phone, from time to time I missed the functionality of updatedb / locate that I so got used to within Linux environment.
I've decided to cross compile the findutils package (I couldn't get the latest version 4.4.2, but an older before, 4.2.33).
Screenshot
You can see the updatedb command followed by some locate commands.
{
"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"
}
Installation
Busybox is required.
1. Copy the archive onto your /sdcard/ folder.
2. mount your /system folder as read-write
3. cd /system/
4. tar xf /sdcard/findutils-4.2.33.tar.gz
It is mandatory that you are inside /system/ folder when you extract the archive.
Then you have to create the database (using updatedb script). It will take a bit of time - but not too much.
Then you can use the locate command giving any part of a file name that you can remember, you can also use wildcards!
Observations
1. No integration with cron / etc. If you know your updatedb database is out of date, rebuild it using "updatedb"
2. Busybox comes with a /system/xbin/find command. The trouble with it is that it doesn't support the fstype argument, and thus, updatedb cannot prune some standard file system type paths. However, the bundled package here comes with its own find utility which unpacks into /system/bin/find.
3. Busybox is required for sort / sed, but updatedb script is patched to use the /system/bin/find (its own find executable) instead of the default busybox one.
4. My phone did not have an /etc/mtab file (list of mounts which mount is supposed to update whenever something happens). Thus, there is a line in the updatedb script which recreates that file on each updatedb invocation (mount > /etc/mtab). If you phone / tablet has it, please modify updatedb script and remove the mount command.
Download
Use it at your own risk!
findutils-4.2.33.tar.gz
This is great! Thanks for your work!
I hope that there will be a file manager for android which uses updatedb/locate to index/search files in the future, that would be sooooo awesome!
Don't know about other software that searches - but it would be nice too.
Maybe I can create something, but I'm sure there are others more integrated - such as looking in SMSes or in mails too, etc.
nice! find takes for ever lol now i have locate!
Any chance of getting the code. Did you create your own Android.mk? Did you use the FindUtils make?
When I run updatedb, I get these errors:
/system/bin/find: /preload: Value too large for defined data type
/system/bin/find: /storage/sdcard0: Value too large for defined data type
/system/bin/find: /system: Value too large for defined data type
/system/bin/find: /data: Value too large for defined data type
yelkarama said:
When I run updatedb, I get these errors:
... <snip>
/system/bin/find: /data: Value too large for defined data type
Click to expand...
Click to collapse
I also get this error
This doesn't work. Might have worked a couple years ago before 4.x Android...
Use something like es file Explorer
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I will rebuild it in the weekend I think back in the days the file systems were only 32bit, and now a lot of phones have 64bit file systems ...
viulian said:
I will rebuild it in the weekend I think back in the days the file systems were only 32bit, and now a lot of phones have 64bit file systems ...
Click to expand...
Click to collapse
Thanks for your efforts, I guessed it needed a rebuild from a google, but given how long ago you posted this I didn't think it would happen. Looking forward to the update!
Sent from my GT-N7100 using Tapatalk
Please upload the new build
viulian said:
I will rebuild it in the weekend I think back in the days the file systems were only 32bit, and now a lot of phones have 64bit file systems ...
Click to expand...
Click to collapse
Hi
Please upload the new built binaries.
Thanks
Don't work with Oreo. Please make a update.
alright follow these steps and you good to go
mounting sd card via command prompt (via adb)
1) go to your's phone's file manager
2) create a folder named external_sd in /sdcard/ (you have to make this folder to mount sd card in /sdcard/ !!!
3) inject this command in cmd (adb)
Code:
su
mount -o bind /mnt/emmc /sdcard/external_sd
and done enjoy ......
{
"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"
}
mounting sd card via terminal (terminal file added for newbies )
first do step 1 and 2 above .
then inject this code in terminal
Code:
busybox mount --bind /mnt/emmc /mnt/sdcard/external_sd
after mounting sd card to /sdcard/external_sd
done ......... enjoy
great! gonna try it! this is one of my reasons for not being in aokp/aosp, 'cause i've linked to much files with directory bind from sdcard to external, so i would have to move them back to internal sd card to re-bind them sdcard- to emmc, let you know if it works, btw, do i prompt this commands with the phone on or in recovery? I'm a noob when it comes to adb
plotinus said:
great! gonna try it! this is one of my reasons for not being in aokp/aosp, 'cause i've linked to much files with directory bind from sdcard to external, so i would have to move them back to internal sd card to re-bind them sdcard- to emmc, let you know if it works, btw, do i prompt this commands with the phone on or in recovery? I'm a noob when it comes to adb
Click to expand...
Click to collapse
1) you can do it when you phone is on
2 ) you have to inject this code after every boot (due to nand suff )
3) just download terminal form my attachment and do it
BTW you can try this method to add this script to boot http://www.xda-developers.com/tag/samsung-vibrant/
apk_xiz said:
2 ) you have to inject this code after every boot (due to nand suff )
http://www.xda-developers.com/tag/samsung-vibrant/
Click to expand...
Click to collapse
I tried to bind emmc to external_sd weeks ago.
The problem is that I couldn't get the script working under init.d. Probably the kernel I was using was the problem who knows.
I used gscript and ran the script at boot with su permission.
Also I suggest you to use this http://forum.xda-developers.com/showthread.php?t=1410262
I made APP
I made an APP to do it on app launch.
h t t p s : / / play . google . com/store/apps/details?id=com.guatedroid.galaxysd
its free no adds, (still in beta) but works.
Hi,
I have a Asus Nexus 7 with the following characteristics:
Android Version: 6.0.1
Kernel Versión: 3.4.0-gae95f7e-dirty
Build Number: MOB30X
I installed NetHunter in it.
I have problems with the OTG conection. I tested 3 type of OTG cables and none of them work.
{
"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"
}
I tested with a ALFA AWUS036H and CROTA2000MW. In addition, I tested with different USB drives, formatted on FAT32 and NTFS.
Besides, I tested with a lot of OTG media manage apps, even Nexus Media Importer app.
Why is it happening this? How can I fix it?
Thank you.
UPDATED:
Recently I bought another OTG cable but in this case with the possibility of adding power supply, but it doesn't work either.
UPDATED 2:
I tried changing init.usb.rc fromde root directory of my Nexus 7. For that, I downloaded this file from the following source:
rootdir/init.usb.rc - platform/system/core - Git at Google
To copy this file to root directory of Nexus 7 and change its permissions, I used adb, but I needed to install "adb insecure" app in the device:
[2014.11.10][ROOT] adbd Insecure v2.00
adbd Insecure lets you run adbd in root mode if your device is rooted. (Note that if you are running a custom kernel, it is likely that it already implements this functionality) If you are running a stock (made by the phone manufacturer) kernel...
forum.xda-developers.com
I installed the app and I executed the following adb commands frommy computer:
Code:
adb shell mount -o rw,remount /
adb shell su -c "cp /sdcard/Download/init.usb.rc /"
adb shell su -c "chmod 646 /init.usb.rc"
adb shell mount -o ro,remount /
The file was copied and its permissions was changes succesfully but when I rebooted Nexus 7, the original file returned with the same permissions.
Hello Friends~!
I decided to play with some forks of android and chrome os in vmware this week, it was a lot of fun!
A problem I would like to create a solution for, is the inability for vmware tools to install natively.
Here is a toolset I prepared called "droidvmtools" DOWNLOAD
I was able to create this toolset based off of the prelGlibc25 Linux iso that came with VMWare, that is stored in Windows in this directory:
{
"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"
}
If you care about the extra steps added to "droidvmtools" I tried to document that process HERE
This exercise is performed using this Prebuilt copy of PrimeOS for VMWare DOWNLOAD
In theory, this method should work on other android images with root access, then likely fail as this example does at the end.
INSTALLATION:
Obtaining the perl binaries:
In termux run the command
Code:
pkg install perl
Then in Root Explorer, go to
Code:
/data/data/com.termux/files/usr/bin
and copy the perl binaries.
Now paste the binaries to:
Code:
/system/bin
To install the Toolset:
Extract droidvmtools and paste it to the root file system. The video goes over this step at 2:34 if you need reference. ( I also used my yt channel to easily dl the tools youtube.com/@jennn/about the tools are there if no usb)
Open a terminal emulator and type:
Code:
su
chmod 777 -R /droidvmtools
Then in Root Explorer, open droidvmtools, select all, copy, and then paste the contents to the root file system
You will be prompted with this message, select these options:
Now when you type:
Code:
perl run.pl
The tools are able to start installation but they crash at this part:
This is the part I am stuck on. I had never heard of recursion until this happened..
Here is a PASTEBIN dump of the code, maybe someone is able to look and see why this would be happening?
This thread is in preparation for a megathread I want to make. If you want to preview some of the images early see HERE
PLEASE NOTE:
I Understand that "Vmware Tools is not supported" in Linux let alone Android, blah blah. Let's try!
I also already know about and have tried every emulator in existence... So Please! Let's refrain from "just use x emulator", this is about problem solving.
I want to get virtual device with root, Google Apps and writable system. Optionally pass SafetyNet checks. Preferably, based on ARM image because I run it on mac m1.
I tried to create a virtual device using Android Studio Emulator.
[email protected]:rootAVD % emulator --version
INFO | Android emulator version 32.1.12.0 (build_id 9751036) (CL:N/A)
ERROR | No AVD specified. Use '@foo' or '-avd foo' to launch a virtual device named 'foo'
Create Virtual Device using Pixel 4 -> "Tiramisu (Ext. level 3) - Android 13.0 (Google Play)"
Spoiler: Screenshots
{
"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"
}
I start my Virtual Device with command `emulator -avd Pixel_4_API_33 -writable-system -no-snapshot-load`
I am able to successfully install Magisk root using rootAVD - https://github.com/newbit1/rootAVD
Spoiler: Magisk screenshot
But I'm not able to remount /system writable.
Usually, I do
adb root
adb remount
But after executing `adb root` - I get error `adbd cannot run as root in production builds`
Also tried:
adb shell
su
mount -o rw,remount /
But getting error `'/dev/block/dm-0' is read-only`
I tried adbd-Insecure from https://github.com/wuxianlin/android_tools/blob/master/adbd-Insecure-v2.00.apk
But getting error "Could not patch adbd !". Which is expected, since this module is from 2014...
Spoiler: Error screenshot
Also tried such apps like Root Browser and FX File Explorer with no luck.
I also tried to create devices based on images without Google Apps preinstalled (without Google Play label) on Android 12 and 11. But then I have trouble installing Magisk OpenGApps on it. https://sourceforge.net/projects/magiskgapps/
It seems to be installed successfully, but Chrome is constantly crashing, and Google Play says "This device isn't Play Protect certified"
Spoiler: Android 12.0 OpenGApps Error
My main goal is to get rooted, ARM Android Emulator with fresh Android version and writable /system. I know there is Genymotion with ARM translation and Android 9.0, but it is slow, Mac M1 is not supported and old Android.
Any help would be appreciated.
I just need help with pinning/saftynet! Java Android Magisk Burp Objection Root Emulator Easy (JAMBOREE)
https://github.com/freeload101/Java-Android-Magisk-Burp-Objection-Root-Emulator-Easy