[Q] Need Help! With Ubuntu 13.04 on android - Android Q&A, Help & Troubleshooting

So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
btw i want to install unbuntu 13.10 i have everything downloaded(Terminal emulator, Complete linux installer, AndroidVNC, and the 3.72gb image file)
Thank's in advance,
GGgamer16

Answer
GGgamer16 said:
So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
btw i want to install unbuntu 13.10 i have everything downloaded(Terminal emulator, Complete linux installer, AndroidVNC, and the 3.72gb image file)
Thank's in advance,
GGgamer16
Click to expand...
Click to collapse
I don't own that phone. And so I cannot say much about it.
But my personal advice is to take backup of everything before you proceed with any changes to your phone.
I found the following links give you an idea:
http://android.stackexchange.com/questions/25396/how-to-find-out-if-my-devices-kernel-has-loop-device-support
http://ubuntuforums.org/showthread.php?t=2189642
http://ubuntuforums.org/showthread.php?t=2193699
Keep searching Google.

Related

[Q] Theme Installation Problem: "mount: Operation not permitted" (Fixed)

I apologise is a similiar issue has been posted on several occasions. I did try the search and couldn't get a solution for my trouble.
As the title saids I am trying to install the Dark10 Series theme but in the CMD box on my laptop I get the error
"mount: Operation not permitted"
Also:
"cannot open for write: Read-only file system"
I am guessing the above error has somthing to do with root. Although I am clueless to be brutally honest.
If someone can give me a simple helping hand I would appreciate it.
Not very knowledgable on the whole adb thing and commands etc.
Thanks in advance for any help!
Edit:
Model number: X10i
Firmware version: 1.6 (Duh! )
Baseband version: 1.1.31
Kernal Version: 2.6.29-rel
[email protected] #2
Build number: R2BA026
Fixed the problem, was somthing to do with the shell being locked or somthing. Got it working though!
Steps I took:
1. Add the java thing to Enviroment Variables (Computer>System properties>advanced settings>enviroment variables)
Path: )\QuickTime\QTSystem\;C:\android\tools\;
Then got a file that unlocks adb script (search forum)
And that was it sorry cant be of more help I zone out when i have a problem and concentrate on fixing it without really knowing what i am doing
U should post the solution and put fixed in the title to help others.
Z3X said:
I apologise is a similiar issue has been posted on several occasions. I did try the search and couldn't get a solution for my trouble.
As the title saids I am trying to install the Dark10 Series theme but in the CMD box on my laptop I get the error
"mount: Operation not permitted"
Also:
"cannot open for write: Read-only file system"
I am guessing the above error has somthing to do with root. Although I am clueless to be brutally honest.
If someone can give me a simple helping hand I would appreciate it.
Not very knowledgable on the whole adb thing and commands etc.
Thanks in advance for any help!
Edit:
Model number: X10i
Firmware version: 1.6 (Duh! )
Baseband version: 1.1.31
Kernal Version: 2.6.29-rel
[email protected] #2
Build number: R2BA026
Fixed the problem, was somthing to do with the shell being locked or somthing. Got it working though!
Click to expand...
Click to collapse
post detailed steps of solution
i always face the same problem
thx in advance
I had the same problem. What you need to do is open darker 10 launcher and go to option 7 from the list. Read the instructions carefully and at the prompts on the screen type in the code supplied.
From what I understand it adds Additional script to your phone that allows you to mount the image.
Make sure phone is in developer mode.
Sent from my X10i using XDA App
thx a lot it workd
Thanks for posting this topic,
I would've spent the whole night on this and probably still wouldn't be able to figure out anything!
I have similar problem with one of the themes.
UNSECURING THE SHELL
Type each of these at the given prompt and press enter after each line.
Dont type the prompt <$ or #> itself!
$ su <NOW CHECK HANDSET FOR A SU REQUEST>
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# chmod 4755 /system/bin/sh
# exit
$ exit
What should i type in $ su ? also if smb can, type all the lines correct,im not a programmer :/
026/rooted/x10i

[Q] Mount NFS / NFS4

Hi,
first of all I'm sorry that I couldn't put this question directly here:
[Kernel] - 2.6.36.4 - OC-VFPv3-d16_FP 1.4GHZ - Galaxy Tab 10.1 (9/13/11; 9.00PM EDT)
Since I'm a new member I'm not allowed to do so...
Question: Did anyone manage to mount a NFS Share on the Galaxy Tab 10.1? I'm not talking about a CIFS/Samba Share!
What I tried so far:
Installed the kernel above, loaded the following modules in the following order:
1. sunrpc.ko
2. auth_rpcgss.ko
3. lockd.ko
4. nfs_acl.ko
5. nfs.ko
When I try to mount my nfs share running on a Ubuntu 10.04 server with this command line:
mount -o nolock -t nfs <IP>:/<Path> /sdcard/<mountpoint>
I'm getting the following error message: Invalid argument
Is this a bug in the kernel/module. Am I doing something wrong?
Any help on this would be highly appreciated!

[Q] Help add xpad.ko

Hey everyone. After trying to connect my x360 controller to my S3 i9300 with cyanogen 10.2 without sucess, i started to look what is wrong. I found that the cyanogenmod doesnt have the file xpad.ko, that is the driver for x360 controller and need to instaled with terminal like that:
Code:
# insmod /mnt/sdcard/tmp/xpad.ko
but it returns an error... exec format error.
theres a forum that say to execute ff-memeless.ko before the xpad.ko
but it also returns an error... 'can't open /mnt/sdcard/tmp/ff-memeless.ko'
some say that must be an issue with kernel and ask for use the command uname -a in terminal to know what kernel is, my kernel is:
Code:
Linux localhost 3.0.64-CM-gd6f2f4a #1 SMP PREEMPT Mon Dec 2 21 : 12:34 PST 2013 armv71 GNU/Linux
anyone know how to proceed ?
the files i tryied to use are in attachment.
Thanks and sorry for my english... i know its very bad =X

[ROM]Samsung S3 Intl Sailfishos

Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attempting since monday tonight.
I'll explain more and I'll give more shots on working.
My issue now is to build the boot, recovery image to flash and boot it. The jolla sailfishos as a GUI operating system on Galaxy S3 I9300 model.
FIY : filename = sfa-i9300-ea-1.0.8.19-my1.tar.bz2
Instructions for chroot co,pilation on ubuntu amd64 x86_64 bit:
Code:
sudo mkdir -p /srv/mer/
mkdir -p $HOME/mer/
nano .bashrc
export $MER_ROOT=/srv/mer/
export $MER_ROOT=$HOME/mer/
ctrl +x to save and y
but type sudo apt-get install -y curl
for do the downloading file.
next do the following commands on terminal:
export $MER_ROOT=/srv/mer/
cd $HOME; curl -k -O https://img.merproject.org/images/mer-sdk/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
sudo mkdir -p $MER_ROOT/sdks/sdk ;
cd $MER_ROOT/sdks/sdk ;
sudo tar --numeric-owner -p -xjf $HOME/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
echo "export MER_ROOT=$MER_ROOT" >> ~/.bashrc
echo 'alias sdk=$MER_ROOT/sdks/sdk/mer-sdk-chroot' >> ~/.bashrc ; exec bash ;
echo 'PS1="MerSDK $PS1"' >> ~/.mersdk.profile ;
sdk
Now, do the following instructions:
$HOST>
nano $HOME/.hadk.env
export MER_ROOT="[/home/$user]"
export ANDROID_ROOT="$MER_ROOT/android/droid"
export VENDOR="[samsung]"
export DEVICE="[i9300]"
ctrl +x and y for save it.
nano $HOME/.mersdkubu.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
export PS1="HABUILD_SDK [\${DEVICE}] $PS1"
hadk
save it again
nano $HOME/.mersdk.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
hadk
now save this file.
Now in ctrl + alt + x, it will show a terminal:
type this:
sdk
type your password
hadk
TARBALL=ubuntu-quantal-android-rootfs.tar.bz2
curl -O http://img.merproject.org/images/mer-hybris/ubu/$TARBALL
UBUNTU_CHROOT=/parentroot/$MER_ROOT/sdks/ubuntu
sudo mkdir -p $UBUNTU_CHROOT
sudo tar --numeric-owner -xvjf $TARBALL -C $UBUNTU_CHROOT
hadk
ubu-chroot -r /parentroot/$MER_ROOT/sdks/ubuntu
exit
git config --global user.name "Your Name"
git config --global user.email "Your email"
back again for
hadk
cd $HOME
mkdir -p $HOME/mer/android/droid
repo init -u git://github.com/mer-hybris/android.git -b hybris-10.1
repo sync
after this, you will have HABUILD_SDK
DEVICE=i9300
export $DEVICE
source build/envsetup.sh
breakfast $DEVICE
now type
make hybris-hal
But now as a ota file for flashing on i9300, in this last 2 days in my laptop core2Duo Extreme I'm facing overheating.
So, everyone can test it.
Code:
A little change on mount fixups.
Go to the directory hybris/hybris-boot
nano mount-fixups on i9305| encore)
put the "i9305" | "encore" | "i9300")
Script for booting sailfishingos on an android terminal. This script is to mount the binds folders and for fixing for preventing the /dev/null issue when we all boot the chroot sailfishos.
name of the script : sailfishos.sh - made it on the /extsdCard/ folder.
1) nano /extSdCard/sailfishos.sh and copy the following code
2) ctrl +x to save it
3) bash sailfishos.sh
Code:
su
mount -o bind /dev /data/.stowaways/sailfishos/dev
mount -o bind /proc /data/.stowaways/sailfishos/proc
mount -o bind /sys/ /data/.stowaways/sailfishos/sys
chroot /data/.stowaways/sailfishos/ /bin/su -
echo "nameserver 8.8.8.8" > /etc/resolv.conf
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
See folders on it.
PS: I'll give more shots also more instructions very soon. Thanx.
Another PS: I'll give more news about Jolla sailfish os very soon.
But I need to tell this, I've got i9300 defconfig kernel for Jolla sailfishos very similar to defconfig i9305 kernel and I got it compiled with very success on hadk Ubuntu chroot on mine Ubuntu 14.04 LTS version.
astronfestmon said:
Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attemptinh since yesterday tonight.
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
sees folders on it.
Click to expand...
Click to collapse
Screenshots?
Sent from my SM-G900F using XDA Free mobile app
Fantastic... I'll give a try. Plz provide some more details, screenshots & new features from your currently running sailfish os. Thanx for sharing
i fed with adb commands & not able to flash
Uhm ... I gonna wait for this ...
Sent from my SM-G900F using XDA Free mobile app
how to install ?
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
astronfestmon said:
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
Click to expand...
Click to collapse
any update on this?
I followed the above procedure and I can see the Sailfish version and the files list from adb. What next?
EDIT: Just saw your PS in OP
In the end of the week probably I'll release the boot kernel working on.
astronfestmon said:
In the end of the week probably I'll release the boot kernel working on.
Click to expand...
Click to collapse
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
astronfestmon said:
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
Click to expand...
Click to collapse
It would be great if you could make it to boot.
I will try to compile the kernel with CONFIG_CMDLINE="console=tty0" . I'm hoping that would direct kernel panic message to the screen so we could idenfity what the problem is with booting hybris-boot.img
So... Any development?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
astronfestmon said:
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
Click to expand...
Click to collapse
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
redrum781 said:
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Click to expand...
Click to collapse
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
rusty88 said:
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
Click to expand...
Click to collapse
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
MaxAndroided said:
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
Click to expand...
Click to collapse
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
msri3here said:
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
Click to expand...
Click to collapse
yes @msri3here technically that is what i'm doing, its using RIL lib based on cm10.1.3 that was working fine before I flash sailfish, but on sailfish the log that RIL daemon dumps is really a mess and haven't figure out why is failing. One thing that I've notice is that RILD (one of its child process) creates the socket at /dev/socket/rild but it's killed afterwards, the sockets disappear and the process restarts all over again
Stracing RILD is not helping either as it seems that everything is Ok.
I'm trying to buy a new smartphone for day to day use so I can dedicate more time to debug on my i9300.
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
tried your rom but stuck on "samsung galaxy s 3 gt-i9300" screen nothing is happening plus if i touch the screen i get a response from the capacitive buttons but thats all

Chromebook Acer C720P getting Google Play Store with Chrome OS 65+ recovery from USB.

It is possible to get Google Play Store perfectly running on Acer CB C720P,
off the USB 3.0 port using a USB 3.0 bootable stick with the recovery rom for Acer Chromebook R11 - it needs adjustments, & a version of Chromium OS above 55 like https://www.dropbox.com/s/kebu46foi6quu96/Camd64OS_R55-8777.0-Special.7z?dl=0
(use WIndows Diskimager to map it to usb stick, then expand the data partition file system to use up all the disk)
A great how-to for this method & the chromefy method is in post 163 by Hnk1,
https://forum.xda-developers.com/showpost.php?p=78806350&postcount=163
Hnk1 said:
https://forum.xda-developers.com/ha...er-c720p-getting-google-t3805304/post78806350
Request : Can you put the link (one I mentioned above, post # 163 )in the first post mate ? So more people can install it on their CB and it will be easier to see. What you reckon?
Click to expand...
Click to collapse
Do not use this, latest cyan Acer C720P CB will not allow booting. Acer & Google teamed up to block this hack -
New recovery roms as per June 2018: https://www.dropbox.com/s/0lh7zamkntisdum/recovery2018_2.conf?dl=0
https://twitter.com/meNabster/status/1012024823885844488
https://twitter.com/inabster/status/1012029701119004673
Use this -
Recovery roms links as per May 2018 in this link: https://www.dropbox.com/s/zje8hlg7fmvp48d/recovery_2008.conf?dl=0
Up to date recovery roms are here:
https://dl.google.com/dl/edgedl/chromeos/recovery/recovery.conf
& adapting this script I hacked:
sudo apt-get install cgpt
# this is if you are doing it from a linux distro or via crouton, cgpt is available natively in the chronos shell...
image_file=chromeos_5841.98.0_link_recovery_stable-channel_mp-v4.bin # the rom you need is cyan for Acer Chromebook R11 (CB5-132T / C738T)
rootfs_start="`cgpt show -i 3 -n -b -q $image_file`"
rootfs_size="`cgpt show -i 3 -n -s -q $image_file`"
mkdir chrome_efi_mount
sudo mount /dev/sdb12 chrome_efi_mount -t vfat
mkdir chromium_efi_mount
sudo mount -ro loop,offset=$((`cgpt show -i 12 -n -b -q $image_file`*512)) $image_file chromium_efi_mount
sudo cp chromium_efi_mount/syslinux/vmlinuz.B chrome_efi_mount/syslinux/vmlinuz.B -f
sudo cp chromium_efi_mount/syslinux/vmlinuz.B chrome_efi_mount/syslinux/vmlinuz.A -f
sudo umount chrome_efi_mount
sudo umount chromium_efi_mount
sudo dd if=$image_file of=/dev/sdb3 bs=512 skip=$rootfs_start count=$rootfs_size
Sorry for now too lazy to write a full step by step how to...
Here are exhibits on my twitter feed
https://twitter.com/inabster/status/1007856882738978816
Hello,
The link to download the rom on dropbox was truncated - can you post it as code ?
Thanks.
guyome said:
Hello,
The link to download the rom on dropbox was truncated - can you post it as code ?
Thanks.
Click to expand...
Click to collapse
The link to recovery_2008.conf is in dropbox, I can access it, so should you.
look up for the rom link in the recovery_2008.conf file.
as I suspect you are lazy, here is the entry:
name=Acer Chromebook R11 (CB5-132T / C738T)
version=10323.62.0
desc=
channel=stable-channel
hwidmatch=^CYAN .*
hwid=
md5=27ae1147ec3984f698a7b7d17a19b676
sha1=e570292bb40155d9de96369e3c9f493369bbc7b5
zipfilesize=1100976852
file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
filesize=2271232512
url=https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin.zip
misc notes Google Play Store on USB stick Acer C720P
Some notes:
Kernel versions -
Official Kernel for Acer Chromebook C720P: (no Play Store)
Linux localhost 3.8.11 #1 SMP Sat Jun 16 19:11:45 PDT 2018 x86_64 Intel(R) Celeron(R) 2955U @ 1.40GHz GenuineIntel GNU/Linux
Official Kernel for Acer Chromebook R11 (CB5-132T / C738T) after Play Store update (which is already in the recovery rom):
Linux localhost 3.18.0-16509-gfd728222c3ad-dirty #1 SMP PREEMPT Tue Mar 20 23:42:10 PDT 2018 x86_64 Intel(R) Celeron(R) 2955U @ 1.40GHz GenuineIntel GNU/Linux
Official Kernel for Asus Chromebit CS10 as per latest update: (no Play Store yet, though planned)
Linux localhost 3.14.0 #1 SMP PREEMPT Fri Jun 15 04:13:16 PDT 2018 armv7l ARMv7 Processor rev 1 (v7l) Rockchip (Device Tree) GNU/Linux
To me Google is playing to force consumers to buy newer machines, it's a capitalist move, Play Store runs perfectly on Acer C720P, & Google Chrome OS is far more stable & snappy than with Kernel 3.8 they want to keep.
It will be cool if a good firmware coder could flash the firmware of C720P making it look like an Acer CB R11 - that will allow to install the R11 recovery rom onto the C720P SSD - so not having to go through putting it on a usb stick, though personally, it doesn't bother me.
This would be redundant if Google + Acer decide to officially support C720P - instead of being greedy.
https://twitter.com/inabster/status/1008526962439147520
Here are exhibits on my twitter feed
https://twitter.com/inabster/status/1007856882738978816
Hello,
Thank you for your answer, but I was speaking of this link : https://www.dropbox.com/s/kebu46foi6...pecial.7z?dl=0
Regards
---------- Post added at 10:24 AM ---------- Previous post was at 10:01 AM ----------
Ok, I found the recovery rom for Acer R11 thanks to your post - it was indeed in the conf file.
After, I put this Rom on a usb stick with Windows Diskimager - Ok
Then, I enter the recovery mode on the C720P by holding the Esc and Refresh keys then pressing the power button, and I restore the image on the USB key, so the Acer R11 image - OK
After, what do I do ? Restart the C720P ? Where should I use your script lines ?
Thanks !
guyome said:
Hello,
Thank you for your answer, but I was speaking of this link : https://www.dropbox.com/s/kebu46foi6...pecial.7z?dl=0
Regards
Click to expand...
Click to collapse
OK I regenerated the link, for some reason dropbox removed the share
https://www.dropbox.com/s/kebu46foi6quu96/Camd64OS_R55-8777.0-Special.7z?dl=0
this is what you need imaging to a usb stick.
then boot to the chromebook & apply the script from a shell, with the usb having chromium R55.
Here are instructions on how to do
step one - install chromium OS to the usb stick -
https://arnoldthebat.co.uk/wordpress/chromium-os/
step two - apply the script with assumed /dev/sdb being your usb device (with chromium OS in it, which you modify using the R11 Chrome OS image from Acer/Google.
Will this work on a standard C720 (not a touchscreen)
TheDevFreak said:
Will this work on a standard C720 (not a touchscreen)
Click to expand...
Click to collapse
Test it, & report
The odd bit:
Image recovery for C740 does not work, even though C720 & C740 are very similar.
Also using latest chromium OS 67 (arnoldthebat) will not work.
What I got working is Chrome OS R11 recovery with the arnoldthebat chromium OS rom I linked to above, others might work, but I posted what was successful, so I provided the links to them on my dropbox.
https://twitter.com/inabster/status/1009289981024702466
! @arnoldthebat latest special build Camd64OS_R67-10575.B-Special doesn't boot on Acer W700 hybrid tablet, Apple Macbook Air 2011, and Acer CB C720P (+only efi no mbr) -
your old build Camd64OS_R55-8777.0-Special works on all (efi+mbr) - I use it for this: https://forum.xda-developers.com/ha...er-c720p-getting-google-t3805304#post76864776
Thanks for the dropbox link
Ok, if I have understood everything :
- I install chromium OS on the USB key - the file is the one on Dropbox Camd64OS_R55-8777.0-Special.7z
- I copy the recovery image of the Acer R11 - link provided in the conf file - so chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
- I boot the chromebook, and plug the USB Key
- I launch a shell session (no need to be in developpper mode ?)
- I execute your script lines but should not the second line be "image_file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin" instead of "image_file=chromeos_5841.98.0_link_recovery_stable-channel_mp-v4.bin" , so the name of the downloaded recovery image ?
Thank you for your answers
Of course -
image_file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
guyome said:
Thanks for the dropbox link
Ok, if I have understood everything :
- I install chromium OS on the USB key - the file is the one on Dropbox Camd64OS_R55-8777.0-Special.7z
- I copy the recovery image of the Acer R11 - link provided in the conf file - so chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
- I boot the chromebook, and plug the USB Key
- I launch a shell session (no need to be in developpper mode ?)
- I execute your script lines but should not the second line be "image_file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin" instead of "image_file=chromeos_5841.98.0_link_recovery_stable-channel_mp-v4.bin" , so the name of the downloaded recovery image ?
Thank you for your answers
Click to expand...
Click to collapse
And no developpper mode needed to execute your script lines ? Thanks
And I have to boot on the usb stick with chromium ? With CTRL+U starting in developper mode ?
Wow I can't believe this! Can't wait to try on mine. I always thought it would be able to get android play store/apps on it! Waiting to see how it all works out and will try to install soon. Thanks so much to the OP for this, so stoked to see someone has managed to do this!
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
guyome said:
And I have to boot on the usb stick with chromium ? With CTRL+U starting in developper mode ?
Click to expand...
Click to collapse
How'd you get on installing this? Did you get it up and running?
I am trying to find how it works for the moment - I think I know almost all the steps to be done
guyome said:
I am trying to find how it works for the moment - I think I know almost all the steps to be done
Click to expand...
Click to collapse
Please let me know if/when successful. I believe I understand it in the main, but waiting to hear re your question whether we need the Chromebook in dev mode. Mine currently is as have Linux xfce on it as well as the stock dev chrome OS image. I assume though that as this installs on the USB as opposed to the internal SSD, that chances of breaking the Chromebook as pretty remote, as you can pull the USB and go back to the internal SSD...I await your attempt!
I think that you have to boot on the USB key containing Chromium OS and the image file you want to deploy, and then execute the command lines in a shell in order to install the image on the Chromebook. After, you should be able to remove the USB key and to boot on the SSD with the new deployed image (one of Acer R11)
You need to be in developer mode to boot from usb.
guyome said:
And no developpper mode needed to execute your script lines ? Thanks
Click to expand...
Click to collapse
No, ctrl-L
guyome said:
And I have to boot on the usb stick with chromium ? With CTRL+U starting in developper mode ?
Click to expand...
Click to collapse

Categories

Resources