NEWS :
Koush's bmlunlock (a simple IOCTL send to the bml device) is just out and can replace redbend_ua !
http://github.com/CyanogenMod/android_device_samsung_bmlunlock
Hey
Is Flashing from update.zip the new trend ?
'Don't know but here is how you can do it quite easily using this template.
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
If you target another Galaxy S phone or another version of Android, you'll need to adjust ro.hardware and ro.build.id properties accordingly.
This template is done for Linux/Unixes/OSX.
If Linux cost too much for you or your employer, please contribute by sending a .bat equivalent to the .sh
Of course, you also need to put a valid zImage to replace the template's empty zImage
Feel free to adjust to your needs. License is WTFPL
Note : requirement are Java and Android source repo, already build.
Looks awesome!
I have a question though... why do you need to flash the kernel in an update.zip at boot?
As far as I know, the system will read the kernel at boot up time and load it into ram. It won't access the on-disk file again until the next boot. If that is true, then flashing while running should be 100% safe, right?
RyanZA it's an update.zip, not a ramdisk.
The point is getting an easy flashing method, requiring no computer.
And you don't even need to root your phone !
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
edit:
sorry for major dumbness, but do you think this could also somehow be used to reflash a nandroid backup?
FadeFx said:
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
Click to expand...
Click to collapse
I don't think the signing tool works on android -- maybe it does? Anyway editing scripts on a phone seems a bit silly!
FadeFx said:
curio, as i see this script is quite simple, so dont u think this all could actually be done on the phone directly? i mean if people cant afford a linux machine...
edit:
sorry for major dumbness, but do you think this could also somehow be used to reflash a nandroid backup?
Click to expand...
Click to collapse
Nope actually this is not dumb at all
Yes the flashing part run in updater-script can be started manually.
In the script :
Code:
"redbend_ua", "restore", "zImage", "/dev/block/bml7"
The update.zip presented here mainly targets custom kernel creators in order to give them another way to distribute their work.
This is a working example of how to use redbend_ua programmatically, hopefully it may help new ideas coming. redbend_ua usage is not limited at all to kernel flashing.
PS : you can use this template with windows as well, you'll just need to translate the ulta-basic .sh to a .bat script, or do the signing part manually.
supercurio said:
Hey
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
Click to expand...
Click to collapse
quick question, the build-update-zip.sh is not a must if i only want to flash zImage, rite?
looks like that, I need to modify updater-script (if needed), as well as putting a zImage into ur zip file, and finally remove the build-update-zip.sh from ur zip attached
then, ur zip file can be used for flashing
is it correct?
thx
So this will let people flash any rom from an update.zip (once the ROM makers take this into account) via RomManager without ever having to use Odin to get off stock?
Awesome!
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
supercurio said:
Hey
Is Flashing from update.zip the new trend ?
'Don't know but here is how you can do it quite easily using this template.
If you target a GT-I9000 on Eclair, you'll need to customize one thing :
In build-update-zip.sh, set DROID_HOME to the source code path for your local Android repository.
If you target another Galaxy S phone or another version of Android, you'll need to adjust ro.hardware and ro.build.id properties accordingly.
This template is done for Linux/Unixes/OSX.
If Linux cost too much for you or your employer, please contribute by sending a .bat equivalent to the .sh
Of course, you also need to put a valid zImage to replace the template's empty zImage
Feel free to adjust to your needs. License is BSD anyway.
Note : requirement are Java and Android source repo, already build.
I'll add some documentation later.
Click to expand...
Click to collapse
dseo80 said:
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
Click to expand...
Click to collapse
Thats for the updater-script i believe. In most cases, theres a update-script in the zip's as well and the recovery picks that up in which case it doesn't need the binary and hence works.
Okay !
Answers hour
ykk_five said:
quick question, the build-update-zip.sh is not a must if i only want to flash zImage, rite?
looks like that, I need to modify updater-script (if needed), as well as putting a zImage into ur zip file, and finally remove the build-update-zip.sh from ur zip attached
then, ur zip file can be used for flashing
Click to expand...
Click to collapse
When you run ./build-update-zip.sh,
- it produce a temp zip file containing appropriate files in it.
- then there'is the signature part, building another .zip, ready to be used.
- this "final" update.zip is put in the same current directory and you can use it as it is.
No further complication
Brantyr said:
So this will let people flash any rom from an update.zip (once the ROM makers take this into account) via RomManager without ever having to use Odin to get off stock?
Awesome!
Click to expand...
Click to collapse
Yes, to flash a complete ROM (several partitions) one more thing is needed.
On command line, redbend_ua accept only one command.
In order to run several commands successively (ie flash multiple partition like Odin does), you'll need to write them in a file.
The file /cache/ota/command should do the trick, but it's untested right now.
There may be other method to prevent rebooting after flashing (hacking the redbend_ua binary, finding the appropriate command line option or removing the reboot command temporary)
dseo80 said:
Thanks for the update script curio! this looks great.
One quick question - ive noticed several update.zip scripts for the galaxy S
have update-binary included.
Does anyone know what that does?? where did you get yours?
ive had success in using update.zips without that file at all.
Could anyone post information on what that binary is/does?
Click to expand...
Click to collapse
Right, many update.zip done today are made without knowing anything about how it really works
I studied a bit before creating mine, here is a walk-through this fairly undocumented process :
- recovery mounts /sdcard/
- recovery search for a default file named : META-INF/com/google/android/update-binary in the zip and runs it : see the source in bootable/recovery/install.c
- update-binary is actually updater in sources
- updater looks into the zip file to the script file named updater-script, update-script is obsolete
- updater then runs the commands listed in updater-script : here is the list of commands.
- then reboot
The only documentation I know for this command is the recovery/updater/install.c file itself
supercurio said:
When you run ./build-update-zip.sh,
- it produce a temp zip file containing appropriate files in it.
- then there'is the signature part, building another .zip, ready to be used.
- this "final" update.zip is put in the same current directory and you can use it as it is.
Click to expand...
Click to collapse
ok,thx
but one more thing i want to know is, u said the path must be changed to the android repo, so do u mean the source code for the kernel like linux-xxx-2.xxx dir?
Thx
@ykk_five
Content of build-update-zip.sh v1 :
Code:
#!/bin/sh
DROID_HOME="/home/curio/dev/mydroid"
zip -r /tmp/update.zip META-INF/ redbend_ua zImage
java -jar \
$DROID_HOME/out/host/linux-x86/framework/signapk.jar \
$DROID_HOME/build/target/product/security/testkey.x509.pem \
$DROID_HOME/build/target/product/security/testkey.pk8 \
/tmp/update.zip update.zip
rm /tmp/update.zip
adb push update.zip /sdcard/
DROID_HOME="/home/curio/dev/mydroid" : you set here the directory of your Android AOSP directory.
See : http://source.android.com/source/download.html
Create an empty directory to hold your working files:
$ mkdir mydroid
$ cd mydroid
Run "repo init" to bring down the latest version of Repo with all its most recent bug fixes. You must specify a URL for the manifest:
$ repo init -u git://android.git.kernel.org/platform/manifest.git
* If you would like to check out a branch other than "master", specify it with -b, like:
$ repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
Click to expand...
Click to collapse
This is this mydroid directory
The one that contains Android git source home directory, and compiled files in the out/ subdir
many thx for ur detailed explanation, supercurio!
Thanks curio,
very helpful explanation!
Thanks supercurio for the template!
However, there is no need to spend many hours (depending on hardware and bandwidth) pulling down 100s of megabytes of source and compiling it all if all you want is to sign an update.zip with test keys (if you already have the zImage)!
Just google around for "signapk.jar test keys" and you will get there.
BTW: I know that koush, leshak and wesgamer have Samsung Galaxy S trees up at Github but are they fully merged with AOSP yet?
I'm planning to go build my own kernel for this beast to try to solve the mono FM radio mystery, but last time I checked around it was said that the SGS tree required the use of a custom toolchain to get it to work at all.
Any comments on this?
Hey miki4242 !
Good to know that signapk.jar doesn't require hundred of megs of dependencies
About toolchain, you can use the one indicated by Samsung (CodeSourcery) but you'll face the big and ugly WakeLag.
I recommend you crosstool-ng or buildroot to build toolchains, with gcc 4.3.x march=arm mcpu=cortex-a8 mtune=cortex-a8 (no 4.4.x with march=armv7-v)
The building tutorial will be a part of the documentation I'll publish with my lagfix opensource release
Right now these info are too hard to find.
PS : I send you a mail with attached .config for ct-ng !
supercurio said:
Hey miki4242 !
Good to know that signapk.jar doesn't require hundred of megs of dependencies
Click to expand...
Click to collapse
supercurio said:
PS : I send you a mail with attached .config for ct-ng !
Click to expand...
Click to collapse
Thanks for the info !
Sorry for my ignorance, but does this mean someone can package Froyo in an update.zip and we could update it directly on our phone without needing Samsung Kies or Odin?
@supercurio:
Thanks for this well working template.
In updater-script:
Code:
line 17: package_extract_dir("zImage", "zImage");
should be
Code:
package_extract_file("zImage", "zImage");
But it did work with package_extract_dir, for some reason, too.
Btw, could you send me the config for ct-ng ?
I'm also struggling with this wakelag.
Been using st0kes' thread (http://forum.xda-developers.com/showthread.php?t=709105) and have checked out the AOSP tree, and build a ROM from it that boots on my phone, however....
How do I get the build to stop including things like the recovery image (rather than deleing the folder from the final zip)?
How do I get the build to include additional repo's, such as superuser?
I attempted to follow the guide myself, but when it comes to the command :
source build/envsetup.sh
I just get a "Bash: file not found"
But i don't know anything about the recovery...have you tried the cyanogen wiki?
Josh.
sounds like you're not in the correct folder..
Anyway, in answer to my original question... I found some useful posts on http://howto.ccroms.net/:
http://howto.ccroms.net/android_project/build/mod/recovery
http://howto.ccroms.net/android_project/build/mod/busybox
and
http://howto.ccroms.net/android_project/build/mod/root
I've got Superuser.apk / bash / busybox included, and my compile box is running with the changes from the /recovery howto now (Thank God for 24 core boxes, it compiles a full otapackage in ~10-15 minutes!)
Good evening. I am having a sort of difficult time 'trying' to figure this out.. I have downloaded JB4.2.2 from source for the maguro, also CM10.1. Both have successfully finished the process [.imgs/ .zip] files. I have gone through the whole thing with downloading pdroid2.0 /syncing, etc. I have the sources for JB in /android/source and CM in /android/system. Including PDroid2.0 in CM worked out fine _followed the instructions_ and everything eventually came together. When doing the same for the JB source it doesn't complete. On first make of the source into four .img files/ then I made an ota.zip. Pdroid wasn't included. Anyone have any insight or advice?
Did you "make clobber" before buliding again? Also, you realize that you only get the "framework" and need to install the app as well (that's what happened when I was installing OpenPDroid). BTW why use Pdroid2.0 and not OpenPdroid?
My Gnexi said:
Did you "make clobber" before buliding again? Also, you realize that you only get the "framework" and need to install the app as well (that's what happened when I was installing OpenPDroid). BTW why use Pdroid2.0 and not OpenPdroid?
Click to expand...
Click to collapse
No, I didn't . Thanks. There are two separate guides for fedora I've been referring to and only one had the command you mentioned... And about the .apk, I got that after my first successful build. I wanted to give PD2.0 a try and that involves building from source. And I wanted to do that for a first time.
So you compile a rom yourself and add opd? Instead of the auto_patcher?
Yes I compile AOKP with OpenPDroid. Patching instructions are here: http://forum.xda-developers.com/showpost.php?p=36679267&postcount=4
After flashing install Pdroid Manger (from xda or Play Store). If you want to include it in the ROM (like if you want to publish the ROM for others to download), see part 8 of this guide: http://forum.xda-developers.com/showthread.php?t=2217175
BTW: "make clobber" will remove the outputs of the build, for example when you type "brunch" .java files will compile into .class-es (among other things), when you type "make clobber" it will delete the .class files.
Sometimes after making certain changes you will need to "make clobber" or they won't work.
Hello All,
This may be in the wrong place so if it is, I am sorry, anyway to my question I'm trying to build CM for my S4 Mini LTE Serranoltexx everything was going fine until I got this message after running extract-files.sh
Code:
Extracting /system/lib/egl/libGLESv2S3D_adreno200.so ...
remote object '/system/lib/egl/libGLESv2S3D_adreno200.so' does not exist
Now after adding "libGLESv2S3D_adreno200.so" (if you search Google for it it's the top github link) I managed to get it to build the actual .zip and it does flash properly but it doesn't seem to have the correct graphics drivers (I thought this process wouldn't work and I was right), the guide on the how to build it doesn't help with this problem either so any help would be extremely appreciated
I've attached the logcat for reference (if it's needed) as a .docx file as the .txt file was 1.1mb and because I don't have a pro account on pastebin.
The problem with newer Android versions is that if often require new libraries which are not available in stock rom, so the extract method is actually not very useful unless we have a stock rom of the same version we are building for. To bypass this issue we use libraries from other phones that have the matching Android version. I suggest using the blobs that's on TheMuppets github, as those are up to date.
https://github.com/TheMuppets/proprietary_vendor_samsung
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"