Just a heads up for people using t800, t700 and t705
You can now use dualboot patcher to dual/tri boot your roms so no need to choose between tw and aosp or cm
I have tested and i have confirmed working triple boot
Tw 5.0.2 iromrom, 6.0 aosp dualboot and cm 12.1
I helped the dev get t800 device get supported and i hope everyone enjoys
Download the latest version to start multi booting
https://snapshots.noobdev.io/
This didn't work for me. Not sure what the deal is. I posted my log down below.
[D] Initialized installer for zip file: /mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip
[D] [Installer] Initialization stage
[E] /mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip: Failed to open archive: Failed to open '/mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip'
[E] Failed to read zip file
[D] [Installer] Chroot creation stage
[V] Creating chroot environment
[D] Running command: [ mount, /system ]
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running command: [ mount, /cache ]
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running command: [ mount, /data ]
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] [Installer] Environment set up stage
[E] /mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip: Failed to open archive: Failed to open '/mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip'
[E] Failed to extract all multiboot files
[V] Failed to extract multiboot files from zip
[D] [Installer] Cleanup stage
[V] Failed to flash zip file.
[V] Destroying chroot environment
[E] Failed to unmount /chroot/system: Invalid argument
[E] Failed to unmount /chroot/cache: Invalid argument
[E] Failed to unmount /chroot/data: Invalid argument
[E] Failed to unmount /chroot/mb/system.img: No such file or directory
[V] The log file was saved as MultiBoot.log on the internal storage.
[V] Finished cleanup
noxarcana said:
This didn't work for me. Not sure what the deal is. I posted my log down below.
[D] Initialized installer for zip file: /mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip
[D] [Installer] Initialization stage
[E] /mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip: Failed to open archive: Failed to open '/mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip'
[E] Failed to read zip file
[D] [Installer] Chroot creation stage
[V] Creating chroot environment
[D] Running command: [ mount, /system ]
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running command: [ mount, /cache ]
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] Running command: [ mount, /data ]
Usage: mount [-r] [-w] [-o options] [-t type] device directory
[D] [Installer] Environment set up stage
[E] /mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip: Failed to open archive: Failed to open '/mnt/shell/emulated/legacy/Download/cm-12.1-20151216-NIGHTLY-klimtwifi_dual.zip'
[E] Failed to extract all multiboot files
[V] Failed to extract multiboot files from zip
[D] [Installer] Cleanup stage
[V] Failed to flash zip file.
[V] Destroying chroot environment
[E] Failed to unmount /chroot/system: Invalid argument
[E] Failed to unmount /chroot/cache: Invalid argument
[E] Failed to unmount /chroot/data: Invalid argument
[E] Failed to unmount /chroot/mb/system.img: No such file or directory
[V] The log file was saved as MultiBoot.log on the internal storage.
[V] Finished cleanup
Click to expand...
Click to collapse
seems like a corrupt download or root problem
if redownloading and rerooting doesnt work
delete /cache/multirom
i have tested cm 12.1 so it definately works
What root method did you use? Everything else requiring root works fine for me. My copy of CM flashes fine in TWRP and I don't have a /cache/multirom folder to delete.
Sent from my SM-T700 using Tapatalk
noxarcana said:
What root method did you use? Everything else requiring root works fine for me. My copy of CM flashes fine in TWRP and I don't have a /cache/multirom folder to delete.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
what rom are you using
flash super su from chainfires website
My main rom is stock TW 5.0.2 and rooted (obviously).
Sent from my SM-T700 using Tapatalk
noxarcana said:
My main rom is stock TW 5.0.2 and rooted (obviously).
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
change directory
seems the app cannot access the zip
Can I have a full tutorial and keep all the data in the apps becuz last time in did not work I was on touchwiz dualbooted to cm12.1 but data of apps was lost help
rookie12 said:
Can I have a full tutorial and keep all the data in the apps becuz last time in did not work I was on touchwiz dualbooted to cm12.1 but data of apps was lost help
Click to expand...
Click to collapse
http://m.youtube.com/watch?v=CpegzNc4ZH0
See this video guide for note 4
Ashwin Prabhunerurkar said:
http://m.youtube.com/watch?v=CpegzNc4ZH0
See this video guide for note 4
Click to expand...
Click to collapse
Thats what i watch but data of apps will be erased
Cant wait for a Dummy proof instruction manual to come out for the 800. Been dying for a VM type tablet method to come out. I am just very newblish when it comes to this as its foreign to me so ill wait for this to grow into something that can be done more simpler for people like myself.
Great effort. !!
Question can I patch a AROMA zip file wanted to upgrade my primary TW IRON ROM
I dont know why people are having such great difficulty with this
Ok to answer a few questions
Patch the rom zip to dual or ext(if you want to install /system on external card)
Data partiton of all roms remains on internal storage
You can simple just patch the zip and then flash that rom from recovery without it wiping your original rom
Dont worry relax and experiment a little bit
From my side i can say this is very safe with very less probability of you ruining your primary rom
Ashwin Prabhunerurkar said:
I dont know why people are having such great difficulty with this
Ok to answer a few questions
Patch the rom zip to dual or ext(if you want to install /system on external card)
Data partiton of all roms remains on internal storage
You can simple just patch the zip and then flash that rom from recovery without it wiping your original rom
Dont worry relax and experiment a little bit
From my side i can say this is very safe with very less probability of you ruining your primary rom
Click to expand...
Click to collapse
Probably because until now no one said we could flash the patched rom in recovery. I've been under the impression that it all had to be done within the app.
Sent from my SM-T700 using Tapatalk
noxarcana said:
Probably because until now no one said we could flash the patched rom in recovery. I've been under the impression that it all had to be done within the app.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
just patch all the zips and flash via twrp/cwm
Hope this helps
anybody tried it on t805??? or is there any alternative which works on t805??? plz reply!
Can this be used with the T705 too?
I helped the dev to add support for the T705. Anyone here who wants support for the T805 dm me.
Gesendet von meinem SM-T705 mit Tapatalk
haimann95 said:
I helped the dev to add support for the T705. Anyone here who wants support for the T805 dm me.
Gesendet von meinem SM-T705 mit Tapatalk
Click to expand...
Click to collapse
i have forwaded to the developer hope he adds soon for you guys
Ashwin Prabhunerurkar said:
i have forwaded to the developer hope he adds soon for you guys
Click to expand...
Click to collapse
The T705 is supported now, the only device is the T805. I have a T705, but anyone who has a T805 can direct message me here on Xda and we can help the dev to add support for the T805 too.
Gesendet von meinem SM-T705 mit Tapatalk
Related
Original thread (Thanks mercianary):
http://forum.xda-developers.com/showthread.php?t=744236
Instructions
Here is a direct link to zipped .img file with deboot file both to be placed onto on root of SD card
http://www.megaupload.com/?d=7MON3O0J
Ingredients
debian.img + deboot (to be placed on the root of your SD card)
Better Terminal Emulator (or other terminal emulator) + AndroidVNC (or other VNC client) from the market
To automate one click startup process via Better Terminal Emulator:
Preferences>Initial command:
Code:
export PATH=/data/local/bin:$PATH:.
su
sh /sdcard/deboot
Or type this for each new session in any terminal emulator:
Code:
su
sh /sdcard/deboot
You should get a blank screen showing "localhost:/#" after a couple of seconds.
Then leave Terminal running in background (don't let it close via task killer or otherwise), hold down the hardware menu or home button to switch programs for a bit and connected in via VNC (AndroidVNC)...
address: localhost port: 5901 and password: password ... then hit connect (login details will be saved for next time)...
its working fine software keyboard etc and at good speed. In menu options select 24bit colour, local mouse, 1:1 scaling and Touchpad only to make navigating menus much easier.
Normal phone and Android functions should be fine.
Short press hardware menu key to get mouse options etc and longpress to bring up software keyboard (using Android VNC).
This debian image cannot be shut down unless the phone is rebooted.
I am using the Hyperdroid Rom off NAND, overclocked at 1.2ghz and a 16GB class 6 microsd (although it should be independent to all this... worth mentioning)
Edit 1. This is a bare image with LXDE on top but the repository for Debian is large and you can use apt-get install openoffice.org, apt-get install abiword etc to grab whatever you want to fill the 1.5GB image... unlike Ubuntu all the applications are free.
Edit 2. Its possible to have debian and ubuntu on your SDcard.
2g SDcard. Can running ?
This is too small I think, you should have at least a 4GB card!
This will sound stupid but is it possible to run this if you have sdcard android build and not nand?
Ty for reply.
Sent from my HTC HD2 using XDA Premium App
Hmmmmmm can any body tell me exactly WHAT IS THIS?!?
sorry for stupid Q
farhang_za said:
Hmmmmmm can any body tell me exactly WHAT IS THIS?!?
sorry for stupid Q
Click to expand...
Click to collapse
Linux running as some sort of virtual machine on android by using vnc(rdp) software.
Sent from my HTC HD2 using XDA Premium App
maneken25 said:
This will sound stupid but is it possible to run this if you have sdcard android build and not nand?
Ty for reply.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No. But look out for this.
Hmmmmmm can any body tell me exactly WHAT IS THIS?!?
Click to expand...
Click to collapse
Its a versatile linux OS of desktop quality, affectionately known as the mother of all linux operating systems, it is the 4th most popular linux variant as compliled by distrowatch as of 2010 and third in terms of downloads in early 2011. Ubuntu was number 1.
Here are some positive traits of Debian.
How to set into Chinese
So, ok, Ive got this working,.. where does the image come from exactly? how was it built and can any linux variant be used?
imperiallight said:
Original thread (Thanks mercianary):
http://forum.xda-developers.com/showthread.php?t=744236
Edit 1. This is a bare image with LXDE on top but the repository for Debian is large and you can use apt-get install openoffice.org, apt-get install abiword etc to grab whatever you want to fill the 1.5GB image... unlike Ubuntu all the applications are free.
Click to expand...
Click to collapse
Nice, will have to check it out. Used to use debian on my IBM X31 'cos Ubuntu was just little too resource hungry until my PB butterfly arrived Just looked into the 'paid apps' for Ubuntu. OMG!!! Are they having a laugh? Who is seriously gonna pay for commercial codecs when you can just download the 'bad' and 'ugly' packs from the repos!!! Off topic I know, but, seriously, what???
well i have tried my best but this is NOT realy working for me!
i get this Error :
# su
# sh /sdcard/deboot
mkdir failed for /sdcard/debian, File exists
losetup: /dev/block/loop5
mount: mounting /dev/block/loop5 on /sdcard/debian failed: Device or resource by
mount: mounting devpts on /sdcard/debian/dev/pts failed: No such file or directy
mount: mounting proc on /sdcard/debian/proc failed: No such file or directory
mount: mounting sysfs on /sdcard/debian/sys failed: No such file or directory
mount: mounting /sdcard on /sdcard/debian/root/sdcard failed: No such file or dy
net.ipv4.ip_forward = 1
chroot: can't execute '/bin/bash': No such file or directory
#
finallly got that working!
but this damn androidVNC wont connect!!
it says VNC connection failed!!!
farhang_za said:
finallly got that working!
but this damn androidVNC wont connect!!
it says VNC connection failed!!!
Click to expand...
Click to collapse
https://market.android.com/details?id=com.toremote.vncpro
I use that... remote vnc pro.... like $6 but it works great.....
diesburg said:
https://market.android.com/details?id=com.toremote.vncpro
I use that... remote vnc pro.... like $6 but it works great.....
Click to expand...
Click to collapse
yeah! it worked thanks maan
I keep getting the error message
"sdcard/deboot: line 5: syntax error: unexpected "else"
#"
I checked out the linked thread by the OP and downloaded another deboot file but still got the same error.
I have got WP7 dual booted with american android with a 16GB SDcard partitioned 50:50
I managed to get Ubuntu 10.10 working via VNC off the SDcard but would like to get this debian to work to free up storage space.
Any suggestions would be appreciated
i also got this error
# su
# sh /sdcard/deboot
mkdir failed for /sdcard/debian, File exists
losetup: /dev/block/loop5
mount: mounting /dev/block/loop5 on /sdcard/debian failed: Device or resource by
mount: mounting devpts on /sdcard/debian/dev/pts failed: No such file or directy
mount: mounting proc on /sdcard/debian/proc failed: No such file or directory
mount: mounting sysfs on /sdcard/debian/sys failed: No such file or directory
mount: mounting /sdcard on /sdcard/debian/root/sdcard failed: No such file or dy
net.ipv4.ip_forward = 1
chroot: can't execute '/bin/bash': No such file or directory
#
what do you have to do to fix it. is it a rom problem becouse i have hyperdriod gbx v12
http://forum.xda-developers.com/showthread.php?t=918899
is it different form hyperdriod gbx 2.01 becouse that is what imperiallight is using, im even using a 16gb sdcard but class 2
I also got the same problem...
any body know how to fix it??
Edit: solve the problem, reinstall the ROM from scratch..
Next.. ubuntu
plasmastrike said:
i also got this error
# su
# sh /sdcard/deboot
mkdir failed for /sdcard/debian, File exists
losetup: /dev/block/loop5
mount: mounting /dev/block/loop5 on /sdcard/debian failed: Device or resource by
mount: mounting devpts on /sdcard/debian/dev/pts failed: No such file or directy
mount: mounting proc on /sdcard/debian/proc failed: No such file or directory
mount: mounting sysfs on /sdcard/debian/sys failed: No such file or directory
mount: mounting /sdcard on /sdcard/debian/root/sdcard failed: No such file or dy
net.ipv4.ip_forward = 1
chroot: can't execute '/bin/bash': No such file or directory
#
what do you have to do to fix it. is it a rom problem becouse i have hyperdriod gbx v12
http://forum.xda-developers.com/showthread.php?t=918899
is it different form hyperdriod gbx 2.01 becouse that is what imperiallight is using, im even using a 16gb sdcard but class 2
Click to expand...
Click to collapse
When connection via VNC client fails try:
vncserver :1
or
vncserver :2 (the port is 5902)
in the debian console
plasmastrike said:
i also got this error
# su
# sh /sdcard/deboot
mkdir failed for /sdcard/debian, File exists
losetup: /dev/block/loop5
mount: mounting /dev/block/loop5 on /sdcard/debian failed: Device or resource by
mount: mounting devpts on /sdcard/debian/dev/pts failed: No such file or directy
mount: mounting proc on /sdcard/debian/proc failed: No such file or directory
mount: mounting sysfs on /sdcard/debian/sys failed: No such file or directory
mount: mounting /sdcard on /sdcard/debian/root/sdcard failed: No such file or dy
net.ipv4.ip_forward = 1
chroot: can't execute '/bin/bash': No such file or directory
#
what do you have to do to fix it. is it a rom problem becouse i have hyperdriod gbx v12
http://forum.xda-developers.com/showthread.php?t=918899
is it different form hyperdriod gbx 2.01 becouse that is what imperiallight is using, im even using a 16gb sdcard but class 2
Click to expand...
Click to collapse
First off, you already have the .img mounted(/sdcard/debian device busy), and the rest of the file structre wasn't created right.
to create it manually, run these in terminal:
Code:
cd /sdcard
rm /debian
mkdir /debian
cd debian
mkdir /dev/pts
mkdir /proc
mkdir /sys
I just managed to boot this using SD Android via haret.
I couldn't get it to work before using ACA sd, see my previous post.
I used http://forum.xda-developers.com/showthread.php?t=1437463 SD ICS from tytung.
First boot created debian folder ok but after second boot I could not connect with VNC due to localhost:1 being used by /tmp/X1-lock. I tried using 5902 but no go.
After reading up whether you can delete this, it seems you can.
So using root browser (from market-free) I deleted /mnt/sdcard/debian/tmp/X1-lock (and also X11-UNIX in same place, as this also gives the same problem) and then entering the commands in terminal
I haven't had any problems so far.
Remember to backup everything before trying this, I don't accept responsibility etc.
Note; megaupload link in first post gone, use link in original thread
Hi,
I'm trying to get backtrack loaded on galaxy task 10 with pershoot's latest kernel and the script fails while trying to mount the loop device. I have searched all over the place and have found other people with the same or similar problems. I'm pretty sure the problem is that I do not have ext2 support on the kernel.
Does anyone know if one of the extra modules for pershoot's kernel will enable ext2 support?
I have included the error below in case anyone has any other ideas.
Thanks.
Code:
[email protected]:/sdcard/bt # sh installbt.sh [ STEP 1 ]
BackTrack CHroot v0.2 for SGS2
This process does NOT damage Android OS!
based on Xperia X10 Customization by Anant
modded for SGS2 by DooMLoRD
Cleaning up old Chunks . . .
Creating necessary directories
Setting up files
[ STEP 1 COMPLETE ]
BackTrack is now configure!
to Start BackTrack type 'startbt' (without the quotes)
[email protected]:/sdcard/bt # startbt
[ STEP 2 ]
mknod: /dev/block/loop254: File exists
mount: mounting /dev/block/loop254 on /data/local/bt failed: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
/system/bin/startbt[21]: cannot create /data/local/bt/etc/resolv.conf: No such file or directory
/system/bin/startbt[22]: cannot create /data/local/bt/etc/resolv.conf: No such file or directory
/system/bin/startbt[23]: cannot create /data/local/bt/etc/hosts: No such file or directory
BackTrack Loader by Anant based on ubuntu loader
[ STEP 2 COMPLETE ]
BackTrack is ready just type 'bt' (without the quotes)
[email protected]:/sdcard/bt #
..bump..
Anyone?
Greetings-
I just built my first image of AOSP for a Samsung Note 3. I have, in the past deployed a Cyanogenmod nightly release on my phone. Now I am trying to deploy my image. I used this link to build my environment http://forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/189699-guide-ubuntu-compiling-android-source-12.html . But the install does not go well. I am moving the zip file to the external sd card, and using TWRP to install it. I get the following messages: E: Unable to mount '/usbstorage' Full SELinux is present In istalling '/external_sd/full_toroplus-ota-eng.root.zip checking for MD5 file Skipping MD5 check: no MD5 file found. assert failed: getprop ('ro.product.device") == "toroplus" || getprop ("ro.bild.product") ==toroplus" e:error executing updater binary in zip 'external_sd/full_toroplus-ta-eng.root.zip' error flashing zip '/external_sd/full_toroplus-ota-eng.root.zip Updating partition details.. E:unable to mount 'usbstorage'
What am I doing wrong? Is there some other way I can do this?
Sean
sansari123 said:
Greetings-
I just built my first image of AOSP for a Samsung Note 3. I have, in the past deployed a Cyanogenmod nightly release on my phone. Now I am trying to deploy my image. I used this link to build my environment http://forums.androidcentral.com/ve...guide-ubuntu-compiling-android-source-12.html . But the install does not go well. I am moving the zip file to the external sd card, and using TWRP to install it. I get the following messages: E: Unable to mount '/usbstorage' Full SELinux is present In istalling '/external_sd/full_toroplus-ota-eng.root.zip checking for MD5 file Skipping MD5 check: no MD5 file found. assert failed: getprop ('ro.product.device") == "toroplus" || getprop ("ro.bild.product") ==toroplus" e:error executing updater binary in zip 'external_sd/full_toroplus-ta-eng.root.zip' error flashing zip '/external_sd/full_toroplus-ota-eng.root.zip Updating partition details.. E:unable to mount 'usbstorage'
What am I doing wrong? Is there some other way I can do this?
Sean
Click to expand...
Click to collapse
What phone do you have? Toroplus is galaxy nexus of course that won't ever flash on a note 3 you should be building hlte for note 3
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
What phone do you have? Toroplus is galaxy nexus of course that won't ever flash on a note 3 you should be building hlte for note 3
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks. Are you saying hlte is an option for the lunch command? Here is how I got toroplus; I saw it in the android source site. https://source.android.com/#q=sprint samsungese
Basically, these are my options:
[email protected]:~/WORKING_DIRECTORY# lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. aosp_deb-userdebug
6. aosp_flo-userdebug
7. full_grouper-userdebug
8. full_tilapia-userdebug
9. mini_armv7a_neon-userdebug
10. mini_mips-userdebug
11. mini_x86-userdebug
12. full_mako-userdebug
13. full_maguro-userdebug
14. full_manta-userdebug
15. full_arndale-userdebug
16. full_toroplus-userdebug
17. full_toro-userdebug
18. full_panda-userdebug
Which would you like? [aosp_arm-eng]
sansari123 said:
Thanks. Are you saying hlte is an option for the lunch command? Here is how I got toroplus; I saw it in the android source site. https://source.android.com/#q=sprint samsungese
Basically, these are my options:
[email protected]:~/WORKING_DIRECTORY# lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. aosp_deb-userdebug
6. aosp_flo-userdebug
7. full_grouper-userdebug
8. full_tilapia-userdebug
9. mini_armv7a_neon-userdebug
10. mini_mips-userdebug
11. mini_x86-userdebug
12. full_mako-userdebug
13. full_maguro-userdebug
14. full_manta-userdebug
15. full_arndale-userdebug
16. full_toroplus-userdebug
17. full_toro-userdebug
18. full_panda-userdebug
Which would you like? [aosp_arm-eng]
Click to expand...
Click to collapse
This is not a nexus device so Google would not have it in there. .... if you want to build aosp and not cyanogen or some other flavor that had already supported hlte then you will have to add support yourself
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
This is not a nexus device so Google would not have it in there. .... if you want to build aosp and not cyanogen or some other flavor that had already supported hlte then you will have to add support yourself
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks. I started to use Cyanogenmod, and went through this link: How To Build CyanogenMod Android for Samsung Galaxy Note 3 LTE ("hlte")
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
When I issue breakfast to get the device specific modules, I get the following message:
#:~/android/system# breakfast hlte
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
Device hlte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_hlte
Default revision: cm-10.2
Checking branch info
Default revision cm-10.2 not found in android_device_samsung_hlte. Bailing.
Branches found:
cm-11.0
stable/cm-11.0 Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
--------------------------------------------------------------------------------------------------------------------------------------------------------------
I am now downloading version 11.0 instead of 10.2. Do you think that would fix my issue? I do not know what it is complaining about.
sansari123 said:
Thanks. I started to use Cyanogenmod, and went through this link: How To Build CyanogenMod Android for Samsung Galaxy Note 3 LTE ("hlte")
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
When I issue breakfast to get the device specific modules, I get the following message:
#:~/android/system# breakfast hlte
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
Device hlte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_hlte
Default revision: cm-10.2
Checking branch info
Default revision cm-10.2 not found in android_device_samsung_hlte. Bailing.
Branches found:
cm-11.0
stable/cm-11.0 Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
--------------------------------------------------------------------------------------------------------------------------------------------------------------
I am now downloading version 11.0 instead of 10.2. Do you think that would fix my issue? I do not know what it is complaining about.
Click to expand...
Click to collapse
I don't remember if their was ever a 10.2 that worked so yes I think it best to use 11.0 ... cyanogen should build with no problem. .. what os are you using that may be a problem I think most use 12.04 Ubuntu ... but I use 14.04 and the difference is a few different things ....
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
I don't remember if their was ever a 10.2 that worked so yes I think it best to use 11.0 ... cyanogen should build with no problem. .. what os are you using that may be a problem I think most use 12.04 Ubuntu ... but I use 14.04 and the difference is a few different things ....
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I am using 12.04. Do you think I should upgrade?
I just noticed a comment about fastboot. Will I need it for this task? I just can not get fastboot working on my laptop. I think it is because I only have usb 2.0.
I have tried 11.0 twice now, and I get this error:
* [new branch] cm-11.0 -> github/cm-11.0
Fetching projects: 100% (447/447), done.
Traceback (most recent call last):
File "/root/android/system/.repo/repo/main.py", line 408, in <module>
_Main(sys.argv[1:])
File "/root/android/system/.repo/repo/main.py", line 384, in _Main
result = repo._Run(argv) or 0
File "/root/android/system/.repo/repo/main.py", line 143, in _Run
result = cmd.Execute(copts, cargs)
File "/root/android/system/.repo/repo/subcmds/sync.py", line 690, in Execute
project.Sync_LocalHalf(syncbuf)
File "/root/android/system/.repo/repo/project.py", line 1158, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/root/android/system/.repo/repo/project.py", line 2178, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/root/android/system/.repo/repo/project.py", line 2335, in rev_list
p.stderr))
error.GitError: CyanogenMod/android rev-list ('^bf81824cd948e185fdc86626f237a8c3e85a4687', 'HEAD', '--'): fatal: bad object HEAD
What should I do?
Epix4G said:
I don't remember if their was ever a 10.2 that worked so yes I think it best to use 11.0 ... cyanogen should build with no problem. .. what os are you using that may be a problem I think most use 12.04 Ubuntu ... but I use 14.04 and the difference is a few different things ....
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Hey Epix, thank you so much for your help so far. I was able to download cd-11.0. I had to delete the .repo directory a number of times ( about ten ), and it still did not work. I then deleted other git related files. I used this linke http://stackoverflow.com/questions/1213430/how-to-fully-delete-a-git-repository-created-with-init I hope this helps others.
I would really appreciate it if you can help me with fastboot issue. I posted a comment earlier. I am also now running into some other potential issues when I issue "./extract-files.sh" command. Below you see the result of grep for the words permission, and failed. Would this cause me issues? The permission issue is related to my device.
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i permission
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
Extracting /system/etc/permissions/com.qualcomm.location.xml ...
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i failed
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte#
I tried to fix the permission issue by issuing the command mount, which according to the Cyanogenmod wiki here, http://wiki.cyanogenmod.org/w/Doc:_Building_Basics mounts the directories as read/write. But I ended up with the same amount of permission denied'sssssssssss so I used adb shell and issued mount -o remount,rw /system, and then issued the Cyanogenmod script command "./extract-files.sh'. But I still get the same number of permission denied messages. Any ideas?
sansari123 said:
Hey Epix, thank you so much for your help so far. I was able to download cd-11.0. I had to delete the .repo directory a number of times ( about ten ), and it still did not work. I then deleted other git related files. I used this linke http://stackoverflow.com/questions/1213430/how-to-fully-delete-a-git-repository-created-with-init I hope this helps others.
I would really appreciate it if you can help me with fastboot issue. I posted a comment earlier. I am also now running into some other potential issues when I issue "./extract-files.sh" command. Below you see the result of grep for the words permission, and failed. Would this cause me issues? The permission issue is related to my device.
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i permission
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
Extracting /system/etc/permissions/com.qualcomm.location.xml ...
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i failed
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte#
Click to expand...
Click to collapse
You have to setup android sdk ..and add it to bash and path so that in any terminal you can type android and it opens sdk ... Until then you can't extract files
Sent from my SM-N900P using Xparent BlueTapatalk 2
Hi, friends.
I'd really appreciate your help.
My phone is suffering from consequences of kernel flash, which was obviously not a very successful :silly:
Short <intro>, if I may:
I have been using Cyanogenmod 12.1 nightlies (lollipop 5.1.1) for a long time. Everything was great.
One day I decided to try out Dorimanx kernel for lollipop, compatible with CM, of course. Big mistake.
After the flash (wiped Cache, Dalvik, System before the flash) I lost /eMMC, since Dori is lacking ext4 support for /eMMC, which I wasn't aware of.
Tried to flash my previous rom back (wiped Cache, Dalvik, System before the flash), but I got even more processes failing, probably due to different SELinux policies (Dori - permissive, stock CM - enforcing).
While I had Dori on board, I managed to backup /eMMC(copy-paste over MTP bridge to Windows PC) and /data(as binary image and TWRP-backup).
Now, even when I restore those two (eMMC or /data) under new clean ROM installation - I keep getting errors.
</intro>
/emmc issue example:
Code:
[ 12-20 22:20:42.885 8856: 9388 E/CacheManager ]
Cannot instantiate cache!
java.io.FileNotFoundException: /storage/sdcard0/Android/data/com.android.gallery3d/cache/imgcache.idx: open failed: EACCES (Permission denied)
at libcore.io.IoBridge.open(IoBridge.java:456)
...
[ 12-20 22:20:42.923 8856: 9388 W/Worker ]
Exception in running a job
java.lang.NullPointerException: Null pointer exception during instruction 'monitor-enter v6'
at com.android.gallery3d.data.ImageCacheService.getIm ageData(ImageCacheService.java:65)
/data issue example:
Code:
[ 12-14 17:03:07.745 6350: 6350 W/com.google.android.gms ]
type=1400 audit(0.0:2308): avc: denied { lock } for comm=4173796E635461736B202331 path="/data/data/com.google.android.gms/databases/reminders.db" dev=mmcblk0p10 ino=123233 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:system_data_file:s0 tclass=file
What I've tried so far:
e2fsck (/emmc)
twrp - fix permissions (/data)
twrp format partition + copy paste from PC (/emmc)
find /emmc/Android/data/ -type d -exec chmod 775 {} ';' (/emmc)
find /emmc/Android/data/ -type f -exec chmod 664 {} ';' (/emmc)
restorecon -FR (/emmc)
install Kitkat-permissive rom on top of broken /data
Unfortunately, nothing helps.
I really want to keep my old /data partition, what's why I spent on this around 2 weeks, and I'll keep trying.
Can you please guide me from the technical perspective?
P.S. The /emmc issue was a dumb thing that I always forget:
Code:
[email protected]:/mnt/media_rw # find sdcard0 -type d -exec chmod 775 {} ';'
[email protected]:/mnt/media_rw # find sdcard0 -type f -exec chmod 664 {} ';'
[email protected]:/mnt/media_rw # chown -R media_rw:media_rw sdcard0
But the 2nd issue with /data is still unsolved.
Please assist!
If you need to restore your data only, you could manually mount the /data image on your PC (if you're not using Linux as your desktop OS, you can install Ubuntu or Mint under a virtual machine like VMware Player, which is free - if you need help with that, or mounting the image, PM me), wipe your device and copy over data for any apps you need to the new file system. Then, reapply proper permissions for copied data. Titanium Backup Pro can do that for you with a GUI, but requires a CWM backup if I remember correctly and won't talk with TWRP/raw images (I might be wrong).
Now, this all looks nice and all, but that "reapply proper permissions" part is a bit messy. It's because Android creates a new Linux user and group for every individual Android app you install. There are some special users/apps sharing certain details, but regular apps will have a new account like "u0_a47" or something like that created for them. If you just copy and paste any data to your new filesystem, you'll get hit with access errors (pretty much exactly what you've described). Reinstall all apps from .apks (if you have bare .apks backed up somewhere, or have extracted them from your /data, you can reinstall them all en masse with adb), then in terminal (as root, otherwise you won't be able to peek inside /data/data): ls -la /data/data > /storage/sdcard0/applist.txt, pull /storage/sdcard0/applist.txt to your computer (with adb), and then the messy part: Copy over any data you want, and reapply proper permissions for any app you've restored with chown -R uX_aY /data/data/org.your.app, where uX_aY is your app's user/group (listed in applist.txt), and org.your.app is your app identifier (also listed in applist.txt).
This is messy as hell, but it works.
Thank you for the answer! Can you confirm, please, if I'm getting this right?
1. Install from google play all the needed apps under clean rom (to get list of proper permissions)
2. Save output of ls -al from clean rom in a text file (proper permissions)
3. Extract apps from backed up /data image
4. Push them into /data of the clean rom
5. Run chown on each of the restored folders, using ouput of ls -al
6. Reboot
Now, the point where I extract apps from image is also tricky... afaik, single app is scattered between multiple directories under /data. Do you know any explanatory article on this subject? What's app structure under /data etc?
Extract apps and data from /data image, but yeah, everything else looks good. Under Android 6.0 (older versions aren't that different if I remember correctly), with a single user, you have two folders: /data/app which contains installed .apks, and /data/data which contains your app's data - everything else is system-specific and will get generated automatically if needed, regular apps can't touch these at all. Simply extract these two folders and you're good to go.
Cool! I will try that during the weekend. If this works - it may become a very useful article.
Are those changes persistent? I did chown for some /emmc files under TWRP recovery, reinstalled rom, and i can tell that root explorer& terminal do not show my changes at all... :-/
Yes, they should be as long as your file system is mounted R/W. Did you chown -R (recursively)?
Unfortunately, your solution is missing something... still getting errors... [ 12-26 19:53:38.802 4124: 4124 W/com.socialnmobile.dictapps.notepad.color.note ]
type=1400 audit(0.0:197): avc: denied { lock } for comm=4173796E635461736B202331 path="/data/data/com.socialnmobile.dictapps.notepad.color.note/databases/colornote.db" dev=mmcblk0p10 ino=123103 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:system_data_file:s0 tclass=file
[ 12-26 19:53:38.802 4124: 4124 W/com.socialnmobile.dictapps.notepad.color.note ]
type=1400 audit(0.0:198): avc: denied { lock } for comm=4173796E635461736B202331 path="/data/data/com.socialnmobile.dictapps.notepad.color.note/databases/colornote.db" dev=mmcblk0p10 ino=123103 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:system_data_file:s0 tclass=file
[ 12-26 19:53:38.802 3821: 4125 E/FlurryAgent ]
java.io.FileNotFoundException: /data/data/com.socialnmobile.dictapps.notepad.color.note/files/.flurrydatasenderblock.ba285603-75ea-4129-84cd-8ac36726fb02: open failed: EACCES (Permission denied)
at libcore.io.IoBridge.open(IoBridge.java:456)
Ummm, looks like SELinux is set to restrictive and prevents app from touching what is not exactly theirs. Unfortunately I can't help you with this, I don't know how to configure SELinux properly :/
Is it possible to replace only the 'databases/colornote.db' file?
I don't know how to copy it over and set correct permissions to make it work with restrictive SELinux policies, but you can use a database viewer/editor or sqlite3 binary on the device to export/import the data inside.
1. Copy your colornote.db with data somewhere accessible (not /data/....). Wipe the app's data completely, then start it once. It should regenerate all required files. Connect your phone to PC, and fire up adb shell. (You can do this with the terminal on the device directly too.) Get root access with "su".
2. "cd" to the folder with your colornote.db (which you want to use). Then (as root) do this on your device: https://stackoverflow.com/questions/4389930/exporting-data-from-sqlite-3#4390636 - sqlite3 and any text editor (vi, most likely) should be available in your ROM (if not, install Busybox). You should now end up with 2 .sql files in the same folder.
3. Still as root: "sqlite3 /data/data/com.socialnmobile.dictapps.notepad.color.note/databases/colornote.db", then ".schema" (there's a dot before "schema"). It'll write out a few statements like "CREATE TABLE foo". There shouldn't be too many, you'll have to "DROP TABLE foo;" for every single one of them, then ".read schema.sql", followed by ".read inserts.sql" - both files created in step 2, you'll have to supply full paths to be read. Then ".exit", and you're done.
(And someone will probably come and tell me all of this can be done in a few seconds with two-three commands I didn't know about before. )
Thanks for your time, mate. I will probably try to dig into CM sources of SELinux implementation, or to read a really detailed book on the subject. I guess it's the only way to fix my backed up /data.
Dragoon Aethis, tell me one more thing, please: if I grab/push single application, as you suggested, getting bad selinux feedback, then MOVING app to sdcard (built-in function of CM rom), and moving back? Should it restore proper permissions, what do you say? Of course, I'll try that on the weekend, since my i9100 is a daily driver, I cannot experiment during the week I thought of this, because most of the time sdcard has different filesystem than /data, which makes impossible to keep permissions there.
Weeeell, you can format /sdcard as ext4 and your problems are gone, but so are proper Android permissions for that it thinks should be on /sdcard Moving it might work, but moving apps to SD is hit and miss most of the time anyways, so you'd have to try.
Ok, I'll try. My /emmc is ext4 anyway. Not sure if this is a good thing, since I'm expecting the transferred application to lose permissions and selinux properties during move & restore. It is the only way to trigger creation of the proper properties. Otherwise it's only copy-paste of the same broken properties, as well as the files themselves. Of course I haven't seen the implementation on the github, but I will try that on weekend, and reply back.
I've had the Samsung Chromebook Plus for about 2 weeks now, and I love it! Chrome OS is pretty good at handling itself for notetaking with the stylus, and the gorgeous screen is great for high res stuff (although Chrome OS is in desperate need of DPI scaling). It even runs Android apps out of the box! So far, I only have 2 major gripes about Chrome OS:
-It cannot do multitasking on anything (Android or Chrome app) when in tablet mode (buttons disappear, window drags are disabled) even on the beta branch
-Android cannot be rooted on the Chrome OS (so I think).
That second one is the one I'd like help with. Can you root the Android OS installed on the Chromebook? I'd love to know; I have a game called War Robots I want to play on it, but I can't manually turn down the graphical fidelity without using GLTools.
Any help is appreciated!
Nilithium said:
Can you root the Android OS installed on the Chromebook? I'd love to know; I have a game called War Robots I want to play on it, but I can't manually turn down the graphical fidelity without using GLTools.
Any help is appreciated!
Click to expand...
Click to collapse
Yes, certainly you can root Android on Chrome OS. The rootfs of the Android container is read-only by default, so the method I've been using involves making a writeable copy of the Android rootfs .img in /usr/local, adding SuperSU (adding its binaries to /system/xbin, the SuperSU apk to /system/priv-app, and modifying init.rc to autoload daemonsu), then replacing the original Android rootfs .img file path with a symlink to the rooted one. In addition, a couple of flags (mount-as-read-only and font sharing) need to be changed in one or two of the /etc/init/arc* files (CrOS version dependent), and also the SElinux policy file needs to be patched.
I have written a script to automate the above procedure, if you would like to try it out you can do so by entering the following into the Chrome OS shell (then rebooting).
Code:
curl -Ls https://raw.githubusercontent.com/nolirium/aroc/onescript/RootandSEpatch.sh | sudo sh
You need to be in Dev mode to get into the shell (Ctrl+Alt+T; type 'shell'), and rootfs verification needs to be switched off to modify system files (the script will give you the command to do this, if you haven't already done it).
It would be prudent to make sure any important files are backed up prior to making any changes to the rootfs.
Edit: If any errors occur, or problems are are experienced after using the script, such as Android (apps) failing to load, it's usually not necessary to powerwash. The script makes a backup of the original Android system.raw.img, which can be restored with the following command:
Code:
sudo mv /opt/google/containers/android/system.raw.img.bk /opt/google/containers/android/system.raw.img
Nolirum said:
Yes, certainly you can root Android on Chrome OS. The rootfs of the Android container is read-only by default, so the method I've been using involves making a writeable copy of the Android rootfs .img in /usr/local, adding SuperSU (adding its binaries to /system/xbin, the SuperSU apk to /system/priv-app, and modifying init.rc to autoload daemonsu), then replacing the original Android rootfs .img file path with a symlink to the rooted one. In addition, a couple of flags (mount-as-read-only and font sharing) need to be changed in one or two of the /etc/init/arc* files (CrOS version dependent), and also the SElinux policy file needs to be patched.
I have written a script to automate the above procedure, if you would like to try it out you can do so by entering the following into the Chrome OS shell (then rebooting).
Code:
curl -Ls https://raw.githubusercontent.com/nolirium/aroc/onescript/RootandSEpatch.sh | sudo sh
You need to be in Dev mode to get into the shell (Ctrl+Alt+T; type 'shell'), and rootfs verification needs to be switched off to modify system files (the script will give you the command to do this, if you haven't already done it).
It would be prudent to make sure any important files are backed up prior to making any changes to the rootfs.
Click to expand...
Click to collapse
On a general basis, running scripts from random strangers on the Internet is a bad thing. But I'll take it!
I've encountered an ID10T error though: I set the debugging password during setup, and I THOUGHT that was the sudo password to run your script. Problem is, that's not true, and I've no idea what it is.
Tried Google Account password, no dice.
Tried Chromebook PIN, no dice.
Tried Debug Pass set in Setup, no dice.
Tried password, no dice.
Tried null password (no input), no dice.
What is the sudo password? Did I miss something?
Nilithium said:
What is the sudo password? Did I miss something?
Click to expand...
Click to collapse
Yeah, this seems to be quite a common issue. Perhaps it would be more user-friendly if more information was available during the initial OOB setup, such as a link describing the 'debugging features' feature's features in a bit more depth.
Anyway, if you go into a VT with e.g. Ctrl+Alt+F2, you should be able to log in there as the user 'root' with your debugging password, and then you can run the command chromeos-setdevpasswd to set a sudo password for chronos.
Nolirum said:
Yeah, this seems to be quite a common issue. Perhaps it would be more user-friendly if more information was available during the initial OOB setup, such as a link describing the 'debugging features' feature's features in a bit more depth.
Anyway, if you go into a VT with e.g. Ctrl+Alt+F2, you should be able to log in there as the user 'root' with your debugging password, and then you can run the command chromeos-setdevpasswd to set a sudo password for chronos.
Click to expand...
Click to collapse
DELETE
Worked for me on Samsung Chromebook 3.
Manually downloaded and extracted SuperSU.zip to downloads.
Manually downloaded busybox using curl in shell. Moved it manually to /usr/local/bin/ believe thats correct.
Then re-ran script and it worked.
Anyone tried it on Pixelbook?
Nolirum said:
Yes, certainly you can root Android on Chrome OS. The rootfs of the Android container is read-only by default, so the method I've been using involves making a writeable copy of the Android rootfs .img in /usr/local, adding SuperSU (adding its binaries to /system/xbin, the SuperSU apk to /system/priv-app, and modifying init.rc to autoload daemonsu), then replacing the original Android rootfs .img file path with a symlink to the rooted one. In addition, a couple of flags (mount-as-read-only and font sharing) need to be changed in one or two of the /etc/init/arc* files (CrOS version dependent), and also the SElinux policy file needs to be patched.
I have written a script to automate the above procedure, if you would like to try it out you can do so by entering the following into the Chrome OS shell (then rebooting).
Code:
curl -Ls https://raw.githubusercontent.com/nolirium/aroc/onescript/RootandSEpatch.sh | sudo sh
You need to be in Dev mode to get into the shell (Ctrl+Alt+T; type 'shell'), and rootfs verification needs to be switched off to modify system files (the script will give you the command to do this, if you haven't already done it).
It would be prudent to make sure any important files are backed up prior to making any changes to the rootfs.
Click to expand...
Click to collapse
holy cow, script works flawlessly! (Samsung Chromebook Plus)
Anyone know why my Tivo app and Sirius XM don't work on my new Samsung Chromebook Plus V2? They install and than don't open and crash any other workable apks that anyone knows about? Sirius I can do online Tivo won't play all my recorded shows online just some and I really bought this Chromebook to use the Tivo app to watch shows when not at home or sitting outside. I know this thread is about rooting but I thought someone here may be able to help me. I also posted in the Tivo Community Forum also and am waiting for a response. Thanks!
MsWadera said:
Anyone tried it on Pixelbook?
Click to expand...
Click to collapse
This is the question I'm interested in also as I will be receiving my first PixelBook in a couple of days. Having root access in the Android container along with a Linux install would rapidly move this to my daily driver.
Can anyone confirm this?
phonefreedom said:
This is the question I'm interested in also as I will be receiving my first PixelBook in a couple of days. Having root access in the Android container along with a Linux install would rapidly move this to my daily driver.
Can anyone confirm this?
Click to expand...
Click to collapse
Well, I gave this a try and can say this is a no go for the Pixelbook. It did make Android unusable though causing me to powerwash and reload.
phonefreedom said:
Well, I gave this a try and can say this is a no go for the Pixelbook. It did make Android unusable though causing me to powerwash and reload.
Click to expand...
Click to collapse
When you say it was unusable, did Android (apps) appear to fail to load up completely, just the icon spinning? Or something else?
Did you happen to notice if any errors were shown on the script's output at all?
For example, there was this issue reported on github when the Pixelbook was first released, in which the Android rootfs container created by the script turned out to be a bit smaller than required, and so errors occurred when copying files to the new rooted /system. The user was able to successfully continue after manually editing the script so it created a container that was slightly bigger.
The script has been updated since then to reflect the increased space requirements, so that particular problem should no longer occur. Other potential sources of error might include if there could have been a problem downloading the required files (SuperSU, BusyBox), a problem patching SE Linux (in which case there is a separate script to do this part) , or maybe something else, possibly due to Chrome OS changes/updates.
In the case of the script rendering Android unusable, it's usually not necessary to powerwash. The script makes a backup of the original Android system.raw.img, which can be restored with the following command:
Code:
sudo mv /opt/google/containers/android/system.raw.img.bk /opt/google/containers/android/system.raw.img
Entering the above will restore the original read-only squashfs unrooted rootfs, which, after a reboot, should then load up as normal.
I think I'll edit my earlier post in this thread to add the command to restore from backup. Apologies for failing to mention it here initially. I might add an explicit message in the script itself regarding this, as well.
Flashing zips
Hey first time poster here. This may seem like a newbie question, but how do I flash zips without a custom recovery?
Is there a way to sideload to the container? I tried several apps like Flashfire (used an unofficial build since I could not disable the time bomb on Chrome Os) and Flash Gordon, but it did not seem to work.
Thanks
do-tim said:
Hey first time poster here. This may seem like a newbie question, but how do I flash zips without a custom recovery?
Is there a way to sideload to the container? I tried several apps like Flashfire (used an unofficial build since I could not disable the time bomb on Chrome Os) and Flash Gordon, but it did not seem to work.
Thanks
Click to expand...
Click to collapse
Depends what you want to flash, probably.
You might be able to rewrite the relevant edify commands in the update-binary that you want to flash into an equivalent shell script for the Chrome OS shell.
However, by default the Android rootfs container is in a read-only squashfs format, so normally cannot be modified directly. One way to modify it is to make a writable copy of the container in /usr/local, then replace the original file pathname with a symbolic link to the R/W copy. This works fine for the most part (but does takes up extra disk space, and needs to be re-done after an OS update).
For instance, here is part of the rooting script mentioned upthread, which makes a writable copy of the Android container, copies the files from the original container therein, renames the original to .bk, replaces the original file pathname with a symlink to the copy and, at the end, changes a couple of relevant envs in CrOS's /etc/init/arc-setup-env file.
Code:
#!/bin/sh
# Detect CPU architecture
case "$ARCH" in
x86 | i?86) ANDROID_ARCH="x86";;
x86_64 | amd64) ANDROID_ARCH="x86";;
armel) ANDROID_ARCH="armel";;
arm64 | aarch64) ANDROID_ARCH="armv7";;
arm*) ANDROID_ARCH="armv7";;
*) error 2 "Invalid architecture '$ARCH'.";;
esac
# Make some working dirs
mkdir -p /usr/local/Android_Images
mkdir -p /usr/local/Android_Images/Mounted
mkdir -p /usr/local/Android_Images/Original
# Create container image file. Intel devices need a slightly larger file.
if [ $ANDROID_ARCH=armv7 ]; then
cd /usr/local/Android_Images
fallocate -l 1.7G /usr/local/Android_Images/system.raw.expanded.img
else
if [ $ANDROID_ARCH=x86 ]; then
cd /usr/local/Android_Images
fallocate -l 2.2G /usr/local/Android_Images/system.raw.expanded.img
# Format the .img file.
mkfs ext4 -F /usr/local/Android_Images/system.raw.expanded.img 2>/dev/null
# Set SELinux to permissive.
setenforce 0
# Check that the stock Android container exists and is not already a symlink.
# If this is the case, mount it in order to copy files.
if [ ! -L /opt/google/containers/android/system.raw.img ]; then
if [ -e /opt/google/containers/android/system.raw.img ]; then
umount -l /usr/local/Android_Images/Original 2>/dev/null
mount -o loop,rw,sync /opt/google/containers/android/system.raw.img /usr/local/Android_Images/Original 2>/dev/null
else
# If the stock container's missing, check if there is a backup.
if [ -e /opt/google/containers/android/system.raw.img.bk ]; then
umount -l /usr/local/Android_Images/Original 2>/dev/null
mount -o loop,rw,sync /opt/google/containers/android/system.raw.img.bk /usr/local/Android_Images/Original 2>/dev/null
else
# If there's no backup in the expected location, check in ~/Downloads, too.
# NOTE: We can also use a container from a different device/other OS versions by putting it in ~/Downloads.
# To use a different container, we just need to rename any existing containers in /opt/google/containers/android/
# e.g. rename /opt/google/containers/android/system.raw.img.bk to /opt/google/containers/android/system.raw.img.bk.bk
# Containers from different devices/OS versions are unlikely to boot, however.
if [ -e /home/chronos/user/Downloads/system.raw.img ]; then
echo "Mounting /home/chronos/user/Downloads/system.raw.img and copying files"
umount -l /usr/local/Android_Images/Original 2>/dev/null
mount -o loop,rw,sync /home/chronos/user/Downloads/system.raw.img /usr/local/Android_Images/Original 2>/dev/null
else
echo
echo "Error!"
echo "System.raw.img not found"
echo
exit 1
fi
fi
fi
fi
ANDROID_ROOTFS=/usr/local/Android_Images/Original
# Mount the new .img.
mount -o loop,rw,sync /usr/local/Android_Images/system.raw.expanded.img /usr/local/Android_Images/Mounted
# Copy the files.
cp -a -r $ANDROID_ROOTFS/. /usr/local/Android_Images/Mounted
# Rename the original container to .bk.
if [ -e /opt/google/containers/android/system.raw.img ]; then
if [ ! -L /opt/google/containers/android/system.raw.img ]; then
echo "Moving original Android rootfs image to /opt/google/containers/android/system.raw.img.bk"
mv /opt/google/containers/android/system.raw.img /opt/google/containers/android/system.raw.img.bk
# Make the symlink from the original pathname to our writeable rootfs image.
echo "Replacing original Android rootfs image path with symlink to /usr/local/Android_Images/system.raw.expanded.img"
ln -s /usr/local/Android_Images/system.raw.expanded.img /opt/google/containers/android/system.raw.img
fi
else
if [ -e /usr/local/Android_Images/system.raw.expanded.img ]; then
echo "Creating symlink to /usr/local/Android_Images/system.raw.expanded.img at original Android rootfs image file path"
ln -s /usr/local/Android_Images/system.raw.expanded.img /opt/google/containers/android/system.raw.img
fi
fi
# Change the envs for writeable mount and debuggable in CrOS's /etc/init.
sed -i 's/export WRITABLE_MOUNT=0/export WRITABLE_MOUNT=1/g' /etc/init/arc-setup-env 2>/dev/null
sed -i 's/export ANDROID_DEBUGGABLE=0/export ANDROID_DEBUGGABLE=1/g' /etc/init/arc-setup-env 2>/dev/null
The rooting script is basically just the above, with the addition of a couple of other bits, including the relevant commands from the update-binary script in the SuperSU zip, slightly rearranged from Edify to regular shell script for the CrOS shell. That part of the script can be seen here.
So you could maybe do a similar script, with the files you want to flash. Also, once you have a R/W Android rootfs, it may be possible to update files from directly within Android, although, as mentioned in the last few posts in this thread, on some recent CrOS builds, some people have been running into an issue with the rootfs still getting mounted RO within Android, even with a writable container. This does not occur on all devices though, and should be just a temporary issue.
It would probably also be possible to set up a sort of overlay configuration, somewhat similar to Magisk in effect, but due to the somewhat convoluted mount configuration of the container based system, and the almost constant changes/updates (to the container, its config, and so on) that have been occurring with each update to Chrome OS, this would likely require quite a bit of work to implement and maintain.
Corrective measures to run the script...
Spoke too quickly - all installed but no root detected in SuperSU...
Yes, thanks, it seems to work.
I wonder why the script cannot handle downloading SuperSU & busybox on its own, some corrections are needed.
justqt said:
Worked for me on Samsung Chromebook 3.
Manually downloaded and extracted SuperSU.zip to downloads.
Manually downloaded busybox using curl in shell. Moved it manually to /usr/local/bin/ believe thats correct.
Then re-ran script and it worked.
Click to expand...
Click to collapse
Is it possible that I don't have write access to /system of the Android container or am I doing something wrong?
Davestar2000 said:
Is it possible that I don't have write access to /system of the Android container or am I doing something wrong?
Click to expand...
Click to collapse
Yes, depending on the Chrome OS version you're on, it's possible that the container's still being mounted read-only. They keep changing around some bits and pieces related to the container mount config with (almost) every new version release of the OS. There was a change that they made to config.json (which could be worked around by editing the file) a while back which broke the RW mount, but this was reverted quite quickly. Some other related changes have been made recently though, causing the issue to crop up again.
I've been reluctant to add something in to the script to deal with this read-only mount issue as yet, since the need for it has been CrOS version-dependent. The following fix should work on v69 and 70 (enter it in a Chrome OS root shell):
Code:
sed -i 's|mount rootfs rootfs / remount bind ro|mount rootfs rootfs / remount bind rw|g' /opt/google/containers/android/rootfs/root/init.rc
After a reboot (or just rebooting Android), the container should mount as R/W as expected. Let me know if this doesn't work.
Nolirum said:
Yes, certainly you can root Android on Chrome OS. The rootfs of the Android container is read-only by default, so the method I've been using involves making a writeable copy of the Android rootfs .img in /usr/local, adding SuperSU (adding its binaries to /system/xbin, the SuperSU apk to /system/priv-app, and modifying init.rc to autoload daemonsu), then replacing the original Android rootfs .img file path with a symlink to the rooted one. In addition, a couple of flags (mount-as-read-only and font sharing) need to be changed in one or two of the /etc/init/arc* files (CrOS version dependent), and also the SElinux policy file needs to be patched.
I have written a script to automate the above procedure, if you would like to try it out you can do so by entering the following into the Chrome OS shell (then rebooting).
Code:
curl -Ls https://raw.githubusercontent.com/nolirium/aroc/onescript/RootandSEpatch.sh | sudo sh
You need to be in Dev mode to get into the shell (Ctrl+Alt+T; type 'shell'), and rootfs verification needs to be switched off to modify system files (the script will give you the command to do this, if you haven't already done it).
It would be prudent to make sure any important files are backed up prior to making any changes to the rootfs.
Edit: If any errors occur, or problems are are experienced after using the script, such as Android (apps) failing to load, it's usually not necessary to powerwash. The script makes a backup of the original Android system.raw.img, which can be restored with the following command:
Code:
sudo mv /opt/google/containers/android/system.raw.img.bk /opt/google/containers/android/system.raw.img
Click to expand...
Click to collapse
If it says no android system detected, I downloaded it in 2 parts from here: ( github(dot)com/nolirium/aroc ), followed the instructions, and then it worked for me.
Nolirum said:
Yes, depending on the Chrome OS version you're on, it's possible that the container's still being mounted read-only. They keep changing around some bits and pieces related to the container mount config with (almost) every new version release of the OS. There was a change that they made to config.json (which could be worked around by editing the file) a while back which broke the RW mount, but this was reverted quite quickly. Some other related changes have been made recently though, causing the issue to crop up again.
I've been reluctant to add something in to the script to deal with this read-only mount issue as yet, since the need for it has been CrOS version-dependent. The following fix should work on v69 and 70 (enter it in a Chrome OS root shell):
Code:
sed -i 's|mount rootfs rootfs / remount bind ro|mount rootfs rootfs / remount bind rw|g' /opt/google/containers/android/rootfs/root/init.rc
After a reboot (or just rebooting Android), the container should mount as R/W as expected. Let me know if this doesn't work.
Click to expand...
Click to collapse
thanks for all the help. I have chromebook plus v1,I am on chrome osversion 74. I tried to follow the instruction
but my android apps did not start after restarting. I tried doing it manually but i got stuck at remounting file system as read only. Please help if possible. Thanks again.
Hi,
I'm having problems with this. I have an HP Chromebook with an Intel cpu, Chrome OS Version 75.0.3770.144 (Official Build) (64-bit). When I run the scripts this is the output:
Setting 'ANDROID_DEBUGGABLE: true' and 'WRITABLE_MOUNT: true' in /usr/share/arc-setup/config.json
The file at /opt/google/containers/android/system.raw.img is already a symlink!
Removing symlink
Using /opt/google/containers/android/system.raw.img.bk
Creating new Android system image at /usr/local/Android_Images/system.raw.expanded.img
1814633472 bytes (1.8 GB, 1.7 GiB) copied, 13 s, 140 MB/s
1800000+0 records in
1800000+0 records out
1843200000 bytes (1.8 GB, 1.7 GiB) copied, 25.2601 s, 73.0 MB/s
Formatting system.raw.expanded.img as ext4 filesystem
mke2fs 1.44.1 (24-Mar-2018)
Discarding device blocks: done
Creating filesystem with 450000 4k blocks and 112672 inodes
Filesystem UUID: fe69179d-f136-475f-84de-007de70ff729
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Converting system.raw.expanded.img to sparse image
Mounting system.raw.expanded.img
SELinux successfully set to 'Permissive' temporarily
Copying Android system files
Formatting system.raw.expanded.img as ext4 filesystem
mke2fs 1.44.1 (24-Mar-2018)
Discarding device blocks: done
Creating filesystem with 450000 4k blocks and 112672 inodes
Filesystem UUID: fe69179d-f136-475f-84de-007de70ff729
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Converting system.raw.expanded.img to sparse image
Mounting system.raw.expanded.img
SELinux successfully set to 'Permissive' temporarily
Copying Android system files
Creating symlink to /usr/local/Android_Images/system.raw.expanded.img
SuperSU files not found in ~/Downloads! Attempting to download BusyBox and SuperSU now...
Downloading SuperSU-v2.82-SR3
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5810 100 5810 0 0 5624 0 0:00:01 0:00:01 --:--:-- 9078
Unexpected file size. Trying again...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
50 6756k 50 3407k 0 0 305k 0 0:00:22 0:00:11 0:00:11 311k
Unzipping SuperSU zip, and copying required directories to ~/Downloads.
/usr/local/bin/busybox: 1: /usr/local/bin/busybox: Syntax error: word unexpected (expecting ")")
cp: cannot stat 'common': No such file or directory
cp: cannot stat 'armv7': No such file or directory
Downloading SuperSU-v2.82-SR3
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6756k 100 6756k 0 0 328k 0 0:00:20 0:00:20 --:--:-- 351k
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
Copying sh from system/bin/sh to system/xbin/sugote-mksh and setting permissions and contexts
Adding extra files system/etc/.installed_su_daemon and system/etc/install-recovery.sh
cp: cannot stat '/home/chronos/user/Downloads/common/install-recovery.sh': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
Symlinking system/bin/install-recovery.sh to system/etc/install-recovery.sh
Adding system/bin/daemonsu-service.sh
cp: cannot stat '/home/chronos/user/Downloads/common/install-recovery.sh': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
Creating file init.super.rc in Android rootfs
Adding daemonsu service to init.super.rc
Adding 'import /init.super.rc' to existing init.rc
Substituting '|mount rootfs rootfs / remount bind rw' for '|mount rootfs rootfs / remount bind ro' in existing init.rc
A backup of init.rc will be stored as init.rc.old
sed: can't read /../init.rc: No such file or directory
Removing temporary files
Done!
Please check the output of this script for any errors.
Please reboot now, then run script 02SEPatch.sh.
[email protected] / $
Any help would be very much appreciated. I've done a good bit of searching and so far have been unable to figure what the problem is. Thanks alot, guys.
JR