Related
Ok, I'm sure this is been asked before and I'm sure there's references somewhere...I've looked for a couple of days and found what should be answers, but nothing is working like the instructions I've seen...
Here's the simple question; How do I get the Android SDK and Java JDK setup in Ubuntu? I've tried the sudo commands to get the JDK to install, not working for me (as Ubuntu tells me it can't find the files I'm looking for). I've tried moving the SDK into the Root Folder (in the File System area itself), don't have permissions even though I'm logged in as the administrator. I've tried getting the SDK Manager to run through Terminal (home/android-sdk-xxxxx_xxxx/tools/android), can't find the file in terminal, but it's there in the file system exactly where I'm pointing it to.
I'm very new to Linux, but if I'm going to do things that I want to do, I'm going to have to learn. For the most part, I'm prepared to read whatever I need to in order to learn from this, but I also know when I need to ask for some help here. It seems like every command shown to get this started is just not working in the partition I have setup for this. If anyone can help get me started, I'm sure I can pick the rest up along the way!
Thanks in advance!
Macrodroid said:
Ok, I'm sure this is been asked before and I'm sure there's references somewhere...I've looked for a couple of days and found what should be answers, but nothing is working like the instructions I've seen...
Here's the simple question; How do I get the Android SDK and Java JDK setup in Ubuntu? I've tried the sudo commands to get the JDK to install, not working for me (as Ubuntu tells me it can't find the files I'm looking for). I've tried moving the SDK into the Root Folder (in the File System area itself), don't have permissions even though I'm logged in as the administrator. I've tried getting the SDK Manager to run through Terminal (home/android-sdk-xxxxx_xxxx/tools/android), can't find the file in terminal, but it's there in the file system exactly where I'm pointing it to.
I'm very new to Linux, but if I'm going to do things that I want to do, I'm going to have to learn. For the most part, I'm prepared to read whatever I need to in order to learn from this, but I also know when I need to ask for some help here. It seems like every command shown to get this started is just not working in the partition I have setup for this. If anyone can help get me started, I'm sure I can pick the rest up along the way!
Thanks in advance!
Click to expand...
Click to collapse
I think you could possibly use part of the EasyDev-v6 script in the Development and just cut out everything after installing prerequesites. It probably installs the JDK and the SDK among everything else, and it probably wouldn't hurt with the other things that installs, too. Just cut out everything after the prerequesites (it's just a regular text file but it'll be easier to edit in Ubuntu with OpenOffice).
Also check out http://maketecheasier.com/install-android-sdk-in-ubuntu-karmic/2010/01/11. As far as I know it worked when I tried it.
roirraW "edor" ehT said:
I think you could possibly use part of the EasyDev-v6 script in the Development and just cut out everything after installing prerequesites. It probably installs the JDK and the SDK among everything else, and it probably wouldn't hurt with the other things that installs, too. Just cut out everything after the prerequesites (it's just a regular text file but it'll be easier to edit in Ubuntu with OpenOffice).
Also check out http://maketecheasier.com/install-android-sdk-in-ubuntu-karmic/2010/01/11. As far as I know it worked when I tried it.
Click to expand...
Click to collapse
Dude, thanks so much! That worked perfectly. Thanks!
Sent from my Froyo Tazz using XDA App
You're welcome!
I was wondering if anyone has figured out a way to get HULU to work. Thanks!
For WebOS there is a work around, search from it. For CM7, just as simple as downloading the app
erick161 said:
For WebOS there is a work around, search from it. For CM7, just as simple as downloading the app
Click to expand...
Click to collapse
Hulu does not work in webOS.
Nburnes said:
Hulu does not work in webOS.
Click to expand...
Click to collapse
they blocked the new method too?
both WebOS and Cm7 works with Hulu....same method (mod flash and change user agent)
Nburnes said:
Hulu does not work in webOS.
Click to expand...
Click to collapse
There was a recent work around after the patch failed, never tried it, never cared enough too.
As for CM7, why flash anything? There's an app. Granted you must be a subscriber..
erick161 said:
There was a recent work around after the patch failed, never tried it, never cared enough too.
As for CM7, why flash anything? There's an app. Granted you must be a subscriber..
Click to expand...
Click to collapse
Ahh never knew there was a fix for the fix.
Edit: Mind linking?
was working till the webOS upgrade to 3.0.4
this workaround was working until the new webos 3.0.4 the new update...the patch says ” could not find area to patch (unknown file version)
claptop dot com/2011/08/make-hulu-work-on-hp-touchpad/comment-page-1
I fixed hulu with a patch for 3.0.4...
It's an alpha, it's quick and dirty, but it works. Find the patch itself here:
forums DOT precentral DOT net/3218146-post139.html
For some reason I can't upload it here (maybe not enough posts or something).
Ok, after much annoyance and a couple webOS doctors, I think I FINALLY have an all-in-one fairly idiotproof patch...
WARNING!!!!!! If you have already done this patching process manually, this patch MAY NOT WORK! You may break your flash player if you run this patch after having performed the manual work and require a visit to the webOS doctor! DO NOT RUN THIS PATCH UNLESS YOUR TOUCHPAD IS COMPLETELY BACK TO STOCK ON IT'S USER AGENT AND FLASH IDENTIFIER STRING.
Please note, this is an ALPHA patch. It will likely throw an error or two but it should work. You should be able to run this patch and it will install the hulu user agent fix AND the flash fix without requiring a reboot. Again, this is an ALPHA patch and I am not responsible if you install it and it magically borks your touchpad. This will do nothing a webOS doctor won't fix, so gauge your willingness to test this patch on whether or not you'd be ok running a doctor if things go wrong.
To install:
Step one: Download the file attached to THIS post and EXTRACT (unzip) it to an easy to find spot (like your desktop).
Step two: "send" this file (tools > send file) using webosquickinstall to /media/internal
OR: put the touchpad into USB mode and drag/drop this EXTRACTED file to your touchpad (that will automatically put it in the /media/internal directory)
Step three: open a linux command line (tools > linux commandline) in webosquickinstall
OR: open a terminal window on the touchpad itself in xterm (you will need to install xecutah, xserver, and xterm from preware to do this).
Step four: type this exactly into the terminal window:
/media/internal/hulu
The device will very likely pop an error or two (again this is an ALPHA patch), but it should finish up without any real trouble in under 30 seconds. There is NO reboot required.
TADA, HULU works once more! Your app catalog is now broken.
If it's still not working (black screen on videos) you need to remove any adblocking patches you have (adblock or max blocker), delete cache/history/cookies in the browser, and reboot the touchpad. Now Hulu will work.
When you want to fix your app catalog so you can download new programs, go back to the linux command line again (in webosquickinstall) and type:
/media/internal/hulu uninstall.
This will break hulu and fix your app catalog. It'll take 30 seconds or less to complete and you're back in business.
The patch will stay on the device, so you can easily flip back and forth from hulu installed and uninstalled.
Perhaps he doesn't want to subscribe??
There are patches and fixes etc etc for other phones, and I'm sure ultimately its all the same.. its just like the WebOS packages.. Im sure you can apply it on the touchpad, but I haven't done it or anything.. this is to allow you to watch it within a browser of course.. app is great if you pay for it..
Ya Im a poor college kid so I was really wondering what was the latest and greatest modded flash zip file. There are a few million online and I didnt want to have to flash 20 before I got one that worked. In the end I was able to find one that works like a charm so thanks guys!
Hulu!
Uninstall what ever version of adobe flash (if any). Search Vgeezyflash 74 in google, it should be the first post on a "toshiba Thrive" forum. Download the modified adobe flash 11 .apk ("apk" is file for you noobs. Install, and reboot for good luck. Then open the android stock browser (i could never get it to work right on any other), change the user agent to IE6 and delete all cookies, etc. This process worked for me on the Touchpad and on my Nook Color.
or...just go to
Code:
http://download.hulu.com/huludesktop.swf
tested...working on webos
Hulu working
Have you hit the upgrade prompt?
it seems to work better if you click ignore...but still works either way
hulu on WebOS
takes a few tries but it will go eventually - I've tried either way as well - sometimes shows crash in the middle of the episode and you have to start over - as well as restarting the instance randomly - hit Menu and select TV - starts to spool and eventually will take you to start again
Since new users can't post to the development forum, I am posting here the APK I built to root the Transformer Prime without using ADB or a PC. The source code is also included. This work is an unofficial extension of the work done by jcase (Justin Case).
Instructions:
1. Install APK on to your tablet
2. Open the NachorootPrime application. It should say that stage 1 is done and to reboot the tablet. Power off and then power on the tablet.
2. Open the NachorootPrime application again, and this time it should say that stage 2 is done and to reboot. Power cycle.
3. Open the NachorootPrime application for the last time, it will be blank for a few seconds, then automatically power cycle. Su is now installed in /system/bin/su.
4. Install the Superuser application from the Marketplace. You can uninstall the NachorootPrime application.
If you run the NachorootPrime application after the third time, it should tell you that your tablet is already rooted.
I am publishing the source code since the exploit is not very complicated, and if ASUS cared they could easily figure it out. Information wants to be free.
thanks..this is needed for people with no PC access or don't feel like booting up PC and connecting prime to it. will await to see someone test this and confirm it works.
Also F.Y.I I think the mods will **** this thread down quick. just based on rules of forum. you have to credit originator of Nachoroot, Jcase. even before that though. u were supposed to ask for his permission roms use his exploit. someone else tried to do something similar without following xda or developers rules and it was shut down quick. just trying to give you heads up. I already saved the apk though . now waiting for a guinea pig to test and confirm this works without problems.
z0_ said:
Since new users can't post to the development forum, I am posting here the APK I built to root the Transformer Prime without using ADB or a PC. The source code is also included. This work is an unofficial extension of the work done by jcase (Justin Case).
Instructions:
1. Install APK on to your tablet
2. Open the NachorootPrime application. It should say that stage 1 is done and to reboot the tablet. Power off and then power on the tablet.
2. Open the NachorootPrime application again, and this time it should say that stage 2 is done and to reboot. Power cycle.
3. Open the NachorootPrime application for the last time, it will be blank for a few seconds, then automatically power cycle. Su is now installed in /system/bin/su.
4. Install the Superuser application from the Marketplace. You can uninstall the NachorootPrime application.
If you run the NachorootPrime application after the third time, it should tell you that your tablet is already rooted.
I am publishing the source code since the exploit is not very complicated, and if ASUS cared they could easily figure it out. Information wants to be free.
Click to expand...
Click to collapse
contact jcase before you put this apk man. you need his approval for using any of his code in the forums
good to see the developing started!
****. remove the source at least. we dont want asus finding that and fixing the root
Just to be clear, I did not use any code provided by jcase. The code does use the technique discovered by jcase, and I credit him for such in my first post.
z0_ said:
Just to be clear, I did not use any code provided by jcase. The code does use the technique discovered by jcase, and I credit him for such in my first post.
Click to expand...
Click to collapse
So this isn't Nachoroot then? Thin line if I say so myself. If it isn't his code then this isn't Nachoroot and shouldn't be displayed as such. Even if you are using only his exploit you should talk to him before you put the exploit up in the forums. I would pull the apk until you talk to him. Just my $.02
Good job at reversing the stuff I was trying not to publicly out until after the ICS OTA, then publicly publish without any kind of protection.
I was going to open source it after the OTA.
I really appreciate it man </sarcasm>
z0_ said:
Since new users can't post to the development forum, I am posting here the APK I built to root the Transformer Prime without using ADB or a PC. The source code is also included. This work is an unofficial extension of the work done by jcase (Justin Case).
Instructions:
1. Install APK on to your tablet
2. Open the NachorootPrime application. It should say that stage 1 is done and to reboot the tablet. Power off and then power on the tablet.
2. Open the NachorootPrime application again, and this time it should say that stage 2 is done and to reboot. Power cycle.
3. Open the NachorootPrime application for the last time, it will be blank for a few seconds, then automatically power cycle. Su is now installed in /system/bin/su.
4. Install the Superuser application from the Marketplace. You can uninstall the NachorootPrime application.
If you run the NachorootPrime application after the third time, it should tell you that your tablet is already rooted.
I am publishing the source code since the exploit is not very complicated, and if ASUS cared they could easily figure it out. Information wants to be free.
Click to expand...
Click to collapse
At the very least you could of asked before posting it, so I could of
A) made a bin just for you to post
and
B) explain why i didnt post it as a shell script just yet
z0_ said:
Just to be clear, I did not use any code provided by jcase. The code does use the technique discovered by jcase, and I credit him for such in my first post.
Click to expand...
Click to collapse
i'm also saying your an idiot.
their is a reason why he didn't put a source.. because he didn't want ASUS figuring it out and patching it when ICS came out.. now we have a potential of no rooted devices for ICS.
thanksssssssssssssssssss
I think developement for prime is gonna be huge. I think the fact that its a first in alot of aspects of the tablet world entices people. we got people popping out the woodworks with stuff for the Prime.
I wonder if this will work with Voodoo OztA rootkeeper once ICS drops.
I have a folder filling up in my downloads folder called Android tools. I have all the stuff from the developement section saved in my prime for when I'm ready to make that move
edit: oh S?!#..lol I see a Developers war done started. I really hope Asus doesn't find out and patch up the exploit in ICS. all they have to do is get a hold of this then its a wrap for root on ICS. at least through this exploit method. Things are heating up as we get closer to ICS release.
demandarin said:
I think developement for prime is gonna be huge. I think the fact that its a first in alot of aspects of the tablet world entices people. we got people popping out the woodworks with stuff for the Prime.
I wonder if this will work with Voodoo OztA rootkeeper once ICS drops.
I have a folder filling up in my downloads folder called Android tools. I have all the stuff from the developement section saved in my prime for when I'm ready to make that move
Click to expand...
Click to collapse
ICS will completely wipe the /system/ folder, so rootkeeper will not work
You should want ASUS to fix an obvious vulnerability in its software.
In its current state, any application you download and install on your tablet could get root permissions using this technique. At that point it could install a rootkit, send off all of your email and SMS to a remote server, log all of your passwords, etc. Especially if you want to use your tablet as a computer replacement, you want it be secure.
Removed files per original devs request.
Hello,
I'm willing to try and build a custom rom, but I've been diving through the site for a few days and I still don't get it. I believe I do have the required background to do this: programming, linux, etc. and I have wide experience as a phone user, etc. It's just that either I'm not reading what I need or the way I want it. The problem, I believe, is that all I find are guides telling me to install this and those tools and then open this and that and voila! you got your rom. But they're not explaining WHAT exactly goes into those roms, or what is expected to go there, what's the purpose of those contents, etc., and I can't really catch with that. I feel at a loss and hate wasting my time turning around for nothing.
1. I don't understand the difference between a flashable rom and one that is meant to be installed through recovery, although I can see they're different. Do they both models contain the same kind of data? Is there any restriction to what one model can contain over the other one? If so, how would I convert from one to the other? But please, don't tell me to use this or that tool. I just need the theory behind it. Something of sorts like: "You need to extract this or that from this tarball, then mount this image, then the directory tree there goes in that directory over the other model of rom"
2. update-binary: Okay I guess this is run when installing from recovery, and this takes care of installing the rom, right?wrong?. Is this a per-rom thing, per-device thing? generic? If it's per-rom, how to generate it? do I need to compile something? Is there any generic source code that can be used as a start?
3. Although I have a basic understanding of how the Linux directory tree works, I know Android works on top of a heavily modified Linux. So can you explain briefly how the directory tree works? For instance, I believe /data/data is where Android apps install to, in /system/bin or xbin I can find busybox binaries/symlinks if present. /dev and /proc look the same as in Linux. I don't know about /sys. Also how are both rom models deployed to this tree? What is basically being copied?
4. If I were to compile a kernel, where do I find the Android kernel sources? or is it just a generic Linux kernel? where can i get a basic config for the device? Last time I checked my device hadn't /proc/config.gz but maybe I could get it from another rom with it enabled or something. What toolchain and where to get it? Oh and if you know of a native arm version of gcc or whatsnot, I'd prefer that. Setting up IDEs or toolchains is a nightmare. I don't like crosscompiling. But crosscompiling or not, a directory with all needed binaries without needing to set up system variables nor other stuff, would be amazing.
I surely have a lot more questions that I can't get from the back of my mind now, and I'll have yet more as you explain. But the point of my questions was mainly trying to explain the degree of the loss I'm at, so you can assist me better.
If it looks like a foolish petition, well, that's because I'm quite stubborn and can't catch things that don't go my way. I really need to understand the basics before I can move into actually doing something. I want to build a rom for the right reasons(to me). It's not just about packing a set of apps or themes with it, but about learning and doing other stuff like trying to fix things that are not supposed to work for the device in that Android version, etc.
If you can't help, congrats for reading through here anyways But any help is greatly appreciated :good:
oxiroxt said:
Hello,
I'm willing to try and build a custom rom, but I've been diving through the site for a few days and I still don't get it. I believe I do have the required background to do this: programming, linux, etc. and I have wide experience as a phone user, etc. It's just that either I'm not reading what I need or the way I want it. The problem, I believe, is that all I find are guides telling me to install this and those tools and then open this and that and voila! you got your rom. But they're not explaining WHAT exactly goes into those roms, or what is expected to go there, what's the purpose of those contents, etc., and I can't really catch with that. I feel at a loss and hate wasting my time turning around for nothing.
1. I don't understand the difference between a flashable rom and one that is meant to be installed through recovery, although I can see they're different. Do they both models contain the same kind of data? Is there any restriction to what one model can contain over the other one? If so, how would I convert from one to the other? But please, don't tell me to use this or that tool. I just need the theory behind it. Something of sorts like: "You need to extract this or that from this tarball, then mount this image, then the directory tree there goes in that directory over the other model of rom"
2. update-binary: Okay I guess this is run when installing from recovery, and this takes care of installing the rom, right?wrong?. Is this a per-rom thing, per-device thing? generic? If it's per-rom, how to generate it? do I need to compile something? Is there any generic source code that can be used as a start?
3. Although I have a basic understanding of how the Linux directory tree works, I know Android works on top of a heavily modified Linux. So can you explain briefly how the directory tree works? For instance, I believe /data/data is where Android apps install to, in /system/bin or xbin I can find busybox binaries/symlinks if present. /dev and /proc look the same as in Linux. I don't know about /sys. Also how are both rom models deployed to this tree? What is basically being copied?
4. If I were to compile a kernel, where do I find the Android kernel sources? or is it just a generic Linux kernel? where can i get a basic config for the device? Last time I checked my device hadn't /proc/config.gz but maybe I could get it from another rom with it enabled or something. What toolchain and where to get it? Oh and if you know of a native arm version of gcc or whatsnot, I'd prefer that. Setting up IDEs or toolchains is a nightmare. I don't like crosscompiling. But crosscompiling or not, a directory with all needed binaries without needing to set up system variables nor other stuff, would be amazing.
I surely have a lot more questions that I can't get from the back of my mind now, and I'll have yet more as you explain. But the point of my questions was mainly trying to explain the degree of the loss I'm at, so you can assist me better.
If it looks like a foolish petition, well, that's because I'm quite stubborn and can't catch things that don't go my way. I really need to understand the basics before I can move into actually doing something. I want to build a rom for the right reasons(to me). It's not just about packing a set of apps or themes with it, but about learning and doing other stuff like trying to fix things that are not supposed to work for the device in that Android version, etc.
If you can't help, congrats for reading through here anyways But any help is greatly appreciated :good:
Click to expand...
Click to collapse
I am not terribly knowledgeable about all of this, but I will take a crack at it. Others can feel free to correct me.
1. "Flashing" is usually done through the recovery from a zip with an update script inside. That script is in a language called "edify". Read more about Edify Here and Here.
The only other common way that I know of installing a ROM is through fastboot in the bootloader, but that is normally only used with official factory images. Also, I think Samsung ROMs are often flashed with a proprietary program called Odin.
2. I think that the update-binary is standard across all recent devices. I think it is just an interpreter for the Edify scripting language. Old versions of android used a somewhat different scripting language and required a different file. You can probably pull the binary out of another recent zip and use that. The main thing you have to worry about is the update script (instructions for what the zip does) and the folder structure of the zip.
3. I am not confident to explain much here, but the apps and their data are stored in different places. User apps are stored in /data/app with app data stored in /data/data, I think. System apps are installed in /system/app. There is more files stored on the "sdcard" partition which can be internal or external, depending on the device.
4. Kernel sources are usually provided in the source code from whatever repo you are using. Different ROMs use different bases. Here is some info about grabbing the AOSP kernel sources with git: http://source.android.com/source/building-kernels.html
Many of the more popular ROMS have specific build instructions on their individual github pages (Cyanogen, Paranoid Android, etc), so you might what to look at those, too. Also, depending on the individual devices, there might be proprietary binaries sourced from the device or hardware manufacturers for things like camera drivers, graphics chips, etc.
If you want a walk through of the basic build process google has a tutorial. The last time I checked there seemed to be some outdated info, but it might give you a general idea of the build process. http://source.android.com/source/initializing.html
Hopefully someone more knowledgeable can give you more info, but that is all I got
synesthete said:
I am not terribly knowledgeable about all of this, but I will take a crack at it. Others can feel free to correct me.
1. "Flashing" is usually done through the recovery from a zip with an update script inside. That script is in a language called "edify". Read more about Edify Here and Here.
The only other common way that I know of installing a ROM is through fastboot in the bootloader, but that is normally only used with official factory images. Also, I think Samsung ROMs are often flashed with a proprietary program called Odin.
2. I think that the update-binary is standard across all recent devices. I think it is just an interpreter for the Edify scripting language. Old versions of android used a somewhat different scripting language and required a different file. You can probably pull the binary out of another recent zip and use that. The main thing you have to worry about is the update script (instructions for what the zip does) and the folder structure of the zip.
3. I am not confident to explain much here, but the apps and their data are stored in different places. User apps are stored in /data/app with app data stored in /data/data, I think. System apps are installed in /system/app. There is more files stored on the "sdcard" partition which can be internal or external, depending on the device.
4. Kernel sources are usually provided in the source code from whatever repo you are using. Different ROMs use different bases. Here is some info about grabbing the AOSP kernel sources with git: http://source.android.com/source/building-kernels.html
Many of the more popular ROMS have specific build instructions on their individual github pages (Cyanogen, Paranoid Android, etc), so you might what to look at those, too. Also, depending on the individual devices, there might be proprietary binaries sourced from the device or hardware manufacturers for things like camera drivers, graphics chips, etc.
If you want a walk through of the basic build process google has a tutorial. The last time I checked there seemed to be some outdated info, but it might give you a general idea of the build process. http://source.android.com/source/initializing.html
Hopefully someone more knowledgeable can give you more info, but that is all I got
Click to expand...
Click to collapse
OMG Finally some light! THANK YOU, THANK YOU, THANK YOU for all the info. I didn't get much right now, I'll need to read through your post a few times before I get it all, haha. I'll be sure to check the links too. Thank you!
As you might know, palm rejection on non stock roms has not worked for a long time. The symptoms are that when you try to draw with the s-pen in apps like squid or OneNote, often what you draw gets immediately erased.
I went back to CM13.0, where it supposedly did work, and checked what the difference is. I got lucky, and found the right files. It seems that palm rejection was removed from the file InputReader.cpp in frameworks_native/tree/p/services/inputflinger.
I'm sure there was a very good reason for that removal, probably because this is not the right place to do it. I tried to see what would happen if I put it back. I compiled XenonHD with the change, and now my s-pen works great! I tried squid, one note, gboard handwriting and others, and all works. I think this change can probably be easily incorporated into all AOSP/LOS roms.
The files are at https://github.com/ghostwheel/frameworks_native/tree/p/services/inputflinger , and you need InputReader.cpp and InputReader.h
As I said, there is probably a better way to enable palm rejection, but this works for now.
Update Actually, it seems the change was introduced between 14.1 and 15.0 . Look here: https://github.com/LineageOS/android_frameworks_native/blob/cm-14.1/services/inputflinger/InputReader.cpp. But I can't find the particular change that
caused this. Maybe it didn't have a great reason?
help me how to implement this to a rom
Might be interested in trying this (assuming I just replace/modify some files, right?) I'm assuming its harder than that.
Can you please make detailed tutorial? Both Havoc and LineageOs android 10.0 have this problem.
You just need to take InputReader.cpp, InputReader.h and also InputDispatcher.cpp from the github above to the code, in frameworks_native/services/inputflinger/. The problem is that usually you don't have control of that dir. If you take control, it is easy.
ghostwheel said:
You just need to take InputReader.cpp, InputReader.h and also InputDispatcher.cpp from the github above to the code, in frameworks_native/services/inputflinger/. The problem is that usually you don't have control of that dir. If you take control, it is easy.
Click to expand...
Click to collapse
Im suspecting you can use something like ES File Explorer (yes I still use an older version I have saved in TB) to just copy those files into the directory?
Dave
I used to use ES file explorer...
All these are source files that need to be compiled together with the android dist.
It might be possible to just copy the result, maybe services.jar inside framework??? Not sure. The right way is to download a distribution, copy the files into the right place, and compile. XenonHD has nice instructions of how to do all that. Though, XenonHD already has all that built in, for exactly that reason....
Thanks a lot, I am really new to all the terms you are using. All I know is to download zip file and flash it with TWRP recovery installer. I can also get the files fro github. What I dont know is: How to modify rom zip file and recompile it back to flashable zip?
Due to this issue, I am keeping my Note 4 in stock android 6.0 unfortunately, this will be life saver for me if you can help anyhow,
Thanks a lot.