ads

Affichage des articles dont le libellé est OmniRom. Afficher tous les articles
Affichage des articles dont le libellé est OmniRom. Afficher tous les articles

jeudi 17 septembre 2015

How to Expand Data Store Omnirom 5.1.



Hi Everybody ;

İ'm new at forum also custom roms My device is Samsung Galaxy TAB 7 P1000 İ've installed Omnirom,But after installed i've realized that data store on Apps space is 1.5 GB and quickly it became full .the device has 16 GB disk and in this situation free size is about 12 GB on total space

İ can not install and app because of disk size İs there and solution to fix this problem



jeudi 10 septembre 2015

About flashing latest Omnirom 5.1



its smooth.. the bigmem on adv. settings helps a lot.. troubled at first because of partitioning, using twrp it always saying E:\cant mount data.. return back to stock and used cwm to partition.. everythings fine.. but sometimes it soft reboots.. never know the reason..

heres my log..

bml_over_mtd.log

Quote:









+ export PATH=/:/sbin:/system/xbin:/system/bin:/:/sbin:/system/xbin:/system/bin:/tmp:/sbin
+ busybox cat
+ busybox date
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
################################################## ######################################
#
# Flashing boot image with bml_over_mtd on Mon Sep 7 05:22:35 CDT 2015
#
################################################## ######################################
+ /tmp/bml_over_mtd scan boot
/tmp/bml_over_mtd.sh: line 1: /tmp/bml_over_mtd: not found
+ status=127
+ test 127 -eq 15
+ echo Running flash_image...
Running flash_image...
+ /sbin/flash_image boot /tmp/boot.img
mtd: successfully wrote block at 0
mtd: successfully wrote block at 40000
mtd: successfully wrote block at 80000
mtd: successfully wrote block at c0000
mtd: successfully wrote block at 100000
mtd: successfully wrote block at 140000
mtd: successfully wrote block at 180000
mtd: successfully wrote block at 1c0000
mtd: successfully wrote block at 200000
mtd: successfully wrote block at 240000
mtd: successfully wrote block at 280000
mtd: successfully wrote block at 2c0000
mtd: successfully wrote block at 300000
mtd: successfully wrote block at 340000
mtd: successfully wrote block at 380000
mtd: successfully wrote block at 3c0000
mtd: successfully wrote block at 400000
mtd: successfully wrote block at 440000
mtd: successfully wrote block at 480000
mtd: successfully wrote block at 4c0000
mtd: successfully wrote block at 500000
mtd: successfully wrote block at 540000
mtd: successfully wrote block at 580000
mtd: successfully wrote block at 5c0000
mtd: successfully wrote block at 600000
mtd: successfully wrote block at 640000
wrote boot partition
+ exit




omni_bml.log

Quote:









+ check_mount /efs /dev/block/stl3 rfs
+ /tmp/busybox grep -q /efs /proc/mounts
+ /tmp/busybox mkdir -p /efs
+ /tmp/busybox umount -l /dev/block/stl3
umount: can't forcibly umount /dev/block/stl3: Invalid argument
+ /tmp/busybox mount -t rfs /dev/block/stl3 /efs
+ /tmp/busybox test -e /sdcard/backup/efs.tar
+ /tmp/busybox rm -f /sdcard/backup/efs.tar
+ /tmp/busybox rm -f /sdcard/backup/efs.tar.md5
+ /tmp/busybox mkdir -p /sdcard/backup
+ cd /efs
+ /tmp/busybox tar cf /sdcard/backup/efs.tar imei nv.log root updated_filesystem
+ cd /sdcard/backup/
+ /tmp/busybox md5sum -t efs.tar
+ /tmp/busybox test -n /sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip
+ PACKAGE_LOCATION=/sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip
+ /tmp/busybox echo /sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip
+ /tmp/busybox echo install_zip("/sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip");
+ /tmp/busybox echo install /sdcard/omni-5.1.1-20150831-galaxys4gmtd-HOMEMADE.zip
+ /tmp/busybox rm -f /sdcard/clockworkmod/.settings
+ /tmp/busybox rm -f /sdcard/TWRP/.settings
+ /tmp/flash_image boot /tmp/boot.img
+ [ 0 != 0 ]
+ /tmp/busybox echo Successfully wrote kernel to boot partition
Successfully wrote kernel to boot partition
+ /tmp/busybox sync
+ /tmp/busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ /tmp/busybox sleep 10
+ /sbin/reboot




omni_mtd

Quote:









+ /tmp/busybox mkdir -p /radio
+ /tmp/busybox grep -q /radio /proc/mounts
+ /tmp/busybox umount -l /dev/block/mtdblock6
umount: can't forcibly umount /dev/block/mtdblock6: Invalid argument
+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock6 /radio
+ /tmp/busybox test -e /radio/modem.bin
+ /tmp/busybox umount -l /dev/block/mtdblock6
+ /tmp/erase_image radio
+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock6 /radio
+ /tmp/busybox cp /tmp/modem.bin /radio/modem.bin
+ /tmp/busybox sync
+ /tmp/busybox umount -l /dev/block/mtdblock6
+ /tmp/erase_image boot
+ /tmp/bml_over_mtd.sh boot 72 reservoir 4012 /tmp/boot.img
+ /tmp/busybox umount -l /system
umount: can't forcibly umount /system: Invalid argument
+ /tmp/erase_image system
+ /tmp/busybox test -e /sdcard/omni.cfg
+ /tmp/busybox echo Updating from a BML rom. Format /cache and /data, and attempt to restore /efs
Updating from a BML rom. Format /cache and /data, and attempt to restore /efs
+ /tmp/busybox rm -f /sdcard/omni.cfg
+ /tmp/busybox rm -f /sdcard/extendedcommand
+ /tmp/busybox rm -f /sdcard/openrecoveryscript
+ /tmp/busybox umount -l /cache
+ /tmp/erase_image cache
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/make_ext4fs -b 4096 -l -16384 -a /data /dev/block/mmcblk0p2
SELinux: Loaded file_contexts from /file_contexts
Creating filesystem with parameters:
Size: 1024188416
Block size: 4096
Blocks per group: 32768
Inodes per group: 7824
Inode size: 256
Journal blocks: 3906
Label:
Blocks: 250046
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/62592 inodes and 8162/250046 blocks
+ /tmp/buybox/umount -l /datadata
/tmp/updater.sh: line 1: /tmp/buybox/umount: not found
+ /tmp/erase_image datadata
mtd: not erasing bad block at 0x18b40000
+ /tmp/busybox touch /cache/.startrecovery
+ /tmp/busybox test -e /sdcard/backup/efs.tar
+ /tmp/busybox umount -l /efs
umount: can't forcibly umount /efs: No such file or directory
+ /tmp/erase_image efs
+ /tmp/busybox mkdir -p /efs
+ check_mount /efs /dev/block/mtdblock4 yaffs2
+ /tmp/busybox grep -q /efs /proc/mounts
+ /tmp/busybox mkdir -p /efs
+ /tmp/busybox umount -l /dev/block/mtdblock4
umount: can't forcibly umount /dev/block/mtdblock4: Invalid argument
+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock4 /efs
+ cd /sdcard/backup/
+ /tmp/busybox md5sum -c efs.tar.md5
efs.tar: OK
+ MD5RESULT=0
+ /tmp/busybox test 0
+ cd /efs
+ /tmp/busybox tar xf /sdcard/backup/efs.tar
+ /tmp/busybox umount -l /efs
+ exit 0




dont know how to attach :laugh:



jeudi 3 septembre 2015

Unofficial omnirom moto g 2014





OmniROM is a free, community built, aftermarket firmware distribution of Android 5.1 (LolliPop), which is designed to increase performance, reliability and features over stock Android for your device. It's also about options, which is the beauty of Android.


Code:


#include <std_disclaimer.h>
/*
 * 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.
 */


OmniROM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts.
All the source code for OmniROM is available in the OmniROM Github repo.

Homepage:
=================
http://omnirom.org/

Wiki;
=================
http://docs.omnirom.org/Main_Page

Gerrit:
=================
https://gerrit.omnirom.org/

IRC:
=================
irc.freenode.net #omnirom
Installation Instructions:
=================
First time installing OmniROM to your Moto G 2014, or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running a proper working ClockworkMod-Recovery/Team Win Recovery Project - WITH SELINUX SUPPORT!
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!

Downloads
=================
Build number 1

Device Sources
=================
https://github.com/Thecrazyskull/and...ee/android-5.1
https://github.com/omnirom/
https://github.com/Thecrazyskull/and...torola_titan-1
https://github.com/Thecrazyskull/and...msm8226-common

BUGS
This is still in testing stage so please bare with me :p
Bluetooth is not working
Audio is half working half broken
RIL is broken (only tested on dualsim model, xt1068 single sim models xt1063 and xt1064 SHOULD have RIL working)
Camera is broken
Bluetooth share fc at booth (as workaround remove the bluetooth apk from system/app)

CREDITS:
CyanogenMod for their device trees.
@xc-racer99 for linking me a patch i missed :p
@rr46000 for thread template.
XDA:DevDB Information
[OMNIROM][UNOFFICIAL][5.1], ROM for the Moto G 2014

Contributors
Thecrazyskull
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: OmniRom

Version Information
Status: Testing

Created 2015-09-03
Last Updated 2015-09-03



lundi 31 août 2015

OmniRom 5.1.1 unofficial



So finally here it is, omnirom 5.1.1 for Z1 Compact.

Changelog:
General:M2 specific:
Kernelsources for this rom you will find here

Installation:
In order to install one of my custom roms on your Sony Xperia, YOU MUST UNLOCK & UPDATE YOUR BOOTLOADER!
I wrote a little howto for installing, you will find it on this page of my website.

Known bugs:
  • camera

  • pink/green overlay on videoplayback

I labeled the rom as stable, even with the two bugs above. Imo these are value added services, phone is functioning rocksolid.


Awaiting all your feedback here. As I opted for D5503 to have official omni status, usefull input is important. But... Please donot report bugs without relevant logs and steps-to-reproduce. I will not look into that if I cannot reproduce it myself, if you report comes without a log

And at the end of this long story, we should not to forget to type a download link

>>>> DOWNLOAD HERE <<<<

Enjoy

Thanx are well in place for:
omnirom dev team[*]fxp dev team (especially to @kholk for simplifying things and @jerpelea for opening these opportunities for sony devices)
my wife (there is allways enough coffee around here!)
And many I probably forgot but hey, this list is editable


XDA:DevDB Information
OmniRom 5.1.1 unofficial, ROM for the Sony Xperia Z1 Compact

Contributors
erikcas
Source Code: https://github.com/erikcas?tab=repositories

ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: OmniRom

Version Information
Status: Stable
Current Stable Version: pre official

Created 2015-08-31
Last Updated 2015-08-31



dimanche 30 août 2015

Omnirom 5.1.1 unofficial



So finally here it is, omnirom 5.1.1 for M2.

Changelog:
General:M2 specific:
Kernelsources for this rom you will find here

Installation:
In order to install one of my custom roms on your Sony Xperia, YOU MUST UNLOCK & UPDATE YOUR BOOTLOADER!
I wrote a little howto for installing, you will find it on this page of my website.

Known bugs:
  • camera

  • pink/green overlay on videoplayback

I labeled the rom as stable, even with the two bugs above. Imo these are value added services, phone is functioning rocksolid.

Known issues
There is an issue with a series of D230X / D240X devices with use different accelerometer and magnetometer then the device I have, and the FXP devs have. This issue is that the device bootloops. It is probably caused by the sensorhal which is provided by sony, i.e. we donot compile it from source.
There is a way to boot it, but you will have no sensors working (magno/accelero/proximity/light). This is relatively simple: Open up the zip (on win I advise 7zip), remove sensors.msm8226.so from system/vendor/lib/hw in the zip, and close the zip (click yes if prompted to save changes).
This issues kept me wake for weeks, but is yet not solved. You can read some more background info here

Awaiting all your feedback here. As I opted for D2303 to have official omni status, usefull input is important. But... Please donot report bugs without relevant logs and steps-to-reproduce. I will not look into that if I cannot reproduce it myself, if you report comes without a log

And at the end of this long story, we should not to forget to type a download link

>>>> DOWNLOAD HERE <<<<

Enjoy

Thanx are well in place for:
  • omnirom dev team

  • fxp dev team (especially to @kholk for simplifying things and) @jerpelea for opening these opportunities for sony devices

  • @galaxyfreak

  • @Th3Ant (testing sensors over and over again)

  • my wife (there is allways enough coffee around here!)

And many I probably forgot but hey, this list is editable

XDA:DevDB Information
Omnirom 5.1.1 unofficial , ROM for the Sony Xperia M2

Contributors
erikcas
Source Code: https://github.com/erikcas?tab=repositories

ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: OmniRom

Version Information
Status: Stable
Current Stable Version: pre official
Stable Release Date: 2015-08-30

Created 2015-08-31
Last Updated 2015-08-30



samedi 29 août 2015

Undo the omnirom 5.1.1 installation



I tried to install the omnirom build and it really messed up the ouya. I think it's because it tried to upgrade to lollipop 5.1.1 and it changed the directory structure. The only thing I could get working again is the ouya image however there is no spot for download anymore. Instead there is a 0/download. Anyway to flash firmware so that the box is completely back to ouya. Right now it is saying there is no external storage. Can anyone help me out of this problem?



Best phone hardware supported by OmniROM



Hello everyone,

I'll choose my next phone based on its compatibility with OmniROM.

What's the best phone supported by OmniROM?