Hello,
I try to run Backtrak5 on my photon, every thing is ok, but when i have to browse to the sd card to make the boot with the terminal emulator i can cd the sdcard-ext,
i try to do this:
su
cd /sdcard/BT5 <--------(here is where i have the problem, cant access)
sh bootbt
export USER=root
vncpasswd
(make up any password)
i follow the instructions of this :
https://www.facebook.com/notes/opensourcegangster/how-to-run-backtrack-5-on-android/372480502807728
I will apreciate any help,
Thank´s a lot in advance.
cd /sdcard-ext/BT5
If you get a grey screen with an X when you VNC into it, try another ROM/Kernel combo. It's seems to be an Atrix/Photon thing.
Related
OK. Firstly, I have extensive experience with rooting moto droids and custom roms. That said I got cocky and didn't do enough homework trying to root my girls Eris and proceeded following the instructions in the "1.5 to rooted 2.1" thread. Step 1 went fine. I THINK I have root access. Anyway, like I was tired and couldn't get adb shell working so I left it at that with intent to finish today when I get home from work. Now she's telling me her icons are different and some are linking to different programs. Any ideas? Second, can someone point me in the direction of an adb shell how to, on my Droid I can just use terminal emulation and don't actually need a computer so I'm not too familiar with the process... sorry for the stupid newborn questions, don't pull the flame throwers out yet, thanks!
You can use terminal emulator, same thing for the most part as adb... I use that more then adb, faster then having to connect to a pc IMO.
I tried the terminal emulator and got adb not found or not allowed or some craziness like that. Does that mean I didn't root like I thought? Also, any clue about the icon s changing or linking to other apps like shes claiming? I'm going to try again when she gets home
In the terminal emulator you would not need to type adb.. adb is the program you would be using on a pc to talk to the phone... what is it that you are trying to type through adb or the terminal?
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part... im guessing i dont tye shell either, but i do type mount?
evilsway said:
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part...
Click to expand...
Click to collapse
Oh I see, for that yes you will need to get the SDK setup on your PC as per step 2... There is another thread that has a batch file that does all of this for you. You still need the SDK though.
see: http://forum.xda-developers.com/showthread.php?t=651669
ok, i have the sdk, i followed these instructions to the letter, and i still couldnt get it running last night, where in the sdk do i do this from or is it a command promp, or can i use the terminal emulator?
yes in the command prompt, typically adb.exe will be in your tools folder.
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
evilsway said:
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
Click to expand...
Click to collapse
yes, adb needs to be ran through the command prompt, if you click on it in windows it wont work... read the thread I linked you to, you wont need to run adb if you use that method, it does it all for you.
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
evilsway said:
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
Click to expand...
Click to collapse
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Renocat said:
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Click to expand...
Click to collapse
Yeah, once you do what he states and type...
cd androidsdk\android-sdk-windows\tools ... or where ever you have your SDK saved at on your computer ... you should be good to start running those scripts in the directions.
i searched and cant seem to find anything on my problem....i connect via mass storage mode , it detects the phone, but for some reason it doesnt let me access the files on the card....in other words ,i cant open them...any help ????
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
I am using it just fine on Ubuntu 10.4
I connect my phone and it is mounted automagically, and I can move the files from/to the phone.
Do you have se_linux installed?
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
thanks, I'll give this a try, let you guys know tomorrow...
Gotta say it works on Ubuntu better then does on Windows XP. You may have some permissions fudged somewhere. Do as the guys above said and let us know.
the3dman said:
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
Click to expand...
Click to collapse
this is not working for me
aksoutherland said:
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
Click to expand...
Click to collapse
nothign when i enter command
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
lqaddict said:
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
Click to expand...
Click to collapse
nothing again.....i have it set to ask on connection, then i swithced to mass storage mode....... what else should i do?
error message : "could not display" "the file location is not a folder "
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.
lqaddict said:
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.[/QUOTE]
thanks, I appreciate the help, I will give this a try in the morning
Click to expand...
Click to collapse
So ive been trying to figure out how to push files onto my eris for like a week now and im not smart enough with computer to so it. Ive downloaded the mac ADB, and have a 2.2 emulator up and running. But when i plug my phone in i cant ever find it using terminal. Im pretty sure its just cause im using the wrong commands so if anyone knows them for a mac that would be awesome. Any info would help me, Thanks.
No emulator is involved. Find the adb executable, and cmd+c to copy it. Fire up terminal and cmd+v to paste it, then type a space, then "push" (without the quotes), then a space, then drag the file you want to copy onto the terminal window, then type the location on your phone you plan on pushing to (like /system/app/ for example). And that's it! But you should do an adb remount before pushing. Again, to do a remount, paste the adb file into terminal or drag it in, then type a space, then "remount" (without the quotes).
It's been a while since I did the initial install steps, but the main difference to the commands is having to use a dot and a slash before the command "./" to specify the command you want to run is in the directory you're working in. Other than that, the PC steps are the same.
For example, my files are in a sub-directory under my user profile: /Users/<user_name>/Phone/android-sdk-mac_86/tools/ which can also be typed as ~/<user_name>/Phone/android-sdk-mac_86/tools/
So, in Finder, I go to that directory and double click the android file. That starts terminal which also starts the Android app. I go back to Terminal, press Command+T to open a new tab in Terminal (just so I won't have a ton of windows open), change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/ then I run the adb command typed as ./adb
So, to re-cap step by step:
My adb files are located in ~/<user_name>/Phone/android-sdk-mac_86/tools/
Make sure your phone is connected in USB debugging mode
In Finder, go to the above directory and double click android
Switch back to Terminal, press Command+T to open a new tab and change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/
Type: ./adb remount
Type ./adb shell (or whatever adb commands you want to run)
I probably installed adb/sdk wrong, but adb worked for many things then I got stuck>
adb push stock-hc-flyer-hboot_1.11.0006.nb0 / && adb shell dd if=/stock-hc-flyer-hboot_1.11.0006.nb0 of=/dev/block/mmcblk0p18
^STUCK, at this -- either it says nothing when i press enter, OR cannot find
...and yes Ive put the file in basically every directory
dinguznomad said:
I probably installed adb/sdk wrong, but adb worked for many things then I got stuck>
adb push stock-hc-flyer-hboot_1.11.0006.nb0 / && adb shell dd if=/stock-hc-flyer-hboot_1.11.0006.nb0 of=/dev/block/mmcblk0p18
^STUCK, at this -- either it says nothing when i press enter, OR cannot find
...and yes Ive put the file in basically every directory
Click to expand...
Click to collapse
You either need to tell adb where the file is, or put it in the same folder as the adb.executive.
I am trying to get my Wolfgang AT-AS53N rooted but no luck yet. It is a clone of the Spice MI-530. I have tried the root possibilities for this device but to no avail yet.
What can I do to see where it goes wrong?
I tried the following procedure and it did get me some progress:
http://forum.xda-developers.com/showthread.php?t=2168608
I installed the driver (ADB Interface) worked like a charm. But when I tried to root it using bin4ry's method I get stuck. When I go for option 2 and try root, I do the "Restore My Data" bit and it seems to work but the second time round when I do the "Restore My Data" bit the shell seems to hang. It does copy the Terminal program but that is about it.
I have tried this manual on another Wolfgang Phone (older model):
https://sites.google.com/site/mobileatas43d/rooting/rooting-english
And all goes well until:
To backup the original "su" on the mobile, type at the command prompt:
On Linux: "./adb shell mv system/xbin/su system/xbin/su.original" (without the quotes)
On Windows: "adb shell mv system/xbin/su system/xbin/su.original" (without the quotes)
The shell then tells me the path does not exist, with that it says "system" can't be found. Could this path be named different on my phone?
All help is appreciated.