Hey guys,
I am having a problem patching the 11-18 IOKP build for use as my second ROM on my S4. I am using chenxiaolong's PATCHER app, so his DUALBOOTPATCHER supports IOKP and have never had a problem with it until now. Whenever I drag the IOKP .rar file to the "patch-file" batch file to patch it, it gives me an error. When the batch file is extracting the ramdisk, it says " ---ERROR BEGINS--" Ive included a screenshot of the entire error its giving me. Ive even tried to patch the boot.img file with no luck. I would ask chen himself, on his thread, but XDA wont let me since im new. Any help will be greatly appreciated. Thanks! :highfive:
also
also im using CWM and Dirty Unicorn as my primary ROM
Anything guys?? I still cant figure out why im getting this error. Any help would be great!:fingers-crossed:
I'm pretty sure you have to use touchwiz as primary unless something has changed that I don't know about
Ive been using Dirty as my primary since it has been available for tmo and IOKP as my second ROM with no problems before the 11-18 build. I haven't had any problems until now. Plus, I talking about the DualBootPatcher file that automatically patches a ROM to use as your second ROM. Whenever I try to patch the 11-18 IOKP .rar file, it gives me the error that is shown in the picture I uploaded. Thanks though man!
Related
Hi all,
I recently began editing the Galaxy S kernel, from the downloadable open source package.
After some time I compiled my changes into a zImage. My problem is, it won't flash when i put it in the most recent PHONE_I9000XWJG5.tar.
Odin3 just hangs at Flashing zImage...
My zImage is about 2.5MB in size, and the original JG5 zImage is 4.6MB, so I guess I am missing something.
I think I am missing the modules (which you can also compile). But I'm not sure.
Does anyone know how to compile a working kernel for the Samsung Galaxy S?
Thanks in advance!
First:
Read here: http://www.cianer.com/androidg1/28-building-android-kernel-images
Then here: http://www.receptorblog.com/wordpress/howto-compile-a-linux-kernel-for-samsung-galaxy/
and finally here: http://forum.samdroid.net/f9/dev-vmware-image-build-i5700-kernel-2-6-29-android-2-1-a-984/
not update.zip,why?
In recovery, no sd update.zip option, how can I tune out?
I'm also trying to make a new kernel based on JM5.
My goal is to fix the BlueTooth issues.. I think i've found the problem in a kernel's .c file...
I'm following this link:
HERE
I'm downloading the GT-i9000 opensource ZIP from Samsung, but i don't quite understand where can i get the Android Toolchain....
Is It really 6GB as it says HERE ?
I wish there was a XDA-like tutorial for this
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers, and to prevent confusion, please only discuss Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
Please accept my apologies if this has been answered before. I did a search and did not find a similar problem. I am a noob and will read any guide or how to that you refer me to in order to learn how to get better. I am new to Ubuntu/Linux and terminal but if you point me in the right direction I can probably figure it out. I will try to provide as much detail as possible.
I have recently built a Jelly Bean AOSP ROM following this XDA Guide.
I am using Ubuntu 10.04 LTS x64.
repo synced with this branch
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r3
which is build JRO03H
I downloaded and extracted the binaries on the Nexus Binairies page. I did notice that prior to building that unlike the ICS branches the JB device/samsung/toro folders do not have a extract-files.sh file
I made an otapackage using the full_toro-userdebug command.
I flashed the rom using ClockworkMod 6.0.1.0. I did a factory reset and wiped the cache prior to flashing. I also installed gapps-jb-20120726. Everything booted up fine and for the most part everything works except for the camera app. When I press the camera button I receive a message that says "Unfortunately, Gallery has stopped working." Or I get a black screen and nothing happens then I'm back in the app drawer. I have tried fixing the permissions and that did not fix the problem.
Can you explain to me what I need to do to get my camera and gallery app working? This is the only issue I have with my rom thus far. Do I need to extract the camera binary some how?
The camera and everything works fine my AOSP IMM76L build but not with my JB Build.
I have flashed other roms such Peter Alfonso's JB rom and his camera works fine, so any directions or links would be greatly appreciated.
Seeing the same.
I have this same JRO03H build (except I use CentOS 6.3 to compile AOSP 4.1.1_r3) with the EXACT same issue you describe. When the camera applet is selected it complains "Unfortunately, Gallery has stopped". Everything else in the build (24hours+ fresh) appears okay so far.
I fixed it.
I figured out the problem and was able to get the camera and everything to work. I did a couple of searches on Google and came across a thread from Android Central. I cant post the link since I have less than 10 post, but pm and I will send it to you.
We are still missing some proprietary files. Namely 6. The camera is named ducati or something and you have to either get it from another rom or extract it from ICS. I personally used Peter Alfonso's github for Jelly Bean and compared his vendor folder to mine and copied lines from his make files. Took me a couple of hours of comparing every file to realize that you need to focus on vendor some other files in core folder.
You can get his github information from his webpage and also look inside his OTA compared to your OTA to make it work. Also if you want to use Google Wallet you are going to have to edit your build.prop file in your OTA to make it not say full_toro use the 4.0.4 release keys.
I'm not at my testbox to walkthrough the steps but that's what I did. But sure to backup your source folder before you start tweaking, Came in handy twice before I got it right.
Hope that helps. Good luck.
could you please share your Rom? I also have the same issue. but still not fix it.
paternal_techie said:
I figured out the problem and was able to get the camera and everything to work. I did a couple of searches on Google and came across a thread from Android Central. I cant post the link since I have less than 10 post, but pm and I will send it to you.
We are still missing some proprietary files. Namely 6. The camera is named ducati or something and you have to either get it from another rom or extract it from ICS. I personally used Peter Alfonso's github for Jelly Bean and compared his vendor folder to mine and copied lines from his make files. Took me a couple of hours of comparing every file to realize that you need to focus on vendor some other files in core folder.
You can get his github information from his webpage and also look inside his OTA compared to your OTA to make it work. Also if you want to use Google Wallet you are going to have to edit your build.prop file in your OTA to make it not say full_toro use the 4.0.4 release keys.
I'm not at my testbox to walkthrough the steps but that's what I did. But sure to backup your source folder before you start tweaking, Came in handy twice before I got it right.
Hope that helps. Good luck.
Click to expand...
Click to collapse
wangyu7988 said:
could you please share your Rom? I also have the same issue. but still not fix it.
Click to expand...
Click to collapse
I am uploading to mediafire as I don't think I have a high enough post count to post the rom here.
Whiles there's currently an excellent port from the 7100 MIUI build it has a couple of flaws which I'm not totally sure can be resolved. It's been a long time since I looked at developing anything but figured I'd have a look at the current patchrom implimentation to see if we could get a proper 317 build going.
Here's some details about patchrom, and what I've done so far.
First up. https://github.com/MiCode/patchrom already has a note2 tree, so we can use that as a base for changes for the 317.
Have all the same pre-recs installed as you would to compile cm.
In linux you'll need to make a patchrom folder
1.mkdir patchrom
micode doesn't yet have all the repo setup for jellybean, so I just downloaded the following zip tardballs and extracted them into their respective folders;
https://github.com/MiCode/patchrom_miui/tree/jellybean -> patchrom/miui
https://github.com/MiCode/patchrom_tools/tree/jellybean -> patchrom/tools
https://github.com/MiCode/patchrom_build/tree/jellybean ->patchrom/build
https://github.com/MiCode/patchrom_note2 ->patchrom/note2
https://github.com/MiCode/patchrom_android/tree/jellybean ->patchrom/android
Once that's complete you can pretty much follow the developer guide here;
https://github.com/MiCode/patchrom/blob/ics/Patchrom Developer Guide.pdf
I highly suggest installing this as your source rom, (http://forum.xda-developers.com/showthread.php?t=2016575&highlight=stock) installing it as a stock build first (no themes tweaks etc)
Create a folder patchrom/317 and start following the guide to create your stockrom.zip
Copy the following from the note2 folder into your new folder
makefile
miuihome
miuisystemui
originalsettings
mms
overlay
phone
settings
thememanager
customize_framework.sh
customize_miuiapp.sh
phoneapps.mk
Camera maybe?
Edit the makefile to update the directory references to your new build folder.
Run the make workspace to unzip and decompile the frameworks that are going to be modded.
By following the guide, with what you've done we're now at the firstpatch phase. That's what I'm currently working on as well.
The directions are a little convoluted so hopefully this helps.
When you run make firstpatch what it tries to do is automatically patch the miui smali bits into the framework/services smali files. Whenever it can't it'll create a *.rej file for you.
What you need to do is edit the associated file and manually put in the diffs from the rej files. Where we have this super great advantage is there's already the 7100 framework with the patched in rej in the note2 folder you downloaded earlier. So really you just need to compare that smali file against yours and apply the changes noted in the rej file. (tip. you edit the original files created during make workspace, nothing in the temp directory, just in the framework.jar.out folder etc)
Here's a really great post detailing an example; http://forum.xda-developers.com/showpost.php?p=25713236&postcount=171
Boy.. that doesn't sound easy.. but believe me it's easy once you start looking at it.
Ok I've dealt with the *.rej files now what?
Holy congrats! Your a step ahead of me at this point Next up you just need to run make fullota. It *should* at this point build an ota you can flash from recovery.
copy to sdcard, reboot recovery flash and.. it should boot. Really I expect there should be little or no issues thanks to the 7100 work we've already borrowed.
Assuming it works, let's get it on github and shared with the miui team. That'll go a long way to making it a weekly build.
Good luck and have fun!
If you get somewhere, let us know.
An additional source is the changelog for patchrom on the note2 (7100). Here's the manual commit details. This is also a pretty good map for what we need to do.
https://github.com/MiCode/patchrom_note2/commits/jellybean?page=2
Brother, are you now doing this job？I want to do but is too difficult for me...
I have been using MIUI 3.1.25 from the T-Mobi Galaxy Note 2 thread. I really like this ROM. But there are issues since it is not optimized for the i317 note 2 phones. Example: I can't access my 64GB SD card on MIUI v5. I reverted to the previous version (MIUI 3.1.25) and my SD card forks fine. Have anyone followed the instructions in the original post above and was able to port MIUI to the i317 note 2 phone? I would really like to know how to port this ROM. I am looking into how to get started.
Thanks for sharing this! Idk if anyone has improved on miui from this? Im willing to look into it, would you be willing to help me out with fixing some issues once i get it flowing? If so i appreciate it, just toss me a pm at your convenience.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
dirtydroidx said:
Thanks for sharing this! Idk if anyone has improved on miui from this? Im willing to look into it, would you be willing to help me out with fixing some issues once i get it flowing? If so i appreciate it, just toss me a pm at your convenience.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the post but belive me fixing rejects is not that easy job. You will get hundreds of rejects while patching the smali code by MIUI patchrom.
If anyone got success with this, I would love to get in touch with you.
Guys please help with Patchrom Tool for Note 2
Hey guys,
as some of you know bponury ended the support for his TouchControl (formerly PGM) app. What means that if somebody wanted to change a kernel to a different one or switch to a different device he will be unable to use the app (which is great IMHO). My idea on this thread is to put all the modules for all kernels and devices so that we'll be able to still use the app. I'm not a developer so if anybody can create flashable zips from those modules I'll be grateful (if this thread kicks-off I'll learn to do it by myself but for now I believe we can manage)
Thanks to bponury who shared a location of modules I was able to extract those from DirtyV. I attach them below. Please send me more modules and I'll put them below.
FYI - if you want to extract the modules by yourself you need to download i.e. File Manager, turn on the Root Explorer option and copy the contents of "/data/data/me.paranoid.touchcontrol/files/" folder.
I believe if we managed to gather greated number of modules this thread could be linked in forums of other devices. But let's start from Gnex. Cheers
I have the Ponury stock modified module. It works on Fancy kernel and the FML omni rom too.
Here's a link to download https://www.dropbox.com/s/79scinuv2q1676m/ponury_stock_modified.zip
Flashable zip containing bponury TC module - View attachment tuna-TCmodules-bponury.zip
Flashable zip containing DirtyV TC module - View attachment tuna-TCmodules-DirtyV.zip
I put together these packages which successfully flashes the file to the right place as described by @bponury (/data/data/me.paranoid.touchcontrol/files), please report back with your results. The file has the same permissions (rw- --- ---) and installs to the right place, so it is totally harmless to flash, it won't mess with anything outside of the TC data folder. Looking forward to any feedback, and I am happy to make some more packages for other kernels if people can provide the modules. The DirtyV version worked perfectly for me after the update to 4.4.3
* technically I did test the bponury version with FancyKernel and it didn't work, but my device is bad to test with because, ever since the update from version 1.x to version 2.x, I almost always need to reinstall the modules after any simple reboot.
Okay this is module for franco kernel
Anyone got the modules to work?
I tried flashing them and copy/pasting them to the files folder, but still the app doesn't detect the module and wants to load it online, which isn't possible anymore. Trying it with latest franco r398.
Had it working up until this morning. All of a sudden it hangs on loading the the module.
Sent from my Galaxy Nexus
Likewise...today it stopped working...tried flashing the modified stock zip still no result...really disappointed for this outcome...it's my most useful application.
Does not work for me too. I use franco r398
Just look for the 2.2.1 TouchControl apk and it should work again. Currently i'm using the latest fancy kernel and i don't need to flash an additional files since it still automaticly downloads the modules when using the apk mentioned before.
"Make it COUNT"