[ROM][PIE]Havoc-OS-v2.9-20191027-t0lte By Comico - Galaxy Note II N7105 Android Development

[ROM][PIE]Havoc-OS-v2.9-20191027-t0lte By Comico - Galaxy Note II N7105 Android Development

Code:
/*
* Your (probably expired. If not please let me know how you
managed this :)) ) 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.
*/
{
"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"
}
Havoc-OS 2.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI by @SKULSHADY.
So many features that you probably won't find in any ROM.
All you can dream of and all you'll ever need.
Just flash and enjoy...
The rom is still in a testing phase.
DON'T ASK FOR ETA

Known bugs:
DON'T REPORT BUGS WITHOUT GIVING DETAILS ABOUT IT AND LOG'S
Boot animation flashing at the end
Gps dosen't work
Proximity, compass not always working
Model number in options will always be N7105
RIL? (Needs testing)
Compatible models
GT-N7105/N7105T
SGH-I317/I317M
SGH-T889/T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Credits:
@ChronoMonochrome
@rINanDO
@pascua28
@Marc0601
Lot's of thanks to everyone who helped me with this project.
Link's:
ROM: https://www.androidfilehost.com/?fid=4349826312261608623
WiFi fix for murata chips (required if you have murata): [url]https://www.androidfilehost.com/?fid=11410963190603897550[/URL]
Install instructions:
Backup EFS and Modem and keep it safe
Flash ROM
Flash Gapps 9 Pico arm
Boot then flash Magisk v19.2 (Else you will fail SafetyNet)
And enjoy
If you like my work then please consider donating.
PayPal: https://www.paypal.com/Comico
Patreon:https://www.patreon.com/ComicoHAVOC-OS Team
PayPal: https://www.paypal.me/vhermann | https://www.paypal.me/ANUSHEK
UPI: [email protected]
Contributors
ComicoX
Source Code:https://github.com/ChronoMonochrome/android_kernel_samsung_smdk4412
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 2.7-07-22-2019

Changelog:
20191027
Fixed audio
Fixed general problems
Updated havoc
?RIL NEEDS TESTING
20190722
Updated kernel maybe now RIL works
20190719
Updated RIL classes
20190718-BUILD2
Updated the kernel. Now I'm 90% sure that RIL is going to work

Reserved 2

thanks for your working！

Excellent !
I'll be flashing this after work and testing RIL etc.
We sure appreciate this !....g

waihung0626 said:
thanks for your working！
Click to expand...
Click to collapse
RIL works?

Just installed the ROM but is stuck in boot atm. How long does it take for it to start up from clean install?
Anyways, thanks for your work. This was a nice surprise
edit - stuck in boot. it won't get past it
using TWRP 3.3.1, clean install, tried flashing just ROM & ROM + pico ARM.. same result on both

ComicoX said:
RIL works?
Click to expand...
Click to collapse
I don't have installed,I will flash and test it now

I get baseband unknown,I think I need back to stock and try again

I go back RR rom,get this (look at pictures),I need go back stock rom and unlock sim

waihung0626 said:
I get baseband unknown,I think I need back to stock and try again
Click to expand...
Click to collapse
Send me a logcat

@waihung0626 Remove your SIM pin. And test the new version please
And give me a logcat if RIL still dosen't work

ComicoX said:
@waihung0626 Remove your SIM pin. And test the new version please
And give me a logcat if RIL still dosen't work
Click to expand...
Click to collapse
ok ,if have time,I will test it again, than you,!
and I don't know how to get location of RIL
---------- Post added at 01:43 PM ---------- Previous post was at 01:38 PM ----------
i have open Developer options>ADB
phone is connected to computer and you can't transfer files

Any with SGH-I317 successfully flash & start up the ROM? Mine won't get past boot animation.
Went back to RR for now.. hopefully others are able to install the ROM.

shinzz said:
Any with SGH-I317 successfully flash & start up the ROM? Mine won't get past boot animation.
Went back to RR for now.. hopefully others are able to install the ROM.
Click to expand...
Click to collapse
Logcat. I need logs

ComicoX said:
Logcat. I need logs
Click to expand...
Click to collapse
Ahh, sorry. Thought I did

shinzz said:
Ahh, sorry. Thought I did
Click to expand...
Click to collapse
Do:
adb logcat > log.txt
That's the TWRP log

Will sound like a novice but not sure how I can get a logcat except the recovery log from TWRP.
Can't access ADB as the ROM won't boot except stay in boot animation/loop. Tried access adb shell from TWRP & during boot loop but only receiving unauthorized. Tried TWRP terminal.. and nothing.
edit - or did you want a logcat after i reinstall RR ROM, gain ADB debug access & logcat from there...

not able to access ADB since it stays unauthorized & "waiting for device" but i pulled this log from "cache" section from TWRP.

shinzz said:
Will sound like a novice but not sure how I can get a logcat except the recovery log from TWRP.
Can't access ADB as the ROM won't boot except stay in boot animation/loop. Tried access adb shell from TWRP & during boot loop but only receiving unauthorized. Tried TWRP terminal.. and nothing.
edit - or did you want a logcat after i reinstall RR ROM, gain ADB debug access & logcat from there...
Click to expand...
Click to collapse
USE WINDOWS SEARCH AND FIND THE FILE :
adbkey.pub
copy it to your external sd card.
Rename it to adb_keys (without .pub in the end)
Boot in recovery and copy that file to data/misk/adb
open adb in your pc
run adb logcat command in your PC
REBOOT phone to system
ADB logcat will start showing in your pc

Related

[ROM][6.0.1][DISCONTINUED] CyanogenMod 13.0 Unofficial for Samsung Galaxy A3

Hi all!
NOTE: PROJECT DISCONTINUED, THIS ROM WON'T BE UPDATED ANYMORE.
CyanogenMod 13.0 Unofficial for Samsung Galaxy A3 (SM-A300FU) (2015)
Currently supported variants:
For SM-A300F, SM-A300H & SM-A300M go here:
http://forum.xda-developers.com/sam...al-samsung-t3490429/post69375432#post69375432
* SM-A300FU
DISCLAIMER
Code:
#include
/*
* Your warranty is now void.
* The ROM is under developement and have some bugs.
* We are 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 us for messing up your device, we will laugh at you. By flashing this ROM, you accept this disclaimer.
*/
What's not working:
* Audio
* Camera
* Wi-Fi
* RIL
{
"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"
}
CyanogenMod 13.0 for Galaxy A3 (2015)
NOTE: THIS ROM IS MADE FOR GALAXY A3, OBVIOUSLY IT WILL NOT WORK ON ANY OTHER DEVICE.
Click to expand...
Click to collapse
Uploading my files elsewhere is not appreciated, if you need to upload my files, just use the links provided here. Thanks.
• Download link to the latest build: (Developement and Updates provided by @mygalaxya)
For A300FU only →
https://www.androidfilehost.com/?fid=457095661767110337
Other useful links:
• SuperSU 2.66 (for root) :
https://download.chainfire.eu/896/SuperSU/BETA-SuperSU-v2.66-20160103015024.zip?retrieve_file=1
• Google Apps (choose arm and for Android 6.0):
http://opengapps.org/
• Camera Patch (if you have the "can't connect to camera" error message):
https://www.androidfilehost.com/?fid=24438995911970219
• Steps for a Clean Install:
1) Put the .zip file in Internal or External Storage.
2) Reboot in Recovery Mode (Using TWRP/CWM Recovery)
3) Wipe Data, Cache, Dalvik Cache and format /System
4) Install the ROM.
5) After first reboot, the device may hang on starting apps, so press Vol-, home button and power button and reboot to Recovery then flash this boot.img:
https://www.androidfilehost.com/?fid=529152257862676138
6) Reboot again and Enjoy!
Click to expand...
Click to collapse
Note: you need to flash the boot.img at every reboot. I didn't find why this issue happen yet.
Contributors:
mygalaxya @vl_w
@Jonny_Hood (Testing),
Credits:
@TheWhisp for the A5 Device Tree. @vl_w for his ramdisk.
Sources:
https://github.com/mygalaxya/android_device_samsung_a3-common?files=1
Version Information:
ROM Status: Preview
ROM OS Version: 6.0.1 Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Marshmallow bootloader and Modem.
Based On: CyanogenMod 13.0
Created: 2016-03-01
Last Updated: 2017-02-24

Changelog==============
2016-11-01
==============
* New A300FU release.

Reserved

Nice work!! will try on A300Y and get back to you, did u want me to post any particular logs/statistics ?

MpandAUS said:
Nice work!! will try on A300Y and get back to you, did u want me to post any particular logs/statistics ?
Click to expand...
Click to collapse
Hi, yes, if you can take some logs using adb, this may help me to fix some bugs you may have on your variant.

?????
will try now!!!!!

Hi,
maybe there is a chance to port your rom of the A300FU :good:
we wan't it flash too
mate, please don't forget us, we are all the A300 community
best regards :good:

thanks for cm 13
Very happy to see cm 13 for a3.thanks for this.will try today at 23 pm means 11 pm

mygalaxya said:
Hi, yes, if you can take some logs using adb, this may help me to fix some bugs you may have on your variant.
Click to expand...
Click to collapse
How do i do that?

MpandAUS said:
How do i do that?
Click to expand...
Click to collapse
You can use this tutorial to take logs: http://forum.xda-developers.com/showthread.php?t=1726238

I can not flashed . its give me Failed in recovery

cast-away said:
I can not flashed . its give me Failed in recovery
Click to expand...
Click to collapse
I can't help you without some details; what variant and what TWRP are you using? What is the error that you're getting when trying to flash it?

mygalaxya said:
I can't help you without some details; what variant and what TWRP are you using? What is the error that you're getting when trying to flash it?
Click to expand...
Click to collapse
A300F 5.0.2 . recovery TWRP 2.8.7.0 \ I do restore now my backup. sorry I not catch the error just readed failed word

cast-away said:
A300F 5.0.2 . recovery TWRP 2.8.7.0 \ I do restore now my backup. sorry I not catch the error just readed failed word
Click to expand...
Click to collapse
You need to have latest TWRP 3.0 recovery from here: http://forum.xda-developers.com/showthread.php?t=3322907
After flashing this new TWRP, try to reflash the ROM again, it should work fine.

mygalaxya said:
You need to have latest TWRP 3.0 recovery from here: http://forum.xda-developers.com/showthread.php?t=3322907
After flashing this new TWRP, try to reflash the ROM again, it should work fine.
Click to expand...
Click to collapse
thank you bro. I will trying and replay you

mygalaxya said:
You need to have latest TWRP 3.0 recovery from here: http://forum.xda-developers.com/showthread.php?t=3322907
After flashing this new TWRP, try to reflash the ROM again, it should work fine.
Click to expand...
Click to collapse
hello bro thank you its working but The phone does not see the sim card . when start say . cant find the kernel by red color . maybe the kernel is different .
vpn FC . just a small thing . the icon in all phone a little bit biggish "Home screen , Settings , Notifications"
and thank you boss . you did a great job

wifi and camera drivers dont work on the A3H variant !! any help

getts error about binary
installing twrp 3.0 will solve problem or not

New build uploaded, fixes SDCard and Internal Storage, and resolution dpi adjusted. Download link on first post. Updated changelog.

bugs in cm 13
this is for galaxy a3 sm a300h
bugs in 1st build
1)after installation reboot device and after reboot every thing stops except system ui
2)second camera works by default there is option for secondry camera
3)no offline charging .no online charging
4)screen dpi
hope that you will fix in second build .if not fix in third build mygalaxa

[DEV][β] OmniROM [Unofficial] [8.1] [D6603/33/53/83] Z3 (Leo)

{
"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"
}
OmniROM
Android 8.0
Sony Xperia z3 (all variant)

What is Omnirom?
A Android custom rom announced at the BABBQ (Big Android BBQ) in late 2013 by @XpLoDWilD, @Chainfire, @Dees_Troy & Team.
"The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. "
For more information go to omnirom's website
Code:
#include <disclamer.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.
* If you dont like this rom, Stay away from this thread!
*/
TWRP with hardware decryption support can be found here
Usefull Links
You want to contribute to Omni? CLICK ME
You want to see the github? CLICK ME
Omni Wiki LOOK HERE
Contributors CLICK HERE
Who can use it
It is only for Z3 (single or dual) and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash TWRP / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data (factory-reset)
Install rom zip (+
% gapps if you need it, any size is ok
%Install root from @phhusson )
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
Stock compatible TWRP
Sources
Manifest file.
Everything else is omnirom.
Contribute gerrit.
This rom is not pure OmniRom, but close to, for convenience purpose. Roms are build from this script and can contain some lightweight modifications (like mkshrc, or TWRP app disabling, @nailyk certificate authority included, etc...) but will never have heavy changes like replacing an app by another, etc...
Downloads:
Latest release
2018-01-01:
md5: d6b1929cb7ce4f6c8fbc06d1487cd881
download mirrorWhat's new:
Switch to OmniRom 8.1
Full treble device
Clean camera code
Reworked devices trees
Add APTX support
GPS fixes
Click to expand...
Click to collapse
Release Timeline
2017-12-10:
md5:
downloadWhat's new:
Do not forget this update require a full wipe!
2017-11-03:
md5:
download
2017-11-01:
md5:
downloadWhat's new:
Code:
Restore double tap to wake from 26502 & 26504
Attempt to fix wifi acess point with 26524
Enable Messaging app (26526) & FM app (26527)
2017-10-29new:
md5: 70bf59e28cef54046e7eb4822a95c906
downloadWhat's new:
^z^z^z
Let's start again 
XDA:DevDB Information
omnirom-oreo-z3, ROM for the Sony Xperia Z3
Contributors
nailyk, Dobsgw
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: OmniRom
Version Information
Status: Beta
Created 2017-10-29
Last Updated 2018-01-01

Known issues:
- Video recording broken
- 120fps / 4k recording
- Wifi access point on 5GHz until country is set
- Off mode charging while connected to computer
- Quick charge
- Dual sim swap problem. After a change all the slot1 is lost!
- 4G connection issue until connected to a WIFI network.
- Audio problems. Depending on actual test could be:
1. No audio while ok siri is enabled,
2. Echo while on speaker mode.
- Wifi drop while ipv6 is set with router advertisements

How to post
Reports without logs or step to reproduce are useless (read contribute).
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to report any typo, error, etc...
Try to keep thread clean as a dev reference. Thanks in advance.
How to report problems
To report problem, please provide logs.
It is always better to include reference to the Installed version. This guide is really detailed and explained everything about bug reports.
If you have any doubts, take the most logs. There is never enough logs
How to get logs
If your device is not booting at all, we need information about how you flash and all the handling you do, the display status, light status, and if available a dump of /proc/last_kmesg*
If you have a non working peripheral (non-working radio/wifi/etc...) please provide a full logcat and full dmesg, example:
Code:
adb reboot
adb wait-for-device
adb shell dmesg > dmesg.log
adb logcat -d > logcat.log
If you have a non working app please provide a partial logcat:
Code:
adb reboot
adb wait-for-device
adb logcat -c
<launch your app>
adb logcat -d > logcat.log
On this rom, there is a script who detect device at install time and provide the right functions for single or dual sim. If you have modem problems (like data not working or no signal) please also provide the /tmp/recovery.log.:
If you have ADB access to your device in twrp just use
Code:
adb pull /tmp/recovery.log .
after flashing omnirom.
If you do not have ADB access use the 'copy to SD' button in the advanced tab, then transfer it the way you like.
then upload your files to a service like pastebin.com / paste.omnirom.org
How to contribute
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.

bar

Excited for the fresh start on Oreo
Thanks for supporting Leo!

Taste, thanks for you hard work ?

And now delete text and save it? Thats right?
Problem with error7 on d6603 (leo)
Sent from my Xperia Z3 using XDA-Developers Legacy app

santeria27 said:
And now delete text and save it? Thats right?
Problem with error7 on d6603 (leo)
Sent from my Xperia Z3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Xperia Z3 using XDA-Developers Legacy app

Hello guys,
As mentioned error 7 for 6603, but can be fixed via provided workaround for now☺
My sim card was not detected at all. System was asking for sim card insertion. ? (I wiped everything before installation, flashed zip and gapps nano, tried also the same with sideload)
I had to directly switch back, because I need working phone today. But I will try to provide logs as soon as possible.
Thank you a lot!

santeria27 said:
View attachment 4317281
Sent from my Xperia Z3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Xperia Z3 using XDA-Developers Legacy app

Hi, I'm still failing

i got error 7, i made changes to script file, zipped the entire folder again. now the twrp says the zip file is corrupt. what am i missing.

Gixchi said:
i got error 7, i made changes to script file, zipped the entire folder again. now the twrp says the zip file is corrupt. what am i missing.
Click to expand...
Click to collapse
Check the basic structure of your zip, if it corresponds to the original one. If this is not the problem zip it with other tool...

am gonna upload a fixed zip.

@nailyk will you update the rom to fix the BT and Hotspot soon?
And thanks for this great rom

release 3
That's a failing launch
So new zip with already removed assert, and some fix for single sim who do not have data. Please wipe /system before flashing.
Looks like another expected issue pop out: BT is broken. We are currently working on it. (bt was working 2 days ago )
Sorry for the mess

Looks very good. Even with October security patch level.
I know it may be a little early, but can you say anything about battery life (especially standby) compared to 7.1.2 or stock?

nailyk said:
That's a failing launch
So new zip with already removed assert, and some fix for single sim who do not have data. Please wipe /system before flashing.
Looks like another expected issue pop out: BT is broken. We are currently working on it. (bt was working 2 days ago )
Sorry for the mess
Click to expand...
Click to collapse
I excited to install it but i think to wait stable release to be good for daily use

Br4no said:
Check the basic structure of your zip, if it corresponds to the original one. If this is not the problem zip it with other tool...
Click to expand...
Click to collapse
thanks it helped. zip structure was not right

Ok lets start again.
New zip uploaded, we will base the work on this one.
Sorry again. Wont post zip at 4AM anymore!

[ROM][MM][INTERNATIONAL] FlymeOS 6 for moto x 2013 [01/10/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:
#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.
*/
Notes
This ROM is in a W.I.P state, don't expect 100% stability (or even smoothness, battery, etc).
The are probably bugs that i'm not aware of, to report them, open the Log Report app, click on Record Logs and record MobileLog/BasicLogs. After that, reproduce your bug, stop recording and send the zip to me.
Magisk isn't supported at this moment, if you want to have root access, flash SuperSU.
This DOESN'T come with root, you've been warned.
Download Kernel Adiutor if you want to have a better control of the kernel.
Working:
Mostly everything
Not Working / Bugs:
Screenshot resolution is wrong (720x1184)
Status bar icon color doesn't update until you swipe it down.
Screen capture through QS Tile
Features:
tycoo's moto_x_kernel-v1.5 with the updates from LineageOS
Patched for CVE-2016-5195 (Dirty COW)
Patched for CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13084, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088 (KRACK)
Install
As always, backup your data before installing this ROM, in case something goes wrong.
1. Wipe Dalvik / ART Cache, Data, Cache and System in recovery
2. Flash the ROM and GApps
3. Reboot
4. First boot may take 10 to 15 minutes.
Downloads
ROM: Open the "Downloads" tab and download the lastest file.
GApps: The Open GApps Project
XDA:DevDB Information
FlymeOS International for moto x 2013, ROM for the Moto X
Contributors
Rahh1112, tycoo, Rendyindo, zoujunhua
Source Code: https://gitlab.com/h4ndshake/flyme_device_motorola_ghost
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-11-02
Last Updated 2017-11-01

Reserved
If someone doesn't have a ghost_retail, please send me via pm the output of the commands
Code:
adb shell getprop ro.build.device
Code:
adb shell getprop ro.build.fingerprint
A "hack" was required in order to build the rom correctly, the was done by adding these two properties to our build.prop.
Currently, our init (the process that manages all processes) already does that, so I'm uncertain if it will correctly set if these two properties are already there.
For more information, see commit 7790514f3ec08b253fee1953ab34f69c23cc9cc3 at the source code.

Reserved

Wow! it is very interesting have this ROM for the moto x.
Thanks a lot!!!

Waiting to test, thanks.

Waiting to download

Download was already uploaded (it's been there for about 1 day lol, I was out of home, sorry), just open the "Downloads" tab and download the lastest file.

Rahh1112 said:
Download was already uploaded (it's been there for about 1 day lol, I was out of home, sorry), just open the "Downloads" tab and download the lastest file.
Click to expand...
Click to collapse
Hi! I don't understand what you mean when you say "If someone doesn't have a ghost_retail"... My ghost is xt 1052, should I expect problems if I flash your rom? Thanks

stefanowall said:
Hi! I don't understand what you mean when you say "If someone doesn't have a ghost_retail"... My ghost is xt 1052, should I expect problems if I flash your rom? Thanks
Click to expand...
Click to collapse
That means, other than ghost retail..

R324D said:
That means, other than ghost retail..
Click to expand...
Click to collapse
I had already understood that part, what isn't clear to me is whether my moto, model xt 1052, can be considered retail...understand?

As said in https://forum.xda-developers.com/showpost.php?p=74376101&postcount=3. I don't know how the init process will behave if you doesn't have ghost_retail, if it will boot.. and setup the radio properly, but please, test it.

It worked on my ghost Will the resolution be resolved?

Jean12ax said:
It worked on my ghost Will the resolution be resolved?
Click to expand...
Click to collapse
What's the output of the two commands in #3?

How can I root this ROM?

You can flash SuperSU.

stefanowall said:
I had already understood that part, what isn't clear to me is whether my moto, model xt 1052, can be considered retail...understand?
Click to expand...
Click to collapse
So why'd you asking on the first place, check your own system version to make you completely understand. Understand?
Cheers.

stefanowall said:
I had already understood that part, what isn't clear to me is whether my moto, model xt 1052, can be considered retail...understand?
Click to expand...
Click to collapse
It isn't as plain as you want to make it seem to be, and my question was addressed to the developer. I'm not stock, I've been using many different roms, during the last two years, so your stamp means nothing. But it isn't so important... Cheers

Just place the output of the two commands in #3 bro.. even if you aren't using Flyme

R324D said:
So why'd you asking on the first place, check your own system version to make you completely understand. Understand?
Cheers.
Click to expand...
Click to collapse
It appears the confusion was "Is my model XT10xx retail?" vs "Oh, you mean is the OS retail?" But now the confusion is cleared up.

Rahh1112 said:
Just place the output of the two commands in #3 bro.. even if you aren't using Flyme
Click to expand...
Click to collapse
:good:

[ROM][PIE][9.0.0_r30]CypherOS 7.0.0 Poundcake[Berkeley]

Encryption and recovery steps for EMUI 8 firmware
Due to the changes of Encryption in Pie, encryption is now broken in TWRP. Unofficial TWRP will not boot with Pie roms installed.
Official recovery should work fine.
For Unofficial recoveries, wipe System, Data, Cache, Dalvik Cache and flash the rom zip. For Gapps you can use BitGapps (Search on XDA) and follow those installation instructions. If you want to go back to an Oreo rom, the steps i use are flashing a GSI in fastboot and attempt to reboot into the 8.1 GSI, if it reboots, quickly hold Vol Up/Dwn while connected to PC and it'll boot into unofficial TWRP where you then perform the usual wipes and flash an 8.1 rom zip.
For Offiicial TWRP users, you must wipe /data in stock recovery and wipe everything else in TWRP, then adb sideload the zip file and gapps
Builds (EMUI 8)
Build 1
Build 2
Build 3
Build 4
Build 5
Build 6
Builds for EMUI 9 firmware
These builds require EMUI 9 firmware to install
Instructions
- Wipe System, Data, Cache, Dalvik Cache (Data will not really wipe but continue) in compatible recovery (I used the unofficial TWRP)
- Install rom (& gapps) (I used adb sideload)
- Reboot to bootloader (Ignore the "No OS" message if it shows)
- Flash stock recovery and wipe Data
- Reboot
These builds do not include a custom kernel
Builds(EMUI 9)
20190202
What doesn't work
VoLTE

Thanks Chris, will try this weekend [emoji106][emoji108]
Powered by View 10

Great ROM so far, but I can't select ringtones in audio settings, is it only an issue for me?
Still need a working TWRP, as the official one crashes and reboots ater 5 seconds on my BKL-L04.
Update: fixed myself, a gapps package caused to uninstall it.

I wonder if the hot issues have been fixed.
I wonder if the hot issues have been fixed.

can i install this ROM on kirin 960 device?

Thanks, atm works fine here on Bkl-L09 [emoji1360]
No heat, boots fast
Run butter smooth and very snappy.
Will try more.
Powered by View 10

I have another device redmi note 4 too running on pie every thing is working fine in it even volte etc..
There is a file for fixing volte if you want I can provide you

Yes @y1402070362

2WildFirE said:
Thanks, atm works fine here on Bkl-L09 [emoji1360]
No heat, boots fast
Run butter smooth and very snappy.
Will try more. View attachment 4580076
Powered by View 10
Click to expand...
Click to collapse
Great! Thanks for the feedback

Ultimate˜¤ said:
can i install this ROM on kirin 960 device?
Click to expand...
Click to collapse
Give it try, let me know how it goes you'll have to remove the assert line in the updater-script to flash

sirhc said:
Give it try, let me know how it goes you'll have to remove the assert line in the updater-script to flash
Click to expand...
Click to collapse
It could boot and work well. I have tried it on my P10P.
---------- Post added at 08:46 AM ---------- Previous post was at 08:46 AM ----------
Ultimate˜¤ said:
can i install this ROM on kirin 960 device?
Click to expand...
Click to collapse
Yes, I tried.

Does this ROM support Pie's new navbar (so I can swipe up to see recents)?

StarStorm said:
Does this ROM support Pie's new navbar (so I can swipe up to see recents)?
Click to expand...
Click to collapse
Yes, all the pie ROMs have that

Seems like I can't access internal storage due to SELinux:
Code:
8-26 15:08:43.683 657 657 W unrmd : type=1400 audit(0.0:3638): avc: denied { read open } for path="/data/media/0" dev="sdd60" ino=1665 scontext=u:r:unrmd:s0 tcontext=u:object_r:system_data_file:s0 tclass=dir permissive=0

honor10开不了机

StarStorm said:
Seems like I can't access internal storage due to SELinux:
Code:
8-26 15:08:43.683 657 657 W unrmd : type=1400 audit(0.0:3638): avc: denied { read open } for path="/data/media/0" dev="sdd60" ino=1665 scontext=u:r:unrmd:s0 tcontext=u:object_r:system_data_file:s0 tclass=dir permissive=0
Click to expand...
Click to collapse
Is this on L09? I can access mine fine

sirhc said:
Is this on L09? I can access mine fine
Click to expand...
Click to collapse
Yup, that's L09. Can't set SELinux to permissive via setenforce though, setenforce 0 just returns
Code:
setenforce 0 setenforce: Could not set enforcing status: Invalid argument.

StarStorm said:
Yup, that's L09. Can't set SELinux to permissive via setenforce though, setenforce 0 just returns
Code:
setenforce 0 setenforce: Could not set enforcing status: Invalid argument.
Click to expand...
Click to collapse
We can't force permissive on View 10 last I heard. I don't own an L09 but I'll check it out or maybe Luk can

sirhc said:
We can't force permissive on View 10 last I heard. I don't own an L09 but I'll check it out or maybe Luk can
Click to expand...
Click to collapse
Oh, okie, thanks. I dislike asking for an ETA (and most likely you won't be able to give one), but I kinda need internal storage to function and since I can't really make proper backups with TWRP switching to another ROM and switching back is rather much effort, so I'd like to avoid that

[ROM][OFFICIAL][montana][11] LineageOS 18.1

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Instructions:
Download the latest build, recovery image and GApps (if you need them)
Flash the downloaded recovery image via fastboot
Boot to recovery
Format system and perform a factory reset
Reboot to recovery
Flash the latest build
Flash GApps and any other necessary add-ons
What's working:
WiFi
Camera and Camcorder
Bluetooth
NFC
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE
USB tethering/audio
SELinux: Enforcing
Known issues:
VoWiFi
You tell me
Downloads:
Official builds: Here
Recovery: Here
Google Apps: Here
Reporting Bugs
All bugs should be reported here: Issue Tracker
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks to:
@GivFNZ for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Code:
2021-04-08:
Initial 18.1 build.
2020-10-13:
Initial release.
Source code:
Common device tree: https://github.com/LineageOS/android_device_motorola_msm8937-common
Device tree: https://github.com/LineageOS/android_device_motorola_montana
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8953

Exciting to see that Android 11 is on a good way

Dan Mornill said:
Exciting to see that Android 11 is on a good way
Click to expand...
Click to collapse
The best thing is:
Jarl:
"Should I compile R?"
"Yea sure"
And now he's working on Los18

Some random said:
The best thing is:
Jarl:
"Should I compile R?"
"Yea sure"
And now he's working on Los18
Click to expand...
Click to collapse
Oh, hey Rush!

GivFNZ said:
Oh, hey Rush!
Click to expand...
Click to collapse
Hey!

The OpenGApps to use is to Android 10?

DHDDS said:
The OpenGApps to use is to ?
Click to expand...
Click to collapse
I used BiTGApps-arm64-11.0.0-R17. OpenGApps for Android 11 is not available.

TatsuMasa said:
I used BiTGApps-arm64-11.0.0-R17. OpenGApps for Android 11 is not available.
Click to expand...
Click to collapse
thanks man
the link for who want

DHDDS said:
thanks man
the link for who want
Click to expand...
Click to collapse
My pleasure.

Please use NikGApps (https://nikgapps.com/), BitGApps modifies the system in ways that may affect behavior of the device. OP will be updated shortly.

JarlPenguin said:
Please use NikGApps (https://nikgapps.com/), BitGApps modifies the system in ways that may affect behavior of the device. OP will be updated shortly.
Click to expand...
Click to collapse
there's any specific package?

DHDDS said:
there's any specific package?
Click to expand...
Click to collapse
Core or Basic should be fine

JarlPenguin said:
Core or Basic should be fine
Click to expand...
Click to collapse
trying with basic one

Hi!,
I had a problem, i didn't notice first boot rule:
Long first boot time due to forced encryption. Please do not reboot your device when it is booting up the first time
I poweroff the device before first boot, i don't know what i should do now to recover my phone, should i try boot it again?

Hi!,
I had a problem, i didn't notice first boot rule:
Long first boot time due to forced encryption. Please do not reboot your device when it is booting up the first time
I poweroff the device, now i don't know what should i do to recovery my phone,
i tried rebooting again but is only loading (i wait more than 40 min)
Also i can't connect to logcat, it shows me unauthorized device
>adb devices
List of devices attached
ZY322KJLWB unauthorized
>adb logcat
- waiting for device -
Any help i will be glad!!

H0LiC said:
Hi!,
I had a problem, i didn't notice first boot rule:
Long first boot time due to forced encryption. Please do not reboot your device when it is booting up the first time
I poweroff the device, now i don't know what should i do to recovery my phone,
i tried rebooting again but is only loading (i wait more than 40 min)
Also i can't connect to logcat, it shows me unauthorized device
>adb devices
List of devices attached
ZY322KJLWB unauthorized
>adb logcat
- waiting for device -
Any help i will be glad!!
Click to expand...
Click to collapse
Format data in recovery

the ROM is ded?

DHDDS said:
the ROM is ded?
Click to expand...
Click to collapse
be patient, thread startet 6 weeks ago and @JarlPenguin take his time to work on it for a good rom
many things already work on lineage-18

CAN U PROVIDE SOME SCREEN SHOT

ALFRED M 456 said:
CAN U PROVIDE SOME SCREEN SHOT
Click to expand...
Click to collapse
no, but google.com can
please refrain from using caps lock as to respect other members

DHDDS said:
the ROM is ded?
Click to expand...
Click to collapse
No, is not dead, @JarlPenguin is working on it, anyways, it takes a lot of work to get a custom rom to get to the stable mark... So, please be patient....

Better Mobile App

welcome