Hi All,
Android 6.0.1
features
Android 6.0.1
kernel of fire885
change or delet Some app
smooth
stable
Battery is very good
Downloads
http://www.mediafire.com/download/mn3pcxiz9pndber/omni+android+6.0.1+LionDroid.zip
changelog ROM
Initial release
Installation
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES: https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel: https://drive.google.com/file/d/0B-2dpW_lpZCPNWtxVnRVdUVTcVE/view?usp=sharing
FOTA: https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES: https://yadi.sk/d/cBPD41VEbP2od
"start" kernel: https://drive.google.com/file/d/0B-2dpW_lpZCPT0VCS0tINHU5cnc/view?usp=sharing
FOTA: https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Sources:
Device: https://github.com/fire855/android_device_samsung_wave
Vendor: https://github.com/fire855/android_vendor_samsung_wave
Kernel: https://github.com/fire855/android_kernel_samsung_aries
Thanks to
fire885 for kernel and rom patches
volk204
omni team
Rebellos
blue59
hero355
Tigrouzen
Benzox
and other Badadroid devs
Thanks Nima.. Downloading..
screen shotbro and ril working?
Hi, respect for your work. I've got few questions...
1. Is there any chance that GPS working better than in all other ROMs here? In other ROMs GPS always pointing north...
2. What about video HD?
3. TV-out is enabled?
4. Any known bugs?
5. Any chance SD installation in the future?
Thank you for your answer
thinhx2 said:
screen shotbro and ril working?
Click to expand...
Click to collapse
added screen shot.yes working
and ram free gt 8530 bro?
how to build rom for ss gt8530
Concerning radio did you modify things compared to the lollipop rom. I tried GearCM, your rom with lollipop, and omni 4.4.4 and I can only use the last one to make call.
nima.yavari, why didn't you say that the SD card does not work ?
update omni 6.0.1 for wave 1 and wave 2
delete some app
fast,smooth and stable
link:https://drive.google.com/file/d/0B-TpiHEnTdWrTnBhWFo0Tkkyd2M/view?usp=sharing
"Tovarishchi" explain why it doesn't work SD card?
gapps link??
Related
Hi All,
Android kitkat 4.4.4
features
Android 4.4.4
base omni
kernel of badadroid
change or delet Some app
rom :100mb
smooth
stable
Battery is very good
Downloads
2015/05/23 Initial release
http://opizo.com/ozpL1
patch for rotate
http://filemoney.com/0ackp75ej824.html
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/ilhyKTaEfTo6L
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/wVGzUA96fGW55
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Enjoy OMNI!
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
http://www.mediafire.com/download/n6u05tt4tskrdtl/gapps+for+omni+tigrouzen.zip
Thanks to
volk204 [for any things]
omni team
Rebellos
blue59
hero355
Tigrouzen
Benzox
and other Badadroid devs
will this work from Wave 3 ? or do you have any plans for Wave 3
*
* 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! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Status:
Working:
RIL
Wifi
BT
Touch
Camera
Internal SD
Audio + vibrate
buttons
Not Working:
selinux is permissive, not sure if its worth investing time in getting it to enforced
sdcard
Installation
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES: https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel: https://drive.google.com/file/d/0B-2dpW_lpZCPNWtxVnRVdUVTcVE/view
FOTA: https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES: https://yadi.sk/d/cBPD41VEbP2od
"start" kernel: https://drive.google.com/file/d/0B-2dpW_lpZCPT0VCS0tINHU5cnc/view
FOTA: https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Enjoy OMNI!
THANKS TO
sooti(rom)
fire855(device,kernel,vendor)
I port complete omni rom 6.0.1(17/1/2016) by sooti from samsung s1 to samsung wave1/wave 2
link update: https://drive.google.com/file/d/0B-TpiHEnTdWrYnhROG81UHFOU2c/view?usp=sharing
XDA:DevDB Information
[ROM[PORT][6.0.1][07/02/16][UNOFFICIAL]OmniROM 6.0, ROM for the Samsung Bada OS
Contributors
thinhx2
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
ROM Firmware Required: omnirom 6.0
Based On: omnirom 6.0
Version Information
Status: Alpha
Created 2016-01-24
Last Updated 2016-02-07
update:https://drive.google.com/file/d/0B-TpiHEnTdWrYnhROG81UHFOU2c/view?usp=sharing
When will be the ROM with working SD card?
Union_Jack said:
When will be the ROM with working SD card?
Click to expand...
Click to collapse
I can see bug sdcard from device tree 6.0 by fire855. But now i dont fix because i sold ss wave. Now i dont test new rom. Bro can test? I will work with no use ss wave in 2 mounth. Oke?
Remix OS installations on hard disks or virtual machines using the "INSTALL=1" option are using the whole ext4 partition given to them, but they need special methods for updates. An OTA update for a Remix OS installation on hard disk or a virtual machine (see "How to install Remix OS in VirtualBox (or to harddisk)") will not work showing the error message "Update failed". Obviously the OTA update works for USB flash drive installations only.
Problem Solution
An updated USB flash drive can be used to perform new (updated) installations and it can be used for updating existing hard disk or Virtualbox installations preserving the data directory (i.e. all changes the user has made before).
The tools you'll need and the single steps of operation are documented here:
1. Download Remix OS You are getting version 3.0.206 B2016101201 since October 12th, 2016.
The old version 2.0.403 (based on Android Lollipop) is not available anymore.
2. Tools (for creating a bootable USB device, for creating/checking partitions, for modifying the Remix OS file system with root privileges, and for mounting USB drives to Virtualbox)
3. Perform a Remix OS USB drive installation using Jide's current iso file
4. OTA-Update of a Remix OS USB drive installation July 15th: Update to version 2.0.403 (2016-07-12)
5. Install Remix OS (on hard disk, virtual machine, with dual boot)
6. Enable/Install Google Play Store
7. Setting screen size and density (mirrowing the output)
8. Update Remix OS (hard disk, virtual machine, dual boot)
9. Rooting Remix OS 2 / Checking and managing built in Remix OS 3 root access (hard disk, virtual machine)
10. Last Lollipop version 2.0.403 (2016-07-12)
11. First Marshmallow Versions 3.0.101, 3.0.102, 3.0.103 (2016-07-26) (2016-08-03)(2016-08-11)
12. New versions 3.0.104(2016-08-11) and 3.0.201 (2016-08-16)
13. Version 3.0.202 (2016-08-23) - 64bit version installable again
14. Version 3.0.203 (2016-08-30) - Installation directory called "RemixOS" now
15. Update from Remix OS 3.0.101 to version 3.0.x
Tools
Tools for creating a bootable USB device, for creating/checking partitions, for modifying the Remix OS file system with root privileges, and for mounting USB drives to Virtualbox
1. Which USB devices are suitable?
You'll need a fast USB device of at least 16 GB. If your computer doesn't have USB 3.0, you can use a fast USB 2.0 flash drive (e.g. Transcend Ultra Speed 16 GB) or an external SSD drive.
2. Creating a bootable USB device containing Remix OS
There are several tools for converting an iso file into a bootable USB device. It doesn't matter which one you take.
The zip archive "Remix_OS_for_PC_64_B2016030106.zip" contains a "remixos-installation-tool.exe" which you can run in Windows.
After booting the USB device and pressing the tab key you'll see this screen:
http://postimage.org/index.php?lang=german
The USB device will have 3 partitions:
- REMIX_OS (4 GB fat32)
- REMIXOSSYS (3 GB fat32, boot flag)
- REMIXOSDATA (8 GB ext4)
Unetbootin is available for Linux, Windows and Mac. It will create only one fat32 partition. The start screen is very similar (!) to the remixos-installation tool:
http://postimage.org/index.php?lang=german
If you use the Windows tool Rufus 2.8 portable or Linux system commands (see link ) you'll create a bootable fat32 partition as well and get an android-x86.org start screen:
http://postimage.org/index.php?lang=german
3. Tool for checking or creating partitions and for modifying the ext4 Remix OS file system with root privileges
You'll need a tool for partition editing if you want to set up a dual boot system with Remix OS.
The file system of your Remix OS has to be modified before updating (see Update Remix OS ) and for rooting (see Rooting Remix OS ).
PartedMagic is a small (350 MB) live distribution for disk management that can run off a CD/DVD or an USB drive (created e.g. with Unetbootin).
Link to a source of the free pmagic_2013_08_01.iso : http://www.heise.de/download/partedmagic-1192431.html .
The pmagic_2013_08_01.iso can be used for booting of a virtual machine with PartedMagic:
http://postimage.org/index.php?lang=german
4. VirtualBox Raw Hard Disk Access
VirtualBox can mount entire physical hard disks - look at http://www.serverwatch.com/server-tutorials/using-a-physical-hard-drive-with-a-virtualbox-vm.html .
This is valuable for 2 reasons:
- Only the bootable USB device with Remix OS can get an OTA update. Mounting this device to Virtualbox will be needed for an update of a Virtualbox installation (if you can't download an iso file containing the current version).
- Running a bootable USB device within a Virtualbox window will allow you to use functions of the host system for taking screenshots or for using external monitors.
Above link (by serverwatch) contains all information needed for Windows, Mac OS, and Linux.
In Linux you MUST add your user account to the vboxusers group for VirtualBox to see your USB. You MUST also add your account to the disk group as well, or you cannot add the .vmdk file to your Virtual Machine (see http://askubuntu.com/questions/693719/how-to-boot-from-a-usb-drive-in-virtualbox ; reboot is needed).
In a first step you'll have to determine the drive name of your external disk.
The Linux command is sudo fdisk -l . An example of the output listed for an USB device created by the remixos-installation-tool is:
. . . .
Disk /dev/sdc: 16.1 GB, 16055795712 bytes
. . . .
Device boot. Start End Blocks Id System
/dev/sdc1 2048 8290303 4144128 b W95 FAT32
/dev/sdc2 * 8290304 14581759 3145728 b W95 FAT32
/dev/sdc3 14581760 31358975 8388608 83 Linux
You are creating a vmdk-file for above example (i.e. drive name = /dev/sdc ) with
VBoxManage internalcommands createrawvmdk -filename ~/usb.vmdk -rawdisk /dev/sdc
In order to run bootable USB drives in Virtualbox you have to plug in a bootable USB drive and to setup a Virtual Machine this way:
http://postimage.org/index.php?lang=german
If you have plugged in a PartedMagic USB drive you'll see it's start screen after having started the virtual machine:
http://postimage.org/index.php?lang=german
Plugging in a Remix OS USB drive and starting the Virtualbox virtual machine will show the Remix OS start screen:
http://postimage.org/index.php?lang=german
This way you can run a PenDrive installation of Remix OS within a VirtualBox window in order to create screenshots.
Remix OS Installation on an USB (flash) drive
The Remix OS iso file has to be converted into a bootable USB drive using one of the tools mentioned in Tools.
The start menu will be
http://postimage.org/index.php?lang=german
Set up Remix OS in Resident mode and wait up to 30 minutes for the screen "Select your language".
Select your keyboard layout and click "Next".
Select your Wi-Fi connection and enter your password.
Click "Start" if you see the message "Setup is complete. Your Remix OS is ready".
By clicking "Settings > Update" you can check whether there is a new OTA update. If yes perform the OTA update.
OTA Update of an USB flash drive installation
Since April 2016 you could download new versions from http://www.jide.com/remixos-for-pc only about one week after an OTA update was possible. So performing an OTA update of your Remix OS USB drive is not necessary if you can wait a few days. Since July, 15th you can download version 2.0.403 directly and go on with installing of new or updating of existing Remix OS installations.
Performing the OTA update
After clicking "Settings > Update" you might get the message "Latest version: Remix OS 2.0.403 ... Please download and install the update"
http://postimage.org/index.php?lang=german
Before starting the "Download" please click the 3 dots and select "Options"
http://postimage.org/index.php?lang=german
OTA-Upgrade after Reboot:
http://postimage.org/index.php?lang=german
You can use the updated USB device for installing of new and updating of existing Remix OS installations.
Installation of Remix OS on Hard Disk or within a Virtual Machine
Step 1: Partitioning and formatting of the (virtual) disk
The Remix OS installation tool offers cfdisk for formatting of the (virtual) disk.
How to use cfdisk has been documented in Installing Remix OS to Hard Drive or Virtual Machine without additional tools.
GParted is a better and more flexible partitioning tool which can be used after you booted your computer or your virtual machine with PartedMagic (see Tools ).
In Virtualbox that can be done by attaching the pmagic.iso as "Optical Drive" to the IDE controller (section "Storage").
http://postimage.org/index.php?lang=german
After booting with PartedMagic you can start the "Partition Editor" (GParted). You'll find a new (virtual) disk "unallocated".
After creating a MS-DOS partition table ("Device > Create Partition Table") you can create an ext4 partition for Remix OS, and a swap partition.
http://postimage.org/index.php?lang=german
The partition table has to be different if you are setting up a dual boot system - see "How to install Remix OS alongside Ubuntu (Dual Boot)"
Step 2: Booting with Remix OS
You'll take a bootable USB device (original or OTA updated) for installing Remix OS on a hard disk.
Working with a virtual machine, you'll attach the Remix_OS.iso to it's optical drive, if it is the current version (case 1).
If you do not have an iso file of the current version, but an updated Remix-OS USB drive, take it for booting (case 2).
Case 1
http://postimage.org/index.php?lang=german
Case 2
If your Remix-OS USB drive has been updated already (see OTA-Update USB Installation ) the source of your installation has to be an USB device. You'll create a VirtualBox Raw Hard Disk Access (see Tools ):
http://postimage.org/index.php?lang=german
Step 3: Remix OS Start options "INSTALL=1 DEBUG="
Press the Tab key shortly after you see the Remix OS boot menu and change the start options with "INSTALL=1 DEBUG="
http://postimage.org/index.php?lang=german
Step 4: Remix OS Installation
- Select a partition where to install Android-x86 (usually sda1, formatted with ext4)
If you are setting up a dual boot system, the partition may be sda2 - see "How to install Remix OS alongside Ubuntu (Dual Boot)"
- Do not format, if you have created the partitions with PartedMagic
If you did not use additional tools (see "Installing Remix OS to Hard Drive or Virtual Machine without additional tools") formatting is needed.
- Do you want to install boot loader GRUB? - usually "Yes". If you are setting up a dual boot system: "No"
- Do you want to install EFI GRUB2? - usually "No"
- Do you want to install /system directory as read-write? - "Yes"
http://postimage.org/index.php?lang=german
Step 5: Setting up Remix OS
After the start of Android-x86 RemixOS will be initialized. Be patient - this can last up to 30 minutes (especially in virtual machines). You'll see "RemixOS" flashing a long time.
If your installation has been performed within a virtual machine you'll need "mouse integration" for the next steps.
In VirtualBox you have to click "Input > Mouse Integration". In VMWare there is a similar command (try Ctrl + G).
You need to manually start and stop the mouse integration (Virtualbox: Right Ctrl key; VMWare: Crtl + Alt), because there are no guest extensions for Remix OS yet.
After a while (the time Remix OS needs to create your new data directory) you'll see the window "Select your language".
- Please click "Select your keyboard layout" first and set up the keyboard layout of your country.
- After clicking "Next" you have to accept a "User agreeement"
- If you are not working with a virtual machine you'll be asked to select your Wi-Fi connection and to enter it's password
- Finally you'll see "Setup is complete. Your Remix OS is ready". Click "Start"
Do not forget to disconnect your installation source before rebooting Remix OS.
http://postimage.org/index.php?lang=german
If you have installed the GRUB boot loader, you can boot with PartedMagic again, start the "File Manager", open the Remix OS partition (e.g. sda1), and open directory grub. After opening of "menu.lst" you can modify "timeout=6" to "timeout=0". This way Remix OS will start without showing you a boot menu.
In case of a dual boot system your main operation system will start after the reboot.
You'll have to customize the GRUB settings - see ""How to install Remix OS alongside Ubuntu (Dual Boot)""
Enabling or Installing of the Google Play Store
Enable the Google Play Store using root terminal commands
Since version 2.0.403 you have to switch on "Enable debug terminal console" (Settings > Experimental features) in advance.
Enter the root terminal (Alt+F1) and type
pm disable com.jide.apppolicy
pm enable com.android.vending
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.gsf.login
Leave the root terminal (Alt+F7)
Restart Remix OS
Clicking the Play Store icon after the restart will allow you to sign on with your Google account and install apps.
New proposal for installing the Google Play Store, coming with version 2.0.202
The new symbol "Install Apps" on the Remix OS 2.0.202 desktop is a link to a google forum "Remix OS for PC": How to download and install Google Play Store on Remix OS for PC based on downloading "GMSActivator.apk"
This approach has 2 disadvantages:
- Installation from unknown sources is required
- It is more time consuming as just typing 5 command lines into a terminal
Update for Remix OS installations
Update for Remix OS 2.0.x or 3.0.x systems which have been set up using the boot option INSTALL=1
Clicking "Settings > Update" (Remix OS 2.0.x) or at "System update" (Remix OS 3.0.x) will show that there is a new version of Remix OS.
With current version 2.0.402 you'll get the information, that there is a new version 2.0.403 (2016-07-12).
http://postimage.org/index.php?lang=german
If you start "Reboot and Install" in a Remix OS system which has been installed using the boot option INSTALL=1 ( see "How to install Remix OS in VirtualBox (or to harddisk)"), the root terminal will show an error message after rebooting the system (typing <Alt + F1> after the restart):
Start updating...
ui_print Warning: No file_contexts
script aborted: /mnt/system.img has been remounted R/W; reflash device to reenable OTA updates
wait pidpid doneError in data/media/0/autoupdater/otapackage.zip (Status 7)
Update failed
So the update has to be performed using a current updated version (downloaded from Jide - in case that exists) or an OTA-updated USB device replacing the system directory with a new one and preserving the data directory.
Step 1: Boot your system with PartedMagic (like in "Installation on Hard Disk or VM" )
Start the "File Manager", and open the Remix OS partition (e.g. sda1)
http://postimage.org/index.php?lang=german
- Delete all files and directories other than the old android directory ("android-2016-03-01" for version 2.0.102, "android-2016-04-05" for version 2.0.202, "android-2016-04-20" for version 2.0.205, "android-2016-06-30" for version 2.0.402, "android-2016-07-26" for version 3.0.101, "android-2016-08-03" for version 3.0.102, "android-2016-08-08" for version 3.0.103, "android-2016-08-11" for version 3.0.104, "android-2016-08-16" for version 3.0.201, "android-2016-08-23" for version 3.0.202)
- Rename "android-2016-08-23" into "RemixOS" for new version 3.0.203.
- Open directory "RemixOS" and delete all files and directories other than "data":
http://postimage.org/index.php?lang=german
- Close the File Manager and shut down PartedMagic.
Step 2: Booting with your Remix OS USB drive (which is the current version or which has been OTA updated before - see OTA-Update USB Installation )
For updating a VM installation (Virtualbox or VMWare) you have to distinguish 2 cases:
- there is an iso file of the current version --> attach it as optical drive
- you have an USB drive only containing the current version --> attach the prepared usb.vmdk (see Tools ) as first entry to your SATA Controller:
http://postimage.org/index.php?lang=german
After popping up of the Remix OS boot menu press the Tab key and change the boot options with "INSTALL=1 DEBUG="
http://postimage.org/index.php?lang=german
Step 3: Remix OS installation
The installation begins with selecting the Remix OS partition. The image shows the 3 partitions of the USB device first (sda1, sda2, sda3), and the 3 Remix OS partitions (sdb1, sdb2, sdb5) below. The ext4 Remix OS partition is sdb1.
http://postimage.org/index.php?lang=german
- Do not format your Remix OS partition (sdb1) because you want to preserve your data directory
- Install a new boot loader GRUB (the old one had been deleted because it pointed to the old android directory)
If you are updating a dual boot system, don't install GRUB (but you have to update the customized GRUB of your main OS - see below)
- Do not install EFI GRUB2
- Install a new /system directory as read-write (the old /system directory has been deleted in step 2)
- Run Android-x86 after the installation has finished
- After quite a while you'll see the message "Remix . . . Finishing boot" and somewhat later your old Remix OS desktop.
- You'll find a new icon "Install Apps" (see Google Play Store ), but you don't need it, because your Google Play Store is still working.
- Shut down Remix OS and remove the USB drive or the iso file which you have used for installation
Step 4: Finishing work
The grub directory and the system directory have been created newly. So all modifications concerning boot menu (see Hard Disk or VM Installation ) or rooting (see Rooting Remix OS ) have to be done repeatedly.
In case of a dual boot system (see http://forum.xda-developers.com/remix/remix-os/how-to-install-remix-os-alongside-t3352890 ) the "Grub Customizer" of the main operating system has to be opened, and the path name of the android directory has to be corrected to "android-2016-07-12" for version 2.0.403 or to "RemixOS" for version 3.0.203)
http://postimage.org/index.php?lang=german
Checking the version (with "Settings > Update") after a restart will show the new version. Your personal data and your old desktop have been preserved.
http://postimage.org/index.php?lang=german
Rooting of Remix OS 2 (Remix OS 3 is rooted by default)
Remix OS has a terminal app (version 3: Termux) and a root terminal (press <Alt + F1>). So rooting is essential only for apps which need root privileges. Remix OS 3 is rooted by default; so you can go on with step 4 (without installing anything).
Rooting of version 2 is based upon file remixroot.zip, whose contents have to be copied into the android directory of Remix OS. Running the shell script remixroot.sh with root privileges will do the rooting. The modfications of the Remix OS file system are performed using PartedMagic.
Step 1: Copy file remixroot.zip into the Download directory of Remix OS
Step 2: Boot the system with PartedMagic (see Tools ) and open the "File Manager"
- Open drive sda1 and go into path /media/sda1/android-2016-04-05/data/media/0/Download .
http://postimage.org/index.php?lang=german
- Double click remixroot.zip and extract its contents (directory su and shell script remixroot.sh) into path /media/sda1/android-2016-04-05/
Result:
http://postimage.org/index.php?lang=german
- Click "Tools > Open Terminal Here" → By entering command "sh remixroot.sh" your Remix OS will be rooted:
http://postimage.org/index.php?lang=german
- Shut down PartedMagic and start Remix OS again
Step 3: Updating App SuperSU (needed for Remix OS 2 only)
After rooting of Remix OS you'll find SuperSU in the Remix OS start menu. SuperSU's task is the administration of all root permissions (see link), and it must have the actual version.
http://postimage.org/index.php?lang=german
After starting "SuperSU" an update is needed: "The SU binary needs to be updated" → Continue → Normal → "Installation success" → Reboot
Opening "SuperSU" again shows version # 2.46.
Another update is needed now, this time after searching the app in the Google Play Store . The next start of "SuperSU" will need a SU binary update again.
After the reboot and opening "SuperSU" you'll see version # 2.65 which is ok.
Step 4: Checking whether rooting was successful
The Remix OS Terminal (version 3: Termux) can be used for a first test. The terminal prompt should change from $ to # after calling su (see link).
The user id should change, too:
http://postimage.org/index.php?lang=german
After entering "su" a window will pop up asking for "denying" or "allowing" the root access (version 3: once, always, or for 10 minutes only).
https://postimage.org/app.php
Allowing root access in Remix OS 3
http://postimage.org/index.php?lang=german
Granting root access in Remix OS 2
You'll have a few seconds only for clicking "GRANT". Otherwise you'll get the message "Permission denied".
For Remix OS 3 only:
The built in function "Settings > System > Superuser" will show you a log of granted superuser requests. Clicking "Settings" you can modify settings concerning superuser access.
https://postimage.org/app.php
or Remix OS 2 only:
SuperSU will show you which apps got root permissions. Below image shows that the first trial of giving root permission to app "Root Checker" was not successful (not granted in time - you have to be fast - see https://su.chainfire.eu/). The second trial worked.
http://postimage.org/index.php?lang=german
OTA update to version 2.0.403 (2016-07-12)
You will be informed that there is an OTA update to version 2.0.403 if you are working with version 2.0.402.
You download version 2.0.403 from http://www.jide.com/remixos-for-pc. So you don't have to OTA update your new USB flash drive.
An OTA update of the new version (see OTA Update of an USB flash drive installation) makes only sense a few days until you can download the new version.
The flash drive with version 2.0.403 can be used then for updating an installed version (created with "INSTALL=1" option - see "Install Remix OS") of Remix OS.
and the new version (2.0.205) now have ability to browse the hdd partition from file manager or another file explorer [emoji4]
Jide's announcement of new version 2.0.402
New
Keyboard mapping for certain games has been added to allow users to play games with keyboards
Supports mirrored output from DP, HDMI & VGA
Supports more Realtek/Broadcom/MediaTek WiFi cards
Pre-installed Chrome and Chrome Switcher that allows users to stay on desktop mode by default
Fix
The task bar disappearing on its own is fixed
Time inaccuracy on Windows when users switch back from Remix OS is fixed
More NVIDIA graphics cards are supported with improved stability
Thermal monitoring system is improved to avoid overheating
How to perform an update to version 2.0.402 of an installed version of Remix OS
Jide's Help Center
Hmm. having issues installing inside a ESXi host.
When booting into RemixOS I get the error message like:
"driver does not support CPU family 6 type 7"
And then it reboots. Any ideas?
Setting screen size and density
Since version 2.0.402 Remix OS supports mirrored output from DP, HDMI & VGA. So you can mirror your output to a second screen. But you have to adjust your screen size and density according to the second screen.
With <Alt F1> you can open a root terminal (see "Settings > Experimental features > Enable debug terminal console").
<Alt F7> will close the terminal.
Typing wm will show you the commands for changing the screen size and density: wm
wm size [WxH]
wm density [DENSITY]
wm overscan [LEFT,TOP,RIGHT,BOTTOM]
wm size will show e.g.
Physical size: 1440x900
Override size: 1280x1024
wm density is the DPI density and will show e.g.
Physical density: 160
Override density: 180
Example:
wm size 1024x768
wm density 140
will adjust your output to a 1024x768 screen.
Versions 3.0.101 (2016-07-26) / 3.0.103 (2016-08-08)
Using the INSTALL=1 command (see Installation Remix OS on hard disk) an installation on a Lenovo T400 or within Virtualbox was not possible (see Remix OS 3.0.101 64bit does not start correctly).
Using the 32bit version, Remix OS started correctly, repeatedly, and with good performance on an 16GB USB device (see Link). Running then 32bit version installed on a hard disk or within Virtualbox (using "INSTALL=1") was possible, too.
So it seems that version 3.0.101 64bit still has problems prohibiting an installation to hard disk or to Virtualbox. I'll keep working with version 2.0.403 64bit until the problems have been fixed.
Version 3.0.102 (2016-08-03)
Remix OS 3.0.102 64bit can be installed on a Lenovo T400. After clicking "English" the menu moves to the left side and vanishes a few seconds later. The screen remains dark. Hitting some keys I finally saw the message: "Jide setup wizard isn't responding - Do you want to close it? Wait - OK". There is no difference to the behaviour of version 3.0.101.
The 32bit version can be installed on a Lenovo T400 and runs. The main differences to version 3.0.101 are:
- Symbols for an "App store" and Games
- A symbol for checking whether there is a "System update". If "yes" an OTA update will be possible in future.
- see official thread "Remix OS for PC update 3.0.102" for more information
Version 3.0.103 (2016-08-08)
Remix OS 3.0.103 64bit still does not work on a Lenovo T400 (see above).
The 32bit version runs. There are only minor updates - see official thread
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Kereke12 said:
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Click to expand...
Click to collapse
I got those in the beginning as well. The fix that I found somewhere was to simply remove your account, add it back, and then clear data/cache of play store and play services before running play store for the first time. It worked.
Kereke12 said:
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Click to expand...
Click to collapse
I got error DF-DLA-15, too, in my first try. I repeated the installation, enabled the Google Play Store, and restarted Remix OS 3.0.101 32bit. This time I could sign on and install apps without problems.
Update from Remix OS 3.0.101 to version 3.0.10x
For Remix OS systems which have been set up using the "INSTALL=1" option, an update (preserving all data) from version 3.0.101 to version 3.0.102 is possible - see link "Update for Remix OS installations".
Version 3.0.102 has the function "System update" wich will be used for OTA updates in future.
Versions 3.0.103 and 3.0.104 could be downloaded the same day there was an OTA update available. So link "Update for Remix OS installations" is ok for an update to version 3.0.10x, too.
remixtester said:
You'll need a tool for partition editing if you want to set up a dual boot system with Remix OS.
The file system of your Remix OS has to be modified before updating (see Update Remix OS ) and for rooting (see Rooting Remix OS ).
PartedMagic is a small (350 MB) live distribution for disk management that can run off a CD/DVD or an USB drive (created e.g. with Unetbootin).
Link to a source of the free pmagic_2013_08_01.iso : http://www.heise.de/download/partedmagic-1192431.html .
Click to expand...
Click to collapse
I would strongly discourage anyone from using the 2013_08_01 version of PartedMagic. Yes, it may be the last free version, but it is also has a high risk of damaging devices. There used to be a message on the PMagic site, long since removed:
This version was released with a very destructive USB corruption bug in the Linux kernel. We removed this file from our official mirrors to minimize the damage and quickly released version 2013_08_10 to replace it. The 2013_08_01 version also included a bug in the OLD Secure Erase GUI that would allow a user to erase an ATA disk through a USB interface. In some cases it would brick the expensive USB device. The OLD GUI would also set the secure erase password to NULL by default and using the disk on a Lenovo BIOS is not possible because a password cannot be entered.
Click to expand...
Click to collapse
I have found the GParted version on SystemRescueCD (regularly maintained and readily available) will work just as well fro what I used to use PMagic for. http://www.system-rescue-cd.org/SystemRescueCd_Homepage
Versions 3.0.104 (2016-08-11) and 3.0.201 (2016-08-16)
Version 3.0.104 (2016-08-11)
Remix OS 3.0.103 64bit still does not work on a Lenovo T400: After selecting the language the screen gets and remains dark.
The 32bit version runs. There are minor updates fixing most Google Activation issues (link).
Looking at a video e.g. using VLC does not need anymore activating the "Auto-hide taskbar" (Settings > Remix OS options) in order to have a full screen image.
Wi-Fi-Problem still existing with version 3.0.104: After starting Remix OS in most cases the Wi-Fi is not connected automatically, as long as the "Wi-Fi" pop-up window is not opened yet. After opening the Wi-Fi pop-up window Wi-Fi is connected automatically a few seconds later. It's not a big problem, just not comfortable.
Version 3.0.201 (2016-08-16)
Release Notes
Remix OS 3.0.201 64bit still does not work on a Lenovo T400: After selecting the language the screen gets and remains dark.
The 32bit version runs. NTFS and EXT4 (new feature!) partitions are mounted automatically. During startup Remix OS tries to mount it's own partition (dual boot with Ubuntu) and creates a message "corrupted".
Being of a little experience I've tried to install three Android releases on a Samsung S8530 with the same result - not being able to prepare /system and /data partitions and the message on the Terminal Command screen
sh: sh partition.sh: not found
The releases I've worked were:
[GearCM][NAND|S85xx][4.4.4] Optimized CyanogenMod 11 for Samsung Wave I/II [20151129]
[ROM][WIP][NAND] Omni 4.4 - 26.01.2016
[ROM[PORT][6.0.1][07/02/16][UNOFFICIAL]OmniROM 6.0
All of the three follow the same procedure path:
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
All of the three use the same BOOTFILES and FOTA.
And of course I've used the same phone but two different Bada 2.0 releases:
S4 Style TurkoCFW V10.1 S8530 by hero355&Frager
S5 Style TurkoCFW V10.2 S8530 by hero355&Frager
Can someone help me with that?
Thanks,
Respectfully.
A success with CarbonRom
My fourth attempt with [ROM][4.4.4] CarbonRom: Wave & Wave II was successful.
Many thanks to the developer.
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! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version for the Samsung Galaxy Note 2 LTE on LineageOS 18.1.
At first I want to thank @rINanDO, @ChronoMonochrome for all your work which was reused here and helped a lot.
This ROM is only tested with N7105, so maybe you could to give me a feedback if it does or does not work with all the different Note 2 LTE variants.
It theoretically should fit for:
SGH-I317
SGH-I317M
SCH-I605
SPH-L900
SGH-T889
SHV-E250S
SHV-E250K
SHV-E250L
SC-02E
GT-N7105/N7105T
SGH-T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Here you can see how far everything is working:
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Wifi
USB
Video playback (HW/SW)
OTA Updates
RIL
GPS
Tethering via USB, WIFI and Bluetooth
Sensors, except compass
Spoiler: Whats not working
Maybe random reboots because of a modem crash
Maybe more
Spoiler: Links
TWRP
ROM
Spoiler: If you're facing installation problems.
Samsung seems to use differen't partition tables for these devices,
so far we know a t889, I317 and maybe other devices != n7105 are having a too small HIDDEN (for us vendor) partition.
So if you're facing problems like here
Getting "E2001: Failed to update vendor image." during clean flash.
This means that you have to resize it, check out these two posts:
Manual way
Zip way
If you are going to use Gapps,
I recommend to use the pico package!
https://opengapps.org/
For the others, you can use microG if you want, I've enabled signature spoofing.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: Changelog
26.10.2021
31.10.2021
09.11.2021
09.12.2021
07.01.2022
19.01.2022
28.02.2022
20.04.2022
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][11.x][N7105/T0LTE][BETA] LineageOS 18.1, ROM for the Samsung Galaxy Note 2 LTE
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 11.x R
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.0
Based On: LineageOS
Version Information
Status: Beta
SELINUX: permissive
Created 2021-10-11
Last Updated 2022-04-20
If you're interested in flashing your first GSI, follow this thread (also alpha, untested till yet):
[GSI][11][ EXYNOS4 SMDK4412 ][N8000, N801X, N8020, I9300, N5100, N51XX, N7100, ...][ALPHA] [EOL]
Here you will find my exynos4 compatible GSI's. This work is based on the magic of @phhusson, so thank you very much for this. Don't forget, that you need an treblelized ROM to support this. Do you like my work? Than you can simply hit...
forum.xda-developers.com
thanks for this.
Getting "E2001: Failed to update vendor image." during clean flash.
Your LineageOS 16.0 builds work fine. Probably related to Project Treble?
Device: SGH-T889
TWRP: 3.5.2_9-1
samsungnote2xda said:
Your LineageOS 16.0 builds work fine. Probably related to Project Treble?
Click to expand...
Click to collapse
Hmm the problem could be, that maybe the T889 has a different partition size. Could you send me the complete recovery log?
html6405 said:
Hmm the problem could be, that maybe the T889 has a different partition size. Could you send me the complete recovery log?
Click to expand...
Click to collapse
here you go
samsungnote2xda said:
here you go
Click to expand...
Click to collapse
I can't see any log file .
html6405 said:
I can't see any log file .
Click to expand...
Click to collapse
my bad can't attach file.
https://ghostbin.com/1PdoR/raw
samsungnote2xda said:
my bad can't attach file.
https://ghostbin.com/1PdoR/raw
Click to expand...
Click to collapse
Ok... try to format the vendor partition before as ext4, then retry to install the zip file.
html6405 said:
Ok... try to format the vendor partition before as ext4, then retry to install the zip file.
Click to expand...
Click to collapse
same issue. formatted partition using make_ext4fs
samsungnote2xda said:
same issue. formatted partition using make_ext4fs
Click to expand...
Click to collapse
Ok, than please send me the output from:
adb shell
su
blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
html6405 said:
Ok, than please send me the output from:
adb shell
su
blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
Click to expand...
Click to collapse
~ # blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
20971520
samsungnote2xda said:
~ # blockdev --getsize64 /dev/block/platform/dw_mmc/by-name/HIDDEN
20971520
Click to expand...
Click to collapse
Thx, I will check this and create a new version.
html6405 said:
Thx, I will check this and create a new version.
Click to expand...
Click to collapse
I'm sorry, but the partition size is too small on your device :/,
on a n7105 the partition size is 587202560.
This means, that you would have to re-partition your device with parted and expand vendor (in the same switch you could expand system up to 2GB).
Or the last thing would be, that I'm building a not treblelized ROM for these devices, but this would be again much work.
html6405 said:
I'm sorry, but the partition size is too small on your device :/,
on a n7105 the partition size is 587202560.
This means, that you would have to re-partition your device with parted and expand vendor (in the same switch you could expand system up to 2GB).
Or the last thing would be, that I'm building a not treblelized ROM for these devices, but this would be again much work.
Click to expand...
Click to collapse
ok so reassign space from /cache?
/cache | /dev/block/platform/dw_mmc/by-name/CACHE | Size: 1259MB Used: 21MB Free: 1237MB Backup Size: 21MB
samsungnote2xda said:
ok so reassign space from /cache?
Click to expand...
Click to collapse
I would make the data partition a little bit smaller.
I couldn't got through google setup, so I flashed only LOS. It's mostly working.
Trust issued 2 warnings: not in restricted mode, and "signed with public key".
Like in other devices there is a problem with quick access settings - blinking when press and hold (occured after reboot). In Note 3 it took some time before resolved.
SIM works, Wi-fi works not sure about GPS. I have 7105 model.
And one more - in update menu can't tick "update lineage recovery", which I dont use.
I tried OGapps pico latest.
Anyway it's a miracle You almost made it brillant .
Many thanks.
P.S.
Switching off icons descriptions solve q.access problem.
html6405 said:
I would make the data partition a little bit smaller.
Click to expand...
Click to collapse
thanks. it worked.
Spoiler: parted
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1432MB 1000MB ext4 CACHE
13 1432MB 3432MB 2000MB ext2 SYSTEM
14 3432MB 4200MB 768MB ext4 HIDDEN
15 4200MB 4208MB 8000kB OTA
16 4208MB 15.8GB 11.5GB ext4 USERDATA
No3te said:
I couldn't got through google setup, so I flashed only LOS. It's mostly working.
Click to expand...
Click to collapse
OK, I had no problem with this, what happened?
No3te said:
Trust issued 2 warnings: not in restricted mode, and "signed with public key".
Click to expand...
Click to collapse
This is normal, because selinux is permissive.
No3te said:
And one more - in update menu can't tick "update lineage recovery", which I dont use.
Click to expand...
Click to collapse
Ah you're right, I will remove or disable this, because I've removed the lineage recovery from the build in general,
I don't wan't that TWRP will be overwritten...
No3te said:
Like in other devices there is a problem with quick access settings - blinking when press and hold (occured after reboot). In Note 3 it took some time before resolved.
Click to expand...
Click to collapse
I'm unsure what do you mean with this
html6405 said:
OK, I had no problem with this, what happened?
This is normal, because selinux is permissive.
Ah you're right, I will remove or disable this, because I've removed the lineage recovery from the build in general,
I don't wan't that TWRP will be overwritten...
I'm unsure what do you mean with this
Click to expand...
Click to collapse
After choosing language in initial set up, it says - google voice services not working, 2 more set up screens and it stops in "wait a minute" screen.
Voice service not working in AOSP keyboard.
Another problem is well known in Note 3 ROMS - 10 and 11.
When you pull qa menu from the top of screen you get icons: wifi, battery etc. While pressing and holding battery icon(and some others) screen blinks to black, says "interface crashed" and goes back to normal.
"Solution" to this is switch off description under icons.
Sorry for not giving "logs" but it's over my skills.
Tried to send "bug report" but it warns about privacy ...
I will try Mind the gapps, what helped me with Note 3.
No3te said:
After choosing language in initial set up, it says - google voice services not working, 2 more set up screens and it stops in "wait a minute" screen.
Voice service not working in AOSP keyboard.
Click to expand...
Click to collapse
Hmm ok, I didn't test google voice service...
No3te said:
Another problem is well known in Note 3 ROMS - 10 and 11.
When you pull qa menu from the top of screen you get icons: wifi, battery etc. While pressing and holding battery icon(and some others) screen blinks to black, says "interface crashed" and goes back to normal.
Click to expand...
Click to collapse
Hmm, strange, this seems to work with my device.