Develop Bugs

[27.05.2010 Neopeek][ANDROID Froyo + Eclair + Ion] ext2-filesystems - NoSquash

Hi all,
just wanted to let you know that i succeeded in putting Android on EXT2 of internal memory.
As I am also involved in Projects like MeeGo, Bada & Others you may contribute to this builds and help me making this builds better. I will post all Project updates here but as stated above I will more frequently visit my own website due to the other Projects. If you need urgent support in this builds you may leave me a message on my website.
Please have a look at my website if you are interested in contributing.
My Website: Contribute Android
UPDATE 27.05.2010: View original article: Android Froyo Eclair Ion Builds
Why moving to ext2 filesystem and leaving root-filesystem contained in squash / image files?
A squashed / imaged root filesystems had to be unsquashed til now if you ever wanted to make changes in them! Therefore all files could be placed directly into the root of your memory (commonyl FAT32).
ext2 is a linux-only filesystem and you will have to get some tricky tools to get it read in Windows. But in Linux you have now the possibility to write directly into files or even update the filesystem as you want. Possible scenarios are placing archives into it to update Android and so on.
We think that until now a lot of users had problems with the squash filesystem and expect to contribute more users to Android-Porting with ext2. Squashfstools won't be needed any more.
If you are an unexperienced user or don't know how to get a virtual system with Ubuntu running:
Don't hesitate to ask us in the communiyt for help. Now let's start:
Step 1: Partitioning your memory!
Please install Gparted in Ubuntu and partition your internal memory (Diamond) or SD-Card (other devices) as seen below in the screenshot (1 x Fat32, 1x ext2, 1x linux-swap):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2: Extracting files onto ext2
* sudo umount /media/disk-1 /*Notice: this could also be something like /media/disk or /media/disk1223-dsf232 etc.! You have to locate the ext2 filesystem which you have partitioned above */
* sudo mkfs.ext2 /dev/sdb2
* sudo mkdir /media/neopeek
* sudo mount -t ext2 /dev/sdb2 /media/neopeek
* sudo tar -xzvf ~/Desktop/neopeek_android.tar.gz -C /media/neopeek /* Alternatively: Neopeek_Android_2.1.tar.gz oder Neopeek_Android_Froyo.tar.gz */
* sudo umount /media/neopeek
Step 3: Extracting files onto FAT32
Download HARET-Paket.zip including latest Kernel. Extract the contents directly onto the root of the FAT32-Partition. That'S it! Unplug your device / sd-card and run Android by executing "HARET.EXE".
Download Android Froyo Eclair Ion
So that's my birthday gift for myself and for you. If anyone wanna make me a gift then move to my site and register / connect to get the latest updates by mail before they appear here and to support my upcoming website!
[/B]
Thanks goes to: XDAndroid-Project, Balsat for the latest builds and many others. You know who you are!
Build notices: Based on XDAndroid's and Balsat's autobuild service for rootfs and kernel. Special thanks go to Balsat for introducing EXT2
Android Ion has buggy WiFi but runs like Myn's Donut!
Android 2.1 runs better for me on ext2. It's the XDAndroid build. On ext2 I can watch videos without stuttering. It's a little bit smoother for me. Test it out!
Android Froyo: This is for the freaks of you! Unproductive / Instable but worth a try hrhrhrrr!
Again i will state this here that it is clear for everyone: This builds are not mine cause I think some of you may think so. The build rootfs is made by Balsat but I have written an tutorial for you and republished builds so that you can get it working with EXT2. The HARET-Packet is modified by me as I couldn't find one from Balsat. Also I will provide you with support / help on how to partition your memory correctly. Especially windows users and beginners will need this support. In the next days / weeks I will port / cook further Android builds on my own and again this will be EXT2.
This thread is intended for introducing EXT2 for all of you who didn't know that it was possible. I either didn't knew it and no one informed me about this. Sure, I inform you!
For anyone having problems with partitioning: Try using fdisk command in console! This should look like this for your $GB internal memory or SD card with equal capacity:
sudo umount /dev/sdb1 or /dev/sdc1 (also sdb2 / 3 if exist)
sudo fdisk /dev/sdb
Press "d" to delete partitons
Select "1" (redo this if you already had mislucked tries with selecting "2" and "3")
Press "n" -> then "p" -> then "1" -> press "enter" -> type "600" or type "+1500M" -> press "enter"
Press "t" -> press "1" -> press "b" -> press "w"
Now you should have partitioned a FAT32 and can use GPARTED to create ext2 and linux-swap (notice: linux-swap-creation only needed for future builds and for testing. No need to create it if you don't wanna test)

Reserved for updates
Reserved....

reserved for updates Part2
Reserved2...

Looking forward to seeing it! I sense a wave of donuts coming...
Also, happy birthday!

Good luck. I hope this time we can have the android.
count on you.
respects

I hope so to,
Will this build have a good battery life so we can use it daily as OS?
Good luck and happy birthday!

good luck and happy birthday

Happy Birthday! We hope that the "diandroid" very fast and stable rom will!

Looking forward too it! And Happy Bday!!

very good man and happy birthday to you!!

do you have a link for your android 1.6? I am looking for a 1.6 w/ working wifi. not found yet. Thanks!

hao214 said:
do you have a link for your android 1.6? I am looking for a 1.6 w/ working wifi. not found yet. Thanks!
Click to expand...
Click to collapse
look arround, on all builds wifi is working, dont be so lazy
vatoloco haerzlichen glueckwunsch zum geburtstag
gruss

Happy Birthday to you.. Man this is best news I have heard in last one and half years !!!
Really looking forward to it. Will definitly test it for you even if its unstable

Can't wait to try your Android build =)

happy birthday

Happy birthday!..waiting for your release

There are already working android avaliable ? Like the one shown in above signature ?

Trying
Hey men...
Im trying your build but i cant synchronizing with my google account...
Anyone have the same issue?

which build are you trying??????????

suhas_sm said:
There are already working android avaliable ? Like the one shown in above signature ?
Click to expand...
Click to collapse
of course..there is XDANDROID,Myn's Warm Donut (the fastest bulid i saw),there is glossy android,Klinux's sense bulid and many other....you can find it in the raphael's android forum or in the blackstone's android forum or here

[26-10-2010][Neopeek's Android Ports][CyanogenMod]

EDIT 26-10-2010: CyanogenMod 6.0 Final and CyanogenMod 5.0.8 Final available now!!
The following CyanogenMod-Ports are available now (stable is marked as FINAL):
VaniljEclair CM5 (Eclair / FINAL V1.3 updated on 26-10-2010 )
"Official" CM6 (Froyo / FINAL V1.0 updated on 25-10-2010])
FroyoRedux CM6
SuperF-Port
many more...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quick-Installation-Guide:
Read this installation instructions by chase21
Thanks go to:
Balsat, XDANDROID-TEAM, Cyanogen + Team and everyone else whom I forgot.
Used kernel + modules: htc-msm-linux by glemson and balsat
Used rootfs: XDAndroid modified to run on EXT2-Partition
Mixed-Up and ported by: Neopeek
Source: CyanogenMod 6, CyanogenMod 5
Download latest release

Added some screenshots and video for the upcoming build. 249views here and no reply here. Not bad! Nevertheless I have enabled JIT Dalvik VM and get a Linpack Benchmark of 4.04MFLOPS. Again this should work also on your devices but til now I have no feedback of anyone if the first release did work on your Blackstones. Anyone wanna try (tutorials provided when you follow main thread on XDA-Developers' HTC Diamond-section).
I only have A HTC Diamond. As described in first post you must update startup.txt with correct values for
- ramaddr
- mtype
- lcd density
If anyone gets it to work in first release than contact me and share your startup.txt with me. Otherwise I will package one into the new build for my own although I have no Blackstone. So help by anyone would be good in this stadium.

Main-thread updated with download link for new build [08.06.2010]. I have also included startups for HTC Blackstone (see main thread or my signature)

i've tried it yesterday(the 04 build!), by creating 2 partitions on my 2gb sd card, the ext one have 1,5gb and the fat32 0,5gb.
I've also modified the startup text file to be like this :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set cmdline "root=/dev/mmcblk0p2 init=/init rootwait rw rootdelay=10 console=tty0 rootdelay=10 fbcon=rotate:1 lcd.density=210 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,-1,3 acpuclock.oc_freq_khz=650000 htcblackstone-panel.no_bkl_off=1"
boot
Click to expand...
Click to collapse
after starting Haret, it loads up and execute all the scripts but it get stuck on the black screen and android don't show up.
I will try today release and i'll post a feedback!

Ok thank you for trying out.

k-zik said:
i've tried it yesterday(the 04 build!), by creating 2 partitions on my 2gb sd card, the ext one have 1,5gb and the fat32 0,5gb.
I've also modified the startup text file to be like this :
after starting Haret, it loads up and execute all the scripts but it get stuck on the black screen and android don't show up.
I will try today release and i'll post a feedback!
Click to expand...
Click to collapse
k.zik don't get higher than 512MB for ext2:
You could do it the following (assuming 2GB sd card):
1.3G FAT32
300M EXT2
300M EXT2
Also it is very important to unmount your device / sd-card before starting android up

Downloading for my Blackstone.
When i try it, i post here...

thank you for trying this out insestito!

it doesn't boot up!
I've tried it several times with the kernels avaible with haret but nothing shows up!
waiting for insestito to see if it works with him.

Can you put here a mini tutorial ???
i need linux in my computer ???
Thanks !

Notice: Sorry guys I don't have a Blackstone but I am using XDAndroid rootfs + kernels. So this should work for you. But I can't test it on my own.
So this is the way to go:
Install Linux (or use LiveCD GParted) to create the ext2 partitions (a Neopeek-User called fu-raz will publish an according tutorial for GParted LIveCD in the evening, he promised me -> otherwise you will have to follow the main thread on diamond section -> see my signature -> SuperEclair)
When you have created succesfully the partitions on your sd card you will have to extract contents of Haret-PaketV1.2.zip to your first partition (Fat32) and put the startup.txt for your device into the root of the fat32-partition
Then you will need to extract superclair02b.zip to your second partition (ext2). For this you will have to use LINUX, It won't work in Windows
After that, please unmount your device and / or sdcard and wait for complete unmount before you start android
Simply just follow the steps which I describe in main-thread and my website and reproduce all steps (+just use sdcard). I Think k-zik is on the right way. It could be just a wrong thing in startup. So you will have to try it out. Even some Diamond users got it working after trying several times. If you think the startup is ok and you don't get any errors regarding partitioning. Then maybe you should give an older zImage + kernel from XDAndroid autobuild service a go as I use the latest. Hope this helps.

where I put the contents of supereclair02b ..... ??
The content of haret-packet i put in partition fat32 ????

you will have to put the content of supereclair02b on the ext2 partition, and all the content of the haret-paket on the fat32 partition with the startup.txt!

kernel panic - not syncing: No init found.
Rebooting in 7 seconds...

@Insestito: You are on the wrong way.
Maybe I should make a video on how to do this?

vatoloco said:
@Insestito: You are on the wrong way.
Maybe I should make a video on how to do this?
Click to expand...
Click to collapse
Yes please....

Will need some time for an explaining vid, though you could also try to follow links in main thread. A lot of people got it running after trying it several times.

I followed all the instructions correctly.
but when I open haret.exe loaded and is on the line KERNEL PANIC ....

Ok thanx indeed for trying to get this running. I think I will have to get a blackstone to get it work. If anyone else want to give it a try then go for it.

i still interested in the project and i'm trying to get it to work, by using different kernels but it always stucks on the black screen and android don't show up!
i dont know where is the problem?!? is there any command that can i add to the startup to get the log file of the booting or someting?!?

[HOW TO] Change/Modify Secondary Splash Screen Initrd/logo.rle

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cant bellieve how hard it was to find any info on this topic
I was working on my rom and wanted to change the secondary splash screen image.
I searched around, asked devs and had no success finding a step by step tutorial on how to do this.
Finally after much research I did it! so here i bring you my experience.​
Click to expand...
Click to collapse
Boot order
​
1. To modify/change the first boot image go here:
http://forum.xda-developers.com/showthread.php?t=895089
2. To modify/change the bootanimation go here for some examples:
http://forum.xda-developers.com/showthread.php?t=1129705
Click to expand...
Click to collapse
First we need to establish where this splash image is located,
the image file is called logo.rle and is located here:
(i used 7-zip to view but don't use it to modify)
This is the file we need to change/modify, you can extract it with 7-zip.
Now we need to be able to convert this logo.rle to .png and back to a logo.rle
​
To do this go here:http://forum.xda-developers.com/showthread.php?t=1140406​
Code:
1.run command promt
a.browse to folder with those bat files
-type:cd \users\you\desktop(if located on desktop)
-copy logo.rle to this folder
b.to conver rle to png type: Convert_rle_to_image.bat logo.rle
c.to convert back to rle type: Convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
If you have your logo.rle ready now we need to replace the one that came in your initrd.gz
this is harder than i thought, because initrd.gz is a image file it cant be modified with 7-zip
first you will need to be running linux (im running ubuntu on a virtual machine)
once you get linux create a new folder on the desktop called "temp" copy
the initrd.gz to this folder, open applications/accesories/terminal
and browse to the temp folder with the initrd.gz file(mine is "cd /home/isidro/Desktop/temp)
now type
Code:
gunzip -c ./initrd.gz | cpio -i
now in the temp directory you have unpacked initrd.gz. Replace logo.rle then when you're done still in the temp directory type:
Code:
find ./ | cpio -H newc -o | gzip > ./initrd.gz
this will replace the initrd.gz with the modified logo.rle
​
Click to expand...
Click to collapse
Now just Copy/Replace the modified initrd.gz to your Rom's boot folder and Test!
This worked for me on the HD2 but I would assume it works on any android Rom. Keep in mind this is the best way I could do it, if you know of a better way please share.​

nice compilation...thanks bro

nice work bro
really
but I hope there i some easier way to do it
cuz this involves linux and virtual machines and I dont think many of us have this

Been looking for this for a while now, thank you very much !

very clear! i search for this a long time
THX bro

nice to see some dev sharing their knowledge ...thanks bro

If anybody cant get this to work at all!!!
send me your initrd.gz and your new image and ill give it a go.

thanks for taking so much time for making this excellent article. thanks added.

Excellent tutorial!! Very time consuming process for changing just one image but definitely easy when given step by step instructions.
Thank you for all your hard work and effort!

Ok, please tell me what am I doing wrong- I want to replace the logo.rle from one initrd.gz to another initrd.gz
I extract both with gunzip -c ./initrd.gz | cpio -i into their own separate folders
I copy the logo.rle I want over the logo.rle I want to replace
I do find ./ | cpio -H newc -o | gzip > ./initrd.gz after ensuring the old initrd is not there in the folder
I flash it on my phone, and it wont boot - if I flash same the initrd.gz without replacing the logo.rle, all is fine. I have tried this so many times

works perfect
10x

works nice. thanks.
you know what's nicer?
removing the logo.rle completely.
and what's even nicer than that?
finding the way to do it to clk boot.img
(how to patch it's initrd.gz or kernel)
then what you get is the First Boot Screen (HSPL) and then boot animation directly.
I can find a way to unpack the boot.img and repack it successfully.
If you find this out, that would be great.
Should be possible to do on linux, but I get a corrupted boot.img every time i try.

Is there any way of changing this after the ROM is installed? Unfortunately the ROM I use requires that you flash a kernel .zip after installing it, which then resets the second splash screen.

ellisbodds said:
Is there any way of changing this after the ROM is installed? Unfortunately the ROM I use requires that you flash a kernel .zip after installing it, which then resets the second splash screen.
Click to expand...
Click to collapse
open the update_kernel.zip with 7zip
replace the initrd.gz with the one with the new image, now just flash
the kernel and that's it

There is guide for change it use Window OS:
http://forum.xda-developers.com/showthread.php?t=1140406

isidromxz said:
open the update_kernel.zip with 7zip
replace the initrd.gz with the one with the new image, now just flash
the kernel and that's it
Click to expand...
Click to collapse
Unfortunately though, that doesn't seem to work. It's got a boot.img, so I had to extract that first in Linux, then I replaced logo.rle and recompiled boot.img. I then replaced the old boot.img in the kernel zip file and attempted to flash it, and I can't remember what happened. Either I got a message about update-script being deprecated and was told that installation was aborted, it flashed fine but didn't work, or it stopped my phone working.
tl;dr: I've spent far too long trying to figure out that one little image and in the end decided to just change the first splash screen to match the second one that flashes with the kernel.
Sent from my HTC HD2

I've follow all your staff and when I repack the initrd.gz with ubuntu I get this message error ( in french the message error so I try to translate) : cpio : the file ./initrd.gz is bigger, 163840 new bytes does not have been copied
That is the problem

BoBaN75 said:
I've follow all your staff and when I repack the initrd.gz with ubuntu I get this message error ( in french the message error so I try to translate) : cpio : the file ./initrd.gz is bigger, 163840 new bytes does not have been copied
That is the problem
Click to expand...
Click to collapse
Yeah I know it says it's not copied but it is just test the initrd after that

I found a guide to do it on window.
I will check and post here if I can find it on my Laptop
Sent from my GT-I9100 using xda premium

I Have tried it and it didn't work. When I tried to flash my phone via clk via rebuild rom installion aborted. Can explain how to put back the moded file on the phone
Sent from my HTC HD2 using xda premium

boot.img-ramdisk.gz: not in gzip format

Hello, I'm trying to modified the kernel of my phone, but I have one problem, when I try to decompile boot.img-ramdisk.gz (with ubuntu) it appear a message that put boot.img-ramdisk.gz: not in gzip format and I cant.
Regards

pepe471 said:
Hello, I'm trying to modified the kernel of my phone, but I have one problem, when I try to decompile boot.img-ramdisk.gz (with ubuntu) it appear a message that put boot.img-ramdisk.gz: not in gzip format and I cant.
Regards
Click to expand...
Click to collapse
what do you want to do ? did you compile the kernel and now maybe you want to prepare boot.img ? or what
anyway there is a .perl script to split boot.img in zImage (kernel compiled) and ramdisk also this will extract ramdisk in "out" folder so work with this folder to change things to ramdisk
search for split_bootimg.pl and you get the answer !
I think here you have a complete reference http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

ruscan.calin said:
what do you want to do ? did you compile the kernel and now maybe you want to prepare boot.img ? or what
anyway there is a .perl script to split boot.img in zImage (kernel compiled) and ramdisk also this will extract ramdisk in "out" folder so work with this folder to change things to ramdisk
search for split_bootimg.pl and you get the answer !
I think here you have a complete reference http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
I want to chage the boot logo and the g-sensor configuration.
I extract the boot.img-kernel and the boot.img-ramdisk.gz with split_bootimg.pl, but then I can't extract the files of boot.img-ramdisk.gz
Thank you

ruscan.calin said:
what do you want to do ? did you compile the kernel and now maybe you want to prepare boot.img ? or what
anyway there is a .perl script to split boot.img in zImage (kernel compiled) and ramdisk also this will extract ramdisk in "out" folder so work with this folder to change things to ramdisk
search for split_bootimg.pl and you get the answer !
I think here you have a complete reference http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Arrogant answer without any help. If you would care to read what people write you would have noticed that he wanted to unpack the boot.img-ramdisk.gz.
I'm trying the same with a ramdisk here but get the same error. And yeah, i did read the tutorial you've link + http://forum.xda-developers.com/showthread.php?t=1477845.
And both say nothing about how to handle the errors we got.
After some googling, and trying out two approaches, i finally found the solution.
The third one i came across worked, at least for me:
http://forum.xda-developers.com/showpost.php?p=31954123&postcount=913
The "boot.img-ramdisk.gz" was compressed in lzma format. So the correct command would be:
lzma -dc ../boot.img-ramdisk.gz | cpio -i
Ramdisk unpacked. Enjoy.

Kaskade said:
Arrogant answer without any help. If you would care to read what people write you would have noticed that he wanted to unpack the boot.img-ramdisk.gz.
I'm trying the same with a ramdisk here but get the same error. And yeah, i did read the tutorial you've link + http://forum.xda-developers.com/showthread.php?t=1477845.
And both say nothing about how to handle the errors we got.
After some googling, and trying out two approaches, i finally found the solution.
The third one i came across worked, at least for me:
http://forum.xda-developers.com/showpost.php?p=31954123&postcount=913
The "boot.img-ramdisk.gz" was compressed in lzma format. So the correct command would be:
lzma -dc ../boot.img-ramdisk.gz | cpio -i
Ramdisk unpacked. Enjoy.
Click to expand...
Click to collapse
or if you are in linux.. since you are making kernel.. you will be..
anyway.. if you are getting this error.. just rename the file with .lzma extension..
then use archive manager or Xarchiver application in linux and extract it.. then extract the file obtained again... you will get all the files and folders inside ramdisk.. no need of any kitchen/anything.. as linux can handle lzma natively

Kaskade said:
Arrogant answer without any help. If you would care to read what people write you would have noticed that he wanted to unpack the boot.img-ramdisk.gz.
I'm trying the same with a ramdisk here but get the same error. And yeah, i did read the tutorial you've link + http://forum.xda-developers.com/showthread.php?t=1477845.
And both say nothing about how to handle the errors we got.
After some googling, and trying out two approaches, i finally found the solution.
The third one i came across worked, at least for me:
http://forum.xda-developers.com/showpost.php?p=31954123&postcount=913
The "boot.img-ramdisk.gz" was compressed in lzma format. So the correct command would be:
lzma -dc ../boot.img-ramdisk.gz | cpio -i
Ramdisk unpacked. Enjoy.
Click to expand...
Click to collapse
Hi,
I am on Linux.
I have installed lzma on the home dir.
I don't know why I am getting Decode error.
[email protected]:~/VIJAY/andriod/work3$ ls -lrt
total 239840
[SIZE="2][COLOR="DarkGreen"]drwxr-xr-x 3 vramaraj sw-team 4096 Oct 9 2011 data/
-rw-r--r-- 1 vramaraj sw-team 70 May 16 2012 installbusybox
drwxr-xr-x 4 vramaraj sw-team 4096 Oct 6 19:03 sdcard/
drwxr-xr-x 16 vramaraj sw-team 4096 Nov 28 22:14 system/
-rw-r--r-- 1 vramaraj sw-team 4073472 Dec 2 22:27 boot.img
-rw-r--r-- 1 vramaraj sw-team 302938 Dec 3 21:14 logo.bin
-rw-r--r-- 1 vramaraj sw-team 236601691 Jan 31 22:18 YONIP_MP_A919_v1.zip
-rwxr-xr-x 1 vramaraj sw-team 6773 Jan 31 22:18 split_bootimg.pl*
drwxr-xr-x 3 vramaraj sw-team 4096 Jan 31 22:19 META-INF/
-rw-r--r-- 1 vramaraj sw-team 3477896 Jan 31 22:50 boot.img-kernel
-rw-r--r-- 1 vramaraj sw-team 591679 Jan 31 22:50 boot.img-ramdisk.gz
-rwxrwxrwx 1 vramaraj sw-team 229 Jan 31 22:55 extractboot*
drwxr-xr-x 3 vramaraj sw-team 4096 Jan 31 22:55 out/
drwxr-xr-x 2 vramaraj sw-team 4096 Jan 31 23:32 ramdisk/[/COLOR][/SIZE]
[email protected]:~/VIJAY/andriod/work3$
[email protected]:~/VIJAY/andriod/work3/out/ramdisk$ ~/lzma -dc ../../boot.img-ramdisk.gz | cpio -i
/users/home40/vramaraj/lzma: Decoder error
cpio: premature end of archive
[email protected]:~/VIJAY/andriod/work3/out/ramdisk$

Deadly said:
or if you are in linux.. since you are making kernel.. you will be..
anyway.. if you are getting this error.. just rename the file with .lzma extension..
then use archive manager or Xarchiver application in linux and extract it.. then extract the file obtained again... you will get all the files and folders inside ramdisk.. no need of any kitchen/anything.. as linux can handle lzma natively
Click to expand...
Click to collapse
Interesting!
I have a similar problem where gzip complained that my boot.img-ramdisk.gz is not in gzip format.
At the advice of this thread [and some others] I ran:
lzma -t boot.img-ramdisk.gz
xz -t boot.img-ramdisk.gz
Neither one worked, so at the advice of your post I copied the file to both a ".lzma" and a ".xz" extension.
Again, neither the lzma nor xz command-line tool worked, but again at the advice of your post I opened them in Ubuntu's Archive Manager and both view and extract just fine!
CORRECTION:
I was too optimistic: Archive Manager can view the file but cannot extract it.
I pulled my file from an official OEM update.zip file that I successfully updated from.
Maybe the file is really corrupt? (which is hard to believe since my update was successful)
Maybe split_bootimg.pl corrupted it?
What command-line do I need to extract these files from...well...the command-line?
Thanks!
Pv
---------- Post added at 07:22 PM ---------- Previous post was at 07:08 PM ----------
swooby said:
CORRECTION:
I was too optimistic: Archive Manager can view the file but cannot extract it.
I pulled my file from an official OEM update.zip file that I successfully updated from.
Maybe the file is really corrupt? (which is hard to believe since my update was successful)
Maybe split_bootimg.pl corrupted it?
Click to expand...
Click to collapse
Looks like it was user error...just not mine!
The update.zip file already has a "ramdisk.img" image in it.
That file binarily identical to the boot.img-ramdisk.gz file that is inside the update.zip's boot.img.
Someone messed up!
I think I've got it from here!
Thanks for a place to brainstorm!
Pv

pepe471 said:
Hello, I'm trying to modified the kernel of my phone, but I have one problem, when I try to decompile boot.img-ramdisk.gz (with ubuntu) it appear a message that put boot.img-ramdisk.gz: not in gzip format and I cant.
Regards
Click to expand...
Click to collapse
if you have a windows OS or Wine.. you can use my GZ fixer..
http://www.wcn.it/Fix-GZ-archives.exe
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

help
I use cygwin to unpack boot.img
Im using code gzip -dc ./boot.img-ramdisk.gz | cpio -i and get error
im success using code lzma -dc ./boot.img-ramdisk.gz | cpio -i
and now im not understand code to compile my ramdisk again...
can anyone help me ?

If you have this problem and above solutions don't work for you (like me), maybe it's compressed in another file format; for example my ramdisk was compressed using LZ4.. to know this under Linux you just use command file <your ramdisk> and it will output your ramdisk file info, after knowing the compression format just google how to decompress that format and you're done

where can download Fix-GZ-archives.exe

[Q][THEME] Replacing PNG in system file

Hello.
I am running this ROM, and my lockscreen looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to replace the white circle around the icon (displayed when hovering the icon, before releasing the finger from the screen). It just needs to be transparrent.
The developer of the ROM wrote this to me:
final Drawable activeBack = mResources.getDrawable(com.android.internal.R.draw able.ic_lockscreen_target_activated);
...
So change icon ic_lockscreen_target_activated.png
Click to expand...
Click to collapse
The commit to the Git is here: https://github.com/IceColdJelly42/frameworks_base/commit/f1971285b709593873bf8c3effd144087b710104
Question: So far, i understand that i must replace the PNG in the system, but where would it reside? I dont think its in an APK as such, as its the system itself (though that could be apk's aswell...?). I was pointed to this tutorial that should have info on how to do it, but the guide refers to APK-filenames, and again, whats the APK filename? I have no APK in data/app or in system/app that matches "com.android.internal" - so im quite out of luck....?
Any advice on how to proceed is welcome. I have downloaded the PNGs attatched in the ZIP, from the source (git), those are the ones i want to replace with (they are all transparrent as they should be, for my project).
Kind Regards
TwinAdk

The image that you're looking for, is in "framework-res.apk\res\drawable-xhdpi.
When you have changed the image, push framework or copy/paste it in system\framework and reboot!
For security, make a nandroid backup

Okay, so framework-res.apk, and then follow the guide i linked to, and just mirror the structure of the folders in the apk (\res\drawable-xhdpi) - correct?
Or should i unpack the apk, replace pics, resign the apk and push instead?
Also, xhdpi, hdpi, etc.. Whats the difference except the size of the images (resolution)? Is it if i have a phone with lower res, i will need the lower res images?
Thanks so far!
EDIT: You made me laugh there sir..! ALWAYS a nandroid backup! Rather 10 useless backups, than one missing..! :victory:

TwinAdk said:
Okay, so framework-res.apk, and then follow the guide i linked to, and just mirror the structure of the folders in the apk (\res\drawable-xhdpi) - correct?
Or should i unpack the apk, replace pics, resign the apk and push instead?
Also, xhdpi, hdpi, etc.. Whats the difference except the size of the images (resolution)? Is it if i have a phone with lower res, i will need the lower res images?
Thanks so far!
Click to expand...
Click to collapse
With winrar or similar, open the apk, go to res\drawable-xhdpi and change image.
Now, you can push framework in rom and see results
I know that change only resolution of icons in that folder

Here you go. Push to /system/framework/ and set permissions.
Don't know if it will work 'cause I don't have ICJ flashed at the moment. Make a backup before trying it.
I had to compress it before uploading because the limit was 8mb.

Sv: [Q][THEME] Replacing PNG in system file
TToivanen said:
Here you go. Push to /system/framework/ and set permissions.
Don't know if it will work 'cause I don't have ICJ flashed at the moment. Make a backup before trying it.
I had to compress it before uploading because the limit was 8mb.
Click to expand...
Click to collapse
Wow, will try that! If it fails ill investigate tomorrow.
Kind Regards
TwinAdk
- Via the XDA app

Hello.
How can i push it to system/framework? I tried adb shell when in recovery, but i cannot access the framework folder.. /system/ nothing (only bin?)
Also, adb push gave this:
C:\fastboot>adb push framework-res.apk system/framework/framework-res.apk
failed to copy 'framework-res.apk' to 'system/framework/framework-res.apk': No s
uch file or directory
Click to expand...
Click to collapse
Output from shell, while in recovery (only place adb shell works, except from when the phone is booted, but i tried renaming the apk via a file explorer, the system crashed, lol).
~ # whoami
whoami
root
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 488.2M 48.0K 488.1M 0% /dev
/dev/block/mmcblk0p13
315.0M 5.2M 309.7M 2% /cache
Click to expand...
Click to collapse
Any advice?

Put / in front of system. It should be /system/framework/
Sent from my One X

adb works in android, not in recovery

Guich said:
adb works in android, not in recovery
Click to expand...
Click to collapse
It does work in recovery too. You should try it.
Sent from my One X

TToivanen said:
It does work in recovery too. You should try it.
Sent from my One X
Click to expand...
Click to collapse
Ill try to add / in recovery. When i did so in android, i got an error that the filesystem was read only.. I am rooted.
Update: It pushed correctly, but i only see that one file..... After reboot the file was not modified.. Verified with solid explorer.
ls while in recovery:
/system/framework # ls -lah
ls -lah
drwxrwxr-x 2 root root 0 Jan 29 20:28 .
drwxr-xr-x 4 root root 0 Jan 29 20:28 ..
-rw-rw-rw- 1 root root 8.6M Jan 29 16:09 framework-res.apk

Oh well, moved the apk with solid explorer, from sd to system/framework (overwrite exsisting) - phone is rebooting now..
UPDATE: Didnt boot up.. Trying to clear cache and dalvik, then well se.. Think ill have to revert to my dear nandroid

Well, damn it. I replaced the pngs with the files you provided, built and signed without an error. It should be OK but as I said I don't have ICJ installed so troubleshooting is a bit difficult.
Try to do it yourself with apktool.
Sent from my One X

Sv: [Q][THEME] Replacing PNG in system file
Will do. Your apk was considerably smaller than my original, also it struck me that you cannot have guessed my version of the custom rom, and thus the correct apk to use as source. I guess it is modified on each version?
Kind Regards
TwinAdk
- Via the XDA app

Hello.
I tried recreating the APK, using my own framework-res.apk as source.
I also found out how to push to system from CWM - you need to mount /system - DOH!
But it fails.... The phone never boots, i even chmodded the apk with 644, so the permissions are the correct ones..
Back to nandroid backup, and drawing table....
Anyone have any clue as to why the new apk failed? Followed this guide, and loaded the sources to UIsystem,apk and framework-res.apk before editing the APK.
When building the APK i got this output, and it does however not match the output in the guide - the "Could not find sources" does worry me a bit, should it..?

Found the reason for the "could not find sources":
A framework-res.apk is itself the source of other apks( when you install it - apktool if...). So the message that you got is normal.
Click to expand...
Click to collapse
Ref: http://forum.xda-developers.com/showpost.php?p=31832660&postcount=12

The .apk I started with was from 1.5.9 and it was 12mb in size.
Apks tend to lose weight when they are de/recompiled and that's why the finished product was only 8mb.
If the apk method fails, you could build the whole ROM yourself on a linux PC.
Keep me posted!
Sent from my One X

Well, though i used unix before, i dont wish to put the effort into building from source It seems building in a VM fails for many, and it requires quite alot of space...
My apk also lost weight, 8 mb after rebuild.. If the image is there, it does not matter what bitdepth and other fancy settings it was saved with, right? Aslong as the apk was build correctly, and chmodded correctly, the phoen should boot, right (and display an ugly image, if it wants - but at least boot!)

Did you sign the package?
Sent from my One X

No, according to the guide i followed:
Now, final step is signing the apk file.
Remember don't sign the apk if it's a SYSTEM app, unless you have edited the AndroidManifest.xml.
Click to expand...
Click to collapse
I suppose its a system app, as it resides in /system/framework...?