Related
Hi just asking if anyone knows any links or archives or anything i can read through, im looking to build my own ROM. any help would be much appreciated and dont mind donating to someone that can help me start to learn.
Thanks
Well, first of all you need to be able to compile Android. This is pretty easy and it's explained directly in the developers google website. If you're not running a Nexus One or a Nexus S, you can't actually compile a working android copy for your own phone "as is" from AOSP. Because of this, you firstly need to change / create some dirs and files in order to add the support for your particular device. I'd start searching on CM repositories for this (I've got the Nexus One and thus I don't have such problems).
After you've compiled Android for your device and your changes (for example root), you'll have some disk images (you can find them all under out/target/product/PHONE_MODEL/, they are the .img files). You can directly flash them via fastboot ("fastboot flash boot boot.img" etc.). You can though create an update.zip file, and this can be made extracting the system.img file in a folder. Remember that you'll have to recreate the symlinks (to toolbox and/or busybox if you want to include it in your build) and set permissions, as zip doesn't save the permissions of the files once compressed.
Thus so far, if you succeed making every single step you should have your ROM on your phone
Cornea's coming back! This thread will have a link to another thread for the new Cornea. Wow, threadception.
Cornea
Cornea is based upon my Motorola XOOM program, XOOT.
It's hard to explain...so I'll try my best.
Check out Cornea's official site at Site is down
THERE ARE TOO MANY ONE-CLICK SOLUTIONS FOR ANDROID.
Cornea has the ability to combine these into one application.
All you need is a toolkit for your Android device. (You can find these in the post below). Copy this into Cornea, and Cornea can suddenly do so much more with your device.
CAN'T FIND A TOOLKIT FOR YOUR DEVICE?
The best thing is, you can develop your own toolkits too. You can find out how to do this in Post #3
In my eyes, this is a revelation for Android hacking.
The possibilities are infinite. Make a toolkit that operates with your bootloader, or one that hacks your recovery. Or make an AllInOne toolkit that has the best of both worlds.
n00b FRIENDLY
It's easy to use for n00bs and hax0rs alike. It eases you through the first worrying steps of hacking, and you've also got a whole forum full of moderators and developers to help you out.
THE KEY TO THE LOCK OF RECOGNITION
If you've made your own toolkit, send it to me and I'll add it to the below post for public download!
Created by Epic118/FaizSaleem118
[Below post: Download Center - download Cornea and toolkits for your device]
[Post #3: Cornea Development Guide]
Download Center
Cornea's coming back! This thread will have a link to another thread for the new Cornea. Wow, threadception.
Change logs
v4.0 (TBA)
A fantastic, easy to use, intuitive GUI.
All toolkits upgraded to GUIs!
The Toolkit Download Center - download toolkits that work on your device only to reduce risk
Fastboot Flash UI - a user interface for the fastboot tool
Internet integration, with Help and Q&A built straight into the application. No need for fiddly websites!
Automatic OTA updates thanks to a new OTA daemon
Works on Windows XP properly. In fact, to guarantee this, the entire of Cornea will be built on XP.
Automatic %PATH% association: No need for administrative privileges like before
Even more!
v3.0 (planned) (NEVER RELEASED)
UNKNOWN
v2.0 (03/24/2012) (LOST)
No more metadata or EXEs - a simple BAT that'll work on all Windows computers
Many more tools for devs!
Official support for Cornea GUIs
OTA toolkit downloading
Universal toolkit enhanced
v1.2.2 (02/13/2012)
Changes version metadata from 0.1.2.1 to 1.2.2.0
Cornea now recognises if a toolkit exists or not, rather than stating "Toolkit not signed" and then FCing
Revamped Readme for easier usage (now includes tiimestamp)
Cornea.sc.bat included in case you want to modify it (find it in the sc folder)
v1.2.1 (03/12/2012)
Icon added (eye with HTC phone in the middle)
Converted into EXE format (no more twiddly batch files)
'Obese' toolkits (toolkits with adb binaries) are now rejected by Cornea
v1.2 (02/11/2012)
Universal Toolkit added
v1.1 (02/10/2012)
Removes ADB binaries from toolkits and adds them to C:\Cornea
v1.0 (02/08/2012)
Initial release
TOOLKITS
3 Toolkits Available.
That's not a lot. However, expect more, both from me and from the XDA community!
To use a toolkit, use WinRAR to EXTRACT HERE and then copy the new folder to Cornea's tooklit folder
Downloads can be...downloaded from the bottom of the page.
Motorola XOOM (Wi-Fi tested, 3G/4G may not work)
Bootloader lock and unlock
Flash CWM recovery (Tiamat)
Root (thanks solarnz, for your Universal Root thing)
Flash to stock images/convert to GED
Flash a non-CWM bootanimation.zip
SAMSUNG Galaxy Ace (limited. S5830, will be updated to have more features soon)
Flash CWM recovery (official)
Enter recovery mode if you have jammed buttons
Odin mode (copies Cooper.ops to Desktop, kicks device to DownloadMode and then opens Odin)
Universal toolkit
Included from Cornea 1.2
Install APK files to /system/app, /data/app and /sdcard
Send shell commands via ADB shell
Push and pull files
Remount system as r/w
Reboot into any supported mode (system, recovery, fastboot, download, rsa)
Show logcat
Cornea's official download site is down, use the mirrors!
Mirrors - Mediafire
Mirror - Cornea 1.2.2
Mirror - Cornea toolkit - S5830
Mirror - Cornea toolkit - XOOM
Cornea Source Code Center
Cornea's coming back! This thread will have a link to another thread for the new Cornea. Wow, threadception.
For the meantime, there'll be nothing here.
Looks great.... waiting for the galaxy ace version...
Anyone brave enough to have tried 3G xoom, as it states it might not work.?
I like the sound of this. Might look into making one for the EVO 3D.
What functions can be written in scripts?
Sent from my SCH-I400 using xda premium
I think something like this (ONE common, extensible 'hacker' platform) is sorely needed. I see tweak threads, but each dev goes his/her own way about it.
One suggestion: Remove the adb files from the toolkit folder, so toolkits are much smaller and one doesn't have 20 copies of adb.exe.
Cornea/
cornea files
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
MySampleToolkit/
toolkit .bat files [Provide a template to setup ../adb.exe reference.]
other files (opt)
Hmm... I don't use ADB, but could the toolkits be written in "sh" style. That way Cornea could also exist as a sh script for rooted BusyBox users?
Just my $0.02.
P.S. I vote option 4: I do/don't know how, but I would rather use other peoples' toolkits.
ciscogee said:
What functions can be written in scripts?
Click to expand...
Click to collapse
From inferring and a 30 second review of the code...
A) On the PC, toolkits are "DOS" batch files. For functions (in the program flow sense), you can do whatever you want with all the quirks of batch files.
B) To change something on your phone, you are using ADB. Read the documentation to learn more. (Personally, I've never used ADB.)
I'm glad to hear that people like the idea of Cornea. I'm a n00b too.
Implementing ADB into Cornea would be a good idea. I was contemplating that but it'd be pretty difficult to do that, particularly if people are browsing through folders during runtime and the like. I had found a way to do it, which was to do it via calling the *.bat instead, but when I got up, my inbox already had a few toolkits in there, and I really couldn't be bothered!
One way I could do this is make an installer for Cornea that copies ADB-required files to C:\Windows\system32 and then update Cornea...tell me what you think!
Also you can execute BusyBox SH files...if I'm right, you could adb push it to a working directory, then do adb shell sh, and then when done you could use adb shell rm to remove the file?
Haraldr Blaatand said:
I think something like this (ONE common, extensible 'hacker' platform) is sorely needed. I see tweak threads, but each dev goes his/her own way about it.
One suggestion: Remove the adb files from the toolkit folder, so toolkits are much smaller and one doesn't have 20 copies of adb.exe.
Cornea/
cornea files
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
MySampleToolkit/
toolkit .bat files [Provide a template to setup ../adb.exe reference.]
other files (opt)
Hmm... I don't use ADB, but could the toolkits be written in "sh" style. That way Cornea could also exist as a sh script for rooted BusyBox users?
Just my $0.02.
P.S. I vote option 4: I do/don't know how, but I would rather use other peoples' toolkits.
Click to expand...
Click to collapse
Oh, sorry! I completely forgot your last question! Erm...no, I can't write it as an sh file because I'm uneducated on the subject. Maybe someone could help who could?
I'm keeping my eyes on this because I think it's a good idea and sorely needed. Before I try to get this in the portal can you add a list of tweaks included in the kits you have already released? Also, any new kits expected soon?
Bentenrai said:
I'm keeping my eyes on this because I think it's a good idea and sorely needed. Before I try to get this in the portal can you add a list of tweaks included in the kits you have already released? Also, any new kits expected soon?
Click to expand...
Click to collapse
1) I will do so, yeah.
2) No kits from ME expected soon, because I only own a Galaxy Ace and a XOOM, both of which have a kit from me.
Provided you still have those retired devices, you could make quite a few kits - it's pretty simple and easy to do. Even if you don't, it'd be interesting to see some Nook hacks.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
Dropbox isn't too happy.
Anyway we can get a mirror?
Thanks for your hard work! I can't wait to take a deeper look into this.
epic118 said:
1) I will do so, yeah.
2) No kits from ME expected soon, because I only own a Galaxy Ace and a XOOM, both of which have a kit from me.
Provided you still have those retired devices, you could make quite a few kits - it's pretty simple and easy to do. Even if you don't, it'd be interesting to see some Nook hacks.
Click to expand...
Click to collapse
Yeah I was gonna try to make a bloat removal script for the E3D but I'm not too versed in the workings of my Nook so I don't have any decent idea there. Actually, on second thought, I can probably whip up one that fixes the market, netflix and the screen density but that's aboot it. I'll get started on it later tonight.
Anybody got a mirror up?
Bentenrai said:
Yeah I was gonna try to make a bloat removal script for the E3D but I'm not too versed in the workings of my Nook so I don't have any decent idea there. Actually, on second thought, I can probably whip up one that fixes the market, netflix and the screen density but that's aboot it. I'll get started on it later tonight.
Anybody got a mirror up?
Click to expand...
Click to collapse
Mirrors now up on both mediafire.com and cornea.site40.net (preferred, Cornea's official site!)
Most new toolkits'll be up on Cornea's official site. Usercreated ones will not be uploaded to mediafire by default. If you want a mirror, you'll have to upload it by yourself and send the mirror URL to me.
Does anyone get a compatibility error message when trying to start Cornea.exe?
Using Win7 32bit. Should I be starting it from a command prompt? I read the README but it didn't specify anything besides moving & renaming the files directory to the root and appending the environment variables path.
I have a feeling this post is going to be REALLY embarrassing for me.
OK, lay it on me. I'm ready. Which stupid human error did I commit?
R1150GSA said:
Does anyone get a compatibility error message when trying to start Cornea.exe?
Using Win7 32bit.
Click to expand...
Click to collapse
That shouldn't be. I've tested a lot, and Cornea has been mostly flawless.
R1150GSA said:
Should I be starting it from a command prompt?
Click to expand...
Click to collapse
No.
R1150GSA said:
I read the README but it didn't specify anything besides moving & renaming the files directory to the root and appending the environment variables path.
Click to expand...
Click to collapse
That's all you SHOULD have to do. Of course, you're having problems.
R1150GSA said:
I have a feeling this post is going to be REALLY embarrassing for me.
Click to expand...
Click to collapse
No, it won't. Even the best of us make mistakes.
R1150GSA said:
OK, lay it on me. I'm ready. Which stupid human error did I commit?
Click to expand...
Click to collapse
None. In fact, if anything, it's probably my fault. You see, I use a BAT-EXE converter to finish off my batches, and I must have accidentally chosen 64bit compiling instead of 32. (Sorry, I'll fix it when I've got time!)
In the meanwhile, you can use the Cornea batch sourcecode, which is included with the Cornea download. It's in the same folder as Cornea.exe, but it's called Cornea.sc.bat (or it's in the /sc folder, depends which version you've got). It's exactly the same thing, and there's not much (if any) difference other than the missing metadata/icon.
Have fun using Cornea!
Epic118
You call this a website?
SHUT UP!
Makes me remember smosh! haha
If you want I'll make you a nice site for free
Take a look at my stuff in my signature......I started making toolkits for different devices some time ago. If you look at my source you can get some new ideas and features
.
This will not be the prettiest post until I have most of the bulk written out. Over time I will refine and improve, but for now I need to get it on paper.
-= READ THIS =-
-= I am not responsible for bricked devices. I know what I am doing when it comes to porting, and am giving you exact details on how to port. These methods have a very small chance of bricking, but if anything happens and you come crying to me, I will laugh at you. Follow this thread carefully and you will have little to no issues. =-
Before we begin, the most important part of android developing is to have Ubuntu (or preferred linux distro) installed on either a separate machine, or dual boot in windows. Most scripts that aid in developing can only be run under linux. A simple installer for dual booting Ubuntu/windows can be found here: http://www.ubuntu.com/download/ubuntu/windows-installer.
You also NEED adb installed, along with necessary Nexus S drivers, and have a basic knowledge of adb commands (I will cover a few). (You will need to install the Android SDK and download the platform-tools addon. This is where adb is located. There are guides online telling how to download these. If you need help, ask and I will include in the OP.) I dual boot Windows and Ubuntu, so I have my adb commands installed on my windows partition. This probably isn't the best way to do it, feel free to install adb under whichever OS you prefer. For this guide, I will be referring to using adb under Windows 7. The most common command needed while porting is simple:
adb logcat
Write this down somewhere if you cannot remember it. I have typed this command over 5000 times, it is used to debug system errors (bootloops, rom not booting, apps not working, etc).
I will also be referring to the "Android Kitchen" throughout this guide, mainly when working with boot.img's. In order to understand it more thoroughly, spend some time reading the first page. Link to Android Kitchen is below.
-= Useful Links =-
Be thankful, I saved you the time of googling
Nexus S adb drivers
Android Kitchen
Android SDK
7zip
Click to expand...
Click to collapse
-= Basics =-
The normal Android ROM consists of 3 main parts;
Boot.img – This is where the kernel and ramdisk are compressed. The ramdisk is what initiates the ROM’s main functions, such as Bluetooth, Wifi, and network connectivity information. The main file to pay attention to while porting is in the ramdisk, called the init.rc. It is a simple text file, and can be editied according to the ROM. A “how to” on unpacking/editing/repacking this file will be later in the guide.
System Folder – This folder contains all of the libs, configuration files, apps, and everything else that is the ROM itself. In this folder is where most of the changes are made, since most libs/framework pieces are device specific. This folder is the main cause of bootloops, and non-booting ports. I will try to explain most of my knowledge on what libs control what part of the phone. Almost all of the fixes for camera, sound, wifi, etc will be made somewhere within this folder. Unzip a ROM and dig around this folder for a bit, understand what folder contains what files, they are somewhat self-explanatory (Apps, framework, libs). This folder will become your best friend, learn to love it.
META-INF Folder – This folder holds all of the initial installer scripts; such as when you flash the ROM in a custom recovery. It is what tells your phone to install the ROM and what files to install. This script controls mount points, important system links, and in some occasions special commands. You can also edit this file to include any custom text you want users to see while flashing your rom. This file is device specific, and should ALWAYS be replaced when porting. Flashing a ROM with the wrong updater-script can either:
a) Corrupt partitions
b) Abort Installation (very frustrating with large ROM’s)
c) Rare occasion, brick your device
Bottom line is, pay very close attention to what exactly is in your custom built ROM before you flash it.
I decided this will be a good preface post. Read here for basic information you need to know BEFORE porting.
Here We GO
In order to port ROM's to the Nexus S, you will need a "base" to pull your files from. In order to port a ROM to the Nexus S, we will need a Nexus S ROM to start with, hence the "base". This base is normally CM7 or Stock Gingerbread, and can also be CM9 - Stock ICS. The base you pull from needs to match with the version of ROM you are porting.
1) Is the ROM I'm porting Ice Cream Sandwhich, or Gingerbread?
-This is very important. Most files are incompatible between versions, so make sure you know for sure, which version your port is going to be.
a) If the ROM you are trying to port is based on Gingerbread, download this ROM as a base to pull from (device specific):
CM7 GSM
CM7 4G
b) If the ROM you are trying to port is based on Ice Cream Sandwhich, Download this ROM as a base to pull from (device specific):
IMM76D GSM
IMM76D 4G
Click to expand...
Click to collapse
2) Download the ROM you are going to port. Place this ROM on your desktop, along with the matching base.
3) Unzip both ROM's (port, and base) using preferred archive utility. Extracted ROM's will be in folders with matching name of the zip, DO NOT mix these up; be very organized with your base and the ROM you are porting.
4) Take a look in your newly unzipped ROM's, they should look exactly as I explained in the first post. We will be starting with the System folder of the ROM you are porting, replacing our needed files.
4a) Click into the System folder; you will see many folders inside. The first one we start with is the lib folder. Click inside; you will now be in the directory /system/lib
4b) In this directory is where all of the libs are located; these are crucial to the ROM. Replacing these without knowing what you are doing will result in a ROM that will not boot.
4c) At the top, you will notice 5 main folders; bluez-plugin, egl, hw, modules, soundfx. The ones that we care about are egl and hw. The egl folder contains the graphics drivers for the specific device, and the hw controls lights, gps, and other hardware features. In the ROM you are porting, delete both of these folders. (egl and hw)
4d) At this point, navigate to your base ROM (Nexus S ROM). Select both the egl and hw folders, and drag them to the lib folder of the current ROM you are porting. Your lib folder will now contain 5 folders again. Moving on.
4e) Navigate to your base ROM folder, into /system/lib again. Select these libs and drag-drop into your current ROM you are porting (this step varies between ICS and GB);
-= Gingerbread =-
-libaudio.so
-libaudiopolicy.so } these libs control audio
-libaudioflinger.so
-libril.so
-libsecril-client.so } these libs control network
-libreference-ril.so
-libs3cjpeg.so
-libFLAC.so } these libs are required for media
-= ICS =-
-libaudioflinger.so (may cause issues with booting in some ports)
-libaudioutils.so } once again, these libs are for audio
-libtinyalsa.so
-libril.so
-libsecril-client.so } these libs control network
-libreference-ril.so
-libs3cjpeg.so
That should be it for the lib folder for now. Exit /system/lib, and return to the main branch of the system folder /system.
Click to expand...
Click to collapse
5) Once we are back into the root of the system folder (/system), observe the two folders towards the bottom; usr and vendor.
usr - contains files that relate to touchscreen, softkeys, keyboard, and other hardware buttons.
vendor - mostly nexus specific, contains additional network libs, graphics, hw, and extra configuration files.
5a) In the ROM you are porting, delete both of these folders. They are of no use, since they are specific to devices.
5b) Copy both the usr and vendor folders from your base ROM, to the current port's system folder. As you can see, there is a lot of copy and paste from our Nexus ROMS to the ports, although we keep the important folders that pertain to the ROM itself.
Click to expand...
Click to collapse
6) Navigate back to the /system folder. You should see a folder named etc. Click into it.
6a) The etc folder is a wonderful place; it is one of the most used folders in the ROM. Observe a few of the folders inside. In our base ROM, you will see a few folders that are pretty self explanatory (wifi, permissions, init.d)
TO BE CONTINUED - I'M TIRED AND HAVE TEST ALL DAY TOMORROW AND WEDENSDAY. I WILL UPDATE WHEN I FIND TIME IN BETWEEN
and also this one. Just in case.
I like this already
Sent from my tweaked aosp Sensation
Swamp spreading your knowledge is 10x more beneficial to the community than releasing a ROM. Thanks man.
Sent from my Nexus S 4G using Tapatalk 2
dreamsforgotten said:
Swamp spreading your knowledge is 10x more beneficial to the community than releasing a ROM. Thanks man.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
+1 on the fishing lessons. Goblin your contribution is appreciated.
You without me is like Harold Melvin without the Blue Notes....
Thanks for this. Will attempt working on some of your ROMs like the Epic Touch one.
Sent from my Nexus S 4G using xda premium
This needs a kick
Sent from my Sensation using XDA
great start, can't wait to read the rest!
I've been super busy this last week, had no time for anything really. I'll finish writing this up, there are so many parts that need to be covered, I guess "simple porting" isn't all that simple to explain
I am just impatient to get this entire guide!! Thanks you
I will take my pain with patience.. haha..
waiting for the second part!!
Looking forward to the rest of the guide! Much appreciated swamp!
I will be following this thread closely. I haven't so much as coded a hello world in years but once this guide is complete, it may serve as the segue to get me started again. Waiting with baited breath.
Does this guide work with any rom port? Or is this Nexus S specific?
sivarticus85 said:
Does this guide work with any rom port? Or is this Nexus S specific?
Click to expand...
Click to collapse
I was actually going to add this to the op. The files I have included are nexus specific, but the actual process should work on tons of other devices.. There are a few areas that are nexus specific, such as build.prop edits and vendor folder, but other than that you should be able to follow this for other devices.
Or do you mean nexus s roms? This guide is kind of general porting; more of the basics. With htc sense and fancy roms like that, there will be more edits that need to be done, etc.
swamp goblin said:
I was actually going to add this to the op. The files I have included are nexus specific, but the actual process should work on tons of other devices.. There are a few areas that are nexus specific, such as build.prop edits and vendor folder, but other than that you should be able to follow this for other devices.
Or do you mean nexus s roms? This guide is kind of general porting; more of the basics. With htc sense and fancy roms like that, there will be more edits that need to be done, etc.
Click to expand...
Click to collapse
Well I own a Photon, another member pointed me here because I wanna learn how to port. My intention is to port HTC Sense to it, and learn something new in the process. I'm using the Photon-specific CM7 as a base, and the Energy Rom from the Sensation as my rom port. Since both run GB and are qHD devices, I figured these would be good starting points.
Thank you very much for your guide.
sivarticus85 said:
Well I own a Photon, another member pointed me here because I wanna learn how to port. My intention is to port HTC Sense to it, and learn something new in the process. I'm using the Photon-specific CM7 as a base, and the Energy Rom from the Sensation as my rom port. Since both run GB and are qHD devices, I figured these would be good starting points.
Click to expand...
Click to collapse
Yeah, you're set up perfectly. I am pretty sure you could follow this guide, although there may be some photon specific libs that have to be added..
swamp goblin said:
Yeah, you're set up perfectly. I am pretty sure you could follow this guide, although there may be some photon specific libs that have to be added..
Click to expand...
Click to collapse
Ok cool. I'm pretty sure it'll be a while before I ever get this port running, so in the meantime I'll be brushing up on what makes my phone tick, and for you to finish your little guide here.
I knew my EVO inside and out almost, so I'm hoping the Photon is easy to learn too. The file system for both is pretty similar, with the exception of Sense-specific files of course.
I've seen a number of new captivate owners who seem to have issues obtaining root or CWM on their phones for the first time. I wrote this batch file to help them get over those first hurdles with a helping hand. I am not a programmer (as you can tell by my coding skills) but I hope this will help a few people out.
Requirements:
Captivate i897 device on Gingerbread
Working USB port
Working Power Button
Preview:
This batch file uses a menu to select the operation. For Root, it uses ADB commands to get a user to download mode and then launches and Odin 1-click to replace the Kernel with the Corn 7.0A Kernel. After flashing, it reboots the user to Recovery and walks them through installing Root from the Corn Kernel CWM options (requires a working power button!). After the user is done, it will take them back to the menu to return to the Stock Kernel if they wish. There are a few extra menu options thrown in for fun.
Instructions for use:
Turn on USB Debugging
Connect Phone
Extract contents of zip to a folder
Run Batch file
Follow on screen instructions
??????????????
Profit!
Screenshots:
http://dl.dropbox.com/u/7368116/Images/Capture1.JPG
http://dl.dropbox.com/u/7368116/Images/Capture1.JPG
Download:
http://db.tt/Dz4fPI7N V1.1
Credits:
Thanks to Vashypooh for the Kindle Fire Utility which gave me the inspiration for this.
Thank you to 4-2ndtwin for the Odin One Click Creator that I was too lazy to download for myself.
Thank you to MTCarey for his Corn Kernel that I use in this batch file.
Thank you to all the devs and others that helped me along the way.
If this helps you or a friend out in any way please donate or Join Dropbox and get me some extra space.
Revisions:
V1.1 - Added the missing pause functions in the Root Procedure to give users time to read the instructions (thanks Machavity!)
V1.0 - Original (Here goes nothing)
Here is an alternative file to just install the Corn 7.0A Kernel.
1. Download an put in the root directory of KK4_Root
2. Run
Nice job on putting this utility together. Should be very helpful.
I will have to attach this thread to my sig.
Sent from my SAMSUNG-SGH-I897 using xda premium
Mirror: Dropbox download link... http://dl.dropbox.com/u/39937043/KK4_Root_v1_1.zip
And thank you for the files. They were the last piece I needed. I do need some real world testing on devices and computers other than mine to make sure I got all bugs worked out.
Took a look at the code, and this looks like it's going to be a handy piece of software for people who just need to do some common commands and don't want to wade through a lot of additional steps.
Well done.
Thanks. That was my idea. I've noticed many of the questions resolve around the simple tasks. By allowing a menu-driven batch file to take care of it, hopefully the users won't have as many issues.
This will allow a stock KK4 user to get root and CWM which will help them start their flashing journey.
Weekend-Thread-Bump for those who haven't seen this yet...
Sent from my SAMSUNG-SGH-I897 using xda premium
the download link don't work
takeoutttt said:
the download link don't work
Click to expand...
Click to collapse
Fixed! I think the L was supposed to be an I in the link. I copied it from the email this time. Work blocks dropbox which makes it hard to test the link. I tested it this time!
Sent from my SAMSUNG-SGH-I897 using XDA
Cool, added this to my toolbox, thanks...
And thank you again for Legend. I'm working on learning more Unix/Linux so I can contribute more in the future.
Sent from my SAMSUNG-SGH-I897 using XDA
That was a huge file hehe. I'll try this later
---------- Post added at 09:50 AM ---------- Previous post was at 09:11 AM ----------
after using the utility my kernel version is CORNv70A is this correct?
Yep. That's the correct version. I wish I could get the file size lower but it's already zipped at Ultra compression. The two kernel files make up most of the size with the driver file making up the rest. I wanted to add in more files/options but it would have made the file even larger.
Sent from my SAMSUNG-SGH-I897 using XDA
I recommend this. Very accurate and helpful. I just want to ask, why do you you pick 7.0a instead of 7.06
Sent from my SAMSUNG-SGH-I897 using xda premium
Some people have stated that the 7.06 kernel causes issues on their phone. I use it on mine with no problems. I just went with the safe bet for the first time users.
Sent from my SAMSUNG-SGH-I897 using XDA
Can I use the tool as an updater for example im running corn kernel 7.03 and i want to upgrade to the latest corn kernel using your tool
The tool will only give you Corn 7.0A or the Stock KK4 Kernel.
If you want to update to 7.06 you will need to download the Odin or CWM package for that version.
What if Corn 7.03 to 7.0a?
Yes. It will work just fine for 7.03.
You'll need to select the Root option which will install the 7.0A Kernel, but not actually follow any of the steps for adding root.
Select Root Option
Let it boot to download mode
Install it via Odin 1-click that script launched
Hit Ctrl+C to break out of script
You don't need the script to put you back into recovery which is why you break out.
Alternative Method:
Unzip downloaded file
Go to EXE Folder
Put phone into download mode
Run KK4_Root.exe
The ADB command to put your phone in download mode is: adb reboot download
Just open a command prompt to the downloaded/unzipped tools folder and type the above command with your phone plugged in.
Alternative #2
I added a new batch file to Post #3 to do just what you are asking.
I put this here because I have only tested with my s5, and its not done yet so wanted a general topic for feedback before putting in a dev section. But please feel free to move this as you see fit moderators.
While playing with making the hotspot mod and other general investigation into things on my s5, it dawned on me that its kind of a PITA to keep things organized. Kitchens do a pretty good job at helping to give you a method to the madness when making ROMs but I haven't found anything too helpful for making mods. So that gave me an idea, I have decided to call it modStudio for now, a place to keep needed tools and a workflow to keep things organized and not chaotic.
This project is far from complete but I think its in a good place now and was hoping to possibly get a little feedback.
I am running on a 64 bit linux machine, and right now that is all that is supported. If you are already building things for android chances are you have a machine like this around already anyway.
I don't have a full tutorial written up, and I would rather spend time adding functionality for now but you can pull down the latest copy by doing:
Code:
git clone https://github.com/miked63017/modStudio.git
There are some examples in the readme, but basically go into the directory that the repo created and source the toolbox file
Code:
source tools/toolbox
This sets up a few commands that I find useful, and hopefully you will too
I will paste what I have in the readme for now, and work on the tutorial as functionality is added, please let me know what you guys think. Any comments, suggestions, requests or contributions are welcome.
In the README.md:
This is a tool I made to aid in the process of making mods for Android phones.
I was tired of having multiple tools in different places and wanted to bring everything together with some easy shortcuts.
This should work on any 64 bit linux distro at the moment, but I have only tested on OpenSuse 13.1 since that is what I use.
Things that are assumed:
you are running on linux 64 bit
you have adb correctly setup and in your $PATH
you have aapt and java setup and in your $PATH
you know how to make changes once you have a decompiled apk
A few commands require you to have your phone plugged in, plug it in.
Some general notes for now:
You must always generate a source directory from which files will be used to modify
The source directory always stays untouched, so if you want to start over you can clean your playground and begin again
If you deodex an apk or ar that does not have a .odex it will be basically the same thing as the playWith command
If you have a source dir populated from your phone decompiling will take a while to search for framework files, unless you trim your source dir down
Example usage:
Code:
#setup modStudio, only need to do once
git clone [url]https://github.com/miked63017/modStudio.git[/url]
cd modStudio
#Need to source this file in your shell everytime you want to use modStudio
. tools/toolbox
#Basic workflow working with a stock odexed system image, must be rooted and have busybox installed
#example given for services.jar but should work with any
cleanSource
cleanPlayGround
pullSystemFromPhone
deodex services.jar
decompile services.jar
#make your changes in playground/system/framework/services.jar.out
build services.jar
odex services.jar
installFromPlayground
#Workflow from zip file, assuming already deodexed ROM
cleanSource
cleanPlayGround
pullSystemFromROM romname.zip
playWith services.jar
decompile services.jar
#make your changes in playground/system/framework/services.jar.out
build services.jar
installFromPlayground
Very nice will check this out when I get some time. Great work this could prove very helpful to the devs.
Sent from my SM-G900P using Tapatalk
vinman12 said:
Very nice will check this out when I get some time. Great work this could prove very helpful to the devs.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Made a few updates, if anybody is testing please do git pull often
Sent from my SM-G900P using XDA Free mobile app
Wicked cool! I assume the re-odex happens right on the phone? I need to get a VM setup so I can play with it..
Sent from my SPH-L710 using Tapatalk
rocket321 said:
Wicked cool! I assume the re-odex happens right on the phone? I need to get a VM setup so I can play with it..
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
The re-odex does happen on the phone and the files are pulled back onto the pc so you can install them when ready. The install command puts everything from your "playground" into the right place on the phone. I plan on still making a function to create a flashable zip, but haven't gotten there yet. Even without the flashable part it still makes things a lot quicker for developing and testing. Also plans on storing mods as patch files and scripts to log your work so you can repeat the same processes on different base systems in one command.
Sent from my SM-G900P using XDA Free mobile app