Database Info

request special splash screen

please, can someone give us hero rom splashscreen as haykuro hero rom ?
yes, new htc logo gif with little android saying bye bye

Here you have the splash
{
"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"
}
But we can't use the program "CreateG1Splash.exe" because converts it into a static file.

and how we can flash a animated splash screen then? the splash screen is fantastic!!

there's a boot.gif file in /system/media. This file is the second splash when android is starting up. I will probe to change it with this one.
It doesn't work. I've copied from roger rom to /system/media boot_configuration.xml, boot.mp3 and boot.gif but i still see the android animation

@ all,
I am on Rogers Rom and for me the above animated splash screen is working
Here are my steps:
Code:
adb remount
adb shell cp system/media/boot.gif /sdcard
adb shell rm -r system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
Enjoy it.
Regards
Puky70

Puky70 said:
@ all,
I am on Rogers Rom and for me the abovve animated splash screen is working
Here are my steps:
Code:
adb remount
adb shell cp system/media/boot.gif /sdcard
adb shell rm -r system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
in another site I found this but don't work too :
Rinominate l'immagine in boot.gif
Scaricate l'audio boot.mp3
Mettete i 2 file nella cartella tools dell'sdk
adb remount
adb push [boot.gif] /system/media
adb push [boot.mp3] /system/media
adb shell reboot
Tra le parentesi quadre mettete il percorso del file.
it's here : http://www.androidiani.com/forum/htc-magic-modding/1514-cambiare-secondo-splash-screen-magic.html
Enjoy it.
Regards
Puky70
Click to expand...
Click to collapse
this code doesn't work for me
when I put this "adb shell cp system/media/boot.gif /sdcard"
it says "cp not found"
any issue ? plz

hi,
you can find the path for cp and rm via:
> adb shell
# which cp
# which rm
for example in my rooted rogers rom:
>adb shell
# which cp
/system/xbin/cp
# which rm
/system/bin/rm
# exit
adb remount
adb shell /system/xbin/cp /system/media/boot.gif /sdcard
adb shell /system/bin/rm /system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
greetz

magic_munich said:
hi,
you can find the path for cp and rm via:
> adb shell
# which cp
# which rm
for example in my rooted rogers rom:
>adb shell
# which cp
/system/xbin/cp
# which rm
/system/bin/rm
# exit
adb remount
adb shell /system/xbin/cp /system/media/boot.gif /sdcard
adb shell /system/bin/rm /system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
greetz
Click to expand...
Click to collapse
why it's not working on my Vodafone magic?
I getting a "no such file" for the '/system/media/boot.gif'
?

the ion rom also seems to have no boot.gif in the system/media folder. i cant get a custom splash screen either...

DOH!
so my vodagroan magic with ION deffinatly cant have a custom animated boot up screen, darn it! i already changed the splash screen, would have been ace if i could have changed the boring ANDROID screen too. hopefully some smart bugger will save the day?!
JamesRead
HTC Magic
GoogleION (r2)
Rooted
OverClocked 527.3Mhz
Custom Splash
dxTop - Carbon Glow
HTC Dream
Haykuro 6.0.1H
Rooted
Overclocked 467.2Mhz
Custom Splash

I am having trouble find cp and rm. I issued #which cp and it comes up which: not found.

mack said:
I am having trouble find cp and rm. I issued #which cp and it comes up which: not found.
Click to expand...
Click to collapse
Those commands are busybox commands and you'll need to create links to the commands or try to type "busybox" before the commands :
busybox cp
busybox rm
If you installed busybox you can also create the needed links by entering : busybox --install -s , this will install the links into /data/local/bin

Has anyone found out where this is on the G1? I did a find and it came up blank.
I would love to have this on my G1, if anyone has an idea on how to do it.
Thanx!

Can anyone find this file in the Ion? I tried moving the copy of the boot splash that I saved onto my SD card into the /system/media folder using Astro and ADB, but no dice.

mack said:
I am having trouble find cp and rm. I issued #which cp and it comes up which: not found.
Click to expand...
Click to collapse
I did something similar ... all I did was grab the file from the phone to use as a backup:
Code:
adb pull /system/media/boot.gif boot.gif.orig
then put the new one in
Code:
adb push boot.gif /system/media/boot.gif
worked for me

Problems
Ok, Im not the greatest, but I like to think I have a grasp on whats going on here...
First, Im on a Dream running JACxHero 1.2 rom.
As far as adb, here's what Ive been doing:
adb remount
adb shell
rm -r /system/media/boot2.gif
ls /system/media (to make sure I took it away)
exit
adb push boot2.gif /system/media
ls /system/media (to make sure I got new one there)
exit
reboot
Well, I dont remember where I put the exit... but still, as you can tell, Im getting rid of, checking, replacing, and checking the boot2 gif. SHOULD be there.
Ok, so then it boots to Hero with the droids popping out, then the ORIGINAL boot 2 (wtfwtf), then jams up on the new gif I added.
SO, where is the original boot 2 lurking so that it keeps coming up after I rm'ed it??
Also, looking thru the XML, (Im not great with this, so slap me if Im wrong) it looks like boot 2 & 3's image sources are the same file?
form the xml:
"BootAnimation image="/system/media/boot.gif" image2="/system/media/boot2.gif" image3="/system/media/boot2.gif" loopimage="/system/media/boot2.gif" image_bg="/system/media/boot_bg.gif" audio="/system/media/boot.mp3" screenX="10" screenY="180" useAudio="1""
So, maybe if I change the bold portion to read "image3="/system/media/boot3.gif", and pushed a new boot3 image, it could run 3? Only issue I see is that it says to loop boot 2.......
Ideas?

Hummeroid said:
Ok, Im not the greatest, but I like to think I have a grasp on whats going on here...
First, Im on a Dream running JACxHero 1.2 rom.
As far as adb, here's what Ive been doing:
adb remount
adb shell
rm -r /system/media/boot2.gif
ls /system/media (to make sure I took it away)
exit
adb push boot2.gif /system/media
ls /system/media (to make sure I got new one there)
exit
reboot
Well, I dont remember where I put the exit... but still, as you can tell, Im getting rid of, checking, replacing, and checking the boot2 gif. SHOULD be there.
Ok, so then it boots to Hero with the droids popping out, then the ORIGINAL boot 2 (wtfwtf), then jams up on the new gif I added.
SO, where is the original boot 2 lurking so that it keeps coming up after I rm'ed it??
Also, looking thru the XML, (Im not great with this, so slap me if Im wrong) it looks like boot 2 & 3's image sources are the same file?
form the xml:
"BootAnimation image="/system/media/boot.gif" image2="/system/media/boot2.gif" image3="/system/media/boot2.gif" loopimage="/system/media/boot2.gif" image_bg="/system/media/boot_bg.gif" audio="/system/media/boot.mp3" screenX="10" screenY="180" useAudio="1""
So, maybe if I change the bold portion to read "image3="/system/media/boot3.gif", and pushed a new boot3 image, it could run 3? Only issue I see is that it says to loop boot 2.......
Ideas?
Click to expand...
Click to collapse
I wanted to do this before... but never seemed to work...
I would replace both gif's with my own... but it would be all staticky(if that's a word... haha...)...
I gave up because no matter what I did... it always ended up not working :/

bump
anyone have any new ideas. how to change from custom cyan image to this?

http://ostebaronen.dk/\
On here it states that ONLY HTC Branded magics can do animated boot screens, Mine will do it with a hero rom but i cant put my own on my 32B running cyanogenmod. I think cyanogen changed the bioot screen on his rom so maybe you need to talk to him?

bonesy said:
http://ostebaronen.dk/\
On here it states that ONLY HTC Branded magics can do animated boot screens, Mine will do it with a hero rom but i cant put my own on my 32B running cyanogenmod. I think cyanogen changed the bioot screen on his rom so maybe you need to talk to him?
Click to expand...
Click to collapse
Cyanogen made a hero build? News to me.
If he didnt, then yeah, he changed his, but thats not a gif. The Cyanogen I run definitely doesnt do gif ani boot screens

Sprint HTC Hero boot/splash screen (Sprint logo)

I'm terribly sorry for posting this, as I'm sure this has already been brought up - I remember finding it previously either on this page or elsewhere while looking for hacks for this phone.
However, after some searching just now, I can't seem to find that information again, so I'm hoping for some help finding information how to change that splash screen and any other information about it.
I know how annoying it is for regular forum members to see multiple posts on a subject, so please forgive me, I did search ahead of time.
Many thanks ahead of time for any assistance.
Cheers

Ahh, I found it.
Note, I have a US Sprint HTC Hero
For everyone who looks, all the bootscreen/splashscreen files are in the /system/media/bootscreen folder on your phone.
editing the boot_animation.xml file and replacing the sprint.gif (in my case since I have a sprint phone) changes the bootscreen - You can replace it with a standard gif or animated.

I've made changes to both files mentioned, but once I do the boot animation just seems to break and I have to restore them. Is there anything specific you are editing in the xml? I've updated the file name I replaced and have even just renamed my gif to one of the previous and it still doesn't work.
This is something I've been trying to get going for 3+ weeks now, any help is appreciated

N0J said:
I've made changes to both files mentioned, but once I do the boot animation just seems to break and I have to restore them. Is there anything specific you are editing in the xml? I've updated the file name I replaced and have even just renamed my gif to one of the previous and it still doesn't work.
This is something I've been trying to get going for 3+ weeks now, any help is appreciated
Click to expand...
Click to collapse
It doesn't support transparency. If you put a gif that has transparency in it as your boot gif then it will start to boot loop.

i need help with this. i cannot edit these files,i do have root access too, and a custom ROM.
please PM me short minimal detailed instructions, thanks

N0J said:
I've made changes to both files mentioned, but once I do the boot animation just seems to break and I have to restore them. Is there anything specific you are editing in the xml? I've updated the file name I replaced and have even just renamed my gif to one of the previous and it still doesn't work.
This is something I've been trying to get going for 3+ weeks now, any help is appreciated
Click to expand...
Click to collapse
This is what I did:
I copied the sprint.gif file from my phone to my local machine so I could edit in Photoshop.
I opened sprint.gif in PS and copied the layer dimensions so I would have the same size animated gif with anything I decided to edit.
I then found an animated gif that I liked and pasted it in PS with the same sized layers as the previous sprint.gif and saved it.
I saved my new animated gif as boot0.gif (i'm sure the name doesn't matter)
I then edited my boot_animation.xml. I commented out the orignal lines I didn't want (<-- --> are xml comments) and added a line for my boot0.gif. My boot0.gif line is the same as the orignal line for the sprint.gif because I just wanted to replace the stupid Sprint with my own.
After I had my two files (boot0.gif and my newly edited boot_animation.xml), I copied both files back into the /system/media/bootscreen/ folder and rebooted my phone.
It worked fine. The only thing off a little is the boot.mp3 and that's because my new boot0.gif doesn't have as many frames as the original sprint.gif. I'll probably just remove that .mp3 anyway.
I'm not sure why yours wouldn't work. My only thought would be if you did what I did - is that maybe the size of your .gif is too big, either in dimensions or file size. I tried to get my as close to sprint.gif as possible to avoid issues.
codelockdown said:
i need help with this. i cannot edit these files,i do have root access too, and a custom ROM.
please PM me short minimal detailed instructions, thanks
Click to expand...
Click to collapse
I have no experience with custom roms. I just rooted my phone yesterday and did the recovery image portion. I have yet to experiment with custom roms, but maybe that could be hindering you? I'm not sure.
Aside from that, the instructions I posted should work if you have root access. Did you try copying them out of the /system/media/bootscreen folder before editing? I'm not sure of the capabilities of the linux OS on this phone, so I didn't even bother trying editing directly from the terminal.
Good luck dude. Hope this helps

mrbrice said:
This is what I did:
I copied the sprint.gif file from my phone to my local machine so I could edit in Photoshop.
I opened sprint.gif in PS and copied the layer dimensions so I would have the same size animated gif with anything I decided to edit.
I then found an animated gif that I liked and pasted it in PS with the same sized layers as the previous sprint.gif and saved it.
I saved my new animated gif as boot0.gif (i'm sure the name doesn't matter)
I then edited my boot_animation.xml. I commented out the orignal lines I didn't want (<-- --> are xml comments) and added a line for my boot0.gif. My boot0.gif line is the same as the orignal line for the sprint.gif because I just wanted to replace the stupid Sprint with my own.
After I had my two files (boot0.gif and my newly edited boot_animation.xml), I copied both files back into the /system/media/bootscreen/ folder and rebooted my phone.
It worked fine. The only thing off a little is the boot.mp3 and that's because my new boot0.gif doesn't have as many frames as the original sprint.gif. I'll probably just remove that .mp3 anyway.
I'm not sure why yours wouldn't work. My only thought would be if you did what I did - is that maybe the size of your .gif is too big, either in dimensions or file size. I tried to get my as close to sprint.gif as possible to avoid issues.
I have no experience with custom roms. I just rooted my phone yesterday and did the recovery image portion. I have yet to experiment with custom roms, but maybe that could be hindering you? I'm not sure.
Aside from that, the instructions I posted should work if you have root access. Did you try copying them out of the /system/media/bootscreen folder before editing? I'm not sure of the capabilities of the linux OS on this phone, so I didn't even bother trying editing directly from the terminal.
Good luck dude. Hope this helps
Click to expand...
Click to collapse
i just made the howto thread, so just find it real quick, thank you anyway

custom bootscreen htc tattoo
i checked and also the htc tattoo does got /system/media/bootscreen whit the xml and files
i pulled /system/media/bootscreen/boot_animation.xml from my tattoo and removed it from my android?
what if i reboot whitout this xml or gif files?
what i want to try is just a console booting instead of splash screens.

rebooted
mmzz id just get the same old boot splash back on the device :|

I have gone into F:\system\media\bootscreen and i see the nexus 1 boot screen and the xml and the mp3 however I do not have these as boot screen. Is there a way to make them work. here is my xml info.
<?xml version="1.0" encoding="utf-8" ?>
- <!--
* Copyright (C) 2008 HTC Inc.
*
-->
- <!--
For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
image2="/system/media/bootscreen/boot2.gif" (optional)
image3="/system/media/bootscreen/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/bootscreen/boot_bg.gif" (optional)
useAudio="0" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
- <!-- For cropped version
-->
- <BootConfiguration>
<BootAnimation image="/system/media/bootscreen/boot1.gif" image2="/system/media/bootscreen/boot2.gif" loopimage="/system/media/bootscreen/boot2.gif" image_bg="/system/media/bootscreen/boot_bg.gif" audio="/system/media/bootscreen/boot.mp3" screenX="40" screenY="0" useAudio="0" />
</BootConfiguration>
- <!-- For full screen version
-->
- <!--
BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot1.gif"
image2="/system/media/bootscreen/boot2.gif"
loopimage="/system/media/bootscreen/boot2.gif"
audio="/system/media/bootscreen/boot.mp3"
useAudio="0"
/>
</BootConfiguration
-->

animal7296 said:
I have gone into F:\system\media\bootscreen and i see the nexus 1 boot screen and the xml and the mp3 however I do not have these as boot screen. Is there a way to make them work.
Click to expand...
Click to collapse
Should look something like this instead:
Code:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright (C) 2008 HTC Inc.
*
-->
<!-- For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
image2="/system/media/bootscreen/boot2.gif" (optional)
image3="/system/media/bootscreen/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/bootscreen/boot_bg.gif" (optional)
useAudio="0" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
[COLOR="Blue"]<!-- For cropped version -->
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot1.gif"
image2="/system/media/bootscreen/boot2.gif"
loopimage="/system/media/bootscreen/boot2.gif"
image_bg="/system/media/bootscreen/boot_bg.gif"
audio="/system/media/bootscreen/boot.mp3"
screenX="40"
screenY="0"
useAudio="0"
/>
</BootConfiguration>
[/COLOR]
<!-- For full screen version -->
<!--BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot1.gif"
image2="/system/media/bootscreen/boot2.gif"
loopimage="/system/media/bootscreen/boot2.gif"
audio="/system/media/bootscreen/boot.mp3"
useAudio="0"
/>
</BootConfiguration-->
And notice the highlighted text in blue -- this what will actually initiate the boot animation for the NEXUS One boot screen. And you should have five files: boot_bg.gif, boot_animation.xml, boot2.gif, boot1.gif, and boot.mp3

done
i sucessfuly rewritten boot1.gif and boot0.gif of the htc tattoo using the insmod tattoo-hack.ko of the next post.
rooting your tattoo
http://forum.xda-developers.com/showpost.php?p=5759184&postcount=317
Originally Posted by coolbits View Post
Reboot and do it all over... copy/paste line by line
adb push su /sdcard/ (for example, somewhere else from previous su)
adb shell
while do /data/local/bin/m7 ; done
/data/local/bin/su
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
insmod /data/local/bin/tattoo-hack.ko
mount -o rw,remount /dev/block/mtdblock5 /data
mount -o rw,remount /dev/block/mtdblock3 /system
cp -f /sdcard/su /system/bin/ (i did it with busybox)
reboot
worked for me...
rootexplorer also works...
Click to expand...
Click to collapse
so replace su whit boot0 tm 3.gif
#insmod /data/local/bin/tattoo-hack.ko
#mount -o rw,remount /dev/block/mtdblock5 /data
#mount -o rw,remount /dev/block/mtdblock3 /system
adb push boot0.gif or boot1.gif
and
#busybox cp -f /sdcard/boot0 t/m 3.gif /system/media/bootscreen/
get back to #
and reboot your htc tattoo

tattoo or other htc devices boot kernel booting question?
Is there a possible way to see your kernel booting instead of booting splash screens?

how would i change the htc white splash i tried the g1 way and all i got failed remote not allowed

thegod2012 said:
how would i change the htc white splash i tried the g1 way and all i got failed remote not allowed
Click to expand...
Click to collapse
coming soon
http://forum.xda-developers.com/showthread.php?t=759955

editing splash1
does anyone know the right way i placed the rgb565 file in desktop and i enter the fastboot flash splash1 C:\Users\oden\Desktop\mysplash.rgb565
i get back
sending 'splash1' <300KB>... FAILED <remote:not allow>
finished. total time: 0.001s

i keep getting the same thing as thegod2012 i am unrevoked not sure whats wrong

hero32 said:
i keep getting the same thing as thegod2012 i am unrevoked not sure whats wrong
Click to expand...
Click to collapse
Awesome someone who knows how to use the search button
-not being sarcastic here, its practically the only way you'd find a thread that was last posted in on Aug 16
Anyway...did you flash the engineering SPL/s-off bootloader? It's required if you want to flash a splash screen.
Check out both the s-off link and this one HERE <-- tehdarkknight's guide on how to flash a custom flash

[GUIDE] change bootanimation w/S-OFF & root AND how to create one

How to replace the stock boot animation with a custom boot animation:
1. rename the extension of the current bootanimation in system/customize/resource to .bak (just skip this if you never want to use it anymore)
For unbranded phones this is bootanimation.zip
branded phones have bootanimation.zip as well as a boot and a down/shutdown animation from the provider.
Vodafone:
VF_bootanimation.zip
VF_downanimation.zip
TMOUS:
TMOUS_bootanimation.zip
TMOUS_downanimation.zip
You only need to replace the two VF_ or TMOUS_ files. As far as I know the normal bootanimation.zip is there but not used for anything for branded phones.
2. rename your bootanimation to what the bootanimation on your device is called. Copy the file to system/customize/resource with root explorer
3. in root explorer hold your finger on the file till the menu pops up. Tap on "permissions"
Owner: read & write checked, execute unchecked
Group: read checked, rest unchecked
Others: read checked, rest unchecked
4. restart and you're done!
How to create your own boot animation:
1. create a folder called "android" and place the frames of your animation in that folder in PNG format.
2. name them as follows:
NAME_01.png
NAME_02.png
...
NAME_xx.png
3. create a text file called "desc.txt" containing for example:
540 960 15
p 1 1 android
explanation of the desc file:
Width Height Frame-rate
p Loop Pause Folder
width: width of your animation
height: height of your animation
frame-rate: how many frames to be shown per second. If your animation has 30frames and you enter 10 then one replay takes 3 seconds
p: just stands for play, don't alter this, just put it there.
Loop: how often to loop the animation before pausing on the last frame. If you enter 0 it will loop indefinitely until the device is done booting. 1 will play the animation once, 2 twice etc.
Pause: For how many frames to pause the animation after every loop. The actual pause time depends on the frame-rate you chose above. For example a pause of 90 with 10 fps will translate to a 9 second pause
Folder: the name of the folder we created above.
4. add the desc.txt and the folder with your png files to an uncompressed zip file
You can do this with 7zip. Right click the files, 7zip -> add to archive -> for "compression level" select "store"
5. sign the zip
not sure if this is necessary although I simply sign everything that goes into my system folders. You can use ZipSigner from the market. (For "key/mode" select "platform")
Here are some qHD HTC quietly brilliant bootanimations that I made for good measure.
blue, dark blue background, qHD
{
"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"
}
green, black background, qHD
blue, black background, qHD

followed every step to the letter not sure how or with what to create a text file so took one from another bootanimation but still not working for me blanc screen.

Can you make me one with green HTC letters? Thanks in advance.

Did anyone notice in the T-mobile Sensation there is a TMOUS_bootanimation.zip, bootanimation.zip, TMOUSdownanimation.zip & a downanimation.zip all in this folder? Which one are we replacing?
There is also a T-jingle.ogg & a writeon_jingle.wav file. Would those be the boot up & shutdown sounds?

Beast84 said:
Did anyone notice in the T-mobile Sensation there is a TMOUS_bootanimation.zip, bootanimation.zip, TMOUSdownanimation.zip & a downanimation.zip all in this folder? Which one are we replacing?
There is also a T-jingle.ogg & a writeon_jingle.wav file. Would those be the boot up & shutdown sounds?
Click to expand...
Click to collapse
Following another guide, what worked for me was, changing bootanimation.zip to bootanimation.zip.bak and then pasting the bootanimation.zip you want to be your new splash screen.
Then, renaming that to the TMOUS_bootanimation.zip
So in the end that's the one you want to replace.
Sent from my HTC Sensation 4G using XDA App

There you go mate!
green, qHD, black background:
[Edit: moved to first post for cleanliness]
@gilbert11231123 you must have either added compression to the .zip or made a mistake with the desc.txt or didn't sign the zip correctly or some other thing. Can't tell from here, sorry!

Beast84 said:
Did anyone notice in the T-mobile Sensation there is a TMOUS_bootanimation.zip, bootanimation.zip, TMOUSdownanimation.zip & a downanimation.zip all in this folder? Which one are we replacing?
There is also a T-jingle.ogg & a writeon_jingle.wav file. Would those be the boot up & shutdown sounds?
Click to expand...
Click to collapse
I have a Vodafone branded Sensation. I only have to replace the VF_bootanimation.zip and VF_downanimation.zip ... I replaced the bootanimation.zip as well but it was not necessary.
the VF_downanimation.zip shows when shutting the phone down. VF_bootanimation.zip shows when booting.
Edit:
here is also a clean blue one with black background. The one in first post has a dark blue background and the "quietly brilliant" is also somewhat blue.
[Edit: moved to first post for cleanliness]

Ok so I tried making on but it didn't quite work. I tried using it for the TMOUS_bootanimation.zip & the TMOUS_downanimation.zip
For the bootanimation, it was just a blank black screen. For the downanimation, it was correct but it had a quick white flash in it. I was wondering if anyone could take a look at what I did & modify it for me. Thanks in advance

Beast84 said:
Ok so I tried making on but it didn't quite work. I tried using it for the TMOUS_bootanimation.zip & the TMOUS_downanimation.zip
For the bootanimation, it was just a blank black screen. For the downanimation, it was correct but it had a quick white flash in it. I was wondering if anyone could take a look at what I did & modify it for me. Thanks in advance
Click to expand...
Click to collapse
your .zip is definitely not signed or it would have a META-INF folder in it. Also, in your desc.txt you have a blank line after the first line. That probably screws things up as well. Lastly, your .zip does also seem to have compression so it doesn't seem like you did anything I described above
Oh and about the white flash - Image 11 is transparent on top and has a white stripe and image 13 is almost entirely white. Suppose that is your white flash
for the shutdown animation android seems to be more loose on restrictions. When I had the compression wrong the downanimation also worked for me but the bootanimation didn't even though it was the same file!

Kupfel said:
your .zip is definitely not signed or it would have a META-INF folder in it. Also, in your desc.txt you have a blank line after the first line. That probably screws things up as well. Lastly, your .zip does also seem to have compression so it doesn't seem like you did anything I described above
Oh and about the white flash - Image 11 is transparent on top and has a white stripe and image 13 is almost entirely white. Suppose that is your white flash
for the shutdown animation android seems to be more loose on restrictions. When I had the compression wrong the downanimation also worked for me but the bootanimation didn't even though it was the same file!
Click to expand...
Click to collapse
Just tried doing it again & this time they switched. The bootanimation had the white flashing screen & the downanimation had a blank black screen. I don't know what I am doing. Think you could whip something up for me with my provided zip earlier?

here is my chaotic thing I did to get it working.
Since root explorer costs so much $$$$. I rebootified in recovery via 'adb reboot recovery'
D:\sdk>cd platform-tools
D:\sdk\platform-tools>adb push bootanimationBB.zip /system/customize/resource
145 KB/s (458475 bytes in 3.082s)
D:\sdk\platform-tools>adb shell
~ # cd /system/customize/resource
cd /system/customize/resource
/system/customize/resource # ls boo*
ls boo*
bootanimation.zip bootanimationBB.zip
/system/customize/resource # ls TMO*
ls TMO*
TMOUS_bootanimation.zip TMOUS_downanimation.zip
/system/customize/resource # ls -l TMO*
ls -l TMO*
-rw-r--r-- 1 root root 869055 May 23 04:06 TMOUS_bootanimation.zip
-rw-r--r-- 1 root root 365229 May 23 04:06 TMOUS_downanimation.zip
/system/customize/resource # mv TMOUS_bootanimation.zip TMOUS_bootanimation.zip.
bak
mv TMOUS_bootanimation.zip TMOUS_bootanimation.zip.
bak
/system/customize/resource # mv TMOUS_downanimation.zip TMOUS_downanimation.zip.
bak
mv TMOUS_downanimation.zip TMOUS_downanimation.zip.
bak
/system/customize/resource # cp bootanimationBB.zip TMOUS_bootanimation.zip
cp bootanimationBB.zip TMOUS_bootanimation.zip
/system/customize/resource # cp bootanimationBB.zip TMOUS_downanimation.zip
cp bootanimationBB.zip TMOUS_downanimation.zip
/system/customize/resource # chmod 644 TMOUS_bootanimation.zip
chmod 644 TMOUS_bootanimation.zip
/system/customize/resource # chmod 644 TMOUS_downanimation.zip
chmod 644 TMOUS_downanimation.zip
/system/customize/resource #
D:\sdk\platform-tools>
I hope you learned something... lol.

WoW man... worked like a charm... chose your Green with Black animation...
looks great... and the procedure to do it cannot be more simpler than you explained...
wonderful...
Thanks +1

Any advice on how to change the boot sound to go along with the animation? The other walkthrough guide references things that don't exist (init.local.rc) on the Sensation. The guide was in the Desire HD forum (I think).

never added a boot sound myself but after asking brother google it seems android doesn't support playing boot sounds as it is. One or more system files have to be altered to get boot sound support such as bootanimation in system/bin ..
http://androidforums.com/liquid0624/234917-gingerbread-bootani-sound.html
that's the first page I found. It says it's for gingerbread but I'd choose not to replace system files unless I'm sure they work on sensation

Kupfel said:
There you go mate!
green, qHD, black background:
[Edit: moved to first post for cleanliness]
Thanks.
Click to expand...
Click to collapse

Hi again,
Could you make this one or one like this one but in qHD?
Thanks in advance.

uhm isn't that exactly like the one I made for you already?

Forget about that. I've another already. Thanks anyway.

I don't really care about the boot animation, but I'd love to get rid of the nasty sound it makes during booting
wakes up everyone in the office and attracts unwanted attention too
at least I could change it from "quietly brilliant" to "loud but ok"

I think I'm gonna try and make my own boot animation but have a few questions about the desc fle-
1. How do u know what to put for the frame rate? I see OP put 10 but what does that mean..? 10 frames per second or what?
2. For loop OP put 0, so does that mean it plays it once, 1 loop would play twice, 2 loop play 3 times etc...?
3. For pause OP put 90? what does that represent like is that 90 ms? How'd you pick that?
4. What did you use to make the images?
Thanks for anyone that can help and for the great guide OP.

[Q] Nexus S voice/sound recorder hidden and not installed?

Hi,i was searching for the stock voice recorder in Ice Cream Sandwich,but i did not find it...
So I've searched into phone memory (root /system/app) and i found Soundrecorde.apk ,bu if i try to install it,installation aborts saying "This application cannot be installed".
Why?

No one use voice recording on Ics?
Neo on Nexus S with Tapatalk®

bump?.......

.:Crack:. said:
bump?.......
Click to expand...
Click to collapse
???
Neo on Nexus S with Tapatalk®

..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
There is not much compatibility for this kind of apps and Ics...
Stock Sound recorder was perfect for me on Gingerbread,i don't understand why it's not compatible anymore...
Neo on Nexus S with Tapatalk®

not sure how you tried to install but you cant install system apps like other apk you have to sign it first....anyways i signed it and installed fine but dont give an option to open after install and still don't see it
edit
just for future reference if you edit an apk or want to install a system app like a normal apk
download Sighnapktic from the market its free and it does it right from your phone really easy to use
https://market.android.com/details?id=com.stericson.signapktic&hl=en

i used Sanity with gingerbread, but I don't know if it still works with ICS
https://market.android.com/details?..._result#?t=W251bGwsMSwxLDEsImNyaS5zYW5pdHkiXQ..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.

XK72 said:
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.
Click to expand...
Click to collapse
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®

..

(THE REAL) Neo said:
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
{
"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"
}
Correct.
Election Day said:
Probably yes. I'm trying to modify the xml's at the moment, but I can't get any usable output.
If I can get it to work I'll post the modded apk here.
Click to expand...
Click to collapse
Directly after this line:
Code:
<action android:name="android.intent.action.MAIN" />
Add:
Code:
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />

..

You also just can use anycut from market and create a homescreen shortcut to soundrecorder.apk

Election Day said:
I guess this should be it. I unpacked the apk with apktool, added the lines, packed it again, unzipped it, added META-INF and rezipped it.
You can flash it with "adb push SoundRecorder.zip /system/app".
Click to expand...
Click to collapse
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®

(THE REAL) Neo said:
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®

jitzbox said:
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied
Click to expand...
Click to collapse
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
(THE REAL) Neo said:
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.

XK72 said:
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.
Click to expand...
Click to collapse
Using this apk,the phone shows me an app called "Recorder" in the app drawer,but i can't tap it,and all the icons showed in the same page of the app drawer.If i change page,icons of other pages are selectable...weird thing...
Now i'm rolled back to previous apk file and everything works...so scary...
Neo on Nexus S with Tapatalk®

BlueStacks Beta 4/3 ROOTED & Play Store Guide

SEE POST 3 FOR ROOT GUIDE
Below you will find the neccesary steps needed to get Google Play to run on BlueStacks Beta
1. Install Root Explore (can be downloaded for free using bluestacks and typing in the app name)
2. Download the Vending.apk and Google Framework from this post.
http://www.androidfilehost.com/main/Misc/Bluestack/
3. Copy them to /data/bst
4. Give them these Permissions
(rwxr-xr-x) or through adb:
Code:
adb shell chmod 755 /data/bst/vending.apk
adb shell chmod 755 /data/bst/googleservicesframework.apk
Click to expand...
Click to collapse
{
"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"
}
5. Reboot Bluestacks
6. Download ADW Launcher if you haven't (this is not a requirement but it helps as if you already have Google Play in your PC you just find it through /data/windowsdata)
7. Find Google Play and sign in with your email and password.
Step by Step Guide on how to get into root.fs and mount the system.img
Click Here
The programs that are listed in the tutorial can also be found on my site here:
http://www.androidfilehost.com/main/Misc/Bluestack/
Along with those programs you will find all the tools,apks, installers you will need to get the market on Bluestacks Beta along with the tools to modify its files.

Lost, Confused, Cant get the Market to run with the instructions above?
Alternative Way-UPDATED 4/2/2012 :
I have uploaded a modified root.fs to my site for you to download
I added the the market per the instructions in the tutorial on the blog.
Steps:
Download the root.fs and overwrite the current root.fs on your computer.
Location:
C:\ProgramData\BlueStacks\Android
Make sure to stop all instances of BlueStacks before overwriting the file. Also Please Please make a backup of your original root.fs before overwriting the file with the modified one.
Once you have copied over the new root.fs start Bluestacks and wait for it to load up.
Congrats you have the newest Market running on BlueStacks.
You might need to install ADW Launcher inorder to see the Play Store/Market. It doesnt show up in the bluestacks launcher
Files can be downloaded from here:
http://www.androidfilehost.com/main/Misc/Bluestack/
------------------------------------------------------------------------
Was going to post my own guide but someone beat me to it.
Here a guide on some of the Registry Tweaks
http://droidhackings.blogspot.com/2012/03/some-useful-registry-tweaks-to-optimize.html

---Rooting BlueStacks Beta---
DOWNLOAD LIST (assuming you already have BlueStacks installed):
Code:
1. initrd-betahack.img ***INCLUDED***
2. ramdisk.img ***INCLUDED***
3. system.img-----------------NOT INCLUDED!!!
4. su.x86 ***INCLUDED***
5. BlueRegistryMOD ***INCLUDED***
--------------------------------------------------------------------------------------------------
Download from Here:
http://www.androidfilehost.com/main/Misc/Bluestack/Rooting BlueStacks Beta/
Code:
These are the custom files needed for root and r/w
-initrd-betahack.img
-ramdisk.img
-system.img
-su.x86
FILE: initrd-betahack.img
-From Beta (modified)
-Place it in \%programdata%\BlueStacks\Android\
FILE: ramdisk.img
-From Mod-V3.zip alpha
-Place it in \%programdata%\BlueStacks\Android\
FILE: system.img
-Extracted from xRepinsSporsx Root.fs (for Google Play)
Or
-Extracted from latest BlueStacks Root.fs
-Place it in \%programdata%\BlueStacks\Android\
FILE: su.x86
-From Androidx86 build (extracted from rooted alpha)
-This is the x86 superuser binary that auto-grants superuser-rights
***This file will be pushed to android using adb later on***
-------------------------------------------------------------------------------------------------
Code:
These files are the stock Beta files and remain in place
-kernel.elf
-Data.fs
-Prebundled.fs
-SDCard.fs
FILE: kernel.elf, Data.fs, Prebundled.fs, SDCard.fs
-From Beta
-Placed in \%programdata%\BlueStacks\Android\
---------------------------------------------------------------------------------------
Changes that need to be made to the registry are contained in BlueRegistryMOD.reg
FILE: BlueRegistryMOD.reg
***WARNING***
YOU MUST ENTER YOUR SPECIFIC USER ID BEFORE RUNNING BlueRegistryMOD.reg !!!
Where the registry key says ENTER-YOUR-GUID-HERE you need to enter the number (with dashes) found here:
FIND YOUR SPECIFIC GUID HERE!!!
[HKEY_CURRENT_USER\Software\BlueStacks]
“USER_GUID”=”SOME-NUMBERS-HERE”
Example of a GUID:
“USER_GUID”=”8dfcb602-4b7d-11e1-9dc9-f3dea6cb4293”
Example of a modified “BootParameters” with correct GUID and changes made to mount /system:
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android]
"BootParameters"="root=/dev/sda1 SRC=/android DATA=/dev/sdc1 SDCARD=/dev/sdd1 GUID=8dfcb602-4b7d-11e1-9dc9-f3dea6cb4293 armApps=true GlMode=1 OEM=BlueStacks "
***ENTER-YOUR-GUID-HERE must be changed in 2(two) places in BlueRegistryMOD.reg***
-------------------------------------------------------------------------------------------
THIS IS THE PROCESS:
***Make sure to exit BlueStacks before proceeding***
1. Paying attention to the guidelines above, place the following files in their correct location – this includes initrd-betahack.img, ramdisk.img, and system.img.
2. After finding your GUID and making the appropriate changes to BlueRegistryMOD.reg in 2(two) places, run the registry file.
3. Start/restart BlueStacks – go to the Start menu>type Start Bluestacks
4. Start adb on your computer
a. Connect to bluestacks - #adb connect 127.0.0.1:5555
b. Ensure you have root access - #adb root
i. You should get message: “adbd is already running as root”
c. Mount system as read/write - #adb remount
d. Remove ‘dummy’ superuser - #adb shell rm /system/xbin/su
e. Push x86 superuser to BlueStacks - #adb push su.x86 /system/xbin/su
i. su.x86 must be in the same Windows directory you are running in the console
f. Correct the permissions for superuser - #adb shell chmod 6711 /system/xbin/su
g. Remount system read only - #adb shell mount -o ro,remount t-ext4 /dev/sdb1 /system
h. Exit adb by closing the console window
5. Restart BlueStacks – go to the Start menu>type Start BlueStacks
6. At this point you should have root and read/write access.
a. Verify root using a tool like Root Check. I suggest Root Check Pro because it will point you to what the problem is if you do NOT have root.
b. Verify read/write access using a tool like Root Explorer.
7. Enjoy.
***This is a sure-fire way to get root and read/write access. However, I find that there are still issues with GAPPS (gmail, calendar specifically)
Download from here:
http://www.androidfilehost.com/main/Misc/Bluestack/Rooting BlueStacks Beta/
Extended system.img
http://www.androidfilehost.com/main/Misc/Bluestack/Extended system.img/

Thank you!
works perfect! Great!

Can not mount r/w system, any idea, is it possible ???

I used the alternative method - with the "root.fs"
that was perfect!
I would like to get the bluestacks-alpha-fullscreen again - without the suggested apps bar etc.
Any idea?
Thanks again,
Sascha

Stapelmeister said:
I used the alternative method - with the "root.fs"
that was perfect!
I would like to get the bluestacks-alpha-fullscreen again - without the suggested apps bar etc.
Any idea?
Thanks again,
Sascha
Click to expand...
Click to collapse
We cant get the whole bar to go away yet. im still experimenting with that. I can make it black but not 100% gone.

milniko said:
Can not mount r/w system, any idea, is it possible ???
Click to expand...
Click to collapse
It is not possible yet. Still working on it

imisa2 said:
Get Maximum out of your BlueStacks Beta, Some useful Registry Hacks, tips and tricks Here:
droidhackings.blogspot.com
Click to expand...
Click to collapse
Well frick lol Was just posting my tutorial/guide on how to do those things. you beat me to it.
MOD-Please combine last 3 Posts.
Sorry

@Repin
I went through the Mod-V3.exe that chevy uploaded for the alpha build that enables r/w access to sytem.
The main changes I saw involved system.img, init-hack.img, ramdisk.img, and registry hacks.
-The registry hacks are fairly self-explanatory, except that now there is a need for a /sde1 to allow for the PrebundledApps.fs
-We already have a good system.img with Superuser to use in place of Root.fs in the /Bluestacks/Android/ folder.
-I tore into the alpha initrd.img and compared it to the alpha initrd-hack.img. The only difference inside both initrd.img and initrd-hack.img was a bash script named init. After a comparison of the scripts I found the point where the initrd-hack init script sets up the /system for r/w access. I then compared the alpha init script and init-hack script with the beta init. The only difference between the alpha init script and the beta init script is that the beta script has two extra 'insmod' entries for HD that the alphs does not. So, I made the same changes to the beta init script that are in the alpha init-hack script to enable /system with r/w. ****I'm not sure how to repackage initrd.img with my modified init script so that we can replace the original***
-The only thing I am unsure of is ramdisk.img. My question to chevy is "Did you make any modifications to ramdisk.img contained in the Mod-V3.zip that was uploaded for the alpha build?"
Sent from my BlueStacks using XDA
(Edited for spelling)

What is wrong ???
Unpack original initrd.img:
mv initrd.img initrd.gz
gunzip initrd.gz
mkdir tmp
cd tmp
cpio -id < ../initrd
Archiving without any change:
find . -depth -print | cpio -o >../initrd
cd ../
gzip initrd.gz
mv initrd.gz initrd.img
The new cpio file initrd.img does not work, even no change ???

@milniko
Exactly. I need a way to repackage initrd.img with the new init script but I don't know how.
Sent from my Droid using XDA

Can you send me the new init script. ill try and repackage it

i have ubuntu in vmware and it very simple:
rename to gz
extract the file inside
copy and past this file in vmware ubuntu from windows
when i have this file on ubuntu i extract this file in a folder
edit the file of my interest in this folder
and for repack i use this when i'm inside the folder:
find . | cpio -o -H newc | gzip > ../initrd.gz
in the final i rename initrd.gz in initrd.img
p.s.
the same thisnks for the ramdisk.img

Blue Stack Help
Hello all, How are you
Thanks for help to root, but i've question
Once I Install Blue Stack, I Get automatically downloading some applications like pulse, Talk... etc . I can not cancel those applications.
Please how to cancel all this applications to download and install automatically.
How can I Manage Start up Items, and What Thnkgs that I Can Remove after Rooting Blue Stack. Thank you
Thanks

imisa2 said:
Try this:
Click to expand...
Click to collapse
Would you mind quoting the post you are responding to next time? It helps keep the thread organized. Additionally, please stop "spamming" the link to your website and simply link to the post in which you originally shared it.
My apologies if I sound like a **** for bringing it up. I assure you it isn't my intention.
We all appreciate your having put together a site with tutorials on it! Very helpful for those looking to play with BlueStacks.

Modified init for initrd.img
This is the edited init file found in initrd.img in Bluestacks Beta. Rename the stock beta initrd.img to initrd.bak. The init file is easily read in Notepad++.
The changes that were made reflect the same changes made in the alpha init that allows for r/w access. Specifically, the changes made are in the part where Androidx86 detection takes place. The script mounts /dev/sdb1 to /mnt and then moves /mnt to /android/system.
This init assumes that the following changes have been made to the Bluestacks Beta filesystem:
-The moddified init file has been repacked into initrd-hack.img. Place it in the \%programdata%\BlueStacks\Android\ folder.
-try the ramdisk.img from Mod-V3.zip alpha as /sda1. Place it in the \%programdata%\BlueStacks\Android\ folder.
-xRepinsSporx system.img file with superuser is to be used as /sdb1. Place it in the \%programdata%\BlueStacks\Android\ folder.
-the beta Data.fs is to be used as /sdc1
-the beta SDCard.fs is to be used at /sdd1
---------------------------------------------------------------------------------------
Changes that need to be made to the registry are:
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android]
"BootParameters"="root=/dev/sda1 SRC=/android DATA=/dev/sdc1 SDCARD=/dev/sdd1 GUID= OEM=BlueStacks"
"Initrd"="C:\\ProgramData\\BlueStacks\\Android\\initrd-hack.img"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\0]
"Name"="sda1"
"Path"="C:\\ProgramData\\BlueStacks\\Android\\ramdisk.img"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\1]
"Name"="sdb1"
"Path"="C:\\ProgramData\\BlueStacks\\android\\system.img"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\2]
"Name"="sdc1"
"Path"="C:\\ProgramData\\BlueStacks\\Android\\Data.fs"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\3]
"Name"="sdd1"
"Path"="C:\\ProgramData\\BlueStacks\\Android\\SDCard.fs"
*** Also, “DisableRobustness” in [HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android] may need to be changed from “0” to “1” ***

zulu99;24242353
and for repack i use this when i'm inside the folder:
find . | cpio -o -H newc | gzip > ../initrd.gz
in the final i rename initrd.gz in initrd.img
[/QUOTE said:
Still does'n work for me, please share initrd.img if it works for you
Thank you
Click to expand...
Click to collapse

i can repack, but the method of tenet24 not work.
the file is this:
http://www.2shared.com/file/wm2Wcqsa/initrd-hack.html
p.s.
i used the system.img inside the original Root.fs->system.sfs and the ramdisk.img of modv3
if i put this 3 files in other folder and correct the regedit to this other folder, the bluestacks hangs on a black screen, after this with hd-adb.exe i can connect to the virtual android and i can remount in rw the /system folder, but the gui of bluestacks not work. i think the ramdisk.img is not good, we can repack also this.

@zulu99
Can you post any debug or logs from when the GUI wont load? Check the Bluestacks folder for their log, and try to use adb to get the last ten lines or so of debug.
Thanks.
Sent from my Droid using XDA