Hi, if anyone would like to run a 4.3.1 Google OS on a Archos G9 80S device (and currently only this), download and extract this file:
19_01_2014-13_32_32
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
What's new ?
------------ since 19_01_2014-13_32_32 -------------
Last attempt to satisfy "H" model users. Wrong fstab definition file was used.
ArchosControlCenter: Alternate command for enabling disabling 3G service activation/deactivation.
------------ since 17_01_2014-20_17_32 -------------
KSM (Kernel samepage merging) support. (Enable it in CM performance options).
HDMI enable for 101 models too.
WLAN MAC address taken from device. Until now in my releases, the MAC address where the same for all devices. (gave some conflicts, when two devices are used in parallel).
------------ since 22_12_2013-13_29_20 -------------
Deactivated PCB temperature sensor. It is not part of the devices, and (my) default setting gives the cpufreq
module a wrong view of the situation. Now it should reduce the reboot which is caused by critical temp, by reducing core speed.
------------ since 19_12_2013-23_43_36 -------------
Using CPUFreq from 3.0.31 omapzoom reference kernel
Included app from @mordesku (modified by me) -> 3G should work!
Note that if you only pushed the image as update, please make sure to delete the /data/data/com.android.providers.telephony/databases/telephony.db
(adb shell rm /data/data/com.android.providers.telephony/databases/telephony.db) and reboot the device to rebuild.
I forgot to include the apns-conf.xml so there are no APN's available (as result no data connection can be established).
Removed my Widget to not affect the archos control center app
Some kernel changes.
Enabled zram and init.d
Initial support for H models (testing and patches are welcome).
Newest CM Updates: Changes since last release
------------ since 02_12_2013-22_56_07 -------------
Removed clicks when audio driver is closed
Reduced the volume a little bit to avoid scratches
Removed default dpi setting on build
Newest CM Updates: Changes since last release
------------ since 21_11_2013-21_45_53 -------------
Using new pvr library SGX-BIN: DDK binaries and KM source [email protected]
HWComposer 1.1 interface
No ICS audio blob anymore. Adapted omap upstream audio HAL.
Some internal audio extensions by TI (omap_enhancement)
Kernel audio sources updated to 3.0.31 omap upstream release.[/INDENT]
------------ since 08_11_2013-22_14_52 -------------
CM10.2
Upstream init.rc
TI Openlink WLAN driver R5.SP6.01
Temporary disabled ClockworkMod Recovery
A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
Initial A101s support.
Something I've not tried...
3G USB Stick is working.
Issues:
- GPS not reliable (as usual for every release....) -> After complete new system ("Reset Android & Storage") the GPS is working very good. Subsequent boots later it gets worse at my device(s):
My Workaround: Go into Settings->Apps->All->Google Service Framework and delete data and cache. Then reboot and GPS should e working. Also I get sufficient results with the GPS Toolbox App.
21_11_2013-21_45_53:
Microphone as degraded sound quality compared to the stock rom.
Some sound clicks here and there when system sounds are turned on.
Audio sound is a little bit quiet compared to the stock rom. (Needs to be adjusted by myself).
Can't test HDMI (both audio/video). (It's also not an use case for me). If someone would like to help....
HDMI scaling issues
"H" models doesn't seem to work.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Archive:
17_01_2014-20_17_32
22_12_2013-13_29_20
19_12_2013-23_43_36
02_12_2013-22_56_07
21_11_2013-21_45_53
08_11_2013-22_14_52
07_11_2013-22_53_33
Archos CM10.2 - 26_10_2013-23_26_11
Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?
mordesku said:
Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?
Click to expand...
Click to collapse
As usual for the custom Android releases for this archos device , they don't replace the original partitions. But it is not possible to run both in parallel. So practically yes, it replace the original system.
Quallenauge said:
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mordesku said:
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
Click to expand...
Click to collapse
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
(Just for reference, when using the update mechanism the file has to placed here:
Code:
sudo cp archos.ext4.update <Mount_Path>/data/[B]media[/B]/archos.ext4.update
)
Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4
mordesku said:
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4
Click to expand...
Click to collapse
Thanks for your reply. I corrected the paths in previous posts.
Is it stable for very day use???
Everithing working lie Cam and HW video?
Using it since yesterday. It's very smooth and fast. No freezes at all.
Sent from my ARCHOS 80G9 using Tapatalk 4
Installation on Mac OS X
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave
stealthdave said:
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave
Click to expand...
Click to collapse
Damn to install it yesterday i installed debian on virtualbox on my macbook
Sent from my ARCHOS 80G9 using Tapatalk 4
My tablet is still showing the snazzy CyanogenMod bootloader image after an hour and refuses to load the Android GUI. I tried starting the process over again with the same results. I am able to get to an adb shell and play around there, but Android never finishes loading. I'm running a G9 80S with 1GHz OMAP 4430 and 512MB of RAM. Logcat attached.
Hi,
thank you for building this and all your other ROMs.
Quallenauge said:
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/archos.ext4
Click to expand...
Click to collapse
This is inconsistent.
Is it local/ or data/local/?
I tried to install the ROM following your instructions.
I renamed "archos.ext4.update" to "archos.ext4".
I reset Android and Storage, exported the USB storage, on my machine it was mounted on /media/username/data.
I then used the following commands:
Code:
sudo mkdir /media/username/data/local
sudo cp archos.ext4 /media/username/data/local/
Then I selected "OK" in the tablet and "Flash Kernel and Initramfs" followed by:
Code:
sudo cp zImage /media/username/A80S_REC/
sudo cp initramfs.cpio.lzo /media/username/A80S_REC/
Then I rebooted the tablet.
Now the tablet was flashing the Archos logo for a second and then rebooting, in a loop.
So I guessed the local/ directory was wrong and I might have to use data/local/.
I repeated the steps above, replacing "local/" with "data/local".
This time the tablet didn't reboot in a loop, but I only got the static Archos logo, not the animated Archos logo or the CyanogenMod logo.
I probably missed a step or misread some instruction.
Any idea where I made the mistake?
@esque: Sorry for the confusion... Your first attempt was right:
Code:
sudo mkdir /media/moronoxyd/data/local
sudo cp archos.ext4 /media/moronoxyd/data/local/
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Just to be sure, reboot the tab and mount the drive and perform a
Code:
md5sum <Mount_Path>/local/archos.ext4
and verify that value with the image on your host.
If there are the same values, we have to find another solution for the problem.
@stealthdave: Your logcat file looks very close to the problem above (file image broken).
Quallenauge said:
@stealthdave: Your logcat file looks very close to the problem above (file image broken).
Click to expand...
Click to collapse
Yes, that was the issue. umount for everyone!!!
Thanks.
Great job, like buying a new tablet.
The only thing I would add is to sudo sync before unmounting.
Quallenauge said:
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Click to expand...
Click to collapse
D'oh! I knew I made a rookie mistake.
Yes, that did the trick.
Thanks Again!
Hi,
Great job.
Is there a possibility to have the same ROM for the 101 version ?
Regards
Sent from my Galaxy Nexus using xda premium
Hi,
After two days of using this rom I must say it is very fast and smooth. But on idle after 6 hours I got -40% battery drain. Also I can feel heat from it. Got installed only 2 apps and one game. Is there any chance to implement deep sleep in this rom, to minimize batery drain?
Related
The SoupKit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2
Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe
Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release
worked great. thanks for a great tool. easy to use.
Awesome...thank you..just set this up on my ubuntu netbook...going to try it today when I update twrp
Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install
Works great!
ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux
wojo797 said:
ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux
Click to expand...
Click to collapse
Yeah, when I updated the script, I forgot to change the permissions...
Give me a little while and I'll fix it for you.
3-16-2013: Fixed issue with permissions on the rootplus script
the issue wasnt with the rootplus it was with the soupkit itself the install.sh script
wojo797 said:
the issue wasnt with the rootplus it was with the soupkit itself the install.sh script
Click to expand...
Click to collapse
That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"
[OK thankOTE=soupmagnet;39303980]That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"[/QUOTE]
Ok thank you.. Appreciate the help and all then work...I'll try as soon as possible
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
Sorry for the inconvenience.
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons.
By the way, there is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon and the requirement to downgrade the stock bootloader before continuing with the 2nd bootloader install process.
Hi,
I'm totally new to linux, and i managed to install the latest Linux mint (v14.0) I was also able to connect to the internet and i downloaded both the soupkit and rootplus using linux. I extractred the files and doubled clicked on the install.sh as per the readme file however, after i double click it, all the contents of the folder disappear and i don't get any options as per the readme file. The same happens with the rootplus install.sh file, all the files disappear.
These are the steps i've followed.
Installed Linux Mint v14.0 on the system after making necessary partitions(ext4 journal)
Internet connectivity present.
Downloaded both the files into the downloads folder and extracted them
double clicked on the install.sh file and everything disappeared fro the respective folders.
Please guide me as i'm completely blank here.
Regards,
CD
Hi,
I was able to make it work. Instead of double clicking the .sh file, i opened the terminal window in the extracted folder, got super user access and executed this command:
sh install.sh
So now my kindle is rooted and ads free.
Thanks a lot @soupmagnet.
Regards,
CD
So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!
anacondo said:
So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!
Click to expand...
Click to collapse
Sorry to answer an old post but yes.
Ubuntu Touch 13.10 SAUCY Rom Triple Boot WebOS, Android, Ubuntu Touch (Or Quad if you need to)
09-27-2013 is the RootFS Date with apt-get dist-upgrade to 9-29-2013
Download Links Updated 09-29-2013 5:44 am central time
http://gdurl.com/d6Qn cm-10.1-20130929-UNOFFICIAL-tenderloin.zip (Install First Kernel\Ramdisk\System Partition)
http://gdurl.com/EnW8 saucy-preinstalled-touch-armhf.zip (Install Last Ubuntu Touch RootFS\Data Partition)
PARTITION CREATOR AND UNINSTALLER (From ACMEInstaller3 and ACMEUninstaller) Thanks Green!
http://www.gdriveurl.com/?idl=813809797536&out=2 UbuntuTouch_Partition_Creator
http://www.gdriveurl.com/?idl=613809797926&out=2 UbuntuTouch_UbuntuDesktop_Partition_Creator
http://www.gdriveurl.com/?idl=513809798298&out=2 UbuntuTouch_Uninstaller
http://www.gdriveurl.com/?idl=413809798725&out=2 UbuntuTouch_UbuntuDesktop_Uninstaller
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOW TO INSTALL!
You will need a little over 2 GB of space on your sdcard to devote to the new LVM Partiitons! This assumes you HAVE installed CyanogenMod (Android), ClockworkMod Recovery, MoBoot and still have WebOS. WebOS is a prerequisite for Audio. ALSO, you need novaterm. http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm AND it's good to have adb as well.
NOTE! If you have Ubuntu 11.04 - 13.XX Desktop Version
The Ubuntu Desktop LVM needs to be Uninstalled and Recreated. I have provided uImage files and Novacom to do this, or you can change the /etc/fstab file to have the correct device mapper paritition number.
Dealing with a small boot partition! It cannot hold all the uImages for WebOS, Android, Ubuntu Desktop, Ubuntu Touch, andClockworkMod at the same time. What I usually do is move the Ubuntu Touch kernel off of /boot to /sdcard (/media/internal in webos) before installing Ubuntu Touch, then move ClockworkMod to the /sdcard after installing Ubuntu Touch, and of course move the Ubuntu Desktop uImage file back to the /boot partition for Quad-Booting. You should only do this, if you know what you are doing, as having ClockworkMod on boot is handy. Know what you are doing or don't do it. (Which is why I should probably stay away from rom building!, haha) https://github.com/jshafer817/Ubunt...mportant files after compiling/data/etc/fstab
*IF YOU HAVE ALREADY INSTALLED THE ROM THAT WAS NOT DUAL-BOOT CAPABLE, YOU SHOULD REINSTALL ANDROID FIRST SINCE WE WIPED IT OUT
*Since we are dual-booting, we need to create 3 LVM Partitions that will use 2 GB of space from the sdcard*
1. Copy the RootFS.zip and the cm-10.zip file to the sdcard
2. Reboot into WebOS Recovery
3. novacom boot mem:// < UbuntuTouch_Partition_Creator
OR
novacom boot mem:// < UbuntuTouch_UbuntuDesktop_Partition_Creator (Requires 6.2 GB of Space, for Ubuntu Desktop 11.XX - 13.XX)
4. Reboot into ClockWorkMod to install the cm-10-*.zip FIRST and the RootFS zip LAST
5. Reboot and chose uImage.UbuntuTouch
Wait 3 minutes, while the touchpad boots. At some point adb will start to run. Eventually you should see a Unity Session..
If you didn't see a session!
a) reboot!
b) Eventually the backlight on the screen will shut off.. Touch the screen or hit the power button or home button some builds to turn the screen on. Still no session? Can you run android-chroot when you get into adb? When you login to adb it should say [email protected] and not BusyBox? You can also run /system/bin/logcat. Hold down the power button for 2 or 3 seconds and Ubuntu Touch will shutdown.
TO FORMAT UBUNTU TOUCH LVM PARTITIONS (in case your wondering create-partition.sh does this.. but what if you want to format after you install to do a reinstall??
novaterm into webos!
mkfs.ext4 /dev/store/ut-data
mkfs.ext3 /dev/store/ut-system
mkfs.ext3 /dev/store/ut-cache
TO REMOVE UBUNTU TOUCH LVM's AND KERNEL
novacom boot mem:// < UbuntuTouch_Uninstall
TO REMOVE UBUNTU TOUCH AND UBUNTU DESKTOP LVM's AND KERNEL
novacom boot mem:// < UbuntuTouch_UbuntuDesktop_Uninstall
Having problems installing WebOS Applications????
https://developer.palm.com/support/applicationupdate WebOS UpdateManager Certificate Fix
http://forum.xda-developers.com/showthread.php?p=42317438
There is an update to WebOS.. If you wipe your device after July 23rd 2013.. Then you must do this.
Ubuntu Touch Notes!
NOTE! If you have Ubuntu 11.04-13.10 NON-TOUCH installed, you will need to:
novacom boot mem:// < UbuntuTouch_UbuntuDesktop_Uninstall
*Built from Milaq's CM 10.1 Source WITHOUT JCSullins Bluetooth fixes
*Bluetooth and Sound come from the Ubuntu 11.04-13.10 Non touch. Mainly the upstart and executables. WebOS does get mounted for sound to get initialized. udev and pulse were patched.
*First Ubuntu Touch device running Saucy (Flipped Image) but with LVM Partitions. For this to work I had to compile lvm and e2label statically and use them in the ramdisk for Ubuntu.
How Saucy Works!?
Kernel is loaded with an Ubuntu Touch Ramdisk (Like normal Linux). Then the data partition is mounted as root, the system partition is mounted as /system. The LXC containter loads android based off of /system, then Ubuntu Touch Session loads. This is not a chroot like quantal.
What works:
*Camera
*Wifi
*Bluetooth
*Sound
*Accelerometer
Bugs and Beta\Alpha Stuff:
1. PulseAudio\GStreamer\Music App is not tied to the Media Service, so the music does not play with the screen turned off. GStreamer keeps playing, but you cannot hear sound unless powerd has turned the screen on and.. ??? Not worth changing until Ubuntu Touch becomes more.. finalized. Sometimes the music does not come back on after a long sleep?
Workarounds:
sudo service powerd stop (with the backlight turned on)
2. Bluetooth only works in terminal
a) this is because Bluetooth Settings has not been written to Ubuntu Touch
3. Camera App only works one time. Needs to be mirrored.. Again. Long story!
4. Brightness or Backlight settings???
as root!
echo "0-255" > /sys/class/leds/lcd-backlight/brightness
to set the screen brightness. 0-255 is a range of values you should use.
0 will turn off the backlight
255 is full birghtness
and of course.. service powerd stop while the screen is on will stop powerd from turning off the backlight if idle.
5. Touchscreen finger liftoff does not always get detected at boot correctly. Need to talk to ubunu-devel about that.? CM-TEAM?? Hmm.. Reboot and try again!
6. Browser cannot download files. Browser cannot play videos because the latest gstreamer "has not landed yet"..
7. 720P H.264 is choppy? 480p plays fine.. Waiting for more updates.
APPARMOR NOTE: Since 2.6.35 Kernel does not have apparmor, we are using /usr/bin/aa-strip with crontab to run every minute. So if you install a click app and cannot run it, wait a minute! sed -i "s/aa-exec.*-- //g" /home/phablet/.local/share/applications/*.desktop
OPEN-SSH NOTES:
Recently they did something to openssh. Do this to install.
apt-get install --reinstall openssh-server
service ssh start (every boot?)
If powerd turns off the backlight, it suspends your ssh session. There is some code in the wifi modules that I believe is causing it. Work on that later.. or disable powerd and turn the lights off to save battery power or backlight by reading brightness notes above.
MTP-SERVER NOTE
mtp-server has been disabled.. want to enable it? As root!
cd /etc/init
mv ../mtp* .
cd /usr/share/upstart/sessions
mv ../mpt* .
reboot
When you do, don't expect adb to work... In Ubuntu 13.10 Desktop, you see the /home/phablet get Mounted on the filesystem via mtp.. I haven't messed with the Windows Driver.. I messed with the google one and changed the pid and vid, and.. no device was found when I ran adb.. so.. perhaps mtp shuts down adb on the touchpad.. I think that was in the upstart file though.. mtp-server-bootup.conf, etc.
MORE USEFUL NOTES
How to copy files with novaterm?
cat filename | novaterm put file:///put/full/destination/path/filename (push example) tested
novaterm get file:///full/destination/path/filename (pull example) untested
novaterm get file:///full/destination/path/filename > filename (pull example) untested
How do I compile uimage-extract to extract a kernel.img and ramdisk.img from a uImage file (boot.img)?
git clone https://github.com/jcsullins/moboot
cd moboot/tools
gcc -o uimage-extract uimage-extract.c -lz
How do I extract the kernel image and initramfs from a uImage file?
./uimage-extract uImage.filename (from inside moboot tools folder)
How to unpack and repack gzip ramdisk images?
mkdir newramdisk
cd newramdisk
gunzip -c ../your-ramdisk-file | cpio -i
make changes, next command is to pack a new ramdisk.img
find . | cpio -o -H newc | gzip > ../newramdisk.img
How to unpack and repack lzma ramdisk images? (I used lzma)
mkdir newramdisk
cd newramdisk
lzma -dc ../newramdisk.img | cpio -i
make changes, next command is to pack a new ramdisk.img
find . | cpio -o -H newc | lzma > ../your-ramdisk-file
How to create a moboot compatible kernel?
mkimage -A arm -O linux -T kernel -C none -a 0x40208000 -e 0x40208000 -n "Kernel" -d kernel.img uImage
mkimage -A arm -O linux -T ramdisk -C none -a 0x60000000 -e 0x60000000 -n "Image" -d ramdisk.img uRamdisk
mkimage -A arm -O linux -T multi -a 0x40208000 -e 0x40208000 -C none -n "multi image" -d uImage:uRamdisk uImage.CyanogenMod.new
How to connect to an open-wifi network without Unity as root?
adb shell
sudo su
service network-manager stop
iwconfig wlan0 essid "essid-you-want-to-connect-to"
ifconfig wlan0 192.168.X.X netmask 255.255.255.0 up
route add default gw 192.168.X.X
sed -i '$ a nameserver 8.8.8.8' /etc/resolv.conf
you should be on the net.
How can I create my own saucy-preinstalled-touch-arm.tar.gz to go into the .zip? (from a runnng device)
adb shell
cd /data/ubuntu
sudo tar --preserve-permissions -zcvf /sdcard/saucy-preinstalled-touch-armhf.tar.gz *
exit
adb pull /sdcard/saucy-preinstalled-touch-armhf.tar.gz .
now put that file in the .zip.
How do I untar the saucy-preinstalled-touch-armhf.tar.gz file?
place saucy-preinstalled-touch-armhf.tar.gz in the folder you want to be in, and go to that folder in terminal
mkdir rootfs
cd rootfs
sudo tar --preserve-permissions -zxvf ../saucy-preinstalled-touch-armhf.tar.gz
sudo make your changes as root, be mindful of permissions.
How do I swap my kernels to quad-boot? (With webOS)
a)Before you install Ubuntu Touch, move a kernel from /boot to /media/internal
novaterm
mount -o remount,rw /boot
mv /boot/uImage.Ubuntu13 /media/internal (or uImage.Ubuntu)
mount -o remount,rw /boot
b) After you install Ubuntu Touch, move it back, but remove ClockworkMod (know what you are doing are don't do this)
novaterm
mount -o remount,rw /boot
mv /boot/uImage.ClockworkMod /media/internal
mv /media/internal/uImage.Ubuntu13 /boot
sync
mount -o remount,ro /boot
How can I run webOS Doctor after all this and just start all over factory clean?
http://forum.xda-developers.com/showthread.php?t=1564938 3rd post but I would skip the creation of /dev/store/cm-* partitions. Be sure to delete cm-data, cm-system, cm-cache, ut-data, ut-system, ut-cache, and ubuntu-store if you have it. Delete them all! Then recreate the lvm. If you need to recreate Android partitions do that with AcmeInstaller ie the usual way to install Android. You must start with WebOS 3.0.0 and then you can do 3.0.5. Be sure to say thanks on that post.
Thanks to:
Ogra (ubuntu-touch, huge thanks!), castrwilliam (ubuntu desktop rom), CalcProgrammer (ubuntu desktop rom), crimsonredmk (archlinux rom), Flemmard (cm team "resizing the boot partition would be stupid", yep), Mystikal57 (sound fixes in desktop that really helped get it going), JCSullins (moboot, cm team, all sorts of stuff), Dorregray (camera fixes I need to reimplement), w-flo (ubuntu-touch), drmarble (ubuntu-touch, cyanogenmod-touchpad, big thanks to him).. and others from the #ubuntu-touch irc channel and Ubuntu 11.04-13.10 threads, cyanogenmod team, etc... "I stand on the shoulders of giants"
Look at the old Ubuntu Touch thread I started around page 17 for more in depth notes on what I did.
OR
https://github.com/jshafer817/UbuntuTouch
I am NOT a developer!!!!
Wow this is exciting news for my little tablet... Been messing around with 13.04f so this will be a blast.
Sent from my Galaxy Nexus using Tapatalk 2
Once you release your build I'll try to iron out some of the bugs.
Sent from my LG-LS970 using xda app-developers app
blmvxer said:
Once you release your build I'll try to iron out some of the bugs.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Thanks! I am going to work on the camera being mirrored and flipped for the next 3 hours or so.. after that.. oh well! =)
Just be sure to post your fixes.
Will do! good luck!! Can't wait to boot this up and get to work!
Sent from my LG-LS970 using xda app-developers app
Any update on the camera bug... Get that baby squashed yet
Sent from my Galaxy Nexus using Tapatalk 2
kicker22004 said:
Any update on the camera bug... Get that baby squashed yet
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Honestly.. a little bit.. Spent all day trying to figure out what file makes the change.. as this has to be done in cm10.1 not ubuntu.
camera.msm8660.so
About 1 try left before giving up.. In the meantime I created a github... Will be very soon. Before I go to sleep again.. Brewing Coffee..
Took a 5 hour nap today though! Sweet!
I found a line for CameraHAL.cpp and I swapped 3/2 to 2/3 and got an ugly green screen. I am trying to swap previewWidth and Height now.. If nothing happens.. I give up and will start to package. FAILED.
The last try will be just telling it to be a front facing camea, as that would explain the mirror, flipping??? New Idea sounds better!
if (read_mode_from_config("preview_mode") == 1) {
info->facing = CAMERA_FACING_BACK;
}
to (remove the if)
info->facing = CAMERA_FACING_BACK; OR?
info->facing = CAMERA_FACING_FRONT;?
Testing both then packaging. dmesg seems to say we are using preview mode 2 so maybe add the 2?
First try:
info->facing = CAMERA_FACING_FRONT; if no change occurs in image (NO CHANG OCCURED), then perhaps Ubuntu Touch thinks the camera IS front facing.. so the next try will be facing back hard coded.. look for a change, if it does.. try adding the 2 with the if statement. Or just keep it this way... as a change would be GREAT.
from dmesg:
msm_camio_set_perf_lvl: S_PREVIEW rc = 0
VFE opertaion mode = 0x2, output mode = 0x5
http://developer.android.com/reference/android/hardware/Camera.html !
android::HAL_getCameraInfo(camera_id, &cameraInfo);
info->facing = cameraInfo.facing;
info->orientation = cameraInfo.orientation;
info->facing = CAMERA_FACING_BACK;
info->orientation = 90;
vs
info->orientation = 180;
Going to try this now.. as the camera WAS being a front camera. Image is no longer mirrored incorrectly. Now we just have to find the right orientation.
:good:
Nice work. Power naps are the best for figuring out problems
Sent from my Galaxy Nexus using Tapatalk 2
Alright.... will be releasing today...
Got the rotation better with... compass\accel.. not the camera...
Going to try a couple more things....
jshafer817 said:
Alright.... will be releasing today...
Got the rotation better with... compass\accel.. not the camera...
Going to try a couple more things....
Click to expand...
Click to collapse
I'm ready!!!!
Sent from my LG-LS970 using xda app-developers app
And I'm charging my tablet lol
Sent from my Galaxy Nexus using Tapatalk 2
Okay... I think we will need to recompile the camera app to change to portrait\landscape correctly...
So.. Rom Released!
I will be testing within an hour once I doctor my tablet and resize the partitions.
Sent from my LG-LS970 using xda app-developers app
---------- Post added at 09:40 PM ---------- Previous post was at 09:34 PM ----------
When you compile your next kernel for your ROM, if you do, will you add fstrim?. As I read there is slow graphics. Trimming the partitions should speed up things.
Sent from my LG-LS970 using xda app-developers app
I'm away from the house...dang!!
Sent from my Galaxy Nexus using Tapatalk 2
Camera App Info!
VideoOutput {
id: viewFinder
property bool shouldBeCentered: device.isLandscape
property real anchoredY: viewFinderGeometry.y * (device.isInverted ? +1 : -1)
property real anchoredX: viewFinderGeometry.x * (device.isInverted ? +1 : -1)
x: viewFinder.shouldBeCentered ? 0 : viewFinder.anchoredX
y: viewFinder.shouldBeCentered || device.naturalOrientation === "landscape" ?
0 : viewFinder.anchoredY
width: parent.width
height: parent.height
source: camera
/* This rotation need to be applied since the camera hardware in the
Galaxy Nexus phone is mounted at an angle inside the device, so the video
feed is rotated too.
FIXME: This should come from a system configuration option so that we
don't have to have a different codebase for each different device we want
to run on */
orientation: device.naturalOrientation === "portrait" ? -90 : 0
/* Convenience item tracking the real position and size of the real video feed.
Having this helps since these values depend on a lot of rules:
- the feed is automatically scaled to fit the viewfinder
- the viewfinder might apply a rotation to the feed, depending on device orientation
- the resolution and aspect ratio of the feed changes depending on the active camera
The item is also separated in a component so it can be unit tested.
*/
Ah HA!!!
Is a Doctor a must? all i'm getting is a black screen right after CID changes faces. I've let it sit for 10 minutes and still same results, Reformatted system,data,cache and re installed in order...same?
A few questions
Been using Ubuntu on my Laptop and liked it. I'm looking to try it out on my TouchPad now but I have a few questions.
Does this replace Android? Or does this create new partitions for Ubuntu and allows triple boot from moboot?
I've notice a few installation instructions saying this is 'based on CM10'. Is this Ubuntu on top of the Android core or a pure Ubuntu installation?
Thanks for clarifying this for me in advance.
Fr3nZy said:
Been using Ubuntu on my Laptop and liked it. I'm looking to try it out on my TouchPad now but I have a few questions.
Does this replace Android? Or does this create new partitions for Ubuntu and allows triple boot from moboot?
I've notice a few installation instructions saying this is 'based on CM10'. Is this Ubuntu on top of the Android core or a pure Ubuntu installation?
Thanks for clarifying this for me in advance.
Click to expand...
Click to collapse
This replaces Android. Backup is your friend!
Thanks to the op for continued development of this rom.
---------- Post added at 08:49 AM ---------- Previous post was at 07:53 AM ----------
kicker22004 said:
Is a Doctor a must? all i'm getting is a black screen right after CID changes faces. I've let it sit for 10 minutes and still same results, Reformatted system,data,cache and re installed in order...same?
Click to expand...
Click to collapse
Same issue here ....
Edit: success! Booted up after a couple of minutes after a reboot.
However, some issues - rotation not working and keyboard is messed up. It comes up in the top left hand corner of the touchpad when in landscape mode, see attached pictures.
Thanks
Well tomorrow I'll give it another try
Sent from my Galaxy Nexus using Tapatalk 2
Hi, if anyone would like to run a 5.1.x Google OS on a Archos G9 80S device (and currently basically verified only with this), download and extract the file
16_12_2015-16_26_24
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important for the first installation. Updating a existing installation (same major version) doesn't require this step !).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient at least ~20 minutes for the first run!
!!Update!!: If you have already installed CM12.0 then it may possible that you don't have to delete the data partition. You only have to copy the kernel/initramfs and ext4 file. I use the command for the last step:
Code:
adb push archos.ext4.update /data/media/ && adb reboot
What's new ?
------------ since 16_12_2015-16_26_24 -------------
Added usual CM updates. -> Also this release include the latest security fixes.
------------ since 05_08_2015-05_48_32 -------------
Added usual CM updates. (See included changelog for details) -> Also this release include the latest security fixes.
Added the 99Performance file from BlackGunZ Big thanks!
------------ since 31_05_2015-19_39_10 -------------
Added usual CM updates. (See included changelog for details)
Add *some* memory improvements, suggested by trevd (big thanks!)
*Maybe last release*
------------ since 23_04_2015-22_05_13 -------------
Initial release.
Re-Enabled Non-PIE Support to support the gps module.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Thanks: @stargo @Hashcode @trevd
@CM community @all the cool omap4 hackers where I taken some code and inspirations !!!
Without these peoples, It would not so easy to make some (working) builds of the CM-12.1.
Archive:
31_05_2015-19_39_10
23_04_2015-22_05_13
XDA:DevDB Information
Archos G9 CyanogenMod 12.1, ROM for the Archos Gen9
Contributors
Quallenauge
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2015-04-24
Last Updated 2015-04-24
Thanks for keeping this old tablet going! I'll give it a try this weekend. :good:
jawiler said:
Thanks for keeping this old tablet going! I'll give it a try this weekend. :good:
Click to expand...
Click to collapse
Hi Quallenauge,
I've tried installing this version, but it just goes to a black screen for over 1/2-3/4 hour. I've tried downloading from both sites and checked the MD5SUMs and everything checks out. I went with a clean install.. I've installed your previous versions without any problems. Any ideas?
thanks
Nevermind, I tried a different computer and it worked this time
jawiler said:
Hi Quallenauge,
I've tried installing this version, but it just goes to a black screen for over 1/2-3/4 hour. I've tried downloading from both sites and checked the MD5SUMs and everything checks out. I went with a clean install.. I've installed your previous versions without any problems. Any ideas?
thanks
Nevermind, I tried a different computer and it worked this time
Click to expand...
Click to collapse
Mostly this error comes into play if the kernel&initramfs step or the update package is transferred and the mass storage drive is not cleanly unmounted.
@Quallenauge I knew I should have waited as I've just built cm-12.0 .... I even used your build environment script. Slightly unorthodox but it gets the Job done :good:
Anyway couple of notes from my side .. a bit of dex_preopting does wonders for the boot time
In the full_archos_g9.mk or similar
Code:
WITH_DEXPREOPT := true
WITH_DEXPREOPT_PIC := true
PRODUCT_DEX_PREOPT_BOOT_FLAGS := --compiler-filter=everything
PRODUCT_DEX_PREOPT_DEFAULT_FLAGS := --compiler-filter=everything
$(call add-product-dex-preopt-module-config,services,--compiler-filter=everything)
Not 100% sure that WITH_DEXPREOPT_PIC is required I threw it in anyway...
I also read up on low memory optimizations ( tricks/hacks ) , dropped all the wallpapers and a ton other other apps that I'm not using
It's pretty smooth ... That can be done at runtime by anyone who is feeling brave .
Hackon folks!
trevd
trevd said:
@Quallenauge I also read up on low memory optimizations ( tricks/hacks ) , dropped all the wallpapers and a ton other other apps that I'm not using. It's pretty smooth ... That can be done at runtime by anyone who is feeling brave .
Click to expand...
Click to collapse
Hi @trevd, I always follow your advice therefore I wonder what changes have you applied to optimize this rom? Could you give us any clue?
Thanks in advance
@Quallenauge First, thank you for your great port and efforts ! God bless you.
I found how to fix the root problem by doing some researches. For so, I edited the following line persist.sys.root_access which is present in build.prop file like this :
Code:
persist.sys.root_access=1
After a reboot, my tablet is correctly rooted and Archos Control Panel enables normally the deep sleep mode at boot.
Have a good day !
Hi! Any chance, to use working USB Stick?
BlackGunZ said:
I found how to fix the root problem by doing some researches. For so, I edited the following line persist.sys.root_access which is present in build.prop file like this
Click to expand...
Click to collapse
Hey, could you explain how you do that?
I have CM 12.1 installed on my Archos 80 G9, ADB is working and when I use 'adb shell' I'm supposedly root but can not write to /system.
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
esque said:
Hey, could you explain how you do that?
I have CM 12.1 installed on my Archos 80 G9, ADB is working and when I use 'adb shell' I'm supposedly root but can not write to /system.
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
Click to expand...
Click to collapse
Of course ! The most secure method is to edit the build.prop with CM File Manager.
Before, using ADB put this command after "adb shell" to mount your /system partition RW. After, do the steps I said below :
Code:
mount -o remount,rw /
First, open the file manager. Then, access to the app's options by taping on its icon at the left and choosing after that its settings icon, which is present at the left down side. Go to Advanced section and tap on Access mode next, choose Root access by this way the app will ask root permissions and a pop-up will appear to accept it. You will be redirected to the root (/ directory) of your Archos, scroll down again and go to /system directory. Screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Secondly, tap on your build.prop file and open it with the file manager's text editor. Choose the line persist.sys.root_access, delete the "3" value and put "1" instead. Screenshots :
Finally, save the file and reboot your phone. Voilà !
esque said:
I can pull the build.prop and change it, but I don't know how to put it back onto /system.
Click to expand...
Click to collapse
Do not forget to change file ownership and permission after pushing it back - or else you'll get a bootloop.
Since you do not know how to remount filesystem, I'd second @BlackGunZ and recommend using any root file editor on android to avoid bootloops and reflashing android (as opposed to adb pull/push).
Bor-ka said:
Do not forget to change file ownership and permission after pushing it back - or else you'll get a bootloop.
Since you do not know how to remount filesystem, I'd second @BlackGunZ and recommend using any root file editor on android to avoid bootloops and reflashing android (as opposed to adb pull/push).
Click to expand...
Click to collapse
That's why I suggested him to use CM File Manager, you're right sir.
@Quallenauge
JustArchi updated his ArchiDroid Optimizations for Lollipop (CyanogenMod). Can they be useful ?
I would really like to try this rom, can anyone help me with a step by step guild for installation, kinda new to installing in this fashion.
i ran the wubi installer to dual boot windows/linux
using ubuntu desktop.
need to know what i need to install prior and how to install it.
Pm me please, i don't want to mock-up the development page
thanks in advance
am i using terminal and going to the usb directory then using these commands?
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
@toolhas4degrees
For Windows, check the quote below and I can confirm that it works (I always use it), but for Linux I can't provide you a help as I don't have it.
taninos said:
Install this rom or other roms using Windows is pretty easy with Ext2Fsd Open Source Project ( it works over Win2k, Winxp, Vista, Win7, Win8, Server 2003, Server 2008/R2). Install Ext2Fsd on your PC and follow the next steps below to achieve this purpose. Neither this tablet drivers nor ADB nor a linux virtualized on Windows are needed.
Steps:
00 install Ext2Fsd
01 reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!)
02 reboot into SDE menu and under Developer Edition Mernu -> "Export Data Partition"
03 connect your Tablet with your PC
04 start Ext2Fsd (ext2 volume manager interface). You should see your local drives and a extra one which is the Linux partition
05 mark that partition and press F7
06 start the service and be sure to check the "Enable writing support for ext3 volumes" and uncheck "Mount all volumes in read-only mode. Press apply
07 again mark your linux partition and press F3 and uncheck "Mount volume in read only mode"
08 now you should see the partition under "myComputer". Open it and if you reseted "Reset Android & Storage" you should see 2 Folders ("media" and "lost+found")
09 make a new folder called "local"
10 rename the archos.ext4.update to archos.ext4 and copy it into "local" folder
11 unmount the linux partition as you would do with any usb drive and then press ok on your tablet
12 go to "Developer Edition Menu" and choose "Flash Kernel and Initramfs"
13 a new drive will appear under "my computer". Copy zImage and initramfs.cpio.lzo to it and press ok
14 reboot your tablet and after a couple of seconds you should see the Archos logo and then Cyanogen logo
Click to expand...
Click to collapse
BlackGunZ said:
For Windows, check the quote below and I can confirm that it works...
Click to expand...
Click to collapse
It is a tad incomplete
11a. go to "Developer Edition Menu" and choose "Remove android kernel" (if not present - skip this step)
Last release? How about working USB stick?
BlackGunZ said:
Of course ! The most secure method is to edit the build.prop with CM File Manager.
Before, using ADB put this command after "adb shell" to mount your /system partition RW. After, do the steps I said below :
Code:
mount -o remount,rw /
First, open the file manager. Then, access to the app's options by taping on its icon at the left and choosing after that its settings icon, which is present at the left down side. Go to Advanced section and tap on Access mode next, choose Root access by this way the app will ask root permissions and a pop-up will appear to accept it. You will be redirected to the root (/ directory) of your Archos, scroll down again and go to /system directory. Screenshots :
Secondly, tap on your build.prop file and open it with the file manager's text editor. Choose the line persist.sys.root_access, delete the "3" value and put "1" instead. Screenshots :
Finally, save the file and reboot your phone. Voilà !
Click to expand...
Click to collapse
Hi
I've tried your method but I can't select root access in cm file manager. It does not work. How can I do ? Any idea ?
Thanks in advance
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk
sashokmc said:
Last release? How about working USB stick?
Click to expand...
Click to collapse
The last release is the one which is present in the OP, for an update we have to wait ! I didn't test the USB stick, sorry. ^^'
ladalgigi said:
Hi
I've tried your method but I can't select root access in cm file manager. It does not work. How can I do ? Any idea ?
Thanks in advance
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk
Click to expand...
Click to collapse
Exit CM File Manager, go to Settings, Developer Options and turn off the root permissions. Then, switch on again the root access to "ADB and applications" and try again
BlackGunZ said:
The last release is the one which is present in the OP, for an update we have to wait ! I didn't test the USB stick, sorry. ^^'
Exit CM File Manager, go to Settings, Developer Options and turn off the root permissions. Then, switch on again the root access to "ADB and applications" and try again
Click to expand...
Click to collapse
Thank you very much ! It works !
Very great ROM
Ladalgigi
Envoyé de mon ARCHOS 101G9 en utilisant Tapatalk
Donate a coffee to support development:
Donate via PayPal to serdeliuk
_______________________________
[UPDATE 22 Jan 2022]
- partial fix for ACPI tables which allow to boot windows
- added startup.nsh to automatically run in shell
-----
Hello,
I started to port EDK2 to my Lavender, Xiaomi Redmi Note 7 in order to bring Windows to this device.
So far i was able to fix ClockDxe that makes, for the first time, the eMMC working on a EDK2 port.
The device is able to boot Windows PE from eMMC
I am still working to fix USB for boot, mouse and keyboard in the first phase.
Anyone interested can download my buttons and clocks patches and build his own EDK2 port from my GitHub repo at https://github.com/serdeliuk/edk2-lavender
Best regards,
Marc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enable Debug
hello, I tried to compile, all look normal but on the end this happend
I do not know what is wrong, please can you help me.
Samuel Ladziansky said:
hello, I tried to compile, all look normal but on the end this happend
View attachment 5469915
I do not know what is wrong, please can you help me.
Click to expand...
Click to collapse
Hi,
You may need to edit edk2-lavender/RedmiNote7Pkg/RedmiNote7Pkg.dsc
and uncomment the line below that contain RegisterFilterLib
Code:
[LibraryClasses]
# RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
VariablePolicyHelperLib|MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.inf
serdeliuk said:
Hi,
You may need to edit edk2-lavender/RedmiNote7Pkg/RedmiNote7Pkg.dsc
and uncomment the line below that contain RegisterFilterLib
Code:
[LibraryClasses]
# RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
VariablePolicyHelperLib|MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.inf
Click to expand...
Click to collapse
Thanks I go to try it
Now it compiled and I tried to boot via "fastboot boot uefi.img" but nothing shows, after that I flashed it to boot partition and still nothing, I need put some operating system on some partition because it tries booting something? Or is something other wrong.
Thanks for reply.
Now works I use wrong (older) version of xbl.
Samuel Ladziansky said:
Now it compiled and I tried to boot via "fastboot boot uefi.img" but nothing shows, after that I flashed it to boot partition and still nothing, I need put some operating system on some partition because it tries booting something? Or is something other wrong.
Thanks for reply.
Click to expand...
Click to collapse
I suppose that you have xiaomi redmi note 7 (lavender) right? If so, the uefi.img should properly boot to uefi shell, if you have a fat32 efi partition on your device with windows will try to load that windows, but the actual state of acpi tables freezes windows during boot.
You may need to enable serialframebuffer and properly set the edk2 debug level to see what is going on.
Yes, I have redmi note 7 (lavender), I tried boot windows and what you said happened, windows freze at boot.
And I do not know where I enable serialframebuffer or set that debug level. I gonna try to find it.
Samuel Ladziansky said:
Yes, I have redmi note 7 (lavender), I tried boot windows and what you said happened, windows freze at boot.
And I do not know where I enable serialframebuffer or set that debug level. I gonna try to find it.
Click to expand...
Click to collapse
good, then you need to replace acpi tables from RedmiNote7Pkg/AcpiTables with the ones from msm8998 then modify the edk2- lavender/RedmiNote7Pkg/RedmiNote7Pkg.fdf accordingly, yo ucan take whole acpitable section from msm8998 edk2 port, right now i am not yet done with my acpitable, but that one should work
1. Install dependencies
```
# On Ubuntu 18.04
sudo apt install -y build-essential uuid-dev iasl git nasm python3-distutils gcc-aarch64-linux-gnu abootimg bspatch p7zip-full zip python-pip
```
```
# On Debian 11
sudo apt install -y build-essential uuid-dev iasl git nasm python3-distutils gcc-aarch64-linux-gnu abootimg bspatch p7zip-full zip pip
```
```
sudo pip install uefi_firmware
```
2. Clone edk2 and edk2-platforms repositories
```
git clone https://github.com/tianocore/edk2.git --recursive
git clone https://github.com/tianocore/edk2-platforms.git
```
3. Download Released File and Unzip
```
wget https://github.com/serdeliuk/edk2-lavender/releases/download/2/edk2-lavender.0.0.2.zip
unzip edk2-lavender.0.0.2.zip
```
4. Edit ` edk2-lavender/RedmiNote7Pkg/RedmiNote7Pkg.dsc`. uncomment the line below that contain RegisterFilterLib
```
[LibraryClasses]
# RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
```
```
[LibraryClasses]
RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
```
5. Place your `xbl.elf` extracted from a firmware update in xbl folder
6. Run `bash xbl-extract.sh` inside xbl folder
7. Run `bash xbl-extract.sh` inside xbl folder
8. Run ` make -C your_path/edk2-lavender/../edk2/BaseTools/Source/C `
9. Run ` bash build.sh `
10. Run ` fastboot flash boot uefi.img `
Samuel Ladziansky said:
Yes, I have redmi note 7 (lavender), I tried boot windows and what you said happened, windows freze at boot.
And I do not know where I enable serialframebuffer or set that debug level. I gonna try to find it.
Click to expand...
Click to collapse
Acpi is broken in this port. So you can use this port: https://github.com/XRedCubeX/edk2-jasmine
Delete jasmine_sprout.dtb, copy lavender.dtb from edk2-lavender to edk2-jasmine and rename lavender.dtb as jasmine_sprout.dtb. Then compile. Windows should boot.
mark251107 said:
Acpi is broken in this port. So you can use this port: https://github.com/XRedCubeX/edk2-jasmine
Delete jasmine_sprout.dtb, copy lavender.dtb from edk2-lavender to edk2-jasmine and rename lavender.dtb as jasmine_sprout.dtb. Then compile. Windows should boot.
Click to expand...
Click to collapse
Thanks, the ACPI problem was explained in post #9, if you have a fix for ACPI tables, other than to suggest to use different repo for a different device please share with us?
I have published a new release that has a partial fix for ACPI tables which allow to boot windows, also added startup.nsh to automatically run in shell
hello again
I tried to replace those ACPI tables as just the folder where they were, but it still didn't work for me and later I didn't have time to try it again.
But still, even though I compiled this new version, I can't boot windows. I added "UseBootProcessorOnly" to the BCD as Fxsheep wrote on his port on MI6. So far I've been trying to boot from BOOT.WIM but it's stuck on the windows logo, now I'm going to try to extract the wim file into the userdata partition and modify the BCD to boot it. I hope it will run.
theory one:
I think when I tried to boot from wim file once when is loaded in to memory and logo shows up, the memory just gone or lost that files.
theory 2:
Can the windows get stuck on bootlogo beause I have inserted SD Card? I asking because I do not know if windows get access to the device or it have bad information about that.
I come across the fact that whether by chance there is the same effect as when the HDD is damaged on the PC and the BIOS / UEFI will remain chopped on the first screen, if you know what I mean
Samuel Ladziansky said:
hello again
I tried to replace those ACPI tables as just the folder where they were, but it still didn't work for me and later I didn't have time to try it again.
But still, even though I compiled this new version, I can't boot windows. I added "UseBootProcessorOnly" to the BCD as Fxsheep wrote on his port on MI6. So far I've been trying to boot from BOOT.WIM but it's stuck on the windows logo, now I'm going to try to extract the wim file into the userdata partition and modify the BCD to boot it. I hope it will run.
theory one:
I think when I tried to boot from wim file once when is loaded in to memory and logo shows up, the memory just gone or lost that files.
theory 2:
Can the windows get stuck on bootlogo beause I have inserted SD Card? I asking because I do not know if windows get access to the device or it have bad information about that.
I come across the fact that whether by chance there is the same effect as when the HDD is damaged on the PC and the BIOS / UEFI will remain chopped on the first screen, if you know what I mean
Click to expand...
Click to collapse
I just re-tested the edk2-lavender.0.0.3.zip version, should work out of the box, see the image, that windows was just booted now
You must have EFI folder and should be complete, you can find a minimal bootable winPE as the one i used in the attached image to test, i cant recall where i found the minimal winPE iso image.....
Also, you can test the installer itself download win10iso with hXXs://uupdump.net/ then mount the iso, copy EFI folder and all other folders to your fat32 partition the installer should boot
I added an sdcard too, does not matter, windows boot
I have iso from that page and I trying. So you did not change any BCD or other files, and how long time to take boot?
by the way it so cool see Rn7 with windows booted
serdeliuk said:
I just re-tested the edk2-lavender.0.0.3.zip version, should work out of the box, see the image, that windows was just booted now
You must have EFI folder and should be complete, you can find a minimal bootable winPE as the one i used in the attached image to test, i cant recall where i found the minimal winPE iso image.....
Also, you can test the installer itself download win10iso with hXXs://uupdump.net/ then mount the iso, copy EFI folder and all other folders to your fat32 partition the installer should boot
View attachment 5519759
Click to expand...
Click to collapse
I will write when I can boot it.
thanks for help
Samuel Ladziansky said:
I will write when I can boot it.
thanks for help
Click to expand...
Click to collapse
that full desktop from the previous image take approx 80 seconds from phone startup (volUP+power) to complete desktop load (full taskbar)
i tested the windows installer, untouched, should boot, that image (win10desktop) is as ii was downloaded, the winPE image the 200MB one ( the one just with terminal) should boot untouched too, please be sure you use v.0.0.3 and not use files from that version copied to another version, possible i changed a lot in fdf/dsc files
serdeliuk said:
that full desktop from the previous image take approx 80 seconds from phone startup (volUP+power) to complete desktop load (full taskbar)
i tested the windows installer, untouched, should boot, that image (win10desktop) is as ii was downloaded, the winPE image the 200MB one ( the one just with terminal) should boot untouched too, please be sure you use v.0.0.3 and not use files from that version copied to another version, possible i changed a lot in fdf/dsc files
Click to expand...
Click to collapse
Is mater where I flash the uefi.img? I have flashed it in to boot partition, but you say (volUP+power) thats for recovery.
+ I get in to this stage.
Ubuntu Touch (ubports) for the Galaxy A5/7 2017
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it!
Source code:Device tree: https://github.com/Exynos7880-Linux/samsung-exynos7880
Kernel: https://github.com/Exynos7880-Linux/android_kernel_samsung_universal7880
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera fixed in V3
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that Fixed in V3
MTP Fixed in V3
Untested:
NFC
Miracast
A7, drivers have been fixed but no real world testing has been done
???
What works:
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:
Spoiler: Using SSH and logcat
How to use SSH:SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:
Download links:
ROM:
V1: https://mega.nz/file/aSgghJQR#hqsJgoWGMb_io4z4bbzRAXV3jDOJ8JDO0mrIL8fUQRs
V2: https://drive.google.com/file/d/1YIxs8EfYvSTt5Y3tTuAVux4RqxsZkGJf/view?usp=sharing
fix: https://drive.google.com/file/d/16hRYtE4oPRDJ4MU4QrRWHYsk_mTRLl09/view?usp=sharing
V3:
Camera and video recording fixed, and a battery drain issue was also fixed
A5: https://github.com/Exynos7880-Linux...bports-a5y17lte-devel-norecovery-20221216.zip
A7: https://github.com/Exynos7880-Linux...bports-a7y17lte-devel-norecovery-20221216.zip
Separate boot partition (only use if you know what you're doing)
A5 V1: https://mega.nz/file/ElRlASjA#qrzBFkZPC_BhEAPcZhfenVBLMYrqv9yvfFpVUnD9-2M
A7 V1: https://mega.nz/file/IkwSWAJT#9aLfme3LcatYTy-qwCcyd42PlJEx6m_-aRbzeKCvgvY
The camera on waydroid is not working. i don't know how to fix it. Camera app isn't installed and i cannot access it. I really want Ubuntu touch and a small camera functionallity for school to installations lessons
Is this stable?
Waydroid is not working. For some reason it crashes.
Also keyboard functions are a bit buggy.
I was trying to go online trough the browser and I made a typo.
After that I was not able to use the keyboard anymore.
I will keep following this threath because it is fun!
Are there new updates coming?
kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017View attachment 5615835
Code:
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it!
Source code:Device tree: https://github.com/aymanrgab/samsung-exynos7880
Kernel: https://github.com/aymanrgab/android_kernel_samsung_axy17lte
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that
Face buttons (other than the home button)
MTP
Untested:
NFC
Miracast
GPS
A7, drivers have been fixed but no real world testing has been done
???
What works:
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:
Spoiler: Using SSH and logcat
How to use SSH:SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017View attachment 5615835
Code:
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it!
Source code:Device tree: https://github.com/aymanrgab/samsung-exynos7880
Kernel: https://github.com/aymanrgab/android_kernel_samsung_axy17lte
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that
Face buttons (other than the home button)
MTP
Untested:
NFC
Miracast
GPS
A7, drivers have been fixed but no real world testing has been done
???
What works:
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:
Spoiler: Using SSH and logcat
How to use SSH:SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
This rom looks cool as f*ck. Can't wait to install it
kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017View attachment 5615835
Code:
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it!
Source code:Device tree: https://github.com/aymanrgab/samsung-exynos7880
Kernel: https://github.com/aymanrgab/android_kernel_samsung_axy17lte
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that
Face buttons (other than the home button)
MTP
Untested:
NFC
Miracast
GPS
A7, drivers have been fixed but no real world testing has been done
???
What works:
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:
Spoiler: Using SSH and logcat
How to use SSH:SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
Man Ubuntu on this brick it works pretty good even i should say better than i expected but of course there are some hiccups like fingerprint dosent work but these are small things. Also one question if its just halium patched kernel and boot can I try booting newer version of Ubuntu Touch GSi?
Great work.
First of all, excellent job! I have tried to port this device myself but thanks to the mess that was the kernel provided by lineage os devs, I wasn't able to. But also, I have an A7 2017 (SM-A720F) so I'm willing to test things out if you want.
Here are my initial feedbacks:
Both SIMs work (They are detected correctly)
Wifi works
Bluetooth works
Camera unsurprisingly doesn't work (Haven't tested the waydroid version)
Touch inputs work (test_input shows the same libis error as on github)
Back and recents buttons don't work but I'm guessing that's to be expected
Volume and power buttons work
The vibrators work (at least when receiving a call)
Mobile data maybe works? (It shows an "L" and I don't know what that means, I also don't have any data to test the connection)
Gyroscope (Auto-rotation) works
Also in dmesg -w on my computer, the device shows up as SM-A520F. But that should be an easy fix for the boot.img and it's something major either.
Arashk2006 said:
First of all, excellent job! I have tried to port this device myself but thanks to the mess that was the kernel provided by lineage os devs, I wasn't able to. But also, I have an A7 2017 (SM-A720F) so I'm willing to test things out if you want.
Here are my initial feedbacks:
Both SIMs work (They are detected correctly)
Wifi works
Bluetooth works
Camera unsurprisingly doesn't work (Haven't tested the waydroid version)
Touch inputs work (test_input shows the same libis error as on github)
Back and recents buttons don't work but I'm guessing that's to be expected
Volume and power buttons work
The vibrators work (at least when receiving a call)
Mobile data maybe works? (It shows an "L" and I don't know what that means, I also don't have any data to test the connection)
Gyroscope (Auto-rotation) works
Also in dmesg -w on my computer, the device shows up as SM-A520F. But that should be an easy fix for the boot.img and it's something major either.
Click to expand...
Click to collapse
Thanks for your feedback,
test_input has an upstream issue
also, camera is hard to debug it works on waydroid use github version https://github.com/aymanrgab/samsung-exynos7880/releases/tag/v2.1
L means LTE and it's work yeah
fell free to contribute https://github.com/Exynos7880-Linux/samsung-exynos7880
kquote03 said:
then flash fix.zip.
Click to expand...
Click to collapse
This no longer required.
kquote03 said:
sudo waydroid container start
and in a separate terminal run waydroid session start
Click to expand...
Click to collapse
These steps are no longer needed after reboot, start waydroid from launcher.
kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017View attachment 5615835
Code:
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it!
Source code:Device tree: https://github.com/Exynos7880-Linux/samsung-exynos7880
Kernel: https://github.com/Exynos7880-Linux/android_kernel_samsung_universal7880
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera fixed in V3
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that Fixed in V3
MTP Fixed in V3
Untested:
NFC
Miracast
A7, drivers have been fixed but no real world testing has been done
???
What works:
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:
Spoiler: Using SSH and logcat
How to use SSH:SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
both versions are for A7 and none for A5. Too bad, the rom seems to be really good.
rafaellancas said:
both versions are for A7 and none for A5. Too bad, the rom seems to be really good.
Click to expand...
Click to collapse
They have extremely similar boards so it does work on the A5. I have tested it on my own.
Cdd100 said:
They have extremely similar boards so it does work on the A5. I have tested it on my own.
Click to expand...
Click to collapse
Perhaps mine is a Brazillian variant then (the model is SM-A520F/DS), because none of my hardware keys work and the model in settings is the one for A7. Too bad, because I just loved the ROM.
@kquote03 sir, I installed your ROM, but it's very old. Do you have an updated one?
Also, did you send your port back to Ubuntu Touch? I know it's a silly question, but I asked for help in the UBPorts forum, convinced they could support, and they told me they can't.
Thanks for any help, have a nice day =)
P.S.: Here is my post on UBPorts https://forums.ubports.com/topic/8660/ubports-on-a-sm-a520f
P.P.S.: By the way, the ROM works as intended, just some minor issues
No one?
chiaravalle said:
@kquote03 sir, I installed your ROM, but it's very old. Do you have an updated one?
Also, did you send your port back to Ubuntu Touch? I know it's a silly question, but I asked for help in the UBPorts forum, convinced they could support, and they told me they can't.
Thanks for any help, have a nice day =)
P.S.: Here is my post on UBPorts https://forums.ubports.com/topic/8660/ubports-on-a-sm-a520f
P.P.S.: By the way, the ROM works as intended, just some minor issues
Click to expand...
Click to collapse
Hello, i already updated it to focal 20.04
A7 https://github.com/Exynos7880-Linux...bports-a7y17lte-devel-norecovery-20230205.zip
A5 https://github.com/Exynos7880-Linux...bports-a5y17lte-devel-norecovery-20230205.zip
Wow, you're GREAT!!!
Does "no recovery" mean I can't use TWRP to install?
Ayman_sp24 said:
Hello, i already updated it to focal 20.04
A7 https://github.com/Exynos7880-Linux...bports-a7y17lte-devel-norecovery-20230205.zip
A5 https://github.com/Exynos7880-Linux...bports-a5y17lte-devel-norecovery-20230205.zip
Click to expand...
Click to collapse
Sorry, I forgot to click on reply when replying