• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

nabil2000

Senior Member
Sep 12, 2005
515
145
London
Acer Chromebook C720P best performance combo

Use
FydeOS 5.3.1 + chromefy Nocturne v71 + chromefy Cyan v70 / Caroline v70
to get
camera + camera migration + Android 7.1.1 + crostini

I got this combo gem on a USB when I want performance & camera within Android.

name=Pixel Slate
version=11151.33.0
desc=
channel=stable-channel
hwidmatch=^NOCTURNE .*
hwid=
md5=0683584ace7530849c286312b1c351c0
sha1=cd612a48d029070e354667fbf593591dc23add80
zipfilesize=1290752927
file=chromeos_11151.33.0_nocturne_recovery_stable-channel_mp.bin
filesize=2690670592
url=https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_11151.33.0_nocturne_recovery_stable-channel_mp.bin.zip

name=Acer Chromebook R11 (CB5-132T / C738T / CB3-132)
version=11021.81.0
desc=
channel=stable-channel
hwidmatch=^CYAN .*
hwid=
md5=777c0aaa9ce5f4cd556fdaff7c316a07
sha1=6f5f2afb95cf990a703a0d7145570193b1a0e83f
zipfilesize=1165786928
file=chromeos_11021.81.0_cyan_recovery_stable-channel_mp-v3.bin
filesize=2271240192
url=https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_11021.81.0_cyan_recovery_stable-channel_mp-v3.bin.zip

name=Samsung Chromebook Pro
version=11021.81.0
desc=
channel=stable-channel
hwidmatch=^CAROLINE .*
hwid=
md5=02451f916e74a97bfab659b91981a39e
sha1=1d237dc2c56e8ce9425beffa3e6c9a8c7d2ecc53
zipfilesize=1162465860
file=chromeos_11021.81.0_caroline_recovery_stable-channel_mp.bin
filesize=2271240192
url=https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_11021.81.0_caroline_recovery_stable-channel_mp.bin.zip

You might need to do

chromefy cyan v69 / caroline v69 first if above does not works - after powerwashing, then repeat the above steps :(

name=Acer Chromebook R11 (CB5-132T / C738T / CB3-132)
version=10895.78.0
desc=
channel=stable-channel
hwidmatch=^CYAN .*
hwid=
md5=871c14b044f14e810fd0b30388400d24
sha1=3a43a46cd5f2cf17d796cda7397aafce6fcb0666
zipfilesize=1147007254
file=chromeos_10895.78.0_cyan_recovery_stable-channel_mp-v3.bin
filesize=2271232512
url=https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_10895.78.0_cyan_recovery_stable-channel_mp-v3.bin.zip

name=Samsung Chromebook Pro
version=10895.78.0
desc=
channel=stable-channel
hwidmatch=^CAROLINE .*
hwid=
md5=78f1e99dd3bdf23c2bf9d141e8de95b7
sha1=786ce070afa58f73427f712ba6873ed1caea7667
zipfilesize=1148374771
file=chromeos_10895.78.0_caroline_recovery_stable-channel_mp.bin
filesize=2271232512
url=https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_10895.78.0_caroline_recovery_stable-channel_mp.bin.zip

Notes -
* this hack also works for flashed or non flashed firmware Chromebooks (with FydeOS 5.3.1)...
* using post 1 method to keep original kernel also works but only with ATB 55 if not flashed...
* flashing the firmware needs to be done properly, so always backup the firmware when prompted...
* flashing the firmware is a great idea, it makes the Chromebook more versatile...
* one can use ATB v72+ & FydeOS 6+ on the flashed firmware Chromebook, so more ROMs to play with...
* & using post 1 method on ATB v72 gives a fully functional with original firmware Chromebook...

Disclaimer -
I have only Acer C720P so for other Chromebooks, mileage vary...

Extra Notes -
* above hack used to yield camera migration for Acer Iconia W700, not anymore - which made me suspect as I posted earlier, that camera gets upgraded in the background by googledevs irrespective of the recovery ROMs used, & they seem to have crippled it so it cannot use camera migration on non Chromebooks.

* from my #Twitter feeds
https://twitter.com/inabster/status/1071703959746854912
Chrome OS R70 on 2014 Chromebook C720P using @Chromefy
script from USB & arguments: chromeos_11021.81.0_eve_recovery_stable-channel & chromeos_10895.78.0_caroline_recovery_stable-channel_mp - + great news from @arnoldthebat
- Chromium OS R71 release imminent via @xdadevelopers
maybe this could still yield camera migration for Acer Iconia W700 (after chromefy nocturne)

* Getting camera migration working on Acer Iconia W700 still possible - needs FydeOS 5.3.1 - Nocturne v71 - cyan v70 - caroline v69 - boring, but could not find any other way...
2 USB's each with FydeOS 5.3.1 - one to boot from, 2nd target to chromefy to...
Use older version of chromefy -
1. chromefy FydeOS 5.3.1 with Nocturne - answer no twice when prompted
2. chromefy result FydeOS 5.3.1 Nocturne with chromefy cyan v70 caroline v69
answer yes to first prompt, & no to second prompt -
- you now get a solid Chrome OS v70 with camera migration, etc (of course no google assistant with cyan).
So far unable to replicate it with eve.

works with eve v70 too... as above but amend as follows -
* Getting camera migration working on Acer Iconia W700 still possible - needs ATB v72 - Nocturne v71 - eve v70 - caroline v69 - includes Google Assistant too ;)

works with eve v71 too... as above but amend as follows -
use 2 USB's with ATB v72
1. chromefy ATB v72 with Nocturne - answer no twice when prompted
2. chromefy result ATB v72 Nocturne with chromefy eve v71 caroline v69
answer yes to first prompt & no to second prompt
3. boot the result - will not allow to login (OK)
4. chromefy result with chromefy eve v71 swtpm.tar
answer yes to first prompt & no to second prompt

some interesting outcomes with eve 70 / 71 on Acer Iconia W700
- in eve 70, penguin crostini kernel is 4.14.67 (which is also FydeOS 5.3.1 kernel)

- in eve 71, penguin crostini kernel is 4.14.74 (ATB v72 kernel is 4.14.83)
Linux penguin 4.14.74-07776-gac52e5f750c8 #1 SMP PREEMPT Thu Dec 6 17:36:39 PST 2018 x86_64 GNU/Linux

in eve 70, camera migration is in native camera, webstore app works lauched from webstore...

in eve 71, camera migration is accessed through third party Android apps, native camera webstore app is the default.

eve 72 uses Android Pie which I have not been able to get to work with camera migration in Acer Iconia W700 (neither with ATB v72 & FydeOS 6.0)

In both error message when doing
$ sudo apt-get update
W: GPG error: https://storage.googleapis.com/cros-packages/71 stretch Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <[email protected]>
W: The repository 'https://storage.googleapis.com/cros-packages/71 stretch Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

cyan v71 gives camera migration

cyan v72 does not give camera migration

cyan v73 gives camera migration (which is great as it's latest so far)

All releases for strago platforms, like cyan have Android Nougat 7.1.1 - I don't think they will recieve Android Pie (their original Linux Kernel is 3.18)

new releases though might remove it again :(
 
Last edited:
  • Like
Reactions: Hnk1 and Ricardoch

Hnk1

Senior Member
Dec 23, 2012
1,463
1,546
Newcastle Upon Tyne
OnePlus 5
Moto G6
i need help with this, i don't know how to even pull this off, someone help please


https://forum.xda-developers.com/ha...er-c720p-getting-google-t3805304/post78806350

There is already a guide with step by step instructions.
Good luck

@nabil2000

I think someone pressed space-bar on my Chromebook at startup screen and boom. Everything is gone. Can we change the key somehow or maybe change the startup screen ?

I think I'll try android 9 with Fydeos and report back.

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?
 
Last edited:
  • Like
Reactions: nabil2000

nabil2000

Senior Member
Sep 12, 2005
515
145
London
https://forum.xda-developers.com/ha...er-c720p-getting-google-t3805304/post78806350

There is already a guide with step by step instructions.
Good luck

@nabil2000

I think someone pressed space-bar on my Chromebook at startup screen and boom. Everything is gone. Can we change the key somehow or maybe change the startup screen ?

I think I'll try android 9 with Fydeos and report back.

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?

OK - I will link up to it...

Some people have issues about how to put their CB into developer mode, they need to google & learn ;)
 
  • Like
Reactions: Hnk1

Hnk1

Senior Member
Dec 23, 2012
1,463
1,546
Newcastle Upon Tyne
OnePlus 5
Moto G6
OK - I will link up to it...

Some people have issues about how to put their CB into developer mode, they need to google & learn ;)

can you link me to fydeos 5.3.1 ?

I have been trying for hours without any success.

I have found a page and it needs baidu account, which I do have but the speed is like 20-30kb per second which translates to 20 hours :/

can you upload or link me to a download site please ?
 

nabil2000

Senior Member
Sep 12, 2005
515
145
London
can you link me to fydeos 5.3.1 ?

I have been trying for hours without any success.

I have found a page and it needs baidu account, which I do have but the speed is like 20-30kb per second which translates to 20 hours :/

can you upload or link me to a download site please ?

OK, I will soon from an alternative Google Drive account - my official one is full...

Here is the link - FydeOS 5.3.1 - FydeOS_PC_v5.31-stable.img.xz
https://drive.google.com/open?id=1SCJB6mgPNeAISiRUngw_AJext9j0UBeU
 
Last edited:
  • Like
Reactions: Ricardoch and Hnk1

nabil2000

Senior Member
Sep 12, 2005
515
145
London
Camera migration using ATB v72 on Acer Iconia W700

Camera migration achieved following this cooking procedure (might be shortened if cracked further) -

1. 2 ATB v72 USB's.
2. Boot from one ATB v72.
3. Use target ATB v72.
4. chromefy2 with Nocturne - answer no twice when prompted.
5. chromefy result with cyan v70 / caroline v69 - answer yes, then no when prompted.
5a. powerwash - sudo umount /dev/sdc1 - sudo mkfs.ext4 /dev/sdc1
6. chromefy new result with cyan v70 / swtpm.tar - answer yes, then no when prompted.

If you wish to try higher versions of cyan, keep chromefying like
7. chromefy new result with cyan v71 / swtpm.tar - answer yes, then no when prompted.
8. chromefy new result with cyan v72 / swtpm.tar - answer yes, then no when prompted.
9. chromefy new result with cyan v73/ swtpm.tar- answer yes, then no when prompted.
etc

Same method might also be used successfully with eve v70 & eve v71
eve v72 will not work as using Android Pie (9.0)

Usefulness, you get a higher kernel as ATB v72 is 4.14.83 (as opposed to FydeOS 5.3.1 which is kernel 4.14.67)...

Note - you use swtpm.tar as second chromefy argument because ATB v72 has swtpm proxy installed...

Might work with FydeOS v6.0/v6.1 - welcome to test & report - too lazy to do so ;)

Not science, just cooking without precise knowledge of mechanisms involved, welcome to make a script if you figure out how it works :) ;)

Results of tests

6. cyan v70 on ATB v72 - OK overall.
7. cyan v71 on ATB v72 - Android very unstable.
8. cyan v72 on ATB v72 - Android takes ages to build / activate, seems OK after.
9. cyan v73 on ATB v72 - OK overall.
10. cyan v74 on ATB v72 - TBD
 
Last edited:
  • Like
Reactions: Ricardoch

nabil2000

Senior Member
Sep 12, 2005
515
145
London
Acer Iconia W700 eve v70 & v71 camera migration

I just got camera migration with eve v70 using similar cooking tricks as above - don't know if it will still hold for eve v71....

1. ATB v72 USB X2...
2. chromefy target nocturne v71 / swtpm.tar - answer no twice.
3. chromefy result eve v70 / caroline v69 - answer yes then no.
4. boot from result - start Android, test camera.

NB. do this using Acer Iconia W700 to allow for camera ID to be properly setup.

eve 71 result -
chromefy eve 71 / caroline 69 gives GUI but cannot login...
chromefy eve 71 / swtpm.tar allows login in...
checking camera...
- webstore camera works
- Android migration camera works :)
cool - that's the best eve one can get working in Acer Iconia W700 with Android 7.1.1 camera migration & google assistant... seems stable :)
 
Last edited:

nabil2000

Senior Member
Sep 12, 2005
515
145
London
Camera configuration latest

A new config file appeared in /etc/camera
$ ls /etc/camera
camera_characteristics.conf media_profiles.xml

media_profiles.xml

$ nano /etc/camera/media_profiles.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright 2017 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE MediaSettings [
<!ELEMENT MediaSettings (CamcorderProfiles,
EncoderOutputFileFormat+,
VideoEncoderCap+,
AudioEncoderCap+,
VideoDecoderCap,
AudioDecoderCap)>
<!ELEMENT CamcorderProfiles (EncoderProfile+, ImageEncoding+, ImageDecoding, Camera)>
<!ELEMENT EncoderProfile (Video, Audio)>

It will control different aspects of camera operation from within Chrome OS.
 

nabil2000

Senior Member
Sep 12, 2005
515
145
London
eve 73 - Acer Iconia W700 Camera Migration

I finally managed to get Android camera migration on Acer Iconia W700 with chromefied eve 73 -

cannot trace back exactly how I managed this, the end result is there - I just fooled around with several chromefy's,

will post the steps I took here -

retracing my steps log (kind of) -

Take the successful eve 71 usb in post #212 above
& do successively

1. sudo bash chromefy2.sh /dev/sdc3 chromeos_11316.165.0_eve_recovery_stable-channel_mp.bin chromeos_10895.78.0_caroline_recovery_stable-channel_mp.bin

2. sudo bash chromefy2.sh /dev/sdc3 chromeos_11647.104.3_eve_recovery_stable-channel_mp.bin chromeos_10895.78.0_caroline_recovery_stable-channel_mp.bin

3. sudo bash chromefy2.sh /dev/sdc3 chromeos_11647.154.0_eve_recovery_stable-channel_mp.bin chromeos_10895.78.0_caroline_recovery_stable-channel_mp.bin

4. sudo bash chromefy2.sh /dev/sdc3 chromeos_11647.154.0_eve_recovery_stable-channel_mp.bin swtpm.tar

You might need to powerwash too...

Welcome to find out how/why it works & design a script that does it with just the last step using pure ATB v72 only...
 
Last edited:
  • Like
Reactions: Ricardoch

nabil2000

Senior Member
Sep 12, 2005
515
145
London
crostini stuff

Latest crostini kernel is 4.19.16 -

for lolz I installed mplayer, mpv & gnome-mpv (all Linux video players)

they do load videos from crostini, but with no sound (this is using cyan & eve v73) -

of course video works great in crouton Linux distros... or in Android with VLC etc...

RFC - Any idea how to get sound working through crostini?

of course this is not needed as within Android or crouton with say Ubuntu bionic, sound is perfectly fine :)
just fooling around crostini ;)

OK got it, sound for crostini will only see the light of day on Chrome OS v74 :confounded:
 
Last edited:
  • Like
Reactions: Hnk1 and Ricardoch

Hnk1

Senior Member
Dec 23, 2012
1,463
1,546
Newcastle Upon Tyne
OnePlus 5
Moto G6
Use
FydeOS 5.3.1 + chromefy Nocturne v71 + chromefy Cyan v70 / Caroline v70
to get
camera + camera migration + Android 7.1.1 + crostini

Hi mate
I am unable to have a fully working camera migration after numerous tries.
I used different methods.
I copy all the files to the internal memory of my CB
Next i go to directory in downloads in terminal and then

sudo bash chromefy.sh Fyde531.img nocturne71.bin

I get a new image FydeNocture.img
Once this is done, I chromefy again without writing it to a USB using
sudo bash chromefy.sh FydeNocture.img cyan70.bin caroline70.bin

So i get a new chromefied image and this I write to a usb and boot with it.
However, camera migration is faulty

Using your method to have 2 usbs and one with Fydeos being booted from. Another which has fydenocturne written and powerwashed. is bootable but stuck at login. I understand this is fine as I need to chromefy again. However, if I try to write again
I get error that USB does not have enough space in sdc3.

I use this to clear
sudo umount /dev/sdc1
$ sudo mkfs.ext4 /dev/sdc1

sudo bash chromefy.sh /dev/sdc3 cyan.bin caroline.bin

Error not enough space

I can not seem to grasp the method by which chromefy twice. If you are kind enough to tell me a step by step method. I can have multiple chromefy without writing to usbs but not directly on a usb. Should I repartion the usb again ?
 
  • Like
Reactions: nabil2000

nabil2000

Senior Member
Sep 12, 2005
515
145
London
Hnk1 camera migration

For Acer CB C720P or Acer Iconia W700 -

important to let Android fully activates -

remove webstore camera app

disable Android camera app from settings

reinstall webstore camera app

check webstore camera app works

enable Android camera app from settings

download a few camera apps from Android Play Store, test...

Also for Acer CB C720P I no longer use the official ROM - I use MrChromebox option 3.

It is fiddly work, cooking, not science - eventually I got camera migration working using ATB v72.... with cyan 73 & eve 73.

NB - also make sure correct VendorID DeviceID is in camera settings in /etc/camera/camera_characteristics.conf
 
Last edited:
  • Like
Reactions: Hnk1

nabil2000

Senior Member
Sep 12, 2005
515
145
London
FydeOS 6.0 / 6.1 notes

To save you the grief

FydeOS 6.0 / 6.1 is crap for Acer Iconia W700 & Acer CB C720P (no WiFi drivers, no camera)

better use ATB v72...

Now if you insist on using FydeOS 6.x (with no camera)
you can copy over the kernel /dev/sdb12 syslinux/vmlinuz.A & kernel modules /lib/modules/4.14.83 of ATB v72 over FydeOS's -
it's pointless though as using ATB v72 directly is much better...
 
Last edited:
  • Like
Reactions: Hnk1

Hnk1

Senior Member
Dec 23, 2012
1,463
1,546
Newcastle Upon Tyne
OnePlus 5
Moto G6

I have done so much cooking that I am going to give up. Can't seem to get camera to work on android. I know it is no science but very frustrating.
I have also Mrchromebox 3rd option and still nothing worthy has come out of it. Last few days has been very frustrating.
I want to have least cooking with best results so I think i will give ATB72 with your instructions above a go.

However, by any chance do you have any img files which you have cooked with working camera migration. I am on non official software myself so I can play with anything now.

There has been some progress but no breakthrough.

So any working IMGs you have which I can write to my usb and then dd it to my hdd

By the way when i chromefy fyde531 with nocturne, i get this error in the end after i select n for Selinux enforcing.

sed: can't read /home/chronos/local/etc/camera/camera_characteristics.conf: No such file or directory

Can you tell me step by step how do you chromefy more than once on USBs?
On fyde531 chromified dd to hard disk , although I select USB as bootable device but it boots from HD regardless which chromefied version I am running from USB. However, on old builds it always detects the correct USB
 
Last edited:

nabil2000

Senior Member
Sep 12, 2005
515
145
London
ATB v72 is best for camera migration

I have done so much cooking that I am going to give up. Can't seem to get camera to work on android. I know it is no science but very frustrating.
I have also Mrchromebox 3rd option and still nothing worthy has come out of it. Last few days has been very frustrating.
I want to have least cooking with best results so I think i will give ATB72 with your instructions above a go.

However, by any chance do you have any img files which you have cooked with working camera migration. I am on non official software myself so I can play with anything now.

There has been some progress but no breakthrough.

So any working IMGs you have which I can write to my usb and then dd it to my hdd

By the way when i chromefy fyde531 with nocturne, i get this error in the end after i select n for Selinux enforcing.



Can you tell me step by step how do you chromefy more than once on USBs?
On fyde531 chromified dd to hard disk , although I select USB as bootable device but it boots from HD regardless which chromefied version I am running from USB. However, on old builds it always detects the correct USB

Yes ATB v72 is best for camera migration -

I can't remember if I ever achieved camera migration with FydeOS 5.3..1

Also for disk space issues you need to increase the size of /dev/sdx3 to around 4GB -
on ATB v72, I just format /dev/sdx5 to ext4 -
resize it to smallest size (100MB I think) -
then reformat it as erased/unformatted,
then resize /dev/sdx3 to take up that space (so gets you 3.9 GB which is enough)

EFI booting, you need to boot from file, & choose the correct file, usually the last entry at the bottom of the list in Chromebox efi boot from file menus.

The file camera_characteristics.conf is not present in nocturne, so the error.

You just keep chromefying the same way, so you need all the files in one folder with the chromefy script.

I can try & provide my /dev/sdx3 of FydeOS 5.3.1 - I need to compress its image big to make it easier to upload - it has webstore camera working, & does boot the modded Acer C720P - maybe you can get it to achieve camera migration after imaging it (you will need to adjust the size as bigger on your disk)
 
Last edited:
  • Like
Reactions: Hnk1

Hnk1

Senior Member
Dec 23, 2012
1,463
1,546
Newcastle Upon Tyne
OnePlus 5
Moto G6
Yes ATB v72 is best for camera migration -

I can't remember if I ever achieved camera migration with FydeOS 5.3..1

Thank you so much mate for your explanation, time and efforts. Highly appreciated!

I think rather than trying for FydeOS5.3.1, I would rather like to have ATB v72 chromefied IMG as it will have everything working. I am currently at the point where I am happy to have everything working and follow something which has already being known to work. So if you have ATB v72 with camera migration working , if you can share the chromefied IMG , that be great. I shall highly appreciate it. Cooking is a very frustrating business as I had some dead usbs along the way and I do not want to sacrifice more on my quest! Yesterday another USB died on me and the total has exceeded 5 now. I think the most frustrating part is the amount of time you are spending on it and in the end you do not get the desired results.

Cooking just messes up the partition tables on your USBs and you can not format it in windows , linux or chromebook or even by using professional programs. Do you know of any method to bring them back to life ? I have few lying around which are detected and show correct partition size and everything, but you can not copy anything to them or format them. Cheers again mate!

UPDATE
Okay so I have a breakthrough with FydeOS 6.1 with google play, linux, camera migration and google assistant all working.

I chromefied using latest chromefy.sh (2.1)
Steps
I copied everything to my chromebook / downloads
Fyde6.1 noturne74 eve73 caroline73

In terminal
shell
cd home/chronos/user/Downloads where D is case sensitive
sudo bash chromefy.sh Fyde61.img nocturne74.bin
answer no for selinux enforcing

Chromefy again the end image with eve and caroline
sudo bash chromefy.sh Fyde61.img eve73.bin caroline73.bin
answer no for selinux enforcing

Next step, copy the Fyd61.img to a windows / linux and write it on a USB using rufus etc.
Boot with the USB.
Repartition ssd to correct size if you are planning to dd it to your hard drive!

So I think I am happy for now to have everything working and I suppose enough cooking for now until I newer builds are released!
@nabil2000
thanks a ton mate. No need to upload any IMG.
Also the top row keys are similar to that of Pixelbook!
Instead of looking for what files are responsible for each key, I simply rearranged the keyboard by taking off the keys!
 

Attachments

  • Keyboard.jpg
    Keyboard.jpg
    247 KB · Views: 214
Last edited:
  • Like
Reactions: nabil2000

nabil2000

Senior Member
Sep 12, 2005
515
145
London
camera migration with FydeOS 5.3.1 with cyan 73 / caroline 73.



Thank you so much mate for your explanation, time and efforts. Highly appreciated!

I think rather than trying for FydeOS5.3.1, I would rather like to have ATB v72 chromefied IMG as it will have everything working. I am currently at the point where I am happy to have everything working and follow something which has already being known to work. So if you have ATB v72 with camera migration working , if you can share the chromefied IMG , that be great. I shall highly appreciate it. Cooking is a very frustrating business as I had some dead usbs along the way and I do not want to sacrifice more on my quest! Yesterday another USB died on me and the total has exceeded 5 now. I think the most frustrating part is the amount of time you are spending on it and in the end you do not get the desired results.

Cooking just messes up the partition tables on your USBs and you can not format it in windows , linux or chromebook or even by using professional programs. Do you know of any method to bring them back to life ? I have few lying around which are detected and show correct partition size and everything, but you can not copy anything to them or format them. Cheers again mate!

UPDATE
Okay so I have a breakthrough with FydeOS 6.1 with google play, linux, camera migration and google assistant all working.

I chromefied using latest chromefy.sh (2.1)
Steps
I copied everything to my chromebook / downloads
Fyde6.1 noturne74 eve73 caroline73

In terminal
shell
cd home/chronos/user/Downloads where D is case sensitive
sudo bash chromefy.sh Fyde61.img nocturne74.bin
answer no for selinux enforcing

Chromefy again the end image with eve and caroline
sudo bash chromefy.sh Fyde61.img eve73.bin caroline73.bin
answer no for selinux enforcing

Next step, copy the Fyd61.img to a windows / linux and write it on a USB using rufus etc.
Boot with the USB.
Repartition ssd to correct size if you are planning to dd it to your hard drive!

So I think I am happy for now to have everything working and I suppose enough cooking for now until I newer builds are released!
@nabil2000
thanks a ton mate. No need to upload any IMG.
Also the top row keys are similar to that of Pixelbook!
Instead of looking for what files are responsible for each key, I simply rearranged the keyboard by taking off the keys!

Great job! I can try your advice one day with FydeOS 6.1 - did you get WiFi too, I tried but there was no WiFi for me even though it's Acer C720P...
(maybe because I did not boot to FydeOS 6.1 first before chromefying?, i just chromefied after imaging)

Also, just for lolz I tested with FydeOS 5.3.1 & I did manage to get camera migration & everything else working using an old USB install I had for Intel Compute Stick, so it is possible...
in this case it was FydeOS 5.3.1 with cyan 73 / caroline 73 (& without resizing the /dev/sdb3 partition)
 
Last edited:
  • Like
Reactions: Hnk1

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    SOME NOTES, BACKGROUND and BASICS
    I only have made instructions more user friendly and writing my experience to help the community as when I started, it took me more than a week to get everything sorted out although I am quite familiar with chromebook and android. I have put links within text (orange colour) to make links more user friendly and this guide neater.

    I have intended to write this guide so that not only C720P users can benefit from it but also for other devices which lack android / linux support on their chromeboks. However, non chromebook users can benefit from it as well by using the second method or following Project Croissant.

    There are essentially two methods/ hacks which work with C720P which I know. All credits to @nabil2000 and Project Croissant @alesimula to make it possible.


    The method one is intended for chromebooks only whereas method two is intended to work on all devices and you can check the link mentioned in the name below.

    The first method was found by @nabil2000. In essence this method simply takes your chromebook image/ custom chromeos as base and uses another chromebook bin to overwrite the files, adding new ones and making it possible for old devices without android or linux support to run google play store and crostini.

    The second method works beyond chromebooks and can run on to almost any device which can be booted via a USB. There is a separate thread for it Project Croissant Link. However, I will also mention in easy steps how I used chromefy (Project Croissant).

    PRE REQUISITES FOR BOTH METHODS
    1. Chromebook running developer mode
    Turn it off and then press Esc+ Refresh+Power
    Ctrl+D to disable chromeos verification off
    This will reset your device so backup everything in advance.

    2. Enabling USB boot + Legacy Boot
    In your Chromebook, Open crouton (ctrl+alt+T)
    Type
    Code:
    Shell 
    
    sudo crossystem dev_boot_usb=1 dev_boot_legacy=1
    
    sudo crossystem dev_boot_usb=1
    Restart and this will enable usb boot

    METHOD 1


    METHOD 1 BASICS USEFUL FOR OTHER CHROMEBOOK USERS
    So the trick is to choose an IMG which supports your device hardware drivers, that's why special builds on ATB are preferred than vanilla ones, while FydeOS 5.3.1 also has a very wide range of driver support.

    Once you have choosen the IMG file, look for a BIN file which has GOOGLE PLAY STORE SUPPORT if you are looking for that, or Google Play Store and Linux if you are looking for both.

    So if you have a Dell 3120 which does not have both, look for a device which has google play store and Crostini and is very similar to Dell 3120 and choose that BIN. However, strangely EVE CAROLINE have more success rate than other builds.
    Another thing note mentioning is that suppose if you are using IMG base as 70, even using BIN file of 71 and 69 yields some great results. However, i think that using all three of same version might yield best results (i had similar success with different versions but YMMV)

    You just need to follow the same method for other devices and you only need to change bin file names and location (sdb sdc etc) in the script after you have chosen IMG and BIN files as close as possible for your devices.

    C720 METHOD
    Requirements

    1. A custom IMG (fyde /ATB/ your chromebook as base)
    2. A software like rufus/windows image write to write that image to a usb
    3. 1 or 2 USBs , 16gb are enough and for older versions even 8 gb is enough
    4. BIN file
    [/LIST]

    STEPS
    1. Write IMG of your choice to a USB ( ATB version 55 Special ) Download CYAN.bin
    2. Place the cyan.bin in your chromebook download folder or you can use a separate usb. I prefer it in chromebook download folder
    Ctrl+Alt+ T and type
    Code:
    shell
    move to your download folder using crouton by
    Code:
    cd home/chronos/user/Downloads     where D is case sensitive
    once you are there, check if your file is in the same folder. This will show your bin file name.
    Code:
    ls

    3.Type the following commands[/B]

    if you rename your file, make sure to rename it in the following command line as well. In my case it is chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
    Also, make sure your name your usb sdb accordingly. The last command will take some time so be patient.

    Code:
    rootfs_start="`cgpt show -i 3 -n -b -q chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin`"
    
    rootfs_size="`cgpt show -i 3 -n -s -q chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin`"
    
    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 chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin`*512)) chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin 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=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin of=/dev/sdb3 bs=512 skip=$rootfs_start count=$rootfs_size

    Once everything is done, turn off your PC and use ctrl U to boot from the USB. If everything working and all drivers are working well for your device, you can think of even writing your USB to your SSD. Intructions are after method 2


    METHOD 2
    Requirements
    1.Fyde 5.3.img
    2.Caroline 71.bin
    3.Cyan 71.bin
    4.Chromefy.sh
    5.Chromebook running developer mode which has usb boot enabled + legacy. Instructions above
    6. A live Linux usb. I prefer Ubuntu . You can use 8gb usb for this.

    Remember , You'll need at least 16gb usb for this to work on C720. I suggest use a good usb like sandisk extreme 16gb. I had two Kingston D50 3.0 but after few writes on them, they were dead. (Were easily claimed under warranty)
    However, an old SanDisk 2.0 cruzer blade and 16gb Kingston s9 2.0 survived many writes. So I suggest that get a usb which is 3.0 as it'll take less time to write and boot.

    STEPS
    1.Put all of above in a usb (fyde Caroline Cyan and chromefy) and connect it to your c720 running developer mode.
    2. Ctrl+Alt+T and you will be into crouton
    3. Type the following
    Code:
    shell
    sudo  bash  chromefy.sh  Fyde53.img  cyan71.bin  caroline71.bin
    It will start a script and may take up to 30 minutes. Answer N when prompted in the end. This will write all changes from bin files to your IMG.

    4.Once it is done, copy Fyde53 (or whatever the name was of your IMG) from USB and using either RUFUS / WINDOWS IMAGE BURNER to burn it on a USB having at least 16gb space.
    5. Once you have it burnt on a USB , boot with it by pressing ctrl+u
    6. Check if everything is working out and check playstore and everything is to your liking before you can think of writing it to your SSD.

    You'll notice that in your USB from which you are booting, it doesn't show the actual size of the disk.
    I suggest ignore it for now and you may write chromeos from your usb to your SSD.

    WRITING TO YOUR SSD FROM A WORKING USB
    Make sure you boot from the usb while trying to do this.

    1. In crouton , ctrl alt+t, first see the partitions by
    Code:
    Shell
    Lsblk
    2. Check which is sda and which is sdb etc . Usually SSD is sda while usb could be sdb or sdc . Make sure you check well.
    3.Next , check if your SSD partition size is larger than your usb. This is important because if the size is not same or less than usb size, it may end with errors. In my case, my usb was 28.2gb and my SSD was 29.2Gb. in your case, if your SSD actual size is 15.0Gb , make sure your usb is no larger than 15. Even 14.9 is fine else it may end up with errors.
    4. Type this command which will start writing from usb to ssd
    Code:
    sudo dd if=/dev/sdb of=/dev/sda bs=4MB
    This will end in few minutes. Do NOT STOP IN THE MIDDLE OR SHUT DOWN your PC while this is happening because it can potentially damage your SSD and you may need to buy a new one.

    5.Once this is done, you be running chromeos using ctrl +D from SSD.

    Now the issue of internal memory needs to be sorted.

    I used different Linux flavours (latest even ) to resize ssd partitions. You just need to resize your state partition to maximum size by using Linux gparted live usb. However, there is a very good chance you'll end up loosing attributes making your SSD non bootable. Thus you'll need to add the attributes back to your partitions by booting chromeos from the usb. I suggest before doing this, make sure you try it on a USB to see you can make it bootable again after resizing.

    To check your attributes, after shell in Chromebook crouton or in Linux if cgpt is installed,

    Code:
    cgpt show -d /dev/sda
    where sda is your ssd
    Kern-A will have attributes before resizing your disk and after that, they may be lost so you'll need to add by

    Code:
    cgpt add -i 1 -S 1 -T 5 -P 10 -l KERN-A /dev/sda2
    Where sda2 refers to kernel A partition when using cgpt show command.

    Once done , recheck and see that successful has 1 attribute. If yes, your SSD can boot on its own


    Reboot to check

    @nygmam

    On mrchromebox, you can have everything working with android 9, camera migration, google assistant and linux
    Steps here
    3
    Hi mate
    I have been following your updates for a while. Thanks a lot mate for updates and all your work.

    I was wondering, what is the best combo till now for c720P in which i can use google play and crostini ?
    I have managed to run play store from usb from your guide and want to have it on hard drive. What are my options ?

    Thanks alot

    The best combo so far for Acer CB C720P is FydeOS 5.3 with cyan R70 caroline R70 - you get everything working... but no google assistant as this is R71, which is not yet released for cyan - Acer CB R11 (cyan) is closest match to C720P.

    I never install to internal SSD, but if I wanted to, I will boot to a Linux live USB (ubuntu 18.04) and do:
    $ sudo dd if=/dev/sdb of=/dev/sda bs=4M
    with /dev/sda the internal SSD & /dev/sdb the usb stick that holds a working Chrome OS I chromefied to.

    PS & NB - make sure you saved a recovery USB for your CB in case you bork it...
    Also if you did not know, this is how identify disk drives /dev/sdx (x=a,b,c...)
    $sudo fdisk -l
    3
    [CHROMEFY] Install official Chrome OS w/ Android & crostini for Acer Chromebook C720P

    1. You need two USB sticks with arnoldthebat Chromiusm OS enhanced R69 special build - get it here:
    https://arnoldthebat.co.uk/wordpress/chromiumos-special-builds/
    Using windisk imager, image the 2 sticks with the Chromium OS.
    One stick (with Chromium OS r69) will be to boot to from USB, the other stick (or SSD) will be to install Chrome OS to.

    N.B. The target install partition to hold Chrome OS ROOT-A /dev/sdc3 in my case, needs to be resized to at least 4GB (from 2 GB) -
    I used gparted gui from a Ubuntu livecd to resize it, expand it by 2048MB,
    this requires to rezise/move the /dev/sdc1 partition to the right by 2048MB, then resize /dev/sdc3 by expanding it by 2048MB.

    2. Boot up to the installation/configuration stick (from above) & download the chromefy.sh script from
    https://github.com/imperador/chromefy/releases/tag/v1.1
    to a folder in~/Downloads
    (specifics left to you)

    3. Download from Google repository these two recovery images
    fizz
    chromeos_10895.78.0_fizz_recovery_stable-channel_mp-v8.bin.zip
    caroline
    chromeos_10895.78.0_caroline_recovery_stable-channel_mp.bin.zip

    url addresses in first post of this thread...

    unzip both bin images to a folder in ~/Downloads
    (specifics left to you)

    4. Determine which is the location of the second USB stick you want as target (it has the second Chromium OS you imaged earlier)
    In my case it is /dev/sdc
    (/dev/sda is the internal, /dev/sdb is the Chromium OS you booted into & are working from)

    5. from a shell (ctlt-alt-t)
    $ shell
    $ cd ~/Downloads
    $ sudo df # (or sudo fdisk -l) to determine disk target
    $ sudo bash chromefy.sh /dev/sdc3 chromeos_10895.78.0_fizz_recovery_stable-channel_mp-v8.bin chromeos_10895.78.0_caroline_recovery_stable-channel_mp.bin

    that's it - it will do its thing, then ask you to reboot...
    remove the 1st usb stick, replace it with the 2nd usb stick, boot from it
    & you have, hopefully, a fully working Chrome OS with Linux Kernel 4.14, Android & crostini enabled...

    ack & greets, respect to anoldthebat & the chromefy team for making this possible...

    small caveat - you cannot root android in this setup as trying to make the system r/w wrecks the setup - welcome to solve this ;)

    NB & PS -
    It might be a good idea to use the combo cyan / caroline first in 5) to start with to make sure to avoid the blank screen described below for Acer Chromebook C720P...
    3
    Does Camd64OS_R55-8777.0-Special.7z already contain the chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin recovery, or do I still need to use the script in the original post to add it to sdb3? if not, why not to include it there in the first place? Or is this allows to inject recovery for different devices? What is in sdb3 of the 7z by default?

    ---------- Post added at 11:50 AM ---------- Previous post was at 11:01 AM ----------

    Today I got my first Chromebook - grabbed Acer C720 from eBay. I have 0 experience with Chrome os so had to figure few things out. Here is what I did to get google play store working on my c720 with the touchscreen. All the credit is to the nabil2000. I just collected all he said in one post. Please correct me if i got things wrong:
    1) Download and install win32diskimager-1.0.0-install.exe
    https://ayera.dl.sourceforge.net/project/win32diskimager/Archive/win32diskimager-1.0.0-install.exe

    2) Download extract and write to USB stick:
    Camd64OS_R55-8777.0-Special.7z
    https://www.dropbox.com/s/kebu46foi6quu96/Camd64OS_R55-8777.0-Special.7z?dl=0
    Use 7zip to extract IMG file from the downloaded file.
    Use Win32 Image Writer, then select the IMG file and select the USB device from the menu.
    Click on “Write”.

    3) Download and extract:
    chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin.zip
    https://dl.google.com/dl/edgedl/chr....0_cyan_recovery_stable-channel_mp-v3.bin.zip
    Also, @nabil2000 says you can use this one now:
    https://dl.google.com/dl/edgedl/chr....0_cyan_recovery_stable-channel_mp-v3.bin.zip

    4a) on ChromeOS
    press ctrl + alt + T and this brings you to what's called the crosh shell (command prompt or terminal) on a Chromebook. It'll now launch in a separate tab of the Chrome browser. Once the crosh shell has launched, you'll type “shell” to get to the root Linux shell from within your Chrome Browser

    CTRL-C to copy and CTRL-Shift-V to paste into the terminal

    4b) On Ubuntu machine:
    sudo apt-get install cgpt

    5) Create the script file:
    vi /tmp/myscript.sh
    # Get rid of the space in the first line in "stable" - no idea why xda forum injects a space there:
    image_file=chromeos_10323.62.0_cyan_recovery_stable-channel_mp-v3.bin
    or the line below ,depending on which one you got in step 3
    image_file=chromeos_10575.58.0_cyan_recovery_stable-channel_mp-v3.bin
    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

    6) Copy .bin file to the same folder as a script
    At this point I assume your recovery .bin file should be located in the same folder as the script
    cp /media/samba_share/Downloads/c720/*.bin .
    7) verify that your usb stick is indeed /dev/sdb using dmesg

    8) run the script - on ubuntu I used
    bash -x myscript.sh

    9) to boot from USB you probably need to follow steps 1&3 (not sure if you need step 2) from here http://www.fascinatingcaptain.com/blog/dual-boot-chrome-os-and-linux/
    from the shell:
    sudo crossystem dev_boot_usb=1 dev_boot_legacy=1
    sudo enable_dev_usb_boot

    my system already came shipped with developers mode on, so I have not had to do step 1

    10)Boot from USB stick
    Unmount and remove that flash drive and insert it into one of your Chromebooks USB ports. Boot the device and then, at the startup screen, press Ctrl+l to boot from the legacy BIOS. When prompted, hit Esc to enter the boot menu and select 1 for the USB drive

    At that point my Chromebook booted and I have google play store. Everything is pretty slow, but I think this is due to the old and slow USB stick. I will now buy a faster low profile one. IS my USB stick now my storage. I have very little storage (about 3GB) after booting from USB. How can I expand it if I have a 32 GB stick? Any recommendations on the USB stick to use?

    >There's a more recent ROM (v66) that can be used to load Google Chrome OS with Play Store on USB of hybrid tablet Acer Iconia W700
    Does this also apply to c720?
    2
    I need help. I have downloaded all of the dropbox files there are( the ones that you said to use, not the "Don't use this" ones.), and I don't know where to go from there. If you could email me, that would be better, but I'm okay if I just reply. Thanks in advance.

    take a look at my post (#47) on page 5 of this thread:
    https://forum.xda-developers.com/showpost.php?p=76996301&postcount=47