Related
ok guys,
as some of you know but i doubt alot of you do the best way to get the most up to date version of android on your device, hopefully meaning less bugs is to get a new zimage now these are updated very often so i wouldn't recommend getting every single one but doing this doesn't mean you have to wipe you card every time which is very useful ok well here's how to do it.
1. download a zimage from here i recommend not always getting the most recent but look through all the builds and find one that has good rating and has a write up type thing for blackstone i am currently using one from last tuesday.
2. unzip the file straight to your sd card.
3. edit the startup.txt changing start kernel zimage to start kernel<new zimage name> with you guess it <new zimage name> being the file name of the zimage you just download.
4. boot android if you are interesting in linux at all and watch the booting process you will see it has found a new image.
5. use the build, then add your findings to the comments. but please don't post bugs there use the bug tracker.
[/LIST}
hope this helps you to get your device running smoother.
edit: using the rom that came out this morning build zImage.20100215_000813 and seems to be ok sleep mode is better still takes some time but works nearly everytime but froze after waking up once
hey,
this calibration thing doesnt seem to work. i cant download it to my phone it just comes up as text which i cant save anywhere. any help?
That's normal
keridel said:
hey,
this calibration thing doesnt seem to work. i cant download it to my phone it just comes up as text which i cant save anywhere. any help?
Click to expand...
Click to collapse
try hold clicking then save as
good
thx slaming for having a thread for the zImages... with frequent updates, it slightly gets confusing (maybe just me ) to find the latest... and I already know I am far behind...
Any ideas, you will put a chrono order on the first post... or we refer to glemsons..
Be careful: The LASTEST isn't the GREATEST
sraaj said:
thx slaming for having a thread for the zImages... with frequent updates, it slightly gets confusing (maybe just me ) to find the latest... and I already know I am far behind...
Any ideas, you will put a chrono order on the first post... or we refer to glemsons..
Click to expand...
Click to collapse
what do you mean by a chrono order?
EDIT: no i won't be able to add a list of the images there are just to many i wouldn't mind doing every few but my device is broken as the power button is broken meaning i can't test deep sleep issue at all.
thnx for the thread,i've started using android since october,and up to now i hadn't find any zImage that can beat this :
Download
try it,it's the perfect zImage, very fast and smooth,with no Deep sleep or mic issue!
k-zik said:
thnx for the thread,i've started using android since october,and up to now i hadn't find any zImage that can beat this :
Download
try it,it's the perfect zImage, very fast and smooth,with no Deep sleep or mic issue!
Click to expand...
Click to collapse
Hi
Can you tell me the date of this image?
Cant download from hotfile.
commit e6785d034370095ce9247e94fd2e4f9e2fd53ed4
Author: Brendan Shanks <[email protected]>
Date: Sat Feb 27 11:21:36 2010 -0800
Map power-off to reset (because reset works)
Is there a power-off in settings or somewhere else?
Want to try this, but cant find power-off.
These Kernels / Zimages are already being included in my builds... there's no need to install them separately... and it's well documented in the opening post for the builds.
The danger with the VERY latest zimages is that they are highly prone to not working properly, since they are literally built automatically without any checks on them running or not.
brodos123 said:
commit e6785d034370095ce9247e94fd2e4f9e2fd53ed4
Author: Brendan Shanks <[email protected]>
Date: Sat Feb 27 11:21:36 2010 -0800
Map power-off to reset (because reset works)
.
Click to expand...
Click to collapse
you say map power off to reset how do you remapp keys?
Hi,
after many failed attempts, I turn to you for something that is normally easy.
I want to compile a kernel for my Hero.
I am currently on this ROM: VillainROM 3.0 BETA
but in the context of a project (serial communication with the phone), i need a specific kernel.
If someone could edit the .config file with these details:
CONFIG_HTC_HEADSET
This entire line should be replaced with the following:
# CONFIG_HTC_HEADSET is not set
CONFIG_MSM_SERIAL_DEBUGGER
CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE
and replace them with:
# CONFIG_MSM_SERIAL_DEBUGGER is not set
# CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE is not set
compile the kernel and repost it would be great.
Thank you very to everyone, this forum is very interesting.
+
Nymphe said:
Hi,
after many failed attempts, I turn to you for something that is normally easy.
I want to compile a kernel for my Hero.
I am currently on this ROM: VillainROM 3.0 BETA
but in the context of a project (serial communication with the phone), i need a specific kernel.
If someone could edit the .config file with these details:
CONFIG_HTC_HEADSET
This entire line should be replaced with the following:
# CONFIG_HTC_HEADSET is not set
CONFIG_MSM_SERIAL_DEBUGGER
CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE
and replace them with:
# CONFIG_MSM_SERIAL_DEBUGGER is not set
# CONFIG_MSM_SERIAL_DEBUGGER_CONSOLE is not set
compile the kernel and repost it would be great.
Thank you very to everyone, this forum is very interesting.
+
Click to expand...
Click to collapse
Sorry - I did answer you in the thread yesterday.
Have you attempted to compile it for yourself? If so, what was the outcome?
you won't be able to compile a kernel for a 2.1 rom since the sources aren't released yet. if you want to compile your own kernel you are stuck with 1.5 roms...
btw, where is your problem with compiling the kernel? i can try to do it later when i'm home, but again, we have only the 2.6.27 sources, which won't work for eclair roms (including villain).
nprussell said:
Sorry - I did answer you in the thread yesterday.
Have you attempted to compile it for yourself? If so, what was the outcome?
Click to expand...
Click to collapse
Sorry i didn't see it.
Yes I tried but I think without the right items.
I'm not a pro in kernel and ROM.
Already, it is possible to use the Vilain ROM with a modified kernel?
If yes, anyone could build it with the above specifications?
Thank you
oh boy, i need a new phone...
kendong2 said:
oh boy, i need a new phone...
Click to expand...
Click to collapse
???
Why this sentence ???
Nymphe said:
???
Why this sentence ???
Click to expand...
Click to collapse
I am guessing he means it is a lot of work and will need a dev phone to do it
no, actually a NEW phone. i am a bit frustrated with my hero right now, it has come down to noob talk in these forums. people ask for help "help my phone don't work", you ask them "why exactly, what does it say and what did you do before" and they answer "my phone won't work anymore, please help me". if you analyze this conversation it was like this:
a: i need a custom kernel for 2.1 and if i try myself it doesn't work.
b: you can't have one, the sources aren't out yet. what are your problems?
a: can someone make a custom kernel for 2.1? i tried but it didn't work.
going to ebay looking for a nexus, again...
now go and bash me for trying to help, i deserve it. definitely.
Hi devs,
I was trying to compile the eclair AOSP with hero profile. Everything compiled correctly and it boots up on my hero but why does my touchscreen not work??
Anyone could give me a hand on why the touchscreen is not working on my hero? I am using godmode kernel.
Thanks in advance,
Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko
maxisma said:
Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko
Click to expand...
Click to collapse
Thanks Maxima!
But this is for Froyo or also working for eclair?
And another question is it a special kernel config that I need to enable for the touchscreen to work? As I did use a working .config from another 2.1 rom.
Giving those files a go anyhow
Argh! I recompiled the kernel with the config from the kernel you posted. But still touchscreen does not work..
Also the unlock (pincode) screen does not popup so I cant make any calls.
Can anyone please give me some hints on why this is happening?
In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it
dipje said:
In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it
Click to expand...
Click to collapse
Ah! Thanks. Recompiling
btw and what about the pincode popup issue? Why am I not getting that popup when starting the phone?
Works! Nice! Thanks. And my other Question? Pincode unlock is not poping up. I cant get a signal from my provider
Anyone has a clue?
I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?
Shakor said:
I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?
Click to expand...
Click to collapse
RIL-library..
maxisma said:
RIL-library..
Click to expand...
Click to collapse
Cool. Thanks checking this out.
Still no joy.. Argh
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.
Ok, so after having a million questions I thought I'd write up a quick little 'how to' with regards to porting.
And now the warning
Read and learn first, doing this could cause serious issues with your tab or even brick it. The tab is really tough, and hard to brick if you do everthing right but it could still happen. I'm not responsible if it does.
Where to start
Get good at reading, google searching and searching XDA. Lots of porting discussion regarding other phones can apply to the tab.
Learn to use Heimdell
Have a linux distro available, either by virtual box, or natively.
Technomancer where it all began
I've said it before and I'll say it again, without techs work miui wouldn't have been possible.
Reference technomancers thread here: http://forum.xda-developers.com/showthread.php?t=931857 on how to download the cm7 + sgt source, you're also going to want to follow the kernel making part, cause most likely you'll need to make adjustments to the init.rc which is inside the initramfs and requires building the kernel again.
porting x build
Get X build onto your computer and extract the update.zip for it.
Copy the boot.img into your linux environment and extract it using splitbootimg.pl script (note: Google it, plus this doesn't work with samsung builds). Compare the init.rc to your init.rc (from the sgt cm7 kernel source root folder). Specifically the most important part here is the PATH, LD_LIBRARY_PATH statement and BOOTCLASSPATH lines.
Build your kernel with the updated init.rc and flash with heimdell, it should still boot your cm7/miui build (if you were running it before) albeit with errors.
The system
Now following the awesome list of proprietary files (either from your source folder or technomancers github link) check the galaxytab-common-vendor-blobs.mk for the GT-P1000. It lists every file you need that's propreitary to the tab and where to put it.
Also you'll probably need the debuggerd from /system/bin on the cm7 build.
Compare the /system/build.prop of the cm7 build to your port, make sure the ril info is the same as well as the ro; model, brand, device, board, and platform lines.
Create an update.zip (or whatever you want to call it.zip) and try it.
It's not booting
Logcat is great, but I really suggest using the ddms from the android sdk tools. It's color coded, and gives a much nicer view of what's happening.
Using winmerge in windows or a linux file compare program start checking what other bin files may be missing that you require. Special notice to the xbin folder.
It works! I want to post it!
Ok, first up, make sure you have permission if this is someone elses custom build you've ported. Most people/groups are really good about it assuming you ask first and give them credit in your post.
Also credit everyone who helped, answered a question or sent you in the right direction. (it's just polite)
Second your going to want to make sure your update.zip flashes the kernel, read the update_script from the cm7 build to understand how it works.
So that's it for a start. roll up your sleves, gather your courage and get to it!
Please if you have other tips, add them to the thread, what's better 1 or 2 'developers/porters' or 100?
Thanks. This is very useful for me.
Thanks,
Following this method, with slight alterations to adjust, I was able to port an i9000 phone build to the tab in about 10 minutes, it's really not terribly that difficult once you have the right steps.
The first couple times are usually frustrating but after that you get the hang of it
Hi mssmison Thank you for your guide,it will be very useful in the future! I have only one request,how can I contact you? I have a proposal for you about a dev team (regarding an old think tank)
Thanks for the guide...
Is there any ROM left to port by the way?
Sent from my GT-P1000 using XDA Premium App