Database Users

[DISCUSSION][DEV] TWRP for X8

Okay guys. So over the past few days I've tried to compile KXP (AOKP for X8, if you didn't know) and failed.....thrice. The main aim behind this was to get
a) AOKP m6 for X8
b) TWRP running on our device
Now a) is still resulting in failures but b)....well, let's just say it can still be worked on. So this is what I've done so far:
I compiled a CWM version (without compiling KXP) just to get the environment ready for building TWRP. Next I edited the BoardConfig.mk to include these lines under a heading of #twrp like this
#twrp
DEVICE_RESOLUTION := 320x480 (the device resolution)
RECOVERY_GRAPHICS_USE_LINELENGTH := true (this line is supposed to improve graphics on some devices)
TW_NO_BATT_PERCENT := true (this line prevents battery percentage display in the recovery GUI)
TW_NO_REBOOT_BOOTLOADER := true (self-explanatory; we can't reboot into bootloader, can we?)
TW_NO_REBOOT_RECOVERY := true (this option never worked for me and so I removed it)
I sent the binary (obtained by typing make -j# recovery after copying the TWRP repo to the bootable/recovery directory) to feherneoh (the dualboot dude) and asked him to use it in a kernel, changing nothing else but the recovery binary. He said the phone didn't even boot.
Now I've noticed there are a couple of other libs and files built with TWRP. And also there's another recovery binary in /out/target/product/shakira/symbol/system/bin.
What I'm trying to do is compile a kernel with this binary. So far feherneoh's failed. And I'm pretty sure there's something else that needs to be done. I know about the recovery GUI images; I will place them in the res folder and try again but I'm pretty sure it will fail.
So i'm asking experienced X8-ians to help me out, especially devs like Daveee10, Rohin, nAa, alfsamsung, djnilse....the list doesn't end.
Looking forward to replies.

This is what lead dev of TWRP, Dees_Troy had to say:
Re: Compiling TWRP for X8
Originally Posted by sgt. meow
Dear Sir,
I have started a TWRP-porting project for the X8. I have compiled the binary (make -j# recovery) using the following flags:
#twrp
DEVICE_RESOLUTION := 320x480
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TW_NO_BATT_PERCENT := true
TW_NO_REBOOT_BOOTLOADER := true
TW_NO_REBOOT_RECOVERY := true
I haven't tested it myself. However I sent a fellow member (with experience in this field) the binary (from /out/target/product/shakira/system/bin) and asked him to integrate it with a working kernel, changing nothing else but the recovery binary. He said the phone didn't boot up. I believe the images from the /bootable/recovery/gui/devices/320x480/res/images have to be placed in the kernel too, in order to get it working. I am very new to this and would greatly appreciate if you helped me with the following:
What files are related to the TWRP recovery?
What has to be done to integrate it with a kernel?
What files need to be edited?
Do the libs built along with TWRP need to be installed on the phone?
Thanking you and the rest of Team WIN in advance
sgt. meow
Click to expand...
Click to collapse
Generally speaking, the actual recovery files would be in out/target/product/shakira/recovery/root. What you have to have for integrating into your kernel build will depend a little bit on how your kernel ramdisk(s) are packed. You'll need, at the very least, the etc (for the recovery.fstab), sbin (binaries and libs), and the res (theme and zip signature keys) folders. Recovery usually gets its own init.rc so you'll have to do whatever you need to do to get the recovery/root/init.rc integrated into your kernel or at the very least, modify an exising init.rc so that recovery gets the LD_LIBRARY_PATH value as covered in the guide.

Here's the link to a zip I uploaded: http://www.mediafire.com/?ad374fp01274e3z
It contains the output files when TWRP is compiled as a binary (in the "TWRP(binary files)" folder) and the ramdisk-recovery.cpio when TWRP is compiled as an image by issuing make -j# recoveryimag (in the "TWRP(image files)" folder).
Note: The binary didn't build the res images. They had to be taken from the gui folder of the bootable/recovery directory. However the images were there when TWRP was compiled as an image in the ramdisk-recovery.cpio.
Note 2: This is compiled using jb-wip branch. The first binary and image was compiled using master branch. I later found out that I was supposed to use the jb-wip branch instead of the master branch.

Well you should make it to compile with rom together. When its built then u will get "ramdisk-recovery.img" or zip... inside this one you will have all needed binaries and images. Then just open kernel ramdisk and replace those binaries. There are lot more needed binaries than just "recovery".
But first you must compile everything
Sent from my mind using fingers

You mean like make -j# recoveryimage.

sgt. meow said:
You mean like make -j# recoveryimage.
Click to expand...
Click to collapse
Try with brunch
Sent from my X8 using xda app-developers app

Problem with brunch is I run into some errors while compiling the ROM (which stop the building) so I won't get any end product. I tried recoveryimage and got a lot of ramdisk-***.img's and cpio's and what-nots.

sgt. meow said:
Problem with brunch is I run into some errors while compiling the ROM (which stop the building) so I won't get any end product. I tried recoveryimage and got a lot of ramdisk-***.img's and cpio's and what-nots.
Click to expand...
Click to collapse
Thats good too now extract ramdisk-recovery.img if you have it
Sent from my X8 using xda app-developers app

sgt. meow said:
Problem with brunch is I run into some errors while compiling the ROM (which stop the building) so I won't get any end product. I tried recoveryimage and got a lot of ramdisk-***.img's and cpio's and what-nots.
Click to expand...
Click to collapse
The brunch not help Tried a lot of variant (compile only the recovery/compile with rom/millions of different settings/etc...) The phone start the recovery, but not work (the best result is only a flickering image). Earlier I consulted with Daveee10, but he have same results.

I couldn't extract ramdisk-recovery.img but I extracted ramdisk-recovery.cpio and I get a lot of files in the sbin directory like recovery, sdparted, fix_permissions.sh, adbd and a lot of libs. In the etc directory there is a recovery.fstab.

pilu1978 said:
The brunch not help Tried a lot of variant (compile only the recovery/compile with rom/millions of different settings/etc...) The phone start the recovery, but not work (the best result is only a flickering image). Earlier I consulted with Daveee10, but he have same results.
Click to expand...
Click to collapse
Then we are missing some files or there are wrong configurations...
Sent from my X8 using xda app-developers app

How did you try pilu1978? I mean where did you place the libs and the binary?

sgt. meow said:
I couldn't extract ramdisk-recovery.img but I extracted ramdisk-recovery.cpio and I get a lot of files in the sbin directory like recovery, sdparted, fix_permissions.sh, adbd and a lot of libs. In the etc directory there is a recovery.fstab.
Click to expand...
Click to collapse
Now replace all the files in ramdisk with these new ones
Sent from my X8 using xda app-developers app

It won't work. I'm pretty sure about it.
EDIT: Okay apparently it is the right way. Sorry Xmaster8. Lesson learned.

Xmaster8 said:
Now replace all the files in ramdisk with these new ones
Sent from my X8 using xda app-developers app
Click to expand...
Click to collapse
Yes. I examined a disassembled recovery binary from other phone (what is working correctly), the recovery depends on these binaries:
libz.so, libc.so, libstlport.so, liblog.so, libcutils.so, libstdc++.so and linker. These binaries needed in the ramdisk.

But should these be in the sbin?

sgt. meow said:
But should these be in the sbin?
Click to expand...
Click to collapse
Yes, you can place here. Or any other place, but need to add the path in init.rc. For example:
export PATH /sbin
EDIT: I forgot, libm.so also needed

One more thing. Should I try this with ICS or JB?

sgt. meow said:
One more thing. Should I try this with ICS or JB?
Click to expand...
Click to collapse
If you built with ics source tree then ics and if jb then jb
Sent from my X8 using xda app-developers app

sgt. meow said:
One more thing. Should I try this with ICS or JB?
Click to expand...
Click to collapse
I tried with cm7 For my own goal the ICS/JB is too slow/unstable. But Daveee10 working on twrp with his own JB project, looks like he have same results with CM11 than me with CM7. I think the problem source is not the CM version, maybe something missing from the device specific files.

Gionee E7 Stock Kernel

This is the development thread to bring up the stock kernel from source. Currently we have the following options.
1. Use source provided by burakgon.
Pros: Nearly complete and working.
Cons: The panel, backlight and touch screen drivers are missing
Solved: Panel.
Observations and possible solutions:
Backlight: Backlight used is TI lm3630. Use source from Oppo Find 7 or nexus 5.
Code:
backlight ic name = lm3630
Registered led device: lcd-cabc
lm3630 probe done
tps ic name = tps65132
tps65132 probe done
Issues: We do not know the gpio pins used for the backlight.
Touch Screen: From the defconfig, It we know it has "CONFIG_GN_Q_BSP_TP_SYNAPTICS_SUPPORT=y"
It seems to be some custom touch screen based on "synaptics_rmi4_i2c"
We just dont have the firmwares it uses. Needs more research.
Everything else seems to be working just fine.
Look at the video below to see how it boots up currently:
http://youtu.be/xKGzjx66Vj8
Here is log that shows up: http://pastebin.com/wC9ruETB
Here is how it should be (from stock kernel): http://pastebin.com/7F2eWEec
Notice the differences. And also, ignore the qpnp spam messages.
Instructions to build kernel from source.
Export arch, subarch and cc. (I expect you to have prior experience building kernels, so I will not write how to do that.)
Code:
make e7_defconfig
make
dtbTool -o ~/dt.img -s 2048 -p scripts/dtc/ arch/arm/boot/
Now copy over the zImage and initramfs.cpio.gz to a folder and run the command
Code:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x0 --cmdline 'ttyHSL0,115200,n8 androidboot.hardware=qcom loglevel=4 maxcpus=2 user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --dt ~/dt.img -o boot.img
NOTE: YOU NEED TO USE CUSTOM mkbootimg. I will attach some tools later which are compatible.
Copy over to your device and flash it.
Here is a tip: Flash it as recovery to recovery partition and boot from there even if its a normal boot image. That way, even if the kernel wont boot, you can just reboot to get into system as the original boot partition was untouched. From there flash back the custom recovery of your choice.
2. Use sources from CAF directly.
This is much harder but will just be updated. we can start by using msm8974 defconfig and add necessary data. Much harder.
3. Wait for Gionee to release sources.
KEEP YOUR POSTS RELATED TO TOPIC ONLY. THIS IS A DEVELOPMENT SUB FORUM.
XDA:DevDB Information
Stock Kernel, Kernel for the GiONEE Elife E7
Contributors
Ravikirancg
Kernel Special Features:
Version Information
Status: Testing
Created 2014-06-07
Last Updated 2014-06-08

Reserved
Here is dt image from stock boot image
http://d-h.st/NeW
And refer this
http://forum.xda-developers.com/showthread.php?t=2469421

Reserved

Ravikirancg said:
This is the development thread to bring up the stock kernel from source. Currently we have the following options.
1. Use source provided by burakgon.
Pros: Nearly complete and working.
Cons: The panel, backlight and touch screen drivers are missing
Solved: Panel.
Observations and possible solutions:
Backlight: Backlight used is TI lm3630. Use source from Oppo Find 7 or nexus 5.
Code:
backlight ic name = lm3630
Registered led device: lcd-cabc
lm3630 probe done
tps ic name = tps65132
tps65132 probe done
Issues: We do not know the gpio pins used for the backlight.
Touch Screen: From the defconfig, It we know it has "CONFIG_GN_Q_BSP_TP_SYNAPTICS_SUPPORT=y"
It seems to be some custom touch screen based on "synaptics_rmi4_i2c"
We just dont have the firmwares it uses. Needs more research.
Everything else seems to be working just fine.
Look at the video below to see how it boots up currently:
http://youtu.be/xKGzjx66Vj8
Here is log that shows up: http://pastebin.com/wC9ruETB
Here is how it should be (from stock kernel): http://pastebin.com/7F2eWEec
Notice the differences. And also, ignore the qpnp spam messages.
Instructions to build kernel from source.
Export arch, subarch and cc. (I expect you to have prior experience building kernels, so I will not write how to do that.)
Code:
make e7_defconfig
make
dtbTool -o ~/dt.img -s 2048 -p scripts/dtc/ arch/arm/boot/
Now copy over the zImage and initramfs.cpio.gz to a folder and run the command
Code:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x0 --cmdline 'ttyHSL0,115200,n8 androidboot.hardware=qcom loglevel=4 maxcpus=2 user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --dt ~/dt.img -o boot.img
NOTE: YOU NEED TO USE CUSTOM mkbootimg. I will attach some tools later which are compatible.
Copy over to your device and flash it.
Here is a tip: Flash it as recovery to recovery partition and boot from there even if its a normal boot image. That way, even if the kernel wont boot, you can just reboot to get into system as the original boot partition was untouched. From there flash back the custom recovery of your choice.
2. Use sources from CAF directly.
This is much harder but will just be updated. we can start by using msm8974 defconfig and add necessary data. Much harder.
3. Wait for Gionee to release sources.
KEEP YOUR POSTS RELATED TO TOPIC ONLY. THIS IS A DEVELOPMENT SUB FORUM.
XDA:DevDB Information
Stock Kernel, Kernel for the GiONEE Elife E7
Contributors
Ravikirancg
Kernel Special Features:
Version Information
Status: Testing
Created 2014-06-07
Last Updated 2014-06-08
Click to expand...
Click to collapse
Hello bro...can u come on facebook..btw just proposed some changes on the git

check this

what are two lines on display backlight defect? or shadow of some light soutce

dhirajranger said:
what are two lines on display backlight defect? or shadow of some light soutce
Click to expand...
Click to collapse
since the backlight is not working...it is showing like this.

So what to do now???
should we wait fro source release by Gionee?

yasirmujtaba said:
So what to do now???
should we wait fro source release by Gionee?
Click to expand...
Click to collapse
If they are releasing then very good..otherwise..have to try out ourselves...trying different drivers from lg nexus 5, oppo find 7...

hi guys any update ?
i installed omni Rom 4.4.4 on my friends galaxy s i9000 and god damn it,it is buttery smooth !!

simmer14 said:
hi guys any update ?
i installed omni Rom 4.4.4 on my friends galaxy s i9000 and god damn it,it is buttery smooth !!
Click to expand...
Click to collapse
I received a package from Gionee India containing the tools for flashing. Though the tool does not work, I did find a log that can help us. Simply put, we now know exactly what we are looking for.. We might be able to solve the backlight issue but I highly doubt that for touch screen.. as that use some considerably modified source..
LOG: https://www.mediafire.com/?qs4kc1dzras9gow

that's great news that you received something from Gionee itself. Can't they provide you kernel sources directly or indirectly? Have you asked your contact to provide that? Thanks.

Ravikirancg said:
I received a package from Gionee India containing the tools for flashing. Though the tool does not work, I did find a log that can help us. Simply put, we now know exactly what we are looking for.. We might be able to solve the backlight issue but I highly doubt that for touch screen.. as that use some considerably modified source..
LOG: https://www.mediafire.com/?qs4kc1dzras9gow
Click to expand...
Click to collapse
Is That GNQC Downloader One????
Opening Multiple Drives When Connecting????

yasirmujtaba said:
Is That GNQC Downloader One????
Opening Multiple Drives When Connecting????
Click to expand...
Click to collapse
Yes it is the GNQC Downloader.. And the Indian version firmware. But I do not understand what you mean by "opening multiple drives when connecting"
Sent from my E7

use win xp
Ravikirancg said:
Yes it is the GNQC Downloader.. And the Indian version firmware. But I do not understand what you mean by "opening multiple drives when connecting"
Sent from my E7
Click to expand...
Click to collapse
if your e7 is dead and then you connect it to your pc it will pop up 7-8 drives
most of them are blank
use win xp for flashing thats it

Any update about source code???!

need indian version stock rom and flashtool
i need stock indian version rom and flash tool can any 1 help me

@Ravikirancg plz update us about ur work..... plz so that we could help u or get aware of the situation.... its a request plz

So guyz does new update completed ur source code or not ?

Stock recovey of e7 kitkat pls

[Q] Error while compiling CM12.1

--------------------------Solution--------------------------
Thanks to @sdr4wkcab
Notice:You should replace paths with your own.
1.Open /device/samsung/ks01lte/BoardConfig.mk
2.Change
BOARD_PROVIDES_LIBRIL := ture
to
BOARD_PROVIDES_LIBRIL := false
3.Extract libril.so from stock ROM.
4.Add these lines to /device/samsung/ks01lte/Android.mk
Code:
$(shell mkdir -p $(OUT)/obj/lib)
$(shell cp -f ~/cm12.1/others/libril.so $(OUT)/obj/lib/)
5.Put libril.so in a folder "others" right in the root directory of the source file.
Rom then can be built normally.
______________________________________
Hi!
I want to compile CM12.1 myself.
Butttttt
Code:
Import includes file: /home/builder/cm12.1/out/target/product/ks01lte/obj/EXECUTABLES/rfc_intermediates/import_includes
make: *** No rule to make target “/home/builder/cm12.1/out/target/product/ks01lte/obj/EXECUTABLES/rild_intermediates/import_includes” Needed by “/home/builder/cm12.1/out/target/product/ks01lte/obj/SHARED_LIBRARIES/libril_intermediates/export_includes”. Stop.
make: *** Waiting for unfinished jobs...
Export includes file: external/bluetooth/bluedroid/test/rfcommtest/Android.mk -- /home/builder/cm/out/target/product/ks01lte/obj/EXECUTABLES/rfc_intermediates/export_includes
#### make failed to build some targets (02:48 (mm:ss)) ####
This is what I always encounter 2min after brunch. I have re-sync for many times, but it won't help.
Any way to solve this ? Thanks in advance!!

Same here building for Note 4. Any ideas guys?

Well, ROM built with SIM card not recognized.

Try setting BOARD_PROVIDES_LIBRIL := false in the BoardConfig.mk and copying the librild.so by hand from your backup.

sdr4wkcab said:
Try setting BOARD_PROVIDES_LIBRIL := false in the BoardConfig.mk and copying the librild.so by hand from your backup.
Click to expand...
Click to collapse
Thanks! It finally works!

Just remember that RIL (Radio Interface Library) is something Android needs in order to communicate with the phone's modem (i.e. make calls, send msm, change SIM-settings, etc.). If you don't have this in the correct way on your ROM you will have instead of a GSG5 mobile phone a very small non-SIM-capable tablet in the end, running CM
If you are suspicous about using a binary blob like this in your own distribution, rejoice, for your suspicion was justified: RILd is shamelessly backdoored (just google for "Replicant Samsung Galaxy backdoor"). Luckily the Replicant developers managed to initiate an open-source replacement for Samsung's RIL, which heavily needs contributors..

sdr4wkcab said:
Just remember that RIL (Radio Interface Library) is something Android needs in order to communicate with the phone's modem (i.e. make calls, send msm, change SIM-settings, etc.). If you don't have this in the correct way on your ROM you will have instead of a GSG5 mobile phone a very small non-SIM-capable tablet in the end, running CM
If you are suspicous about using a binary blob like this in your own distribution, rejoice, for your suspicion was justified: RILd is shamelessly backdoored (just google for "Replicant Samsung Galaxy backdoor"). Luckily the Replicant developers managed to initiate an open-source replacement for Samsung's RIL, which heavily needs contributors..
Click to expand...
Click to collapse
Thanks for that info.
I have very little skills of coding or debugging on these stuffs.... It can take me a long to look for practical and useful guide or tutorial, or even finally know about the source code.
The Rom I built works normally now, "apparently", with overheat along and occasional sudden freeze. I did sync the source code from cm's github, but the the only maintainer of my device on CyanogenMod seems to stop maintaining this device (ks01lte) :crying: So there must be much to improve.
I'm trying to build kernel from Note 3's source code, which is almost identical to my device except for few things like memory size. But failed today. Will investigate more.

How do I add my own test app to my rom?

I know I build an app and run it on my phone and perhaps even publish it. That is not my goal however. I want to add an executable to a rom, which I have built from source. Little bit of background: I have a build environment for Samsung Note 3. I downloaded the source code from Samsung and Google, and compiled my own image. Now I want to put an executable in the image, which I flash the phone with. So I did some research and found out I should create a project folder in /packages/app/ directory. I did that, and here is what is in the directory...
Code:
[email protected]:~/WORKING_DIRECTORY/packages/apps/use-tbt$ ls
Android.mk use-tbt.c
[email protected]:~/WORKING_DIRECTORY/packages/apps/use-tbt$ more Android.mk
LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE := use-tbt
LOCAL_SRC_FILES:= use-tbt
LOCAL_PACKAGE_NAME := use-tbt
LOCAL_STATIC_LIBRARIES := libcutils libc
include $(BUILD_EXECUTABLE)
[email protected]:~/WORKING_DIRECTORY/packages/apps/use-tbt$ more use-tbt.c
/* Hello World program */
#include<stdio.h>
main()
{
printf("Hello World");
}
But once I compile this project, I do not see the executable on the phone. I also need help with coming up with a faster way to validate weather or not this module makes it to the final image successfully. What I mean is the only way I know of how to do that now is to build the whole thing, create an image and flash the phone, then root it, and install busy box and then do a find in the directory structure. Can anyone suggest a better way?
I am trying to learn how to create an emulator image of what I have, but I do not know how to pack and what files and directories to pack in the images which the emulator uses. I do know I need a system.img. But I do not know which directories from the build system go in the system.img. This question I believe belongs to the developer forum, but I am afraid of posting there. Majority of my posts in those groups are moved to the more general groups. It is done in a very polite and nice way; I have to say that I appreciate that. Nevertheless, I would feel better if this post was in one of those forums. Just sayin!

Miui 8(marshmallow) for otus/surnia

Finally MiCode has released marshmallow based patchrom.
Here's the git address And yeah!!!! they added much waited marshmallow branch.
And with patchrom now it can be easily ported to our beloved surnia. and ofcourse otus too .
I'm trying to port it.and its 99% done.I'm just stuck with some rejects.(5 in particular).
And I'm hoping to see MIUI within a week for our moto e.
Truth to be told I'm a noob in this field but I'm trying my best.It will be really helpful and encouraging if someone /devs invest some interest in this eye candy rom
I'm using this guides for patchrom based porting:-
1)GUIDE 1
2)GUIDE 2
3)GUIDE 3
and for makefile I'm using the following---
PHP:
# Makefile for porting MIUI
#
local-zip-file := stockrom.zip
local-out-zip-file := MIUI_YOURDEVICE.zip
local-previous-target-dir :=
local-density :=
local-miui-modified-apps :=
local-miui-removed-apps :=
local-modified-apps :=
# To include the local targets before and after zip the final ZIP file,
# and the local-targets should:
# (1) be defined after including porting.mk if using any global variable(see porting.mk)
# (2) the name should be leaded with local- to prevent any conflict with global targets
local-pre-zip :=
local-after-zip:=
otatype := fullota
include $(PORT_BUILD)/porting.mk
local-pre-zip-misc:
I urge all the moto e2 community members and the respected devs to make this dream come true.
XDA ROCKSSS!!!!

Heres where I'm stuck at
PHP:
~/patchrom/cyclops$ make firstpatch
/home/arnab/patchrom/build/util.mk:156: warning: overriding recipe for target 'stockrom.zip'
/home/arnab/patchrom/build/porting.mk:308: warning: ignoring old recipe for target 'stockrom.zip'
/home/arnab/patchrom/tools/patch_miui_framework.sh /home/arnab/patchrom/android/base-framework /home/arnab/patchrom/android `pwd`
<<< create temp directory to store the old, new source and destination smali code with .line removed
<<< compute the difference between /home/arnab/patchrom/cyclops/temp/old_smali/framework.jar.out and /home/arnab/patchrom/cyclops/temp/new_smali/framework.jar.out
<<< apply the patch into the /home/arnab/patchrom/cyclops/framework.jar.out
patching file /home/arnab/patchrom/cyclops/framework.jar.out/./smali/com/android/internal/os/ZygoteInit.smali
Hunk #1 succeeded at 354 with fuzz 2 (offset 7 lines).
patching file /home/arnab/patchrom/cyclops/framework.jar.out/./smali/android/content/res/Resources.smali
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #2 succeeded at 840 (offset -11 lines).
Hunk #3 succeeded at 4492 with fuzz 2 (offset -35 lines).
patching file /home/arnab/patchrom/cyclops/framework.jar.out/./smali/android/content/pm/PackageParser.smali
Hunk #1 FAILED at 9660.
Hunk #2 FAILED at 9672.
2 out of 2 hunks FAILED -- saving rejects to file /home/arnab/patchrom/cyclops/temp/reject/framework.jar.out/./smali/android/content/pm/PackageParser.smali.rej
patching file /home/arnab/patchrom/cyclops/framework.jar.out/./smali/android/app/ResourcesManager.smali
Hunk #1 FAILED at 213.
Hunk #2 FAILED at 986.
2 out of 2 hunks FAILED -- saving rejects to file /home/arnab/patchrom/cyclops/temp/reject/framework.jar.out/./smali/android/app/ResourcesManager.smali.rej
patching file /home/arnab/patchrom/cyclops/framework.jar.out/./smali/android/app/SystemServiceRegistry.smali
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 856 (offset 106 lines).
patching file /home/arnab/patchrom/cyclops/framework.jar.out/./smali/android/graphics/Bitmap.smali
Hunk #1 succeeded at 43 (offset 2 lines).
<<< compute the difference between /home/arnab/patchrom/cyclops/temp/old_smali/services.jar.out and /home/arnab/patchrom/cyclops/temp/new_smali/services.jar.out
<<< apply the patch into the /home/arnab/patchrom/cyclops/services.jar.out
patching file /home/arnab/patchrom/cyclops/services.jar.out/./smali/com/android/server/am/ActivityStack.smali
Hunk #1 FAILED at 6636.
1 out of 1 hunk FAILED -- saving rejects to file /home/arnab/patchrom/cyclops/temp/reject/services.jar.out/./smali/com/android/server/am/ActivityStack.smali.rej
patching file /home/arnab/patchrom/cyclops/services.jar.out/./smali/com/android/server/am/ActivityManagerService.smali
Hunk #1 succeeded at 84092 (offset 1113 lines).
patching file /home/arnab/patchrom/cyclops/services.jar.out/./smali/com/android/server/policy/PhoneWindowManager.smali
Hunk #1 succeeded at 503 (offset 40 lines).
patching file /home/arnab/patchrom/cyclops/services.jar.out/./smali/com/android/server/wm/WindowManagerService.smali
Hunk #1 FAILED at 708.
1 out of 1 hunk FAILED -- saving rejects to file /home/arnab/patchrom/cyclops/temp/reject/services.jar.out/./smali/com/android/server/wm/WindowManagerService.smali.rej
patching file /home/arnab/patchrom/cyclops/services.jar.out/./smali/com/android/server/SystemServer.smali
Hunk #1 succeeded at 137 (offset -5 lines).
<<< compute the difference between /home/arnab/patchrom/cyclops/temp/old_smali/telephony-common.jar.out and /home/arnab/patchrom/cyclops/temp/new_smali/telephony-common.jar.out
<<< apply the patch into the /home/arnab/patchrom/cyclops/telephony-common.jar.out
<<< compute the difference between /home/arnab/patchrom/cyclops/temp/old_smali/wifi-service.jar.out and /home/arnab/patchrom/cyclops/temp/new_smali/wifi-service.jar.out
<<< apply the patch into the /home/arnab/patchrom/cyclops/wifi-service.jar.out
>>> patch miui into target framework is done. Please look at /home/arnab/patchrom/cyclops/temp/reject to resolve any conflicts!

Can someone/any respected dev please build the rom??
I'm eagerly waiting...
I guarantee.MIUI for moto e 2015 is going to be the most trending rom in otus/surnia community.most of the users were n are still waiting for this rom..
I'm a noob but if you need some help setting the enviornment .I will always feel good to help you.

@anveshparashar please look
And more devs please port it to our Osprey

ExaHamza said:
@anveshparashar please look
And more devs please port it to our Osprey
Click to expand...
Click to collapse
I think devs are working on this

I'm so excited to test it!
Is one of the best, in fact according to my opinion, the best option after stock!

Stuck at this error.Plss Help
PHP:
-S out/framework-res/res -A out/framework-res/assets \
-M out/framework-res/AndroidManifest.xml -F out/framework-res.apk
/bin/bash: /home/arnab/patchrom/tools/linux-x86/aapt: No such file or directory
/home/arnab/patchrom/build/porting.mk:174: recipe for target 'out/framework-res.apk' failed
make: *** [out/framework-res.apk] Error 127

i urge all the devs in moto e2 community to spare some time and please build this rom

i have succesfully made a build for my device (osprey) but it is not booting yet. i am struck on mi bootanimation and adb is inaccessible. i will help you to make device tree to make a successful build

anveshparashar said:
i have succesfully made a build for my device (osprey) but it is not booting yet. I am struck on mi bootanimation and adb is inaccessible. I will help you to make device tree to make a successful build
Click to expand...
Click to collapse
im stuck with the rejects

anveshparashar said:
i have succesfully made a build for my device (osprey) but it is not booting yet. i am struck on mi bootanimation and adb is inaccessible. i will help you to make device tree to make a successful build
Click to expand...
Click to collapse
You have my support for this project in Osprey.

MIUI ROCKS, please developers do the magic! hehe

EsromG5 said:
You have my support for this project in Osprey.
Click to expand...
Click to collapse
can you help me gettin over rejects?

arnabnx said:
can you help me gettin over rejects?
Click to expand...
Click to collapse
it is not necessary to fix all rejects. rejects are only used to warn you that patching changed/replaced/added/subtracted this code in the smali that is different from the original so user have to check whether it can cause conflict.i suggest you to ignore rejects and proceed further they will be patched automatically and use make fullota or make zipfile command in the terminal
Things to be taken care of:-
1.smali and smali2 folder of the framework should be merged
2.how to extract metdata and is it correct(use patchrom/tools/releasetools/ota_target_from_phone -r
t and make sure root is working and adb debugging is on and su request in set to app and adb allow computer authorisation.this will help you to make proper device tree for miui porting)
3.build.prop should conatin "ro.build.fingerprint" with 6 parameter
4.correctly edit makefile and local vendor apps and local vendor priv-apps in makefile
if you want i can upload my device file so you can edit them according to your device

anveshparashar said:
it is not necessary to fix all rejects. rejects are only used to warn you that patching changed/replaced/added/subtracted this code in the smali that is different from the original so user have to check whether it can cause conflict.i suggest you to ignore rejects and proceed further they will be patched automatically and use make fullota or make zipfile command in the terminal
Things to be taken care of:-
1.smali and smali2 folder of the framework should be merged
2.how to extract metdata and is it correct(use patchrom/tools/releasetools/ota_target_from_phone -r
t and make sure root is working and adb debugging is on and su request in set to app and adb allow computer authorisation.this will help you to make proper device tree for miui porting)
3.build.prop should conatin "ro.build.fingerprint" with 6 parameter
4.correctly edit makefile and local vendor apps and local vendor priv-apps in makefile
if you want i can upload my device file so you can edit them according to your device
Click to expand...
Click to collapse
Thats gonna be really nice if you upload your workspace folder on gdrive

arnabnx said:
Thats gonna be really nice if you upload your workspace folder on gdrive
Click to expand...
Click to collapse
ok i will upload metadata and makefile i am using cm13.1 and aosp as base. i will upload cm13.1 metadata first

anveshparashar said:
ok i will upload metadata and makefile i am using cm13.1 and aosp as base. i will upload cm13.1 metadata first
Click to expand...
Click to collapse
ok...thanxxx

here you go download
it conatin metadata and makefile
you have to make same directory as of angler (nexus 6p)

anveshparashar said:
here you go download
it conatin metadata and makefile
you have to make same directory as of angler (nexus 6p)
Click to expand...
Click to collapse
Thanks lemme trry now

You are best