Database Info

[GPL] [KERNEL] noobnl's Andromeda v1.4.1 [ROM Manager] [Superuser.apk] compatible!

flash it with clockwork
download: http://www.sdx-downloads.com/devs/noobnl/noobnl.andromeda.kernel.v1.4.1.zip
or
older aka one click version ( extract new kernel & just replace zimage in the main dir)
download: http://www.sdx-downloads.com/devs/noobnl/one.click.andromeda.flasherv1.3.0.zip
1. you need samsung galaxy s drivers
64-bit OS http://db.tt/mQv4SX
32-bit OS http://db.tt/8u6HeG
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run run.bat
4. enjoy!
Features:
Codesourcery G++
Busybox, thanks joeykrim
Remount, thanks joeykrim
superuser.apk with su!
-O3 optimization
Cortex a8
ClockworkMod Compatable Kernel
kernel sources: http://www.sdx-downloads.com/devs/noobnl/andromedakernelsources.zip
*******changelog*******
v1.1 fixes root access, properly removes joeykrim root
v1.1.1 removes additional files
v1.2 broken build
v1.2.1 fixes build number & Cortex a8 with NEON Optimization
v1.2.2 took away neon optmization
v1.3.0 rebuild the modules with cortex a8 & -O3 optimization & enabled ThumbEE in the kernel
v1.3.1 ClockworkMod compatible Kernel!
v1.3.2 fixes broken root and fixes busybox permission
v1.3.3 adds superuser.apk!
v1.3.4 fixes the move superuser.apk to system & fixes a flaw with jk-su
v1.4.0 based on di18 kernel!
v1.4.1 prototype tvout (start a shell & type in "start tvout"
Code:
make -j$CPU_JOB_NUM HOSTCFLAGS="-g -O3" ARCH=arm CFLAGS_KERNEL="-O2 -march=armv7-a -mtune=cortex-a8 -mcpu=cortex-a8" CROSS_COMPILE=$TOOLCHAIN/$TOOLCHAIN_PREFIX
uninstaller: http://firon.net/xda/one.click.stock.flasher.&.root.uninstaller-di18.zip
my github: http://github.com/noobnl/]
Link to the stock samsung source that was used for these kernels.
http://opensource.samsung.com/ Please search for SPH-D700 DI18.

Do I need to root first or does it root when I flash and what does it exactly do. does it remove my programs or anything like that?
Thanks in advance

Excuse me but if I used your old method of rooting. Does this still work?

Updated without any problems. I assume that most of these "improvements" are more under the hood than stuff that would be noticable to the average user. Thank you for your work. I hope we get more talented people on this project. Of coarse this project didn't "explode" with new stuff multiple times a day, there's only a small fraction of people working on it. Once again, I wish I could help with something to get the ball rolling better, but I don't know how to code and I'm no linux guru either.
Helping finding bugs, giving help to people trying to do whatever, and giving feedback is contributing.

herbthehammer said:
Updated without any problems. I assume that most of these "improvements" are more under the hood than stuff that would be noticable to the average user. Thank you for your work. I hope we get more talented people on this project. Of coarse this project didn't "explode" with new stuff multiple times a day, there's only a small fraction of people working on it. Once again, I wish I could help with something to get the ball rolling better, but I don't know how to code and I'm no linux guru either.
Helping finding bugs, giving help to people trying to do whatever, and giving feedback is contributing.
Click to expand...
Click to collapse
Yeah I updated with no problems also.

Also, this is VERY important. If you have Auto Mount, you need to dismount the SD Card in order for this to work.

What is -03 optomizations? And is this a different version than you posted last night at sdx

Sorry for the dumb question, but what's the difference between this and "one click root"? And could someone please explain what installing one the these modified kernels do? Thanks.

jarnail24 said:
Do I need to root first or does it root when I flash and what does it exactly do. does it remove my programs or anything like that?
Thanks in advance
Click to expand...
Click to collapse
x2 been wondering this myself

specialk0324 said:
x2 been wondering this myself
Click to expand...
Click to collapse
It will Flash a Custom Kernel. Which will give you root access. It wont delete anything.

This is updated? Can we just run it again or should one remove then re-install
Well re-ran it doesnt seem to cause any harm lol
I had # at one point when doing ADB shell but now I get $

updated!!!!

noobnl said:
updated!!!!
Click to expand...
Click to collapse
Awesome work as usual. couple questions.
1. I know you have busybox included but its an older version "current "1.18.0" and I can not get that to install after doing your kernel. If I use just he exploit method I can ugrade it via the market.
2. The version number is still reading V1? do you plan on changing that with updates so we can tell what we have installed for us dumb peoples lol
Thanks so much donation coming your way

Worked with a hiccup but it must've been my fault. Other than that, awesome job my friend.

noobnl said:
updated!!!!
Click to expand...
Click to collapse
As stated here is your Redbull fund for the week hopefully its enough to get some more work done! lol
1XH33015CN7654102.

Fixter said:
Worked with a hiccup but it must've been my fault. Other than that, awesome job my friend.
Click to expand...
Click to collapse
Same here, I hope we are able to tell which version is which in the future.
Just ran Linpack, I got 8.0 nothing above that...hmmm how can I check im running the right kernel?

1.2.0 was pulled! broken build

noobnl said:
1.2.0 was pulled! broken build
Click to expand...
Click to collapse
Noob. Please explain. Is the Flasher we ran broken? :S

I realize that you pulled 1.2 bc of broken build but when i try to d/l 1.2.1 zip link not there? is it just me?
says page not found

all for now I guess.... wonder if i should uninstall the 1.2 or just wait

[APP] Synergy for Windows RT (1.3.8 stable & 1.4.12 beta )

All,
Please find the attached Windows RT native binaries for Synergy (v1.3.8 stable). See the project homepage for more details:
http://synergy-foss.org/
Haven't found any issues so far with Synergy, however you must run 'launcher.exe' as Admin or some of the functionality won't work correctly (namely key strokes) . I have binaries for the latest beta version as well but only for the command line tools without a GUI - PM me if you'd like those instead but this one should suit everyone fine.
EDIT: I've added the binaries (and QT4 runtime) for Synergy 1.4.12 Beta. I personally don't like this version as much (more heavy weight and takes more effort to configure) but others have asked for it.. and it was a good test of the QT4 runtime port. Please don't ask me how to configure it, there is plenty of information on the synergy website on sorting out configuration issues.
Cheers!

nice! thanks!

Great, thanks!

Just wanted to say that I had left for sharemouse, but this brought me back!

error when running launcer
I can't get this to run on my surface. I am getting error
the procedure entry point ?id.... could not be located in the dynamic link library

ankadeby said:
I can't get this to run on my surface. I am getting error
the procedure entry point ?id.... could not be located in the dynamic link library
Click to expand...
Click to collapse
I'm also getting this error. I can launch other apps like 7z and Putty.

wingmanjd said:
I'm also getting this error. I can launch other apps like 7z and Putty.
Click to expand...
Click to collapse
Can you send me a screenshot of the error?
Cheers!

bfosterjr said:
Can you send me a screenshot of the error?
Cheers!
Click to expand...
Click to collapse
Sure thing. See attached

I had a similar error with my dosbox port, I believe I fixed it by installing the vcredist for ARM, attached to this post. Even if it doesn't work it won't cause any harm.

netham45 said:
I had a similar error with my dosbox port, I believe I fixed it by installing the vcredist for ARM, attached to this post. Even if it doesn't work it won't cause any harm.
Click to expand...
Click to collapse
Netham45 is correct. The import you're getting an error for is from MSVCP110.dll. Using the redistributable VC runtime should fix this problem. Classic 'dll hell' issue.
If installing the VC runtime doesn't solve the problem, let me know.
Cheers!

I'm sorry as I'm completely off topic, but.. whoa:

netham45 said:
I had a similar error with my dosbox port, I believe I fixed it by installing the vcredist for ARM, attached to this post. Even if it doesn't work it won't cause any harm.
Click to expand...
Click to collapse
This worked for me. Did I miss this dependency in an earlier post?

Any updates to this for 1.4.2? I'd love to get the encryption working across all machines.

latest version.
can we get the latest version?

1.3.8 is the latest _stable_ version. I've already built the binaries for the 1.4.10 beta version (command line only). Once 1.4.x comes out of beta.. I'll gladly look at at porting & posting it.
Cheers!

bfosterjr said:
1.3.8 is the latest _stable_ version. I've already built the binaries for the 1.4.10 beta version (command line only). Once 1.4.x comes out of beta.. I'll gladly look at at porting & posting it.
Cheers!
Click to expand...
Click to collapse
thanks dude! i'll keep posted...

Synergy 1.4.12 Beta added
All,
please see the original post.. I've added the 1.4.12 beta binaries for Windows RT.
Cheers!

RT 8.1 Issue
Hi - Not sure if this is applicable to this post.
Thanks for uploading these, put me well on my way to making use of my Surface RT.
Trying to run Synergy on my RT 8.1 Surface.
Have jailbreak installed (successfully) , but I'm receiving an error when running the synergy executable.
Can't post a link to image here, but the error says:
"Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."
Could this be perhaps because the synergy files were signed from RT 8.0?
Any help would be much appreciated at this point, as i'd really love to get this working!!

Would love to give this a try but all I get is a QtGui4.dll not found error. I've tried finding a source for this DLL online but can't find one that is properly compiled for my Surface RT. Is the OP still around with the proper file that might be added to the post?

[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1

This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download! ​
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!

Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.

whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...

mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess

got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build

rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.

Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!

scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4

scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.

vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers

scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app

scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.

vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!

TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.

scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.

mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.

scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.

scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.

[TOOL][ANDROID]Dark_Multitool-CyanogenMod building.kernel developMent.ADB tool..etc..

******* Hi all ********​I have developed this little tool containing a few utilities that should help anyone do a host of stuff like building Cyanogenmod..Compiling kernels..Play with ADB..GIt tools..etc​
DARK_Multitool1.0​
My tool is divided into five Modules(More to come in future if people find it useful)​
Module 1 : CyanogenMod Tools
- Installing the necessary libraries for compiling Cyanogenmod
- Initializing your repository and getting the Cyanogenmod source code
- Getting prebuilt apps/Device proprietary blobs
- Building Cyanogenmod for your device
Module 2 : ADB tools
- Creating logcat to debug your phone
- Installing apps via ADB
- Push/Pull stuff to/from your android device
Module 3 : Kernel tools
-Sony Kernel
Unpack Kernel Source
Create zImage of various devices(any Xperia)
Extract kernel.sin from ftf file
Unpack kernel.sin(to get zImage and ramdisk)
Make dt.img(For Xperia Z1 and Z ultra)
Make kernel.elf or boot.img depending on device
Test your kernel.elf/boot.img without flashing fully(Test run)
-Nexus Kernel
Getting the source code
Checkout the source code
Building zImage
-Samsung kernel
(Is under development as i develop for Xperia devices and not too familiar with samsung atm)
-Download toolchains
-Unpack boot.img to get zImage and Ramdisk
pearl script unpack or umkbootimg unpack
-Unpack or Repack ramdisk
-Build zImage for a generic kernel(Experimental)
-Take kernel log : Thanks @ricky310711 for the commit
Module 4 : Backup TA partition for Sony or EFS partition on samsung
-Backup TA partition for Sony(By dd Method only)
-Backup or restore efs partition for Samsung(tar or dd method)
Module 5 : GIT tools
-Download GIT package on your linux
-Change directory where you want to initialize git
-Git repository setup(New git setup/Changes to old git setup)
-Update your local and remote git repository
-Commit your additions/deletions
-Push/Pull to/from your github repository
-Automatic push commits to your repository(After git setup is done)
-Download any repository using GIT
Download link
Dark_multitool1.0(With Update 1)
Update 2 added...Will upload soon..You can download this and update via tool to the latest version
Its better to download from XDA DevDB. You can either use the link above or click on downloads on top of the thread to download
How to install??
Download the tar.gz file from the link above..Place it in your home directory and run the following command in your terminal
tar -xjvf dark_multitool1.0.gz
How to run it??
cd to the folder dark_multitool1.0 and type ./menu in your terminal and execute
This tool is only for any linux based distro(Ubuntu,fedora etc) atm and i dont know if it will work in cygwin(Tested on Cygwin by kevinrus123 : Some utilities are working)
You can install vitualbox and install ubuntu or any other linux based distro to use the tool if you are running windows
Credits
-xda and its wonderful devs for teaching me everything
-Doomlord for his exceptional threads and tutorials on Xperia devices
-Rickwyatt and Rekoil for Ta partition backup tutorial for Xperia
-Google.com
If i have forgotten anyone then please let me know
Donations
Running a 512 mb laptop with a semi crashed hard disk.....So any kinds of donations are welcome if you like the tool
>Just donate to my email ID : [email protected]
>I am from India..so personal payment wont work
>Select buy me goods/services and it should work
>You can donate via tool as well.....
Sources
My github source : https://github.com/Smk1989/dark_multitool1.0
Mods : Please Move the thread if its in the inappropriate section
Updates
Latest update = Update 1
-I will keep the thread updated with the latest tool and you can also update the tool through the tool itself
FAQs in the second post
Changelogs in the third post
XDA:DevDB Information
[TOOL][ANDROID]Dark_Multitool-CyanogenMod building.kernel developMent.ADB tool..etc.., a Tool/Utility for the Android General
Contributors
Dark Wraith
Version Information
Status: Alpha
Created 2013-12-11
Last Updated 2014-01-03

FAQs
>Why is it giving errors while compiling zImage for Xperia devices????
Answer : You need to add the various makefile and defconfig fixes for the toolchain to work properly
Please refer to this excellent thread by doomlord for various fixes
http://forum.xda-developers.com/showthread.php?t=2447310
>TA partition and EFS partition backup doesn't work properly
Answer : Please remember to specify the memory block correctly. If you still get an error then please tell me the error so that i can check if the error is from the tool's end
>How to add a toolchain????
Answer : Add it under android_toolchains folder in your home directory
Open the tool and navigate to toolchain_selector script under scripts folder
Add the toolchain name and the correct path as given there in the following format
toolchain_name[the number after the last toolchain name]=
toolchain_path[the number after the last toolchain path] =
>How to clean your kernel or Cyanogenmod work directory?
Answer ; Navigate to the kernel or Cyanogenmod work directory and type in Terminal : make clean
I will incorporate this in the next release
>Download toolchains or update tool doesnt work
Answer : make sure you have the git package installed. You can install from the tool itself under GIT tools
>Libraries missing while compiling kernel or cyanogenmod build errors on 64 bit machine??
Answer : Download libraries from cyanogenmod import libraries option( I will incorporate this in the next release) and for 64 bit compile error type : BUILD_HOST_32bit=1(Fixed and added in update 1)
Bugs and Suggestions
Please let me know

Changelogs
Update 2
>Added Xperia J in the build list of the tool
>Added Take kernel log in kernel options..Thanks @ricky310711 for the commit
>Added dry run option for Sony
-Lets you test your kernel.elf/boot.img(In case the kernel doesnt boot up..just restart phone and try again)
Update 1
>Cm-11.0 branch added while initializing repo(thanks mithun shanoj for the commit)
>Added umkbootimg unpack method
>Added import libraries option
>Added BUILD_HOST_32BIT=1 for 64 bit machines

Last one

No one tried??
Sent from my Micromax A110 using xda app-developers app

Maybe I am blind but where do I get the download?

Download Link?
Dude where is the download link???

I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
Dovidhalevi said:
Maybe I am blind but where do I get the download?
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal

Well well well.:beer: cheers.

Dovidhalevi said:
Maybe I am blind but I'll alwhere do I get the download?
Click to expand...
Click to collapse
rhar**** said:
I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
Guys see the download tab on top of the thread.. I'll also add a download link if u want
Edit: Added a download link to the post

I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk

welcome to the world of kitchen creators goodjob!

Nice job man ?
Sent from my Nexus 7 using Tapatalk

Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:

Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..
i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
actually i learnt alot by viewing the content of tools, viewing it in raw format and learning how things work.
it encouaged me to find a way to make a kitchen for windows users and noobs.
so i guess im the perfect example

Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Click to expand...
Click to collapse
You have every right to express your opinion, but that being said, your post makes you sound like a real elitist, one who's upset that his elevated place in the exclusive club is about to be disrupted by those "filthy ruffians" who didn't earn their developer's chops by clawing their way up from the gutter. In my opinion, anything that brings in more developers to the community is a good thing. Sure, there are going to be plenty who use this tool as a shortcut to doing any hard work, but there are going to be those who use it as a starting point to further their knowledge of ROM building and modifying. Everyone needs a place to start, after all, but implying they'll never be "one of the boys" without beating their head bloody against a desk isn't at all helpful. Dark Wraith should be commended for creating a tool that will help bring new blood into the community.

Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
That's one side of the argument, if you re-read the first several pages of @championswimmer's kernel kitchen thread you'll be reminded just how strongly some people feel about this... I'm not in either camp by the way.
My point is that xda is not what it was, if we continue to post toolkits here it will only dilute the pool of serious development further. You just have to dive into an official CM Dev thread (N4 is a good example) at any point and browse, say, 25 pages to see exactly what I'm talking about...
For every one person that takes your tool, pulls it to bits to figure out how it works and goes on to do their own original work and contribute back, I feel sure that there'd be many more that just go ahead without any real understanding of what they're doing, expecting you and I to bail them out when it goes wrong... I hope that's overly cynical but, ironically, from evidence I don't think that is.
Your toolkit might have a place, and again all credit to you for putting it together. Personally I believe it's more hand holding (even more so than ROM or kernel kitchen) which ultimately helps no one.
Sent from my Nexus 4 using Tapatalk

hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss

Good stuff
Sent from my Nexus 5 using Tapatalk

Marsealdelo said:
hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss
Click to expand...
Click to collapse
no bro..its not about support. Cm11 can run on ur device and you can build for it provided that you have the kernel source of your device available..For officially supported devices you will have the kernel source in cyanogenmod repository. For a device with no kernel source you cannot build cyanogenmod. What you are talking about is cyanogenmod porting to an unsupported device. Take a look around in cyanogenmod's wiki. I might add porting options in the tool in future but atm you can build only for offcially supported devices

[MOD] Disable system write protection on stock kernel

This module will disable system write protection on the stock HTC One SV kernel.
To make /system writeable, you must install the module and then remount /system as rw.
For example:
insmod /system/lib/modules/wp_mod.ko
mount -o remount,rw /system
Click to expand...
Click to collapse
You can make an init.d script to load it, or add it to the boot.img. Either way will work, but it's important that this is loaded at boot, as attempting to make changes to /system and then installing this module could corrupt the partition.
This is mainly for devs, who are free to incorporate it into their ROMs.
Unless you are an advanced user, I would wait for it to be included in your favourite ROM.
A credit and a link here so people can thank me in the OP would be much appreciated.
Download:
wp_mod_3.4.10-g6d8dbef.ko
NOTES:
- This is freshly compiled from HTC One (m7) source code for our device.
- Don't say it's not working if you have different kernel name.
- If you want it for your kernel name, give me it and I will make one for you.
Credits: @flar2 for source code
xpirt

Its not tested? Hmm, I am one for testing stuff, but a recommendation would be to test it on your device before presenting it to others and taking the chance of something going wrong for them. Otherwise, just dancing on a thin line.
For example, my Rom port... russellvone knew in advance that I was going to start on it. However, I refused to present it to others until I was confident there would be no harm. Last thing I want is to be responsible for someone else's device because I didn't care to see to them for myself.
Anyways, my point is that I recommend you test this (with responsibility) and then present it to the masses with the updates on what you are aware of in regards to your findings and/or experience.
Maybe it is just me, but that's how I do things.
Not stirring up anything. Just making an opinionated recommendation is all.
--- Happy Hunting!
Sent from my K2_CL using Tapatalk

Hehe I think you are in the wrong place because seems you don't know what is a module.
A module it's very different from a Rom or a kernel. This will not break anything in your phone, it's just a module. If it doesn't work you cannot remove files from system like always, if it works the system is writeable.
How you can see the thread it's in General section, too. If it was in Development section was another thing. I know how to post things, I think I have enough experience on xda.
And of course I test things, but didn't have time to test this, if someone doesn't test it until I have some time I will test it.
Plus I think flar2's module is very useful for people uses stock kernel, if you don't need it just ignore the thread
Oh don't think I'm rude, this is how I speak with all people
xpirt

No worries bro. Just gave my two cents. A means of good practice when generally speaking
Sent from my K2_CL using Tapatalk

Ok. As hTC made some new protections, I didn't want to continue hex-editing as also source code is out, so I compiled from source and I got it working at first! It will be moved to Development Section as soon as mods are free.
So.. updated link on OP! If you people want one for your kernel name, write it here and I will make it for you too.
Enjoy!
xpirt

I just hex edited the kernel version no problem.
Sent from my K2_CL using Tapatalk

Modding.MyMind said:
I just hex edited the kernel version no problem.
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
It works fine? Btw you can post it here if you want so it will be useful for people who have your kernel name.
xpirt

Works fine, but I have no use for it. Just wanted to try it out lol. I'm running on stock boot, stock kernel, etc, etc, but I still have write permission in /system. For example, I can edit the build.prop file right from its location and they stick after reboot. In addition I took the lines from the default.prop file and added them to the build.prop which now allows me to edit the default.prop but I'm still looking at how to keep the changes in the default.prop after reboot. If I can get that, then my accomplishments are complete lol. Anyways, I don't have my pc on me at the moment but I will hopefully upload it soon. May be after the holidays.
Sent from my K2_CL using Tapatalk
---------- Post added at 12:15 PM ---------- Previous post was at 12:12 PM ----------
If someone doesn't want to wait on me, just hex edit the kernel version and it will work . Pretty simple actually.
Sent from my K2_CL using Tapatalk

Exactly but pay attention to don't remove and rewrite the numbers but replace them only
xpirt

Tutorial please
A tutorial would be nice...
My device is still on S-on.. What fastboot commands do I use?
Do I just fastboot this-
insmod /system/lib/modules/wp_mod.ko
mount -o remount,rw /system ???

Hello
HTC OneSV Android: 4.1.2 kernel: 3.4.10-gf43d146
Please send me "wp_mod.ko" kernel module, thank you.

3.4.10-g47d5073 ?
xpirt said:
- If you want it for your kernel name, give me it and I will make one for you.
Click to expand...
Click to collapse
Could You do this for k2ul kernel-3.4.10-g47d5073?
Thank you in advance.