I can get into console mode and mess about with some fedora commands but thats about it. Anyone feel free to take this further...
http://qole.org/files/fedora12-m5-v1a.img.ext2.lzma
Decompress with BitZipper and rename to fedora.img
http://www.mediafire.com/?9fw3vu463rs3vff fedboot
Place both files in sd card main directory and run in Terminal Emulator:
Code:
su
sh /sdcard/fedboot
After a few seconds [[email protected] root] should appear.
Code:
startx
is not a recognised command
Tried switching from Cli to GUI and changing runlevels using:
If you installed using a text login and wish to switch to a graphical login, follow this procedure.
If you are not already root, switch users to the root account:
su -
Provide the administrator password when prompted.
If you have not already done so, install the X Window System and a graphical desktop environment. For example, to install the GNOME desktop environment, use this command:
yum groupinstall "X Window System" "GNOME Desktop Environment"
To install the KDE desktop environment, use:
yum groupinstall "X Window System" KDE
To install the XFCE desktop environment, use:
yum groupinstall "X Window System" XFCE
This step may take some time as your Fedora system downloads and installs additional software. You may be asked to provide the installation media depending on your original installation source.
Run the following command to edit the /etc/inittab file:
vi /etc/inittab
Press the I key to enter insert mode.
Find the line that includes the text initdefault. Change the numeral 3 to 5.
Type :wq and press the Enter key to save the file and exit the vi text editor.
Reboot
Click to expand...
Click to collapse
But no luck after reboot.
Code:
su -c 'telinit 5'
Gives a communication refused message.
Hox do you make those versions? Where can I found a tutorial for learning how to make my versio of this (just for me).
Thanks
I have been using this guide on modmymobile.com:
7. Open the ROOT folder you extracted on your Desktop.
8. Double click on #1-Run this to start ROOT.
This will upload the files needed onto the phone. It might take a few minutes, on the video it was quick as I already had these files in the SDCard of my phone. Once it gets to the point that it says Adb Shell and has a $ with a blinking underscore (_) then we are ready to go to the phone.
9. Open up ConnectBot on the phone that you previously downloaded.
10. Click on where it says SSH and change it to Local. Type any name and press enter. Once you get the black screen with the $ you can type the following lines:
Code:
cd /data/local/tmp
./rageagainstthecage-arm5.bin
11. It will show a message, just wait till it shows
FORKED **** Childs.
**** is a number. Once that happens you can close down Connectbot.
12. Re-Open ConnectBot. If successful you should see a # meaning you have temporary root already.
13. Now type the following commands:
Code:
/data/local/tmp/install-root.sh
14. Nothing should happen, except getting another # sign, meaning that the script has finished.
15. Now go back to your computer and close down the command prompt window.
16. Click on the file called: #2-Run this to start RECOVERY
17. Wait a few seconds and then you will get the $ _
Type:
Code:
su
I can complete steps up to #17 type the code "su"
this is what I get back:
bionic/linker/linker.c:1581:ERROR: 2818 could not load "libbindr.so"
bionic/linker/linker.C:1641:ERROR: failed to link su
bionic/linker/linker.C:1734:ERROR: CANNOT LINK EXECUTABLE 'su"
$
What am I doing wrong or any suggestions on how I can easily root this phone will be appreciated.
Thanks!
[Guide][ARM now supported] Android development/debugging on ChromeOS - ADB & fastboot
What you need to know before we begin:
ChromeOS (Or Chromium OS if you installed it on a non-chromebook) is based on Unix, and you can access a terminal with button combinations. This part of the guide is easy, but if I can get apt-get working, that's where it gets really complex.
What you'll need
A computer running ChromeOS/Chromium OS
An internet connection on it, or the files on a USB drive (and you to copy them to Downloads)
A little Linux knowledge
Some patience
1.) Download the correct files for system:
ChromeOS/ChromiumOS on an x86 based PC
ChromeOS on an ARM based PC
2.) When the zip has downloaded, extract it so both the adb and fastboot files are in the Downloads folder
3.) It's now time to access the terminal mode. It might be a good idea to get this guide on a phone or some other device so you don't have to switch out at any time.
If you're using a chromebook or an official chromeOS build, you need to access developer mode. Note: this will wipe all your data for security reasons. Full info is here: Chromium Project: Developer mode
4.) Press Ctrl-Alt-F2 on your keyboard, and the whole screen will be a terminal. Read the info at the top, and then login
NOTE: If you're using Chromium OS vanilla builds, the username and password are as follows:
Code:
User: chronos
Pass: facepunch
5.) You now have a localhost terminal, with no root permissions.
6.) Run this code, to locate the location of your Downloads folder:
Code:
ls /home
7.) Mount the filesystem as follows:
Code:
mount -o remount,rw /
8.) Using the name other than "root" and "user", run these commands:
Code:
cp /home/<name>/user/Downloads/adb /sbin/adb
For example, the Chromium one would be:
Code:
cp /home/chronos/user/Downloads/adb /sbin/adb
Repeat for Fastboot (replace "adb" with "fastboot" without the quotes)
9.) Test that it has worked by running:
Code:
adb
It should result in adb working
10.) You're done, adb and fastboot should work. You might need to reboot in some cases for it to work fully
11.) For more stuff, like Java and ant, wait a while until I work out how to get apt-get installed from dpkg
Credits:
Thanks to KMyers for compiling Fastboot for ARM devices, thread here
Reserved
And again
Once more, just in case
Whenever I go to check my path I get this response:
"cat: /usr/local/bin:/usr/bin:/bin:/opt/bin:/home/chronos/user/Downloads/android-sdk-linux/platform-tools: no such file or directory"
Help?
awacker89 said:
Whenever I go to check my path I get this response:
"cat: /usr/local/bin:/usr/bin:/bin:/opt/bin:/home/chronos/user/Downloads/android-sdk-linux/platform-tools: no such file or directory"
Help?
Click to expand...
Click to collapse
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Quinny899 said:
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Click to expand...
Click to collapse
And so it seems! Now it appears that any adb command returns a "Permission denied" message. Ideas?
Update: Same response for fastboot commands.
awacker89 said:
And so it seems! Now it appears that any adb command returns a "Permission denied" message. Ideas?
Update: Same response for fastboot commands.
Click to expand...
Click to collapse
Try this:
Code:
cd /home/chronos/user/Downloads/android-sdk-linux/platform-tools
chmod 755 adb
chmod 755 fastboot
Then exit back to the login screen on the terminal, login again and try running adb
Quinny899 said:
Try this:
Code:
cd /home/chronos/user/Downloads/android-sdk-linux/platform-tools
chmod 755 adb
chmod 755 fastboot
Then exit back to the login screen on the terminal, login again and try running adb
Click to expand...
Click to collapse
Still no dice
I'm starting to lose hope. I just keep getting "permission denied."
I thought maybe trying this would do the trick but still no response.
Code:
sudo ./adb devices
[code]
P.S. Guess I should mention that running just adb returns command not found, so I've been using ./adb. Maybe I just don't know what the hell I'm doing but I just can't get it to work.
Hmmm. Well, The SDKx86 (87mb) that were in the instructions so, I downloaded the ADT (399mb) instead, just a hint.
Is there a specific branch that is required to be on in chromeos in order for terminal to act correctly? I never get any chance to login once i get into the "crosh" terminal.
Quinny899 said:
That is perfectly normal, every Linux based thing says no file or directory after the path to my knowledge
Sent from my GALAXY NEXUS using Tapatalk 4 (VIP)
Click to expand...
Click to collapse
Instead of doing
Code:
cat $PATH
you should do
Code:
echo $PATH
The cat command is trying to concatenate a file with the name of your full path, which obviously doesn't exist. echo tells you the value of the $PATH variable, which is what you're actually trying to do.
I was trying to get this to work on my Chromebook Samsung Series 5 550
Furst thing I noticed was the absence of an f2 key - tried a usb keyboard no joy
I assume what I am trying to launch is Shell which can only be accessed with a Chrome OS device in developer mode. I really want to get this working so I will try activating developer mode and report back.
Update:
So Developer Mode resets and wipes your device (doh!) back to Step 1
Update 2: (Dev Mode activated function key labelled as "->" works as f2 and launches shell successfully"
Has anyone got this working? I noticed that the folder coming out of the SDK zip is called "sdk" but all the commands listed in the guide use "android-sdk-linux"
I used "sdk" and just get the Permission Denied issue even after chmod on adb
Will this work on the Samsung Series 3 with the ARM processor?
imtoomuch said:
Will this work on the Samsung Series 3 with the ARM processor?
Click to expand...
Click to collapse
Supposedly pulling the adb binary from an android device (/system/bin/adb) and using that would work. Don't know about fastboot though
Sent from my Galaxy Nexus using Tapatalk 4 Beta
jambamkin said:
I was trying to get this to work on my Chromebook Samsung Series 5 550
Furst thing I noticed was the absence of an f2 key - tried a usb keyboard no joy
I assume what I am trying to launch is Shell which can only be accessed with a Chrome OS device in developer mode. I really want to get this working so I will try activating developer mode and report back.
Update:
So Developer Mode resets and wipes your device (doh!) back to Step 1
Update 2: (Dev Mode activated function key labelled as "->" works as f2 and launches shell successfully"
Has anyone got this working? I noticed that the folder coming out of the SDK zip is called "sdk" but all the commands listed in the guide use "android-sdk-linux"
I used "sdk" and just get the Permission Denied issue even after chmod on adb
Click to expand...
Click to collapse
I had the same problems. And just stopped trying about 2 days of trying to figure it out.
I was able to find a version of adb compiled for ARM but it was from an older version which made it a no go on my Nexus 4 (4.2.2 requires updated adb to work with the new security enhancements built in).
I tried it on my Series 5 550 chromebook. Can't seem to get it to work.
I do all the commands and it shows up in echo $PATH but then when i try adb anything it says permission denied. I do the chmod 755 and still permission denied.
i tried to exit back to the login and then the folder wasn't in the echo path anymore. adb not working either. I tried rebooting chromebook and it wasnt there either.
Would it be cheating to get it running with crouton? Because I did get that done.
Sent from my NookColor using xda premium
yeah i've been having the same issue with my samsung 5 series chromebook. "permission denied" and all that. But on the fun side, i learned if you want to really make your chromebook bug-out; type cat adb whilst in /platform-tools.
Have you just install Ubuntu on your Chromebook and your track-pad is aka broken or did not work. Now you have to suck it up and use a mouse or went back to ChromeOs because of this reason. I'm here to save your day. Listed below is step-by-step to fix your track-pad problem.
Track-pad Fix:
1. Open Terminal and gain access to root:
Sudo -s
2. Once you have login as a root user:
nano -w /etc/modules
or
sudo gedit /etc/modules
3. Add the following lines in this order:
loop
lp
rtc
i2c-i801
i2c-dev
chromeos-laptop
cyapa
4. Save (Ctrl-O)
5. Reboot
*Note if you are run Ubuntu 14.04 the track-pad should work once your system boots back up. If so skip to 10.
6. Log back in to the terminal as a root user:
Sudo -s
7. Download 64 bit kernel 3.11:
*Note if you need the 32 bit kernel I will have it listed below.
wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/linux-headers-3.11.0-031100_3.11.0-031100.201309021735_all.deb
wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/linux-headers-3.11.0-031100-generic_3.11.0-031100.201309021735_amd64.deb
wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/linux-image-3.11.0-031100-generic_3.11.0-031100.201309021735_amd64.deb
8. Now it’s time to install the kernel:
sudo dpkg -i linux-headers* linux-image*
9. Reboot
Ok track-pad should be working like a champ. If you have any problem on the steps above you can pm me.:highfive:
10. Now it’s time to adjust Some Synaptics Options Edit /usr/share/X11/xorg.conf.d/50-synaptics.conf by running:
sudo gedit /usr/share/X11/xorg.conf.d/50-synaptics.conf
Find the line
MatchDevicePath "/dev/input/event*"
and add these after
Option "FingerHigh" "10"
Option "FingerLow" "5"
Option "HorizHysteresis" "12"
Option "VertHysteresis" "12"
11. Save (Ctrl-O)
12. Reboot
<---Please hit the thanks button if this work for you. If not Please post below and i will do my best to help you.:good:
32 bit Kernel:
wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/linux-headers-3.11.0-031100_3.11.0-031100.201309021735_all.deb
wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/linux-headers-3.11.0-031100-generic_3.11.0-031100.201309021735_i386.deb
wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/linux-image-3.11.0-031100-generic_3.11.0-031100.201309021735_i386.deb
Awesome thanks
still doesn't work on ubuntu 14.04
I have Acer c720 with ubuntu 14.04 installed, but after executing 5) (reboot), touchpad still doesn't work.
I need help
I have an acer c7 running 14.04, i followed your instructions but i still cant get the track bad to work
i may be doing something wrong, can you please help
Acer c7 Ubuntu 14.04 Chromebook Touchpad Fix
Thank You SO MUCH !!
Excellent fix and much appreciated after having to rely solely on an external touchpad for almost a year now.
Wish I'd come across your post even sooner.
Well done and now I'm a even a new member of this site so the mods should be thanking you as well.
Cheers !
---------- Post added at 09:11 PM ---------- Previous post was at 08:44 PM ----------
mavingaw said:
I have an acer c7 running 14.04, i followed your instructions but i still cant get the track bad to work
i may be doing something wrong, can you please help
Click to expand...
Click to collapse
Hey man, I'm really just a newbie but I have an idea.
At the beginning of the main post ...
************************************************************************
Track-pad Fix:
1. Open Terminal and gain access to root:
Sudo -s
2. Once you have login as a root user:
nano -w /etc/modules
or
sudo gedit /etc/modules
...
*************************************************************************
Start by entering THIS COMMAND directly into the TERMINAL.
sudo gedit /etc/modules
You'll be prompted to enter your password, THEN ...
When you enter it into the terminal make sure a TEXT EDIT FILE appears in a separate window, not just the modules list showing in the terminal.
You should then be entering the next commands specified by the post - INTO THE TEXT FILE.
3. Add the following lines in this order:
loop
lp
rtc
i2c-i801
i2c-dev
chromeos-laptop
cyapa
4. Save (Ctrl-O)
Make sure you enter them INTO THE TEXT FILE, NOT the terminal directly, then save your commands in the TEXT FILE by hitting the SAVE BUTTON.
This is what was not quite clear to me the first time I tried it.
Again, I'm NO EXPERT but try this and see if it works.
Good luck.
davidxvision
Chromebook Unbuntu: Keys not working / Touch Pad
Meant to start new.
so I have tried multiple different Linux types. and I want to get rid of the most recent one. (Linux Mint) I can delete the partition but my bios says its still there. the next problem I am having is that when I boot into windows recovery mode and click the option "choose a device" I have 3 devices. one is ubuntu which boots into Linux mint. the 2 others are POP OS as one of them failed and the other did successfully install. I want to remove the ubuntu device from my bios and the three devices that are in windows recovery. I have Linux mint reinstalled to make sure that I start from square one. I also want to be able to do this without touching windows (reinstalling or anything like that).
You can try this tool to customise your boot menu:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt update
sudo apt install grub-customizer,
if it is grub bootloader that you're using.
MocnePifko said:
You can try this tool to customise your boot menu:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt update
sudo apt install grub-customizer,
if it is grub bootloader that you're using.
Click to expand...
Click to collapse
i dont want to keep linux. i want it off my entire system. everything linux gone along with the grub line so that it doesnt show up in the bios and windows recovery mode. but i dont know how to remove the grub line. just the linux partition.
You can try this but take note that you're doing it at your own risk and I'm not responsible for any damage you may cause.
1. Run a cmd.exe process with administrator privileges
2. Run diskpart
3. Type: list disk then sel disk X where X is the drive your boot files reside on
4. Type list vol to see all partitions (volumes) on the disk (the EFI volume will be formatted in FAT, others will be NTFS)
5. Select the EFI volume by typing: sel vol Y where Y is the SYSTEM volume (this is almost always the EFI partition)
6. For convenience, assign a drive letter by typing: assign letter=Z: where Z is a free (unused) drive letter
7. Type exit to leave disk part
Now, you can't actually acces this drive through file explorer but you can browse it's content from the ‘Browse’ button from Task Manager -> ‘Run New Task’ . Not sure if it'll let you delete anything but then you can use this:
1. In the elevated cmd prompt, type: Z: and hit enter, where Z was the drive letter you created.
2 .Type dir to list directories on this mounted EFI partition
If you are in the right place, you should see a directory called EFI directory
3. Type cd EFI and then dir to list the child directories inside EFI
4. Type rmdir /S mint to delete the mint boot directory and repeat with all the distros
Do NOT touch those: 'Boot' and 'Microsoft'.
Try Grub2Win or other option like that.