yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] TheATHEiST:
Yup Ive moved onto CWR now, Iver never had a native Android phone before so never gone teh recovery route untill now.

Hopefully all the devs will start releasing zip versions of their releases with update.zip's aswell :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] simax:
well you guys forget the fact, that everything wil be wiped when he installs clockwork :)
[Android Apps and Games] lowspeed:
Which will auto scroll a few pages?
[Desire Q&A, Help & Troubleshooting] ccristal:
Hi all!

I have a corporate application on my Desire which enforces the use of a 8-character, alphanumeric lock screen password.

The keyboard that is shown on the lock screen to enter the password is not the default one: it seems to be a custom keyboard that is used only to enter lock screen alphanumeric passwords. Instead, if I install the same application on a DesireHD, the system's default keyboard (I use Swype) is displayed.

Does anyone know the reason for such a behaviour, and whether I can override the custom keyboard on Desire with Swype?

Thank you!

ccristal
[Desire Q&A, Help & Troubleshooting] mikro:
lotus traveller? :D
[Desire Q&A, Help & Troubleshooting] ccristal:
Indeed... ;)
[Galaxy 3 Android Development] Gsam101:
It didn't work on zImage from Froyo firmware i tried. Great work however :).

Works however for Eclair firmwares i've tested.
[Galaxy 3 Android Development] precurse:
Good work.

Is this based off the i9000 script?

Also, I've noticed with the i5800 Eclair firmwares that the initramfs is gzipped AND cpio'd. So... Kernel + initramfs.cpio.gz are gzipped together.

Basically you need to extract [kernel+initramfs.cpio.gz].gz, extract initramfs.cpio.gz again, then extract initramfs with cpio.

On Froyo, the kernel + initramfs.cpio is gzipped together, but nothing more. So after you extract the kernel and initramfs, you just need to extract with cpio after that.

Hope that kind of helps..
[Galaxy 3 Android Development] mizch:
In didn't go into Froyo for the i5800 until now. I used Eclair. It eases testing if you can compare things to a working kernel tree.

I see that Froyo doesn't use a compressed initramfs within the compressed kernel (which I doubt to make much sense anyway since compressing an already compressed part again is likely to produce a larger result). In theory, thus Froyo is easier to cope with than what I have now, but I have to write the code to handle it. This will need some time, maybe tomorrow, maybe the weekend.

And, no, this is not based on code from the i9000. It was written up from scratch. But I took some ideas from there and thank dkcldark for his good work.
[Galaxy 3 Android Development] precurse:
If we can get this modified for Froyo, it will allow for native ext2 mounting within the initramfs. Then we can add things to it like the way CWM works - busybox, adb, etc... So that we have a recovery adb setup before /system mounts.
[Galaxy 3 Android Development] Gsam101:
Exactly, that could be very useful, since we could get ext2 (ext4 maybe if we compile it as a module ?) in /data natively :)
[Galaxy 3 Android Development] precurse:
I already tried building ext4 and other modules off the i9000 sources... Didn't seem to work too well. Kept complaining about memmap or some random errors when I tried loading them.

Perhaps we can try them against JPF or something.
[Galaxy 3 Android Development] precurse:
Heck.. or even allow a user to use a file off their SD card to loopback mount /system partitions... Or /data partitions - like how the i9000 has a (built-in) 16gb SD card.
[Galaxy 3 Android Development] Gsam101:
I think so. Maybe we should just try to build an ext4 module with standard linux sources with armv6 as target ? Since i9000 has an armv7 processor..
[Galaxy 3 Android Development] precurse:
I setup my .conf to use the same CPU as what the G3 uses. I can't compile a kernel, but the modules compile.

It's a much different error I got from these modules than when I tried loading i9000 modules.
[Galaxy 3 Android Development] FadeFx:
Don't forget the internal SD of the sgs is on fast movienand SD memory, if one would loop back to his sdcard he would have to have a class 10 sdcard at least to get decent speed out of it.
[Galaxy 3 Android Development] mizch:
I've posted a new version of repack-zImage.sh and the associated utilities in the first article of this thread. This version lifts the restriction which until now allowed only compressed initramfs disks. Now uncompressed ones are also supported.

This modification got somewhat tricky, as a newly created initramfs, when compressed, yields sizes different from the original (even if it contains exactly the same files) due to different ordering of the files. For a 2 MB ramdisk, a difference of 3k may not sound like much, but it is - if it is too large by this number in a zImage where the initramfs must fit into the original's room.

Some black magic was needed. Now the files are ordered like in the original, with additional files (if created by the user) appended at the end. Options are provided to change the optimisations if needed.

I tried with JPF and with JPA-custom, so changes are really good that you won't have to bother with the above and can just go ahead and do your own initramfs modifications.
[Galaxy 3 Android Development] Gsam101:
Yeah, that worked for me. Thanks a lot ;).
[Galaxy 3 Android Development] spdwiz18:
have we (you all) found a way to unpack the froyo zimage yet? it worked great on eclair. thank you. and thanks for any help that you might provide.

i have tried on froyo for the epic but as it is unpacking it keeps looping 2 sets of numbers when i run the script. 5748017 5749018 and keeps repeating. any help would be great.
[Galaxy 3 Android Development] coolzarjun:
/Data and /cache ext2 conversion script.

hey here's a script that converts /data and /cache to ext2... i tried it.. worked for me.. i did not made this.. !

this is the work of MOTAFOCA !

quadarant score went from 305 to 515 and the best part.. internal memory shrunk from 176Mb to 161 Mb only :D

the script says its for i5508 but was made for 5800 as said by barquers

anyways.. here's the script.. hoping it will help :)

http://multiupload.com/O2ET4B8K0A

PS: im using MOTAFOCA's ROM... and script was made by MOTAFOCA not me :)
[Galaxy 3 Android Development] mizch:
It should work for any zImage. Sounds like a bug in the end detection for a compressed part. Can you provide me with a link to the zImage or contact me directly (PM/E-Mail) to pass me a copy? Then I'll go into it.
[Galaxy 3 Android Development] coolzarjun:
hey. does the script allows us to tweak the kernel so that it can be overclocked? ??

or we still need to wait for the kernel sources?
[Galaxy 3 Android Development] mizch:
You cannot do that without writing your own cpufreq driver (if at all). You need the kernel sources to do this.
[Galaxy 3 Android Development] spdwiz18:
Soryy gmail was not syncing for somereason. I will send tou what I have when I get home from work thanks.
[Galaxy 3 Android Development] mizch:
Got the zImage, thanks. I could reproduce the problem. What happens:

Using gzip's magic number, I can tell the start of a gzipped section. To determine its end, I need the help of gunzip. It reports "trailing garbage" if its file is too long, "truncated file" if too small, "OK" otherwise.

With your zImage, gunzip reports "truncated" when fed with 5749017 bytes, "trailing garbage" at 5749018. Obviously, only one of the two (not both!) can be correct. But this is what gunzip reports in your case. I found that 5749016 is the correct size. Erm.

As a workaround, I now detect when the gunzip result is oscillating this way and if it does, I search nearby towards lower size values for an exact match. This is not an ideal solution but I have to deal with what gunzip returns and this fits it best.

I'll do some cleanup and some final tests now and if they succeed, I will post the new version in about an hour or so in the first posting of this thread.

EDIT: New version posted.
[Galaxy 3 Android Development] spdwiz18:
thanks worked great.
[Galaxy 3 Android Development] jaskiratsingh:
Hi Guys,

Sorry for the stupid question... What does this do?
[Galaxy 3 Android Development] mumbozver:
Thank for great work.

I have request, can You add LZMA compressed zImage support?

Lastest fugumod has LZMA compression, I tried Lestatious 1.8 - Fugumod 2.2 ALPHA 14 from here
[Galaxy 3 Android Development] marcellusbe:
If you need something, I could give it to you ... just ask me :-)
[Galaxy 3 Android Development] mizch:
Should be doable, at least for the unpacking direction. I'll have a look at it.
[Galaxy 3 Android Development] mumbozver:
I already can extract init files from running kernel, however if they not deleted by later init scripts.

For me more interesting to change init scripts, and put it back to kernel image without compiling kernel myself or ask You to put something in initramfs. Repacking kernel images just more faster.
[Galaxy 3 Android Development] mizch:
Done (for unpacking and packing). See post #1. Note that LZMA is slower and thus the script takes longer to complete on lzma kernels.
[Galaxy 3 Android Development] nullghost:
mizch: I'm getting an error related to the variable at_min

Trying size: 7793816 3896908./repack-zImage.sh: line 284: [: : integer expression expected

At some points it seems to have integers assigned to it, while at other points it seems to have the string "yes" assigned to it.
[Galaxy 3 Android Development] mizch:
To reproduce the error, can you tell me what kernel you are using it on (download location)?
[Galaxy 3 Android Development] vishwanathptl:
mizch great work.

but it wont work on my zImage. its froyo kernel (GALAXY FIT s5670).

my zImage is abt 2.0 MB if pulled from mobile and its abt 3.0 MB if extracted from boot.img.

i am confused. i am not getting the rite zImage. plz help me. if u say i wil post both the zimages here. trying from 2 months but not getting anything.
[Galaxy 3 Android Development] mizch:
I need to be able to reproduce the error here. So please provide a download link to the zImage in question (it's not a problem if it is buried in some .tar for flashing) and I'll look how I can help you.
[Galaxy 3 Android Development] vishwanathptl:
I am uploading boot.img. I am not able to get zImage.

Plz help me to extract zImage and ramdisk.

Here is my mediafire link to boot.img

http://www.mediafire.com/?9kyim818duajyhu
[Galaxy 3 Android Development] mizch:
Sorry, I cannot extract the zImage for you. This is out of scope for this program and for me. Please ask in a forum which handles your brand of phone how to get at the zImage. When you've extracted it and if the script here doesn't handle it, I'll gladly try to help.

I simply cannot be expected to know where each of those many hardwares around bury their zImage, nor do a Google research on this for any number of them. So I hope you can understand that you're on your own with that.
[Galaxy 3 Android Development] vishwanathptl:
its k i can understand but wen i tried with HTC Android Kitchen 0.161 - by dsixda, it extracted zImage and ramdisk. but wen i compared my ramdisk with the initramfs of I5700, there wer some files missing in mine. i dont kmow if kitchen extracted the ramdisk completely. Can u help me with this? can u tell me that kitchen extracted the ramdisk completely? Plz..... here is my boot img extracted from my device.The previous one was from firmware files downloaded from samfirmware.com.

http://www.mediafire.com/?9eq16hbxtgkjcb9
[Galaxy 3 Android Development] dxdiag32:
i have some issue.

i unpack a zImage and then pack it,without any modifications.

but i can't flash it ,it stays bootlogo,what should i do?
[Galaxy 3 Android Development] dxdiag32:
i used fugumod beta3 standard,unpack and repack it,it dosn't work...
[Galaxy 3 Android Development] brisk5181:
Hmm, not working for me:

I always got this error:

./repack-zImage.sh -uv

Warning: there is aready an unpacking directory. If you have files added on

your own there, the repacking result may not reflect the result of the

current unpacking process.

mkdir -p /work/arm/1/zImage_unpacked

cd /work/arm/1/zImage_unpacked

repack-zImage.sh: Can't find a gzip header in file 'zImage'

Terminated

I am using openSUSE 11.2 "Emerald" - Kernel \r (\l).

I tried 2 zImages, one is from

http://derek.theblog.ca/galaxys-i9000m-gingerbread-upgrade

(file: http://www.multiupload.com/N8D9XZ1PIF)

and the speedmod kernel speedmod-kernel-k13e-500hz.tar

Both result the same error.

I tried both V6 and V4 of the script, same thing

Anyone can help?
[Galaxy 3 Android Development] arunmcops:
Hi mizch,

I am getting this error when i am trying to unpack any zImage

repack-zImage.sh: Can't find a gzip header in file 'zImage'

Terminated

(Ubuntu 11.04 x32)

But same kernel i tried to unpack on Ubuntu 10.04/10.10 x64 works perfectly.

So this can't be scripts fault . OS fault possible ?
[Galaxy 3 Android Development] Dharam_Maniar:
well, that can be the reason...I got it working on 10.10, and cdesai couldnt get it worked for 11.04...
[Galaxy 3 Android Development] arunmcops:
Sorry Dharam, posted same thing in ur thread also. :o
[Galaxy 3 Android Development] Jsmokey:
You've just made my day, I've spent almost three days trying to get this kernel unpacked and nothing else worked for me but your script!
[Galaxy 3 Android Development] Kyuta Syuko:
After decompressing the ramdisk I get a bunch of errors that look sort of like this:

Unpacking initramfs
9923 blocks
cpio: misc: Cannot change mode to rwsrwsrwx: Operation not permitted
cpio: busybox: Cannot symlink to `sbin/chgrp': Operation not permitted
cpio: busybox: Cannot symlink to `sbin/uuencode': Operation not permitted
cpio: busybox: Cannot symlink to `sbin/printenv': Operation not permitted
cpio: busybox: Cannot symlink to `sbin/df': Operation not permitted
cpio: ../init: Cannot symlink to `sbin/ueventd': Operation not permitted

And I was wondering if that's normal or if something's wrong.
[Galaxy 3 Android Development] D@rekills4:
Anyone got a fix for this :

?
[Galaxy 3 Android Development] PersianSphinx:
I get the same damned thing... jesus christ how I hate that Operation Terminated screen... you can fix it by changing to x64 from x32 or if you install ubuntu 10.10 :) (thats what dharam said...)
[Galaxy 3 Android Development] carl1961:
I'm assuming this tool is dead, as I get same errors as last posters and seems no one can post the cause
[Galaxy 3 Android Development] Dharam_Maniar:
try following the same steps i've given in my kernel development tutorials and you shouldnt get any errors...
[Galaxy 3 Android Development] carl1961:
Thanks dharamg3 great kernel TUT thread took me some searching to find it, you should add it to your signature

I was still unable to extract zImage with repack-zImage.sh

error Can't find a gzip header in file 'zImage'
[Galaxy 3 Android Development] D@rekills4:
If I remember correctly then I followed the exact same steps from your tutorial and got this error....

I think the tool itself is dead.....
[Galaxy 3 Android Development] carl1961:
I thinks also it's the newer kernels zImage (changing ther layouts, headers) because some said it worked
[Galaxy 3 Android Development] whiskerp:
Thank you for this utility. I've taken the liberty of making a couple of bugfixes - one to initialise compress_list in the -3 option case, and the other to initialise at_min to 0 rather than blank in gunzipWithTrailer. The first stops the -3 option hanging, and the second is cosmetic and prevents sh complaining.

I can confirm it works with zImage 4.0.4 XWLPT for the Samsung Galaxy S II (i9100).

Peter
[Galaxy 3 Android Development] psiva2010:
Please help : repack-zImage.sh: 100: repack-zImage.sh: Syntax error: "(" unexpected

Hi all,

I am getting the follwing error while executing the extraction script how to resolve this?

# sh repack-zImage.sh -u

repack-zImage.sh: 100: repack-zImage.sh: Syntax error: "(" unexpected

Any please help me..

Siva
[Galaxy 3 Android Development] Phil3759:
Thank you a lot, the unpack part works perfect

However:

- it will hang on kernels like CF-Root

- the resulting output zimage, even from a stock fw without modifying the intramfs files will not boot, stuck at Samsung first boot screen

Any help please or a tut how to setup

(using Ubuntu 10.10)
[Galaxy 3 Android Development] whiskerp:
It works for XWLPT and XWLPU (unpacking, clearing the MMC_ERASE_CAP byte and repacking) and provides a working safe kernel. However it doesn't seem to work for XWLPX and I don't know why yet. If I unpack and repack the XXLPX zImage, the resultant zImage is binary identical. However changing the single byte from 1 to 0 to make it safe (this results in piggy.gz being one byte smaller and getting padded by one byte) makes the kernel hang. Why?!
[Galaxy 3 Android Development] tux_mind:
hi all,

i'm trying to decompress zImage from TF201-kernel_V10_4_2_15.zip kernel

unpacking the blob file gives me the attached zImage.

so...since it's a lzma zImage your script try to bruteforce the lzma archive size.....well....let it run...all night....but nothing.....

i can see numbers like 6125813, which means about 6MB, but the zImage is only 5MB.....

sincerely i just need to hexedit the kernel.img not the initramfs, so my quest is:

can someone fix this bug? or can someone add an option for extract and repack only the kernel.img?

thanks in advance.

PS:

now i'm trying to modify this script for extract only the kernel.img, update soon.
[Galaxy 3 Android Development] tux_mind:
i did it

i make some changes to your code.

now if you provide the the -k option it extract only the kernel.img + initramfs(_gz)+part3.

for repacking you have to re-use the -k option with the -4 one.

hope this helps.

note:

/*************************************************************************************************************************

* this is a work around because the script FAIL to extract my lzma compressed zImage ( look @ my previous post ).

* don't use it unless you have my needs ( modifying the kernel only ). Cheers!

************************************************************************************************************************/
[Galaxy 3 Android Development] vampirefo:
The scripts work well, unpack and repack but kernel wont boot. Epic Touch FI27
[Galaxy 3 Android Development] ciscogee:
Gettin error, either permission denied or line 99 unexpected "(

Anyone around?
[Galaxy 3 Android Development] DoR2:
Try to use Ubuntu 10.04 or 10.10 with program.
[Galaxy 3 Android Development] ciscogee:
Thanks for reply, I've been using 10.10, not sure how I got it to work after error... oh yeah I rebooted :D.

Lovely tool!
[Galaxy 3 Android Development] DoR2:
Maybe tool chain installation program wanted you to reboot system but nevertheless it works!
[Galaxy 3 Android Development] lynxdog:
Dont sh just bash

Dont use sh to execute the script, use bash. I know it's an old thread but hey....
[Galaxy 3 Android Development] vbenkovskyy:
Could someone help to extract. Script tells that file is not found but it's in the directory with the script and utils.
[Galaxy 3 Android Development] DoR2:
I have tried to unpack your zImage but I got an error

Separating gzipped part from trailer in 'piggy.gz+piggy_trailer'
Trying size: 2131356 3197034 3729873 3996293 4129503 4196108 4229411 4246063 4254389 4258552 4260634 4261675 4262196 4262457 4262588 4262654./repack-zImage.sh: line 284: [: : integer expression expected

padding check (may take some time): 14

Found uncompressed ramdisk.
Detecting padding (may take some time): 4188
Unpacking initramfs
cpio: Malformed number rrect
cpio: Malformed number cpio m
cpio: Malformed number ethod
cpio: Malformed number used:
cpio: Malformed number use -H
cpio: Malformed number newc
cpio: Malformed number option
cpio: Malformed number o cpio magi
cpio: premature end of file

repack-zImage.sh: cpio -t failed.
Terminated

Also I can recommend running this command in order to get full access to all files in this directory.

chmod 777 *

BTW, you can try to use ArchiKitchen in order to unpack zImage and work on your ROM. Good Luck!
[Galaxy 3 Android Development] gekkehenkie11:
This tool seems outdated, doesn't work on modern kernels including DT it seems ...
[Galaxy 3 Android Development] yhaddad:
It should work on a kernel of galaxy gear s watch?
[Galaxy 3 Android Development] gekkehenkie11:
Still no new kernel unpacker tool ? :(

---------- Post added at 11:53 PM ---------- Previous post was at 11:03 PM ----------

Actually I just found out how to decompress a modern kernel :) Just search the boot.img for 894C5A4F (that's 0x89 followed by "LZO"). In my case I needed the second hit (after some ascii text 'System halted' etc). So cut everything off before that, save it with a .LZO extention and you can simply unpack it with an LZO unpacker :)
[Galaxy 3 Android Development] banxian:
in -p option, tar command will failed if your image is not named as zImage
[Galaxy 3 Android Development] sagarsorathiya433:
repack-zImage.sh: Can't find a gzip header in file 'zImage' :(

please help me to solve this error i have tried 10.10 n 16.04
[Galaxy 3 Android Development] Sutan99:
syntax error 100 :'( on Lubuntu
[Galaxy 3 Android Development] xiaodeng:
20/5000

你有Windows版本吗？非常感谢你！
[Galaxy 3 Android Development] xiaodeng:
Do you have a Windows version? Thank you very much!
[Galaxy S I9000 Q&A, Help & Troubleshooting] JJEgan:
http://xdaforums.com/showthread.php?t=901212

POST 2

jje
[Vibrant Q&A, Help & Troubleshooting] XiaoSiuMai:
I really do love the axura roms but I left to try other roms. Im currently using nerov3 with touchwiz and I just like the overall layout of it. Is there a way to install touchwiz launcher into newer versions of axura. I read about touchwizgtg but wasn't sure if it would work
[Vibrant Q&A, Help & Troubleshooting] jdanisevich:
There's a file in my thread at the bottom of the goodies section that installs both of the Nero v3 launchers. You could always unzip it and push them manually too.

EDIT: There's a link in my signature.
[Vibrant Q&A, Help & Troubleshooting] XiaoSiuMai:
not exactly sure what to do. i unzipped it and i see theres a touchwiz apk. do i take that and put it into my phone and install it like an app?
[Vibrant Q&A, Help & Troubleshooting] blizzard1017:
I believe you just push it to system/app and reboot.
[Vibrant Q&A, Help & Troubleshooting] theronw68:
I have tried installing the GTG launcher on several of the new axura roms and when I did I started getting FC's on the com.phone something. When I removed it the FC would go away. Went back to JL5 for now.
[Vibrant Q&A, Help & Troubleshooting] XiaoSiuMai:
that doesnt sound too promising :(
[Vibrant Q&A, Help & Troubleshooting] theronw68:
It worked fine on Axura 2.2, but, these new ones he has released it has not worked for me. Give it a shot though. It is a pretty easy fix if it doesn't work. I used root explorer to put the file in system\app. If it causes FC's then just delete it. Seems like there are so many different variation's in these phones it might work for you.
[Vibrant Q&A, Help & Troubleshooting] Dattack:
I also tried to use root explorer and get the process com.android.phone has stopped unexpectedly. Once i force closed it , the touchwiz launcher works but I will wait and see if anybody have this fixed,
[Desire Q&A, Help & Troubleshooting] davebugyi:
Hello!

After searching and reading through threads, I came to nothing. I try to find out, if it is possible to record 720p (or even 800x480) video with high quailty audio - I mean in better way than the standard 8khz, AMR, Mono codec.

From the threads here (and other forums) I learned different things. Some people said, it is impossible, some say, it is possible and some say they already have it.

Also tried lgCamera app from the Market (version 4.4) and tried EVERY possible combination of resolution, encoder, bitrate, audio codec, etc. - none of them worked and got Record video failed error.

Any help on this? Recommended settings?

BTW, I am using a rooted Desire (AMOLED) with LeeDroid 2.3C

Thanks in advance,

David