Database Info

[ROM] AOKP 6.0.1(MM)(Testing)

Hello guys ..I have compiled aokp MM for ferrari
Just wanted to confirm your reviews before starting a Whole thread
heres the rom link
https://www.androidfilehost.com/?fid=24421527759889608
i will be very happy for your reviews and yes this thread will be converted into a Rom thread once the rom is stable and working
The flashing instruction remains same
Dont forget to do a clean install otherwise there would be problems
Happy flashing guys and dont forget to send some reviews

wow good work.......!
+1 Thanks....

I flashed MIUI 5.6.11 via fastboot -- flash_all.sh, rooting, install TWRP, format /system, /data, /cache, /dalvik, installed AOKP, but cannot finishing boot. Bootanimation standing more then half hour. Same without gapps or with gapps (Open Gapps).

stiw47 said:
I flashed MIUI 5.6.11 via fastboot -- flash_all.sh, rooting, install TWRP, format /system, /data, /cache, /dalvik, installed AOKP, but cannot finishing boot. Bootanimation standing more then half hour. Same without gapps or with gapps (Open Gapps).
Click to expand...
Click to collapse
Can you send me logcat ...if possible ..attach one ..I.would look into it

Screenshots
Can anyone post screenshots?Please

Tanuj97 said:
Can you send me logcat ...if possible ..attach one ..I.would look into it
Click to expand...
Click to collapse
Sorry cause log, AOKP is my favorite rom, and I realy wanted to attach log, but...
Phone was in bootloop, only way (only way known to me) to get log was via ADB, but last night, when this was happend, my computer was also in bootloop with unsuccessful trying to run new version of PhoenixOS . I was waiting and waiting for Phoenix and asleep. In the morning, when I wake up, I done TWRP restore, sorry.

stiw47 said:
Sorry cause log, AOKP is my favorite rom, and I realy wanted to attach log, but...
Phone was in bootloop, only way (only way known to me) to get log was via ADB, but last night, when this was happend, my computer was also in bootloop with unsuccessful trying to run new version of PhoenixOS . I was waiting and waiting for Phoenix and asleep. In the morning, when I wake up, I done TWRP restore, sorry.
Click to expand...
Click to collapse
No problem ....pls attach one once ur PC is back.... if possible

Can u build the rom without sepolicy(device/xiaomi/ferrari/sepolicy)

faizauthar12 said:
Can u build the rom without sepolicy(device/xiaomi/ferrari/sepolicy)
Click to expand...
Click to collapse
build rom without sepolicy? what about qcom/sepolicy, don't build it also?

haikalizz said:
build rom without sepolicy? what about qcom/sepolicy, don't build it also?
Click to expand...
Click to collapse
Ofc we need qcom/sepolicy
Just try it ,it's my opinion
Cuz i faced bootloop too at temasek MM ,maybe we need to update the sepolicy (at our device tree)

Does that work as that's the issue I've been having building Tesla

sykomaniac said:
Does that work as that's the issue I've been having building Tesla
Click to expand...
Click to collapse
I've build a new one but haven't flashed it.. A dirty flash over slimbit should do it right? don't want to wipe data...

Yeah dirty flash should work I would think

should we build a new device tree based on new miui 7?

haikalizz said:
I've build a new one but haven't flashed it.. A dirty flash over slimbit should do it right? don't want to wipe data...
Click to expand...
Click to collapse
sykomaniac said:
Yeah dirty flash should work I would think
Click to expand...
Click to collapse
alright,let's see !!
ajaxcbcb said:
should we build a new device tree based on new miui 7?
Click to expand...
Click to collapse
maybe :/ ,or wait for Official MM from Xiaomi ,so we can use the new source kernel too

faizauthar12 said:
alright,let's see !!
maybe :/ ,or wait for Official MM from Xiaomi ,so we can use the new source kernel too
Click to expand...
Click to collapse
MM will be a decade away

faizauthar12 said:
Ofc we need qcom/sepolicy
Just try it ,it's my opinion
Cuz i faced bootloop too at temasek MM ,maybe we need to update the sepolicy (at our device tree)
Click to expand...
Click to collapse
i have included qcom/sepolicy while building .....
pls send some logcats ...so that we can find out the real problem

sykomaniac said:
Does that work as that's the issue I've been having building Tesla
Click to expand...
Click to collapse
yes ...that would be the one causing problem ....what did your logact suggest ....
I used fire855 device and kernel sources ...

Tanuj97 said:
yes ...that would be the one causing problem ....what did your logact suggest ....
I used fire855 device and kernel sources ...
Click to expand...
Click to collapse
I had to use a custom device tree just to make it work.. just a few variables removed/added with my kernel sources..

haikalizz said:
I had to use a custom device tree just to make it work.. just a few variables removed/added with my kernel sources..
Click to expand...
Click to collapse
is you kernel mm compatible ??
if yes ...then i would try to build aokp with your kernel rather than fires

Error in repacking boot.img... (Kernel Compilation)

i have successfully compiled kernel and generated dt.img now after this i downloaded latest twrp.img (version 3.0..) and unpacked it and replaced my kernel and dt.img also edited img_info file. But in repacking it is giving error.....
I have posted pic of errors....
Thank you.....

Use anykernel2 for the easiest flashable kernel....
If you don't want to compile the kernel with cm source..

faizauthar12 said:
Use anykernel2 for the easiest flashable kernel....
If you don't want to compile the kernel with cm source..
Click to expand...
Click to collapse
okay will try... but what causing the error btw?
i have set all parameters right
as this is my first kernel i dont want to directly flash it on device instead i want to just boot it by
"fastboot boot boot.img" to test kernel...
Thank you..

[email protected] said:
okay will try... but what causing the error btw?
i have set all parameters right
as this is my first kernel i dont want to directly flash it on device instead i want to just boot it by
"fastboot boot boot.img" to test kernel...
Thank you..
Click to expand...
Click to collapse
Tbh i never pack it like that
I am using cm source for compiling a kernel
Also you set the boot size is too small...
Anyway what's the different between fastboot and flash via recovery
The result is same .-.

faizauthar12 said:
Tbh i never pack it like that
I am using cm source for compiling a kernel
Also you set the boot size is too small...
Anyway what's the different between fastboot and flash via recovery
The result is same .-.
Click to expand...
Click to collapse
i solved it....
problem was missing some 32 bit lib files as i am on 64 bit pc.
kernel booting and flashed properly and just black screen i want log of the errors how can i get that?
i have not changed configuratio file.

[email protected] said:
i solved it....
problem was missing some 32 bit lib files as i am on 64 bit pc.
kernel booting and flashed properly and just black screen i want log of the errors how can i get that?
Click to expand...
Click to collapse
Which kernel source you're using
Which rom ? Miui or aosp?

faizauthar12 said:
Which kernel source you're using
Which rom ? Miui or aosp?
Click to expand...
Click to collapse
miui8 and mi official sources
as i know you have provided one zip file along with sensie kernel for to make it work with miui...
whats with that zip file?

[email protected] said:
miui8 and mi official sources
Click to expand...
Click to collapse
-_-
Ofc you can't
Official kernel source is out a dated and only support miui 6...
Believe me ,if you want to do something with kernel
Start with the proper and already test well
Use aosp rom...

faizauthar12 said:
-_-
Ofc you can't
Official kernel source is out a dated and only support miui 6...
Click to expand...
Click to collapse
okay...
so which source to use?

[email protected] said:
okay...
so which source to use?
Click to expand...
Click to collapse
Ferrari dev team
And it's only works for aosp...
Github.cim/ferrari-dev-team

[email protected] said:
okay...
so which source to use?
Click to expand...
Click to collapse
okay... Thanks got it

[DEV] DT2W for X520x

I began to work on dt2w for x52x . It's based on elementalx dt2w/sw2w gestures. I have also updated the driver (a bit).
https://github.com/mthomos/android_kernel_leeco_msm8976/tree/dt2w
You can compile it ,use it and tell me how it works on your device.
Make a BACKUP first before flashing!
Download : https://drive.google.com/open?id=0B4AOvCehd4v3VU93amRxOTd3SEE
Two options: Kernel with ElementalX wake gestures, repackaged with eui kernel and (eui-dt2w.img) and Kernel with Dt2w of Marlin repackaged with los kernel(marlin-dt2w).
Flash it on top nougat custom roms
To report an issue, share logcat or pstore logs

tysm!! WE needed it so Hard...
Your hard work appreciated!!
---------- Post added at 03:36 AM ---------- Previous post was at 03:29 AM ----------
waiting for someone to compile it!:laugh:

I have fixed the small errors i did. Now make builds successfully. I have also implemented a CAF patch. I will release the kernel after Monday. Have a nice weekend !

Eagerly waiting for the kernal!

marios199546 said:
I have fixed the small errors i did. Now make builds successfully. I have also implemented a CAF patch. I will release the kernel after Monday. Have a nice weekend !
Click to expand...
Click to collapse
Does it work ?

vijethrocks said:
Eagerly waiting for the kernal!
Click to expand...
Click to collapse
It's nt a kernal

In a few minutes i will upload the kernel in the OP. Before you flash, make TWRP backup. I am not sure that touchscreen will work flawlessly with this kernel. So flash at your own risk

Compatible with MIUI?

Leeco Le x522 said:
Compatible with MIUI?
Click to expand...
Click to collapse
No, read OP

tysm for this release!!
gonna test and report :laugh:

Not working on latest Lineage OS 14.1.

Can you try to swipe up from bottom when the screen is off ?

marios199546 said:
Can you try to swipe up from bottom when the screen is off ?
Click to expand...
Click to collapse
i flashed the image on boot partition from twrp and rom is not booting.

Rafeh said:
i flashed the image on boot partition from twrp and rom is not booting.
Click to expand...
Click to collapse
Rom ?

Official latest Lineage - Bootloop

marios199546 said:
Rom ?
Click to expand...
Click to collapse
lineage-14.1-20170804-nightly-s2

New kernel : https://drive.google.com/open?id=0B4AOvCehd4v3S0wzRU1udF91YlU

Rafeh said:
lineage-14.1-20170804-nightly-s2
Click to expand...
Click to collapse
Fine . I uploaded a new kernel, test it. I think it's something wrong with gpu because i encountered a strange build issue with gpu driver without modifying it. I will check again tommorow

marios199546 said:
Fine . I uploaded a new kernel, test it. I think it's something wrong with gpu because i encountered a strange build issue with gpu driver without modifying it. I will check again tommorow
Click to expand...
Click to collapse
Still bootloop.. Carbon rom weeklies

kjsr said:
Still bootloop.. Carbon rom weeklies
Click to expand...
Click to collapse
Can you give the ramoops logs ? Mine boots fine.. Maybe something is wrong with kernel repackaging

[CLOSED][TWRP] OrangeWolf in dev

Changes
Changed the lines in the HEX-editor to remove the "anti-warez" details here (you can put varnishes and fritomes) shhh....
Replaced the SuperSU with a stub (because the SuperSU does not support high frequencies)
I replaced Magisk with a triple version
I replaced AromaFM with a newer one
Fixed some configs
wait for the big update!
In dev!
XDA:DevDB Information
[TWRP] OrangeWolf in dev, Tool/Utility for the Xiaomi Redmi Note 4
Contributors
MrYacha
Source Code: https://forum.xda-developers.com/redmi-note-4/xiaomi-redmi-note-4-snapdragon-roms-kernels-recoveries--other-development/recovery-red-wolf-recovery-project-t3653704
Version Information
Status: Stable
Current Stable Version: V1.0
Created 2018-04-02
Last Updated 2018-04-04

thread prone to be closed

akahroba said:
thread prone to be closed
Click to expand...
Click to collapse
why??

Stupid question i know, but... what is Treble?
Redmi Note 4x(Mido)

Sounds good I'm trying this :silly:

newintage said:
Good job. But the owners of the RedWolf probably report this. They don't like sharing.
So get ready for something like this.
Click to expand...
Click to collapse
Lol, but in fact at Red Wolf open source on github.

This is safe?

is he going to change the brand vendor of our hape model like this?

MrYacha said:
Yes, but i change original RedWolf TWRP. Not compile from source
Click to expand...
Click to collapse
I have a question
This version of Redwolf works on both 2gb and 3/4gb Ram?

bienna6.3 said:
I have a question
This version of Redwolf works on both 2gb and 3/4gb Ram?
Click to expand...
Click to collapse
ooos... tested on 4, 3 gb works fine, but i not tesed 2 gb, if you can pc with fastboot testing please, and reply me
sorry

kikyps said:
This is safe?
Click to expand...
Click to collapse
No! Your phone will explode, boom!

kikyps said:
is he going to change the brand vendor of our hape model like this?
Click to expand...
Click to collapse
The name of the model is made by the ROM developer

MrYacha said:
No! Your phone will explode, boom!
Click to expand...
Click to collapse
Lol

MrYacha said:
ooos... tested on 4, 3 gb works fine, but i not tesed 2 gb, if you can pc with fastboot testing please, and reply me
sorry
Click to expand...
Click to collapse
It works very well and it's ready for treble, for me it's a plus
Unfortunately I don't have the 2 gb ram version
I hope that you continue this dev

bienna6.3 said:
It works very well and it's ready for treble, for me it's a plus
Unfortunately I don't have the 2 gb ram version
I hope that you continue this dev
Click to expand...
Click to collapse
thank you

Soon a dark theme
screenshots

Ah, nice thread. Another try to go against anti-piracy process on XDA. I'm not sure that what you're even thinking. If you try to remove anti-piracy code from any project and then post it on development site such as XDA then be sure that it will be taken down. That's it Also It doesn't matter if you modified it using hex patches. Your sources have to be still up.

@MrYacha could it be used to normally flash other roms than terble? like MIUI builds?

Thank You ! :good:

MrYacha said:
Here`s first OrangeWolf build:
Download
Don't see on name, its official build
Click to expand...
Click to collapse
Official builds can be only maintained by my team. So please don't confuse people.

[Recovery][3.3.1-3] Team Win Recovery Project [9fw][all working]

What is TWRP
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices, although it isn't dependent on a device being rooted prior to installation.
Click to expand...
Click to collapse
About this build
Clean TWRP 3.3.1-2, without any tweaks and modifications. Fixed a lot of bugs in official build like 9th FW, MTP, DT2W, F2FS, Sideload.
Click to expand...
Click to collapse
Information
TWRP Version: 3.3.1-3
Build Date: 27-06-2019
Host: Minimal Omni 9.0
Click to expand...
Click to collapse
Downloads
Recovery page with all builds:
https://www.mcsm.ml/html/twrp.html
Click to expand...
Click to collapse
Source
Device Tree: https://github.com/MyCats/recovery_device_xiaomi_whyred
Minimal Omni Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
Click to expand...
Click to collapse

is f2fs formatting working?

Nuclearom
will you build the nuclea rom for whyred?

SyeedAhmed said:
is f2fs formatting working?
Click to expand...
Click to collapse
Yes, https://github.com/GuaiYiHu/android...mmit/36118d354638645c9c3cb0753ee064fadc2401fa
kuahongolongol said:
will you build the nuclea rom for whyred?
Click to expand...
Click to collapse
NucleaRom project was freezed (or, maybe, abandoned), so there is a lot of building errors.
I'll try to rebuild it after building CarbonROM and LineageOS update

MyCats said:
Yes, https://github.com/GuaiYiHu/android...mmit/36118d354638645c9c3cb0753ee064fadc2401fa
NucleaRom project was freezed (or, maybe, abandoned), so there is a lot of building errors.
I'll try to rebuild it after building CarbonROM and LineageOS update
Click to expand...
Click to collapse
What about omni rom bro. No one maintaining it at the moment.

niyas90 said:
What about omni rom bro. No one maintaining it at the moment.
Click to expand...
Click to collapse
I have tried to build it with official devtree and got a bootloop only. I will try to build it with PE devtree

Is this support oreo and pie fw?

it boot properly on pie fw... thank you

user64byte said:
Is this support oreo and pie fw?
Click to expand...
Click to collapse
Yes, it is universal

Can the data partition be unlocked?

zhanghg said:
Can the data partition be unlocked?
Click to expand...
Click to collapse
Yes

MyCats said:
Yes, it is universal
Click to expand...
Click to collapse
its not boot on oreo fw, i've tried it

fadhlanisatria said:
its not boot on oreo fw, i've tried it
Click to expand...
Click to collapse
Okay, use official TWRP

btw I really appreciate your work... I am not sure is dt2w is official feature of TWRP or not but can you add this or is it possible? thank you again

SyeedAhmed said:
btw I really appreciate your work... I am not sure is dt2w is official feature of TWRP or not but can you add this or is it possible? thank you again
Click to expand...
Click to collapse
+1 it's a nice feature

SyeedAhmed said:
btw I really appreciate your work... I am not sure is dt2w is official feature of TWRP or not but can you add this or is it possible? thank you again
Click to expand...
Click to collapse
It is enabled in device tree, but not working in build. TWRP don't officially support DT2W

MyCats said:
It is enabled in device tree, but not working in build. TWRP don't officially support DT2W
Click to expand...
Click to collapse
oooh ?... but thanks for the reply

SyeedAhmed said:
oooh ?... but thanks for the reply
Click to expand...
Click to collapse
Change of plans. I will try to enable it via updating prebuilt kernel from new Pie GS

I'm waiting ?

New update (21-06-2019)
- TWRP version 3.3.1-1
- Changed devtree base
- Updated prebuilt kernel binary
- Using cryptfs from hardware_qcom_open source_commonsys
- Added DT2W support
- Added keystore to default.prop
- Updated build packages
- Synced with TWRP and OmniRom sources