Database Info

Extra Mod for Haykuro's H Users...

I was messing around with one of my update files on winrar and opened system/Media. There I found boot.gif and boot.mp3 which both play at start up with the htc logo and sound. So I decided to change both with my own. So I did then I signed the update zip and flashed. Worked like a charm, sorry if someone beat me to this if you guys already knew then ill just delete the thread.
How To:
1. You must have a copy of the build/rom you are using. You can use the last update.zip you've used to flash to your latest rom.
2. Open up the update zip file using winrar or whatever unzipping tool you use.
3. Once unzipped goto system/Media.
4. Here you will see two files boot.gif and boot.mp3 these are the files you are going to mod.
5. Editing boot.gif, find a replacement animated gif file you would like to use and rename to boot.gif and add it to the archive replacing the original. MUST BE A .GIF FILE ONLY!
6. Editing boot.mp3, you do the same procedure as step 5 but replace with a mp3 file. MUST BE AN MP3 FILE ONLY!
7. When finished put the update.zip you just edited place on the root of sd card and flashhhh!
8. HAVE FUN!
Alternative with adb without wipe thanks to: Andonnguyen
adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#mv c:\locationoffile\boot.gif /system/media/boot.gif
#mv c:\locationoffile\boot.mp3 /system/media/boot.mp3
#reboot
{
"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"
}
​
Could not add the boot.mp3 but here it is the linux mandriva boot sound.
link to boot sound here:
http://www.zedge.net/ringtones/567398/mandriva-startup-ringtone/

Nice find! Too bad I just got everything set up the way I like it. I'll probably be flashing again on "Firmware Friday." I'll try this out then!
I've got about a million ideas for what I want my phone to do when I turn it on....

Yea its great, I currently have an android dancing gif instead of the htc and Pitbull I know you want me for the boot sound lol. I put it on just to test and now that I know it works, I will also be changing it to something sick on firmware Friday...

There is One big problem
How you sign your update ...
When I used auto sign to signed my mod ... I have a error in recovery mode

aluspl said:
There is One big problem
How you sign your update ...
When I used auto sign to signed my mod ... I have a error in recovery mode
Click to expand...
Click to collapse
Which auto signer are you using? I suggest using Stericson's also make sure your singing the whole update.zip

So this really does work?

i may try this for the next update as well, good find

Anyway you can make a how to or point me to the direction of this information?

Nikeem24 said:
So this really does work?
Click to expand...
Click to collapse
Yup, i've tested and it works.

As an alternative method (for those who don't want to wipe), modify the boot.gif and boot.mp3 then place them somewhere on your hard drive. Next type the following commands in ADB while your G1 is connected via USB to your computer:
adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#cp c:\locationoffile\boot.gif /system/media/boot.gif
#cp c:\locationoffile\boot.mp3 /system/media/boot.mp3
#reboot
Click to expand...
Click to collapse
STERICSON (or anyone familiar with editing the xml files on android), please read below:
In the H builds of 1.5, there is also an xml file called boot_animation.xml in /system/media, the contents are as follows:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright (C) 2008 HTC Inc.
*
-->
<!--
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
image2="/system/media/boot2.gif" (optional)
image3="/system/media/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/boot_bg.gif" (optional)
useAudio="0" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
<!-- Demonstrates configuration for application -->
<!-- Remove background
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
image_bg="/system/media/boot_bg.gif"
audio="/system/media/boot.mp3"
screenX="100"
screenY="130"
useAudio="1"
/>
</BootConfiguration>
-->
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
useAudio="1"
/>
</BootConfiguration>
Click to expand...
Click to collapse
It looks as if we can manage to load multiple animated gif's during the boot process after splash1 and splash2 images. Could you please look into this, and offer any input as how to modify the xml to allow this?

Ok it seems as if the boot gif when changed gets disorted now for some reason, will look into it.

andonnguyen said:
STERICSON (or anyone familiar with editing the xml files on android), please read below:
In the H builds of 1.5, there is also an xml file called boot_animation.xml in /system/media, the contents are as follows:
Click to expand...
Click to collapse
Well the first 2 BootConfiguration tags have been commented out. To comment in xml you type <!-- before your comment and --> after your comment.
Try removing the comment code on the first BootConfiguration and adding comments to the last one. also make sure to remove the (optional), then upload the images using your adb method and see if it works.
Below i cleaned the code up a bit. So you can copy that into your xml.
Also I changed the useAudio to 1 which means yes.
Code:
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
image2="/system/media/boot2.gif"
image3="/system/media/boot3.gif"
screenX="100"
screenY="130"
image_bg = "/system/media/boot_bg.gif"
useAudio="1"
/>
</BootConfiguration>
This is the last BootConfiguration in the xml. The middle one is just a demonstration. I wouldn't delete it though, Android might be expecting a certain file size.
Below is the current active BootConfig which i added the comment tag around.
Code:
<!--
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
useAudio="1"
/>
</BootConfiguration>
-->

So is there anywhere, where there are already made boot screens that i can just get the file and replace it

Jrbourque said:
So is there anywhere, where there are already made boot screens that i can just get the file and replace it
Click to expand...
Click to collapse
Yes search google for any gif files and just replace, same for the boot sound. I know have a cool setup ill upload now.

diaztradeinc said:
Yes search google for any gif files and just replace, same for the boot sound. I know have a cool setup ill upload now.
Click to expand...
Click to collapse
does it have to be a certain size?

Jrbourque said:
does it have to be a certain size?
Click to expand...
Click to collapse
I'm thinking the gif might have to be a certain size because my recent boot gif is distorted when animating. Check first page for boot gif and boot.mp3

adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#mv c:\locationoffile\boot.gif /system/media/boot.gif
#mv c:\locationoffile\boot.mp3 /system/media/boot.mp3
#reboot
Click to expand...
Click to collapse
^^Not working for me; i keep getting the error msg "failed on 'C:\boot.gif' - No such file or directory"
And yes, my boot.gif file is saved in the C:\ directory.
Perhaps it needs to be saved on the sdcard to work? i'll try it and report back.
Edit: SUCCESS. I placed my modified boot.gif and boot.mp3 files on the sdcard, then used the following commands:
adb remount
adb shell
#cd /system
#cd /media
#rm boot.gif
#rm boot.mp3
#cp /sdcard/files/boot.gif /system/media/boot.gif
#cp /sdcard/files/boot.mp3 /system/media/boot.mp3
#reboot
Click to expand...
Click to collapse
And now my man John Stewart (the black Green Lantern... not the Comedy Central host) greets me to the tune of Kanye West's "WE MAJOR".

diaztradeinc said:
I'm thinking the gif might have to be a certain size because my recent boot gif is distorted when animating. Check first page for boot gif and boot.mp3
Click to expand...
Click to collapse
So you're having the same problem I am then? I analyzed the CRAP out of the original boot.gif, and compared it to a customer animated gif I attempted to completely customize my bootup w/ to no avail. I even modified the original boot.gif trying to place text and extra graphics on the existing frames, saved, and the modified version of the boot.gif glitched out too.
So as a test (since I'd only been trying to run modified/created animated gifs after about 3-4 hours of analyzing trying to figure out the difference) I replaced the boot.gif w/ a regular animated gif.
The boot automatically centers the gif (in this case it's not the 320x480 scale of the original boot.gif)... but it's still distoreted. Here are some pictures as an example
this gif -
doesn't animate at all. appears to show 3 different frames all glitched out and looks like this -
Any light anyone can shed on this would be greatly appreciated =( I'd absolutely love to customize my OWN animated gif for my boot image.

what size is it suppose to be?

Transformer Sound Effect
You wouldn't believe how hard it is to find the Transformer sound effect from the 2007 Movie. I finally gave up and used this one here. I kept the stock HTC.gif (H build) because it's timed right with the sound. Just thought I'd post in case anyone else had the same idea. If anyone finds a clean morph fx file, pm me.

[TUT] Change the leo splash screen (first screen after boot)

You just run in dos mode the nbimg 1.1 tool of pof from here
http://forum.xda-developers.com/showthread.php?t=405118
and you put the following parameters:
nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000
Flash the nbh file that is created ( i attach a sample in zip file ready for flashing) and you done it.You only flash the boot image, i mean the one that has the number of radio and rom at the bottom, and nothing else, radio and rom remain unchanged.Follow exactly the commands (capitals or not capital letters).
There is another image that appears just before the image that has the number of rom and radio.This can be changed if you replace the 601 with 600 in the parameters described above (tip goes to Chri55tof in post 2).
So you just need 2 bmp photos 480x800 24bit and the pof nbimg1.1 tool with the parameters i described above, piece of cake.
If you dont like it returm to the stock splash attached below.
Enjoy

Downloaded the file (from link you provided), made a 24bit .bmp file I wanted to use ... followed the command line, flashed to my HD2 and it works !!
Great job !
K.
EDIT :
By the way, flashing .nbh file done that way will replace 2nd splash screen. How to replace first screen ? (the one with white background and green htc trademark) ???
EDIT2 :
Just found it !
0x600 is changing 1st splash screen
0x601 is changing second (not like you stated in topic of this thread !)

What you mean ?
The second screen is the animation which is an animated gif file.
-T is the header type.
I attach the kind of settings:
Mandatory arguments:
-F <filename> Filename to convert.
If the extension is BMP it will be converted to NB.
If the extension is NB it will be converted to BMP.
Optional arguments:
-w <width> Image width in pixels. If not specified will be autodetected.
-h <height> Image height in pixels. If not specified will be autodetected.
-t <pattern> Manually specify the padding pattern (usually 0 or 255).
-p <size> Manually specify the padding size.
-n Do not add HTC splash signature to NB file.
-s Output smartphone format.
NBH arguments: (only when converting from BMP to NBH)
-D <model_id> Generate NBH with specified Model ID (mandatory)
-S <chunksize> NBH SignMaxChunkSize (64 or 1024)
-T <type> NBH header type, this is typically 0x600 or 0x601Example to convert a NB to BMP:

I mean `the very first screen`
This is the one with white BG and green `htc` trademark (the one before `reds` coming out)
0x600 is responsible to change this
0x600 next splash screen

Hi,
Q: So the second one is the animated one?? I'm talking about that one with 'quietly brilliant' ? It comes with the sound - how to change this sound?

pepesz said:
Hi,
Q: So the second one is the animated one?? I'm talking about that one with 'quietly brilliant' ? It comes with the sound - how to change this sound?
Click to expand...
Click to collapse
The sound is the HTC-QuietlyBrilliantBoot.wav in windows folder and the original animated gif (LEO_animated.gif) also in windows folder is attached
Read here
http://forum.xda-developers.com/showthread.php?t=625911

Thanks a lot

0x600 changes Carrier Bitmap (1)
0x601 changes Welcomehead (2)
Animation (3)

chri55tof said:
0x600 changes Carrier Bitmap (1)
0x601 changes Welcomehead (2)
Animation (3)
Click to expand...
Click to collapse
You dont have to do the procedure for changing the welcomehead,bmp because you just replace directly in windows file or cook the bmp file.
The 1st screen with the red letters at the bottom with radio and rom numbers needs to be flashed as is the only way to replace it.

My little contribution ^^
Enjoy !

NIKOSXRI said:
You just run in dos mode the nbimg 1.1 tool of pof from here
http://forum.xda-developers.com/showthread.php?t=405118
and you put the following parameters:
nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000
Flash the nbh file that is created ( i attach a sample in zip file ready for flashing) and you done it.You only flash the boot image, i mean the one that has the number of radio and rom at the bottom, and nothing else, radio and rom remain unchanged.Follow exactly the commands (capitals or not capital letters).
So you just need a bmp photo 480x800 24bit and the pof nbimg1.1 tool with the parameters i described above, piece of cake.
If you dont like it returm to the stock splash attached below.
Enjoy
Click to expand...
Click to collapse
Once I enter the command lines, it says "could not open "picture name".bmp? Am I missing something?

daleandla said:
Once I enter the command lines, it says "could not open "picture name".bmp? Am I missing something?
Click to expand...
Click to collapse
Check again and follow the command line exactly

My Contribution
NIKOSXRI said:
Check again and follow the command line exactly
Click to expand...
Click to collapse
Boom baby. Got it. Here's my contribution...

How do change from second splash screen. (Not the first screen or bios animation)

technomania34 said:
How do change from second splash screen. (Not the first screen or bios animation)
Click to expand...
Click to collapse
You change the welcomehead.png in Operator Pkg, 480x800 24 bits per pixel.
I attach a sample picture which you may use.

is there anyone that has the original 2nd splash bmp file or as a nbh file?
Found it

NIKOSXRI said:
You change the welcomehead.png in Operator Pkg, 480x800 24 bits per pixel.
I attach a sample picture which you may use.
Click to expand...
Click to collapse
Thanks mate

why isn't this or a link to this thread (or similar) in the sticky/wiki at the top?

A word of warning. when you create and flash a splashscreen using the 0x601 memory location, it is not removed when you flash a stock rom. (Tested with several stock roms)
Stock splashscreens are flashed to the 0x600 memory location, and shows for 14 seconds. 7 Seconds when teh phone boots, and 7 seconds when the RGD info shows.
When you have a second splash in place, it shows the first splash for 7 seconds, then the second splash when the RGD info shows for 7 seconds.
The implications of this are that if you need to send back your phone, and you flash a stock rom, your custom second splash will still show.
To remove it (well, make it look like it was gone) I had to make a duplicate of the stock splash and flash it to the 0x601 location, so that it looks like one long splash. (As i found out when i had to return mine to o2.)
More reading

[1st boot & 2nd splash ]
4 HD2 Leo :: choose your BMP shot for it
HERE

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

Getting image out of splash.img

OK. This is a bit embarrassing. I created a splash screen 2 years ago from scratch. But, I didn't keep the original image I used to make it. I have the splash.img. I want to extract the original image from it. Can someone share the method of doing this? Thank you.

First youll have to re add the extention .nb at the end of the file. For example splash.img is kade to splash.img.nb then you Just reverse the command you used to convert to to a splash image
So instead of nbimg -F splash.bmp etc
You'll use nbimg -f splash.img.nb etc

marsdta said:
First youll have to re add the extention .nb at the end of the file. For example splash.img is kade to splash.img.nb then you Just reverse the command you used to convert to to a splash image
So instead of nbimg -F splash.bmp etc
You'll use nbimg -f splash.nb etc
Click to expand...
Click to collapse
Thanks! I tried that before, but I didn't know I had to add .nb extension to it first. I appreciate your help.

[CLOSED][SCRIPT][LINUX] Mount System as read write (Android 10+)

This Linux-only version is pretty much deprecated at this point. Please use the BRAND NEW UNIVERSAL VERSION instead! Thank you.
Ladies and gentlemen. Let me present to you my very first release here at the XDA forums:
Welcome to:
makeSystemRW v1.04
automated bash script by lebigmac for Android 10 and above​Creation date: February 2021
Updated: March 2021
Requirements:​
LINUX ONLY!
Android 10 or newer
This version only supports devices with super image.
Check if you have super by running ls -Alg /dev/block/by-name
phone must be rooted + bootloader unlocked + 10 GB free space on phone
at least 20 GB free space on computer for dumping data
adb and fastboot commands should be in your $PATH environment variable
I'm not 100% sure if this is a necessary requirement but I also disabled dm-verity and verification on my device just in case by simply booting into TWRP and then executing these 2 commands:
Code:
adb disable-verity
adb shell avbctl disable-verification
Description: A script for all Android power users that wish to make their read-only Android 10+ system read-write-able again to remove bloatware and make more thorough customizations to their device.
In a nutshell this is what the script is doing:
dumps your existing super image to your pc
extracts the embedded read-only partitions (system, vendor, product, etc...)
makes these partitions read-write-able
joins everything back together to new flashable super.img
flashes it to device
User data is not affected.
Usage: Simply call the script from the shell.
Optional arguments (replace x with your custom value) :
in=x : With this flag you can specify an existing super.img and skip the entire dumping of the super image process. Here you can use the super_original.img which you dumped earlier with makesysrw or the official super.img from your downloaded firmware. You probably have to unsparse the official super.img first using the included simg2img tool for superunpack to recognize it properly. If omitted, makesysrw will dump super image from phone to ./super_original.img
out=x : With this argument you can specify the output path. If omitted, default output value is ./super_fixed.img
size=x : With this parameter you can specify the extra free space (in megabytes) that will be added to each partition. If omitted, default extra size is 0 (shrink to minimum)
Examples:
Code:
# Run this command if you're first time user:
# Specify the extra free space in megabytes for each partition:
./makesysrw.sh size=100
# Plug an existing raw super image into the script like this:
./makesysrw.sh in=./super_original_raw.img size=100
# Specify both the input file as well as the output destination:
./makesysrw.sh in=./super_original_raw.img out=./super_fixed.img size=100
# For unsparsing the (sparse) super.img from your phone manufacturer's firmware you can do:
./tools/bin/simg2img ./super_sparse.img ./super_raw.img
NOTE: I did not come up with all this by myself. After searching for a solution for countless days without success, going even as far as learning hex editing - I coincidentally came across a couple of very interesting threads burried deep inside the new forum interface where this technique has been described and discussed by various enthousiasts (links can be found below in the credits section). So I take absolutely no credit for the underlying core mechanisms of the script. I'm only the amateur who put it all together into a compact script so that everybody can enjoy an Android system that's read-write-able again. Just like it used to be in Android 9 or earlier. Before this annoying 'shared_blocks feature' was implemented.
Credits: Big thanks to @munjeni for allowing me to use his amazing superunpack tool instead of the default lpunpack. Source code can be found here.
Also big thanks to @Brepro1 without your awesome tutorial guiding me I couldn't have created this script.
Thanks @AndyYan your interesting thread also helped me a lot for automating the script especially the lpdump part.
More thanks @gabrielfrias for his helpful comment
Thanks @YOisuPU and of course @topjohnwu for discovering the 'shared_blocks feature'
Thanks @bynarie for making available his otatools package! A part of it is now bundled with the archive
Disclaimer: This is open source software and is provided as is without any kind of warranty or support whatsoever. By using and viewing this software you agree to the following terms:
Under no circumstances shall the author be held responsible for any damages or negative consequences that may arrise from the (inappropriate) use of this software.
All responsibility and liability lies with the end-user. You hereby agree not to abuse this software for illegal purposes. Use this software at your own risk!
Please feel free to improve this script as you see fit (as long as you don't add anything malicious)
and make sure to post your feedback, suggestions and improvements in the official thread right here.
{
"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"
}
Mod Edit: Download link removed
Please click my like button below if you like it! Thanks​

It would be very helpful if you guys could please give me some feedback if the script works for you.
Which device are you using?
Your Android version?
Did you disable dm-verity and verification before running the script?
Your suggestions to enhance the script. Remember this is only version 1.0
Thanks!
@thor_1979

Great work! Your donation to the developers community is awesome.
The script works perfectly.
Consider keeping going.

Are you serious it actually works on your device? lmao
Congratulations. You are the first person to try it
The script pretty much does the same thing as your awesome tutorial describes.
Without your tutorial this script would not exist so thank you very much for making it available!

How do I use it? I'm really wanting to make my system rw again and this is perfect but how do I use it? It's a tar and Xz?

Simply extract the downloaded archive and open a terminal shell in the extracted folder by right clicking inside it and select Open in Terminal
Then run this command if you're running it for the first time
Code:
./makesysrw.sh size=100
or this command if you already have your raw super.img file
Code:
./makesysrw.sh in=./existing_super_image.img size=100
If you can't launch the script file make sure it is executable on your computer.

I really don't understand how this works why do you need the storage space is it making a system img that you than flash? I thought it just makes the current system read writable so you can install and uninstall system apps.

lebigmac said:
Simply extract the downloaded archive and open a terminal shell in the extracted folder by right clicking inside it and select Open in Terminal
Then run this command if you're running it for the first time
Code:
./makesysrw.sh
or this command if you already have your super.img file
Code:
./makesysrw.sh existing_super_image.img
If you can't launch the script file make sure it is executable on your computer.
Click to expand...
Click to collapse
Thanks I'm supposed to run the shell from my pc terminal or on the android device?

Sorry I see its for linux users. Ok now im getting it I have ubuntu 14 on my hard drive but I need to reinstall the grub menu because I deleted it or something. I have a s10 lite and tab S6 I would love to make the writable on the system so does this make a backup or dump of your system and than you flash it? Do you guys think thatll work on one ui 2.5 and im on lineage 18.1 on my s10 lite

Well in a nutshell this is what the script is doing:
dumps your existing super image to your pc
extracts the embedded read-only partitions (system, vendor, product, etc...)
makes these partitions read-write-able
joins everything back together to new flashable super.img
flashes it to device
User data is not affected.
The script is telling you exactly what's happening under the hood. You can also check out the source code if you have any doubts.
Yes this version of the script is supposed to be run on a Linux computer.
Please report back if it works for you or not.
Lineage OS? Doesn't that have a read-write-able system by default? In that case the script will likely fail.
Please keep in mind this script has been developed on Android 10 (Xiaomi X3 NFC) with a system that's read-only.

lebigmac said:
Well in a nutshell the script dumps your existing super image to your pc.
And then modifies the files to make everything read write able and then flashes back to the device. User data is not affected.
The script is telling you exactly what's happening under the hood. You can also check out the source code if you have any doubts.
Yes the script is supposed to be run on the computer
Please report back if it works for you or not.
Lineage OS? Doesn't that already come with read-write-able system by default? In that case the script will likely fail.
Please keep in mind this script has been developped on Android 10 MIUI 12 (Xiaomi X3 NFC) with a system that's read-only and embedded in a super image.
Click to expand...
Click to collapse
Honestly Im not a 100 percent sure anymore. I know it's a super img and it's really different in twrp there's a ton of new partitions and you have to wipe it off completely to flash a new system. I really haven't dug to deep into everything because I know that S6 oneui isn't writable and actually upset me because it's not like having full root access anymore.

For Windows users with TWRP.
(This is more like a reference)
From adb shell inside twrp.
X = Partition. To find out what block partition is mounted at, mount it in twrp then run 'df -h'.
e2fsck -f /dev/block/dm-x
resize2fs /dev/block/dm-x 3G
e2fsck -E unshare_blocks /dev/block/dm-x
Now reboot to fastbootd and execute:
fastboot resize-logical-partition <partition_slot> $((3*1024*1024*1024))

Thank you for the script.
When I read that I could use it with the super.img I guessed the usage was like
./makesysrw.sh image.img super_edited.img
I have a linux partition, but on a remote server and I was hoping to use it on the file and get my edited file from the server without putting the phone in the server..
Let me knowif you add something like that(-i and -o flags will be useful)
Best

Lossyx said:
For Windows users with TWRP.
(This is more like a reference)
From adb shell inside twrp.
X = Partition. To find out what block partition is mounted at, mount it in twrp then run 'df -h'.
e2fsck -f /dev/block/dm-x
resize2fs /dev/block/dm-x 3G
e2fsck -E unshare_blocks /dev/block/dm-x
Now reboot to fastbootd and execute:
fastboot resize-logical-partition <partition_slot> $((3*1024*1024*1024))
Click to expand...
Click to collapse
As much as I wish for a solution to be available to our fellow Windows users,
unfortunately your suggestion doesn't work here on my device see screenshot below.

lebigmac said:
As much as I wish for a solution to be available to our fellow Windows users,
unfortunately your suggestion doesn't work here on my device see screenshow below.
View attachment 5236719
Click to expand...
Click to collapse
Yeah. These dynamic partitions are weird, because for some reason I only managed to do this on slot A. And only did it on the vendor partition.
Also, this is the reference i was going by;
https://twitter.com/i/web/status/1260577424418488324

lebigmac said:
As much as I wish for a solution to be available to our fellow Windows users,
unfortunately your suggestion doesn't work here on my device see screenshow below.
View attachment 5236719
Click to expand...
Click to collapse
I think the problem is that you are requesting too large amount of memory try to replace 3G with smaller amount of memory

If anybody is good with creating flashable zips contact me! Need help working on universal version right now which will also be compatible with Windows and Mac users!
I am only amateur so need a real pro to give me some assistance here. Thank you.

Redmi note 9 pro. EU 12.0.2 rom. Android 10. It works. I installed WMware Workstation on a virtual machine in Windows. Thanks.(Google translate, sorry)

I can confirm that it works pềctly on my Pixel 4 XL Android 11 (coral-rq2a.210305.006) and Android 10 (coral-qq3a.200805.001), thank you for your awesome hard work!

Tried it on my Oneplus 7T Pro with Android 10. It extracted the superimage but failed at writing it back. It returned this error:
Code:
error: file_write: write: No space left on device
lpmake E 03-02 21:41:55 76867 76867 images.cpp:468] [liblp]sparse_file_write failed with code: -1
lpmake E 03-02 21:41:55 76867 76867 images.cpp:326] [liblp]Could not open image for partition: product_a
makesysrw: Error! failed to create super_fixed.img file./makesysrw.sh super_image.img 14.21s user 37.28s system 51% cpu 1:40.46 total
Any ideas? Thank you for your great work!