Database Develop

[MODULE-|-SOURCE] Atrix 4G Overclock Module -- Up to 1.5GHz!

Welcome to the Motorola Olympus (Atrix 4G) Overclock Thread!
Well, I didn't know what to do today, so I've created something useful, an Overclock Module. However, this is incomplete and I need help for completing it.
More specifically, I don't know how to replace the already loaded table with the one written in this module. If anyone can help, I would appreciate it!
TRY THIS AT YOUR OWN RISK, I'M NOT RESPONSIBLE IF YOUR PHONES BRICKS.
Status: COMPLETE.
Download:
Compiled module: HERE (Min 200MHz Max 1.4GHz)
Module source: HERE (Outdated. It'll be updated when it'll be cleaned.)
What you need:
1. A brain
2. A ROOTED Atrix
3. Patience
4. PC and SDCARD.
How to load it:
1. Download the compiled module
2. Put it on the root of your sdcard
3. On your ROOTED device, run a terminal emulator and do exactly... this:
Code:
su
cp /sdcard/olympus_overclock.ko /data/
chmod 777 /data/olympus_overclock.ko
cd /data
insmod olympus_overclock.ko
4. Use SetCPU for your profiles
And let me clarify a thing: This isn't a kernel. This is a kernel module
Thanks to:
Skrilax_CZ - Without you, I would never had been completed the work.
iggytom & Bakano - Thanks for your kallsyms logs!
Stay Tuned!

=NOT TESTED....what do you expect...put here some modified kernel and want to us test withou any test made by you? lol
You kiring right?

Exciting but Ill wait till a few brave souls test it out first
Sent from my MB860 using XDA Premium App

is this a joke?

frankiedizzle87 said:
is this a joke?
Click to expand...
Click to collapse
he says "completing and uploading"
...maybe he actually plans on testing it first? or maybe he's just trollin'

I've ever done things that I wanted to do.
I'll receive my Atrix next week, so, for now, it isn't tested and it isn't even completed.
DEVS, I need some help. I've modified the struct and, well, sincerely, I don't know how to load it and replace it to the already loaded frequancy table.
I'm posting the source, being confident on other devs that can help me.
P.S.: The module isn't simply setting the maximum frequency for overclocking. Its concept is rewriting the frequency table for getting better scaling and even better battery life adding underclocking features in the future.
EDIT:
@EclipseX
I'm not posting a kernel. Atrix is locked. Read prior to write things.
@raybond25
I don't mean why some people is accusing of trolling when those people don't know who is that guy that is posting these things....

Looks I
To be interesting. Thanks
Sent from my MB860 using XDA Premium App

kholk said:
I've ever done things that I wanted to do.
I'll receive my Atrix next week, so, for now, it isn't tested and it isn't even completed.
DEVS, I need some help. I've modified the struct and, well, sincerely, I don't know how to load it and replace it to the already loaded frequancy table.
I'm posting the source, being confident on other devs that can help me.
P.S.: The module isn't simply setting the maximum frequency for overclocking. Its concept is rewriting the frequency table for getting better scaling and even better battery life adding underclocking features in the future.
EDIT:
@EclipseX
I'm not posting a kernel. Atrix is locked. Read prior to write things.
@raybond25
I don't mean why some people is accusing of trolling when those people don't know who is that guy that is posting these things....
Click to expand...
Click to collapse
if you had described you just said in your last post in the OP, people wouldn't have been quite as skeptical, it seemed as though you were posting saying you'd already completed (or nearly), but hadn't tested it, and were hoping that others were. That's all.
thanks for the clarification on what this is and what you intend to do

Well yes, I was thinking too much easy because I've done other things like this in the past but then I've discovered that this is different... so..

kholk said:
What you need:
1. A brain
2. A ROOTED Atrix
3. Patience
4. PC and SDCARD.
How to load it:
Click to expand...
Click to collapse
From the testers point of view before we even get to looking at this, which kernel did you design this for being we now have three currently out with the retail, the leaked feb version, and the OTA update. Pleas provide your how too asap before someone dose something wrong and burn out their device. That said I'm waiting till I see a proper OP before I look at this again, good luck.

Well the OTA's out of the question since it can't be rooted

kennethpenn and DG if you guys can make this happen. you will be my heros

Djazin said:
From the testers point of view before we even get to looking at this, which kernel did you design this for being we now have three currently out with the retail, the leaked feb version, and the OTA update. Pleas provide your how too asap before someone dose something wrong and burn out their device. That said I'm waiting till I see a proper OP before I look at this again, good luck.
Click to expand...
Click to collapse
It is a SOURCE.
A source can be compiled on every kernel you want if you've got the source for it.
Anyway, only the retail version source is out, so for now we can compile it only for the OLYFR_U4_1.2.6's kernel ...... when it gets completed.

JoeyGuard said:
kennethpenn and DG if you guys can make this happen. you will be my heros
Click to expand...
Click to collapse
DG is gone completely.
Sent from my MB860 using Tapatalk

Okay guys, I'm going to complete this.
Anyone with the OLYFR_U4_1.2.6 firmware installed can execute this command and upload to me the file?
Code:
cat /proc/kallsyms > /sdcard/kallsyms.log
This command creates a log of the kallsyms in the kallsyms.log file stored on your sdcard.
I need that file for finishing the work.
Thanks!

Here you go. 10char

Response
kholk said:
Okay guys, I'm going to complete this.
Anyone with the OLYFR_U4_1.2.6 firmware installed can execute this command and upload to me the file?
Code:
cat /proc/kallsyms > /sdcard/kallsyms.log
This command creates a log of the kallsyms in the kallsyms.log file stored on your sdcard.
I need that file for finishing the work.
Thanks!
Click to expand...
Click to collapse
Here you go. hope it helps =)
It exceeded allowed file size as a "txt" file, so here it is in rar format

Thanks for the kallsyms.
Examinating and finishing the job.

kholk said:
Thanks for the kallsyms.
Examinating and finishing the job.
Click to expand...
Click to collapse
Im very excited for this kholk I know you're good at these things. I have my fingers crossed
Sent from my MB860 using XDA Premium App

if this is possible WOW whata beast, even my netbooks will be jealous LOL

*Bootloader Unlock Research* Cheesecake Clarification

10 charact

..........

Also reserved please

This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium

ROB281 said:
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Well, I'll get to the point soon. still modifying the post. but basically the gist of it is to check ALL of motorola's update servers for updates, not just the one that comes programmed into the device. If we're lucky and we find a hidden update, we may be able to get an unlocked bootloader (or other goodies?), which will allow us to use our device as we please (new kernels, better mods, etc)

Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App

karthakon said:
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well, I was bold and basically just created the files. When I ran the *#*#4636#*#* test, I found that it did indeed change my could update server.
also the com.motorola.blur.setup was in /data/data/ and not the system/etc/motorola.

Thank you.
Sent from my ADR6400L using xda premium

Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.

K.AuthoR said:
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
Click to expand...
Click to collapse
I actually have been testing some methods that may not even req a wipe in between or possible before
Sent from my DROID BIONIC using Tapatalk

Apparently someone found an update somewhere. Good sign. I'm going to check it out in an hour or two. Don't have my hands on it yet.
Sent from my DROID BIONIC using Tapatalk

Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!

kennethpenn said:
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
Click to expand...
Click to collapse
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update

phydo said:
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
Click to expand...
Click to collapse
Just so everyone can see it: the update label will always be for the build ID that the zip is supposed to be installed over. That means if you've got an update:
Blur_Version.1.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "1."
Blur_Version.5.5.886.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "5.5.886."

Was anyone ballsy enough to attempt to install the update? It doesn't have a bootloader inside, but it may still be dangerous.

P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!

cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.

jimmydafish said:
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
Click to expand...
Click to collapse
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!

Enzopreme said:
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Click to expand...
Click to collapse
S-off doesn't apply to Moto products...
Sent from my DROID BIONIC using xda premium

cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
I suppose I was looking for the wrong things. On other devices, "ap20bl.img" was responsible for bringing such goodies as an unlock capability.

|FAQ|For n00bs|Basics-Root,Roms,Kerenl and Recoveries

The objective of this thread is to answer the commonly asked questions, give the newbies a little head-start, protect them from getting flamed and keep this forum focused on more important things
Please go and hit thanks to @aashay960 here: for allowing me use informations here: http://forum.xda-developers.com/showthread.php?t=2323518
1 > What is root?
If you’re an Administrator on a Windows machine, you have access to the entire operating system and you can do whatever you like. That’s essentially what happens if you root your Android device. With root access, you can get around any restrictions that your manufacturer or carrier may have applied. You can run more apps; you can customize your device to a greater degree; and you can potentially speed it up in a variety of ways.
Basically, Rooting a phone grants you the permission to do stuff you normally aren't.
Click to expand...
Click to collapse
2 > Why to Root?
One of the most obvious incentives to root your Android device is to rid yourself of the bloatware that’s impossible to uninstall. You’ll be able to set up wireless tethering, even if it has been disabled by default. You can also access your entire file system, install special apps that require a root, and flash custom ROMs, which can add extra features and streamline your phone or tablet’s performance. A lot of people are tempted by the ability to completely customize the look of their phones. You can also manually accept or deny app permissions.
You can also get the latest android version before Sony releases it. You can also overclock (increase the speed of your CPU) your phone!
Click to expand...
Click to collapse
3 > Why not to root?
There are essentially three potential cons to rooting your Android.
Voiding your warranty: Some manufacturers or carriers will use rooting as an excuse to void your warranty. It’s worth keeping in mind that you can always unroot. If you need to send the device back for repair, simply flash the original backup ROM you made and no one will ever know that it was rooted.
Bricking your phone: Whenever you tamper too much, you run at least a small risk of bricking your device. This is the big fear everyone has. The obvious way to avoid it happening is to follow instructions carefully. Make sure that the guide you are following works for your device and that any custom ROM you flash is designed specifically for it. If you do your research and pay attention to feedback from others, bricking should never occur.
Security risks: Rooting may introduce some security risks. Depending on what services or apps you use on your device, rooting could create a security vulnerability. For example, Google refuses to support the Google Wallet service for rooted devices.
You must be willing to compromise with these factors before you decide to root. Personally, I haven't regretted my decision of rooting even for a second! I'm sure most of the guys on this forum feel the same way. However it is your choice.
Click to expand...
Click to collapse
4 > How do I root my phone?
Root for locked & unlocked bootloaders
Click to expand...
Click to collapse

Recovery
5 > What is Recovery?
A recovery is a small distinct environment separate from Android that allows diagnostic updates, and the ability to perform factory resets. The main purpose of this is to provide a way to reset an Android device when it may be impossible to boot into it.
The Android stock recovery is very basic and controlled via the volume keys and power button at the top of the device.
Custom Recoveries perform the same tasks as the stock-Android recovery with a few addition features, such as the ability to make full system backups, as well as flash custom roms. It is important to note that custom recoveries are recommended to those users with rooted devices, however a rooted device is not required. Anyone with an unlocked bootloader can install a custom recovery on their device.
Basically, Recovery saves your ass when you screw up! But it has many other important features.
Click to expand...
Click to collapse
6 > What are the different Recoveries available for Xperia Z?
Look at this post.
Click to expand...
Click to collapse
7 > How do I install a recovery?
Check here
Click to expand...
Click to collapse
8 > Which recovery is better?
NEVER ask this question! It is a matter of personal choice. It is an insult to the developers of the Recovery if you ask this question. Try out on your own and choose what you like
Click to expand...
Click to collapse

9 > What is a Custom ROM?
A stock ROM is the version of the phone's operating system that comes with your phone when you buy it.
A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way.
So what does the "customized" part mean? Since Android is open source, developers are free to take stock ROMs, modify them, strip them of garbage, optimize them, add things, and pretty much do whatever their imagination and skills allow.
My definition - A Custom ROM is a developer's idea of what the phone 'should have been like'. He takes the stock rom and modifies it to improve performance, looks, animations, battery life etc.
Click to expand...
Click to collapse
10 > Why to install a Custom ROM?
Updated versions: You can load the latest and available Android versions which can make your old phone look new.
Great number of feature filled custom ROMs: It will be a chaotic task for you to find the apt one as there are bunches of great custom ROMs available for different devices.
Personalization: There are a number of features that can be customized to suit your taste and working environment. For instance, Custom themes can bring a new look and feel to your device.
Improve performance: The custom ROMs allow its users to find out the unnecessary apps they have on their device and helps them to get rid of them, thus increases the speed of processing and improves battery life.
Install Apps on SD card: This is currently not possible with stock ROMs. If your phone ran out of space occasionally when install new apps this is a killer feature to have.
Better signal and quality: Custom ROMs help you to improve your base-band which in turn increases the signal and quality of your phone call.
Other reasons that you won't find on Google - "The thrill factor involved", "To show off to your friends" and "Because you can!"
Click to expand...
Click to collapse
11 > Why not to install a Custom rom?
Bricking: This is one of the main reason why people hesitate to root their devices. Some devices after the rooting process may become useless and the only option left with you is to get a new one as the manufacturer will cancel the warranty if they find any attempts of rooting.
Loss of all Data: When you install a new custom ROM, it will clean up your system and therefore you will loss all your installed apps and data.
Risk Factor: Most of the apps will be open source and the trust you have on developers may cause a potential risk to you in the future.
Reboot: If the rooting is not successfully done, the device may enter to an infinite loop of booting.
Even though this may seem concerning, it will happen only if you don't follow instructions correctly or do something extremely stupid. As of now, there is no way to completely brick an Xperia Z! You can fix 'Loss of Data' by taking a backup and you can fix reboot by using the Recovery mode we discussed earlier.
Click to expand...
Click to collapse
12 > What are the different Custom ROMs available for Xperia Z?
Look HERE. Take your pick!
Click to expand...
Click to collapse
13 > Which is the Best ROM for this phone?
NEVER EVER ASK THIS QUESTION!! This is a very subjective question. It differs from person to person. It takes a lot of time/energy/efforts to build a custom ROM and asking this question is a very big insult to the makers of these ROMs! Try out different ROMs and choose what you like.
Click to expand...
Click to collapse

Kernels
14 > What is a Kernel?
The central module of an operating system. It is the part of the operating system that loads first, and it remains in main memory. Because it stays in memory, it is important for the kernel to be as small as possible while still providing all the essential services required by other parts of the operating system and applications. Typically, the kernel is responsible for memory management, process and task management, and disk management.
If our phone was a movie, the Kernel would be the director! It is the brain of our phone. And even though it is the most important part of our phone, it is just a single (.IMG) file and only a couple of MBs!
Click to expand...
Click to collapse
15 > What are the benefits of a custom Kernel?
Adjust CPU frequencies and set profiles like OnDemand, Battery Saving, etc.
Underclock and overclock CPU speeds
Underclock and overclock GPU speeds
Adjust voltage
Adjust touch screen sensitivity
Equip your phone with BLN (backlight notifications)
Custom recovery that allows backups and restorations of entire ROMs as well as installation of .zip files
Minimum screen brightness pushed past the limitations of stock kernel
Conserve battery (with the right settings)
There are a lot of Technical advantages of a good coded custom kernel. Fortunately, you don't have to worry about all that. Most of the work is done by the developer himself.
Click to expand...
Click to collapse
16 > How to flash (install) a custom kernel? OR How to flash boot.img?
Read this
Click to expand...
Click to collapse
17 > Which is the best Kernel for this phone?
NEVER EVER ASK THIS QUESTION!! This is a very subjective question. It differs from person to person. It takes a lot of time/energy/efforts to build a Kernel and asking this question is a very big insult to the makers of these Kernels! And remember, not all Kernels are compatible with all roms
Click to expand...
Click to collapse
18 > How to overclock my phone?
You cannot overclock with a stock kernel. You MUST have a custom kernel to overclock your phone. Once you have a custom kernel you must install either 'SetCPU app' or 'NoFrillsCPU app'. You need any one of these to control the CPU speeds.
Click to expand...
Click to collapse
19 > Is it safe to overclock my phone?
I will not say this is completely safe. But i have yet to come across somebody who actually screwed up his phone just by overclocking. So use at your own risk. Also remember that all phones have a different capacity to overclock. If you try to overclock it higher than that, it will go into a 'reboot loop'. But you can fix that by flashing a lower frequency Kernel. It is not a problem.
Click to expand...
Click to collapse

Extras
20 > What is GAPPS?
Gapps is short for Google Apps. These are apps made by google like Google Maps, Playstore, Gmail, Google search etc. They are available to download in the Play Store and can also be flashed as a zip in recovery mode. For a complete list of apps click HERE. Not all Gapps are available in all countries.
Click to expand...
Click to collapse
21 > How to increase battery life? OR How to save battery?
Read THIS (Not only read it but apply it too! ) . If nothing else works, buy a better battery.
Click to expand...
Click to collapse
22 > Task Managers - Good or Bad?
Long story short - If you don't know what you are doing, Stay away from task killers. If you think that constantly killing apps will free more RAM and therefore speed up your device, you are mistaken. The app that you kill will restart itself and this will cause you more of your phone's resources than you think you saved. In fact, task managers do more harm than good. A lot of Developers agree with this. Android itself does a very fine job of managing tasks so that you don't have to mess with it.
Read this in-depth article on task managers HERE
Click to expand...
Click to collapse
23 > What is Clean Flash? What is Dirty Flash?
Clean Flash is wiping cache, dalvik cache and data before flashing a zip or installing a ROM through recovery.
Dirty Flash is wiping cache and dalvik cache only
Clean flash is much recommended and causes less problems down the road. If the instructions specifically ask to to clean flash, you must do so. You will lose all your data when you will clean flash. But dont worry, clean flash will not affect your internal or external memory card. You will lose your apps and settings and game data. Your phone will act like it is just out of the box.
You can Dirty flash when flashing small modification zip files. Or perhaps a minor update to the rom (unless the instructions ask you to clean flash). You will not lose any data while Dirty flash. But sometimes, you are more likely to face problems like apps closing which could have been prevented by Clean flashing.
Personally, i always clean flash when installing a new Rom. It is a good habit to follow in the long run.
Click to expand...
Click to collapse

Famous Rom Comunties
Android Open Source Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android is an open-source software stack for a wide range of mobile devices and a corresponding open-source project led by Google. Here you can find the information and source code you need to learn more about the Android platform. From there you can create custom variants of the Android software stack, port devices and accessories to the Android platform, and ensure your devices are compatible with the Android compatibility definition.
Click to expand...
Click to collapse
Visit Official Site : source.android.com/
CyanogenMod
CyanogenMod (pronounced sigh-AN-oh-jen-mod), is a customized, aftermarket firmware distribution for several Android devices (See above for supported devices & how to install CyanogenMod on said devices). Based on the Android Open Source Project, CyanogenMod is designed to increase performance and reliability over Android-based ROMs released by vendors and carriers such as Google, T-Mobile, HTC, etc. CyanogenMod also offers a variety of features & enhancements that are not currently found in these versions of Android.
Click to expand...
Click to collapse
Visit Official Site : http://www.cyanogenmod.org/
MIUI
MIUI (pronounced "Me You I", a play on the common abbreviation of the words user interface as UI), developed by Xiaomi Tech, is an aftermarket firmware for cell phones based on the open-source Android operating system. MIUI itself is closed source. It features a heavily-modified user interface that does away with the Android app drawer and has drawn comparisons with Apple's iOS and Samsung's TouchWiz UI. The Custom ROM includes additional functionality not found in stock Android, including toggles on the notification pull-down, new music, gallery, and camera apps, and an altered phone dialer that displays matching contacts as a user enters a number
Click to expand...
Click to collapse
Visit Official Site :en.miui.com/

Reserved1
Res..1

Can you put a bigger signature i don't read it correctly...
Some things are wrong, like rooting your phone avoid your warranty, where did you take your informations?
Why not a single word about the risk of installing a custom kernel? The hard-brick problem, the fact that SUS and PCC won't work on a custom kernel, that's very important informations you should get before thinking about installing a custom kernel.

Great initiative!
QualQuek said:
Why not a single word about the risk of installing a custom kernel? The hard-brick problem, the fact that SUS and PCC won't work on a custom kernel, that's very important informations you should get before thinking about installing a custom kernel.
Click to expand...
Click to collapse
Post suggestions instead of criticisms.

This is really good! :good:
One small suggestion, if I may, I think when it comes to choice of recovery, you should make a small comparison between the types of recoveries available.
CWM non-touch recovery lacks AROMA support, and I think that's a huge drawback.
Maybe you can add more such differences that you can find.

kgs1992 said:
This is really good! :good:
One small suggestion, if I may, I think when it comes to choice of recovery, you should make a small comparison between the types of recoveries available.
CWM non-touch recovery lacks AROMA support, and I think that's a huge drawback.
Maybe you can add more such differences that you can find.
Click to expand...
Click to collapse
In my veiw you are right but anything u say the person my have done hard work to build the recovery.
So i am leaving it for now .
If i get some pms / requests / more suggestions i will think once again

QualQuek said:
Can you put a bigger signature i don't read it correctly...
Some things are wrong, like rooting your phone avoid your warranty, where did you take your informations?
Why not a single word about the risk of installing a custom kernel? The hard-brick problem, the fact that SUS and PCC won't work on a custom kernel, that's very important informations you should get before thinking about installing a custom kernel.
Click to expand...
Click to collapse
It is written that rooting will 'void' warranty which means that warranty will be over if you root the phone. There is a difference between 'void' and 'avoid'

aashay960 said:
It is written that rooting will 'void' warranty which means that warranty will be over if you root the phone. There is a difference between 'void' and 'avoid'
Click to expand...
Click to collapse
That doesn't change that fact that's wrong.

QualQuek said:
That doesn't change that fact that's wrong.
Click to expand...
Click to collapse
So you are saying that if we root our phone, we will still have the original warranty? Ofcourse not

Very informative !!
Thanks
Sent from my GT-S5570I using xda app-developers app

aashay960 said:
So you are saying that if we root our phone, we will still have the original warranty? Ofcourse not
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43971471&postcount=10
Deal with it.

QualQuek said:
http://forum.xda-developers.com/showpost.php?p=43971471&postcount=10
Deal with it.
Click to expand...
Click to collapse
Not to argue with the fact that warranty shouldn't be affected by root (it shouldn't) , but that is solely a European directive.
Sony do not have to stick by that ruling in the rest of the world, including India where the person you are arguing with is from. So, it's perfectly plausible that they could deny a warranty claim because of root and get away with it in some territories (unless a similar ruling is made there).
Also, might I suggest that you do not post in such a confrontational manner when there is no call for it, especially in cases such as now when you haven't considered what might be the case in areas apart from the one you live in yourself.
Sent from my C6603 using Tapatalk 2

kingvortex said:
Not to argue with the fact that warranty shouldn't be affected by root (it shouldn't) , but that is solely a European directive.
Sony do not have to stick by that ruling in the rest of the world, including India where the person you are arguing with is from. So, it's perfectly plausible that they could deny a warranty claim because of root and get away with it in some territories (unless a similar ruling is made there).
Also, might I suggest that you do not post in such a confrontational manner when there is no call for it, especially in cases such as now when you haven't considered what might be the case in areas apart from the one you live in yourself.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Absolutely not, read the wikipedia article.

QualQuek said:
Absolutely not, read the wikipedia article.
Click to expand...
Click to collapse
I have. It only mentions legality in Australia, Europe and the USA. Rulings made in those territories do not cover India and never will.
If you somehow think that India has to stick by a European directive, then I'm not sure what to say about that.
Sent from my C6603 using Tapatalk 2

kingvortex said:
I have. It only mentions legality in Australia, Europe and the USA. Rulings made in those territories do not cover India and never will.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Oh you think that doesn't apply to other countries except that Europe, USA and Australia?
I don't think so, most of other countries haven't any law about it so maybe that make jurisprudence.
Anyway even in India i'm not worried about that.

Android.jar

Please allow us to download the android.jar of omni

dank101 said:
Please allow us to download the android.jar of omni
Click to expand...
Click to collapse
OmniROM does not require a special android.jar. It is completely AOSP compatible and though uses the same android.jar
Every newly added function should not be exposed in an android.jar, because it will break compatibility, if you need to use such a function in a custom app, consider using reflection

MaR-V-iN said:
OmniROM does not require a special android.jar. It is completely AOSP compatible and though uses the same android.jar
Every newly added function should not be exposed in an android.jar, because it will break compatibility, if you need to use such a function in a custom app, consider using reflection
Click to expand...
Click to collapse
It isn't needed, although it does have modified stuff

dank101 said:
It isn't needed, although it does have modified stuff
Click to expand...
Click to collapse
I'm not totally sure what you want to achieve.
The android.jar that is shipped with the SDK does not contain much useable code, it's more like a class+method definition table. So any code changes won't be visible there.
If you want to use any additional added functions (which in most cases is not what you want) you should do this via reflection or your application might do crazy things if internal apis change or it is installed on another rom.

dank101 said:
It isn't needed, although it does have modified stuff
Click to expand...
Click to collapse
Just like MaR-V-In said... why?

XpLoDWilD said:
Just like MaR-V-In said... why?
Click to expand...
Click to collapse
Why not? is the true question, i have no true reason why.

APK Manager / Deodex / Odex Manager

So, I have put together an actual Windows program for a lot of Rom Builders. I used to build a lot of Roms, but really don't do much of it any longer. What I know though, is the tool I built is extremely easy to use and very effective. I thought some of you would very much enjoy this tool. It will also allow a lot more people to start theming and tinkering It has built in Draw9 support and will automatically detect what versions of Java you have and allow you to select which one you would like to use.
So I am going to post it here for now in the Note 4 forum for a few of you to install it and check it out. It will support many phones, if not all. All you have to do is make sure you have some type of Java program installed on your PC. The rest is all self-contained and updated.
The first thing you are going to need to do after install is to go into setup and setup the paths accordingly, to your liking. Once this program is setup it runs great. I have built it with threading, so it won't lag as you are working along.
I will post some screen shots for you all to check out.. I would use these as examples of what your environment should look like. Also, make sure you pull the system, from the adb options tab, from your phone as the first step before doing anything else, it will use the framework files as needed to work. This path is also where your deodex setup paths of originals should point to, the pulled files for app and framework.
Enjoy !!!
Link: https://drive.google.com/file/d/0B31X8bH_5Gl-eUtJODBhcUdPRDg/view?usp=sharing
Update: ** Updated file to fix a small issue.. ** EST: 10:24 p.m.

Thank you for this! Going to take a look into it here tonight!

Updated OP..
Made some modifications to the build..

Very Cool, thank you for creating this tool, I'm going to give it a try tonight after a few Christmas parties this evening.

Sounds like a useful tools. I will check it out when my retail phone gets rooted.

za33ck said:
Very Cool, thank you for creating this tool, I'm going to give it a try tonight after a few Christmas parties this evening.
Click to expand...
Click to collapse
Oh great, it will be even better after a few drinks in you..

Can you post source code as well ?

This looks awesome, so what do we use? Do we take a Odin flash able ROM....I don't understand how to use it?
Sent from my Definitive v1.4 Note 4 using Tapatalk

bdorr1105 said:
This looks awesome, so what do we use? Do we take a Odin flash able ROM....I don't understand how to use it?
Sent from my Definitive v1.4 Note 4 using Tapatalk
Click to expand...
Click to collapse
You just plug your phone in and wait for it to detect it.
From there you need to setup the program, look at the screen shots.

gatesjunior said:
You just plug your phone in and wait for it to detect it.
From there you need to setup the program, look at the screen shots.
Click to expand...
Click to collapse
So basically whatever mods you currently have you then make flushable?
I guess what I am asking is should we Odin the stock base that's odex, pull the folders with your program, deodex it and make whatever mods?
Biggest question, how do we make it flushable, I am extremely new to this
Sent from my Definitive v1.4 Note 4 using Tapatalk

Normal
Normal ? when selecting device? See attached Picture

bdorr1105 said:
So basically whatever mods you currently have you then make flushable?
I guess what I am asking is should we Odin the stock base that's odex, pull the folders with your program, deodex it and make whatever mods?
Biggest question, how do we make it flushable, I am extremely new to this
Sent from my Definitive v1.4 Note 4 using Tapatalk
Click to expand...
Click to collapse
So, I am assuming, you mean flashable. Look around for update.zip files associated with Android. You need to make sure you are rooted / dev edition in order to even pursue this. If you are then do some research on update.zip files and understanding our partition table for our phone or your phone, etc..

Wifi tethering unlock
I have my Note 4 DE ordered/shipped by Samsung. I have never used this program before, how easy is it to do your own Native WiFi Hotspot modification? Or is there any step by step I have missed somewhere? Basically, I am wanting to root, TWRP and then change a few things on my own.
Thanks!

gatesjunior said:
So, I have put together an actual Windows program for a lot of Rom Builders. I used to build a lot of Roms, but really don't do much of it any longer. What I know though, is the tool I built is extremely easy to use and very effective. I thought some of you would very much enjoy this tool. It will also allow a lot more people to start theming and tinkering It has built in Draw9 support and will automatically detect what versions of Java you have and allow you to select which one you would like to use.
So I am going to post it here for now in the Note 4 forum for a few of you to install it and check it out. It will support many phones, if not all. All you have to do is make sure you have some type of Java program installed on your PC. The rest is all self-contained and updated.
The first thing you are going to need to do after install is to go into setup and setup the paths accordingly, to your liking. Once this program is setup it runs great. I have built it with threading, so it won't lag as you are working along.
I will post some screen shots for you all to check out.. I would use these as examples of what your environment should look like. Also, make sure you pull the system, from the adb options tab, from your phone as the first step before doing anything else, it will use the framework files as needed to work. This path is also where your deodex setup paths of originals should point to, the pulled files for app and framework.
Enjoy !!!
Link: https://drive.google.com/file/d/0B31X8bH_5Gl-eUtJODBhcUdPRDg/view?usp=sharing
Update: ** Updated file to fix a small issue.. ** EST: 10:24 p.m.
Click to expand...
Click to collapse
Nice,
I just pulled my /system/
Thanks!!!

radionerd said:
Nice,
I just pulled my /system/
Thanks!!!
Click to expand...
Click to collapse
Great..