Database Develop

[HOW TO] [ROOT] [S-OFF] Change boot logo (skateboards, not boot animation)

DISCLAIMER:
1) You are doing this at your own risk.
2) Educate yourself first and try this ONLY if you feel comfortable with modifying with your phone.
3) If you break your phone it is not my fault nor is it my responsibility to fix your phone.
Things could go wrong but they shouldn't if you follow the directions and have some general knowledge of Android.
##############################
Go from this:-------------------------------------------------To This:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----------
##############################
Things needed:
ADB/Fastboot knowledge - HERE and HERE
RGB565Converter v0.3c - Thanks to DeToX-cz!
UPDATE: You must have the engineering bootloader flashed for access to splash1. Follow the steps here to flash the S=OFF bootloader. -Thanks to jcase
Instructions:
Find an or create an image (.png, .bmp, .jpg, or .gif -- 320x480 is preferrable)
Open RGB565 Converter
Ensure that "To RGB565 (binary)" tab is selected
Click "Open Image", select your image
Click "Convert to RGB565" (RGB565 Converter will make your image 320x480 if it is not already)
CLOSE RGB565 CONVERTER
Reboot phone into Fastboot using this command: adb reboot bootloader
OR Button combo: SEND/CALL + END/POWER
Flash image using this command: fastboot flash splash1 <your_image_name>.rgb565
Reboot phone using this command: fastboot reboot
OR fastboot oem powerdown if not then remove your battery
View the results of your hard work.
Enjoy!

As of right now there is no way to read the splash1 partition to back it up short of some kind of kernel mod to partition splash1 from NAND as a new MTD. At least that's how I understand it, please correct me if I'm wrong.
You must flash the S-OFF BOOTLOADER for this to work.
You can use the RGB565Converter tool to flash your image successfully without needing to type commands.
Below is another method used to keep your phone from rebooting unexpectedly during the process:
joshw0000 said:
I tried using the "Flash Splash1" button that someone had posted earlier and I almost **** myself. I think my phone tried to load the file I originally used to root it. I was getting really nervous so I pulled the battery and, to my relief, it powered on and it booted normally. I'm sure that method works but I'm scared of it now.
I tried the original instructions and it rebooted my phone before I was ready so I did this in the command prompt (this was mentioned on the first page of posts):
cd C:\android-sdk-windows\tools
adb shell
su
reboot bootloader
fastboot flash splash1 <copy and paste file name here>
fastboot reboot
Of course this will only work if you've downloaded the program, converted your picture and placed it in the tools directory of SDK.
Worked great for me. I couldn't be happier!
Click to expand...
Click to collapse

didnt seem to work for me, but im not rooted, ill try this with my brothers rooted phone in a bit and repioret back

Wow that worked great! Thanks

Reboot phone into Fastboot (Power down, hold Send press and hold Power)
Click to expand...
Click to collapse
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?

ch4sethe5un said:
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
Click to expand...
Click to collapse
no, Hold Call button and end button to get into fastboot
and this is ONLY FOR ROOTED PHONES
thanks

thanks i will try it out. Im using ivan's 0.7

Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.

ch4sethe5un said:
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
Click to expand...
Click to collapse
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.

there should be an option to go to HBOOT menu and then into recovery and reboot from there.
I used this one:

Great tutorial. Thanks!
Here's mine if someone likes it they are free to use it.

+1 rep (if only we could do that). I was looking for something like this. Thanks!

t2noob said:
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
Click to expand...
Click to collapse
I did a battery pull myself too lazy to go into recovery from hboot. My phone did not explode after doing a battery pull so it "should" be safe however do so with caution.

moved thread by request of OP.
Best regards,
Flar

Ive learned that battery pull is the easyiest way,

As a fan of FFXIII, I could not pass up the opportunity to do this.
[Taking Requests also ]

Maybe we should come up with a thread so people can post all boot images and animations in one place, no?
Just remember to convert it like mentioned in the first post
Here is one(as a fan =] ):

Was just thinking about changing and found this. Thanks.

Awesome!!!
Thanks for the tutorial.

Worked great!

[BootAnimation] *Updated* Retro Boot Animation for ICS 4.0

Newly updated Retro boot animation for 4.0 ICS
Hope you like it.
{
"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"
}
To install:
Just rename the downloaded file and rename to bootanimation.zip and copy it to /data/local/ on the XOOM – no root required with this method.
http://www.mediafire.com/?q071ix8is858md0

Awesome! I've been waiting for this since I have this animation on my Desire Z.
Seems slightly laggy on the last few seconds, don't know if thats because it's loading or the animation.
I can see a split second of a white bar sometimes too at the bottom. Don't know how to replicate it though.

Perfect!! Thanks

Nice work, do you mind if I add your version to the big thread? We are still missing a Xoom version there
greetz

Yeah that's alright

I've been running this boot anim since you released it and I GREATLY appreciate the updates. It's the little things, you know..

STAT1 said:
I've been running this boot anim since you released it and I GREATLY appreciate the updates. It's the little things, you know..
Click to expand...
Click to collapse
Thanks, I'm glad you like it. However the original boot animation is not my own. I simply updated it.

Hi I can't move it do the data/local folder... U say that we don't need to be rooted but how can I move it? I'm not rooted
Thanks

Are you getting an error message or does it just sit there? If it just sits there, try using 'Copy' Instead of using 'Move'

I tried with Honeycomb file manager HD and Astro both using move or copy but I can't paste it in data/local they dont give me the option

So... how can I install it? Do I have to root?
Sent from my Nexus S using XDA App

Thanks, that's great. Now I feel like I need to power my Xoom off more often

Thanks for this boot animation! No doubt all my friends are going to download this when I show them, haha

Mastaiso said:
So... how can I install it? Do I have to root?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Sorry for the late response. I guess in order to install the boot animation you need to use adb.
I've never been in your position as i have root. This is what I've found.
I am not responsible if you brick your device.
How to Install Using ADB
1. Download the boot animation file
2. Rename to bootanimation.zip
3. Copy to your "Tools" folder that contains adb commands
4. Open Command Prompt and enter the command below
Code:
adb push bootanimation.zip /data/local
Then to test:
Code:
adb shell bootanimation
I’ve confirmed that you do NOT need to be rooted to change your boot animation, although you will only be able to do so using ADB. To install a non-developers version of ADB, follow the instructions here: Setting up ADB on Windows 7 64 bit (and other Windows platforms)
To return to the stock boot animation, just remove or rename the .zip in /data/local and the system will default back to the stock one in /system/media provided you have not changed it in there.
If you feel the need to save the current bootanimation.zip file in that folder, then before copying over it, use this command to pull it into your SDK /tools folder, rename it, then copy the new one into the tools folder and push it onto the Xoom using the following command:
Code:
adb pull /system/media/bootanimation.zip bootanimation.zip
******************************** If you place one of the boot animations on your Xoom, then reboot and your device gets stuck in a boot loop, your file may be corrupted or something isn't quite right. Find a working boot animation in these forums and use the following commands to push them onto your Xoom via ADB. (It will save you having to re-flash your Xoom like I did the first time it happened to me.)
Code:
adb devices adb push bootanimation.zip /data/local
Click to expand...
Click to collapse

I love this retro boot screen. Can you update it for 3.2?

needs 3.2 update !

blinking char
I love this bootanimation... but if you're updating it to 3.2... can I also make a request? how about a small square like character (like █ ) blinking in the bottom of the screen like old school loading from DOS? it would add just another image and keeping looping the current last one and this one with the square character, showing that XOOM is still alive when the boot is slow (like when updating and/or cleaning cache/dalvik cache...)
tks!

needs 4.0.4 update

Sk8er Boi said:
needs 4.0.4 update
Click to expand...
Click to collapse
+1
Sent from my Xoom using xda premium

I'll get right on that.
edit*
I hope you lot dont mind it simply being 4.0. These rom versions are change so quickly.

[DEV][TOOLS] Unpack Repack boot.img (Kernel) Files And Modify Ramdisk

Hello!
This is -at least I hope it is- an easy to follow guide on how to unpack boot.img files (aka custom kernels) and modify the ramdisk.
Now, why would you want to do that?
First and simplest thing that comes to mind is for editing the kernel boot logo (the one that appears before the boot animation).
There are also a lot of other things you can edit in the ramdisk, but they require a bit more advanced knowledge, so we won't talk about them here.
Requirements:
1. Linux (any form will do, for example virtual box etc)
2. Perl (already included in Ubuntu, me thinks)
3. The Xperia Boot Tools package attached in this post
4. The mkbootimg binary (I already compiled it for Linux x86 and included it in the attachment)
5. Reading this post VERY VERY VERY carefully
Step 1: The mkbootimg binary
Let's install mkbootimg (we need it in order to repack the boot.img).
In a terminal window, cd to the directory where you extracted the mkbootimg file and type:
Code:
[B][I]sudo cp mkbootimg /bin/[/I][/B]
And then
Code:
[B][I]sudo chmod 755 /bin/mkbootimg[/I][/B]
Done!
* After first command, terminal will ask for your user password, type it, press enter and the command will be executed immediately.
Step 2: Splitting the boot.img
At this point, we need a boot.img file to play with.
Pick your favorite custom kernel and get the .img.
Place it in a folder along with the 2 perl scripts from the attached package.
In a terminal window, cd to the above-mentioned folder.
Next, type this command:
Code:
[B][I]perl split_bootimg.pl boot.img[/I][/B]
The command will return something like this:
Page size: 2048 (0x00000800)
Kernel size: 3132176 (0x002fcb10)
Ramdisk size: 3484496 (0x00352b50)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Now the kernel is successfully extracted to your current directory.
It consists of 2 files: boot.img-kernel and boot.img-ramdisk.gz.
Step 3: Unpacking ramdisk
So we unvealed the ramdisk in our previous step but it is still of no use to us, so we need to un-gzip and then un-cpio it.
In the same terminal window as before, type:
Code:
[I][B]mkdir ramdisk[/B]
Code:
[B]cd ramdisk[/B]
Code:
[B]gzip -dc ../boot.img-ramdisk.gz | cpio -i[/B][/I]
Last command will return something like:
10503 blocks
Our ramdisk is unpacked now in the newly created /ramdisk folder.
Step 4: Editing ramdisk files
Now you can edit the contents of the ramdisk.
BE EXTREMELY CAREFUL AND NEVER EVER DO ANYTHING "JUST 'CAUSE"...
You need to be fully aware of what you're doing.
Good news is, changing the logo.rle (the static boot logo image) is fairly easy.
You just need to replace it with your .rle file.
I am not going to explain how to make your own .rle files right now.
Feel free to have a look at this thread for more info.
However, I attach the stock SE boot logo in case anyone misses it when he's on custom kernel.
IMPORTANT: Don't accidentally add irrelevant files to the ramdisk directory as cpio will include them too and your new boot.img will be useless.
Also, bear in mind:
DooMLoRD said:
there is a bug in the semc S1 bootloader... sometimes if the boot.img isnt of a correct size then the device will not boot... the workaround is to add a "filler" file (which is say 512KB file with junk data) to the ramdisk so as to increase the size of the final boot.img file...
thanks to jerpelea for this incredible tip... i must have wasted atleast 10-15 hrs trying to figure out why my kernel failed to boot
Click to expand...
Click to collapse
Step 5: Repack the ramdisk
Now that's all done, we need to pack the kernel back up into a flashable img file.
First, we will pack the ramdisk back to it's original state.
In the same terminal window as before, type:
Code:
[B][I]find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz[/I][/B]
Step 6: Repack the boot.img
In our last step, back into the terminal we go to use the "repack-bootimg" perl script that will give us our brand new boot.img.
Make sure to cd to the directory that the perl scripts are, much like in Step 1.
Type this command:
Code:
[B][I]perl repack-bootimg.pl '/.../.../.../boot.img-kernel' '/.../.../.../ramdisk' newboot.img[/I][/B]
Of course, replace /.../.../ with the path to the boot.img-kernel file and the ramdisk directory respectively.
All done! Your new img is newboot.img and is ready to be flashed!
ADVICE: Use fastboot boot and not fastboot flash boot the first time, to test that the new kernel boots. If all is well, proceed with the actual flashing!
FAQ:
- Can I do this on Windows?
- Not that I know of, no. You can use Vmware or VirtualBox to install a raw Ubuntu image (pure command line) on your Windows PC though.
- Great! How can I do this then?
- Wish I knew! I have a Linux partition on my PC, it has been like that forever. Google is your friend!
- This is so complicated, is there an easier way? Can you make a zip for me to use in recovery?
-
{
"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"
}
- OK, don't get upset. Can you do it for me?
- I will have to say no, because I know that the minute word gets out that I take requests, I will be overwhelmed.
Took me several hours to figure all this out but it will take you less than 10 minutes to do it yourself if you carefully follow the instructions.
- I think this or that is wrong and it should be like this or that.
- Thank you very much for correcting me! I am still learning! Please post your corrections here or PM me and I will update the thread ASAP!
References:
- HOWTO: Unpack, Edit, and Re-Pack Boot Images
- How to Port Android to Another Device
- [How-To] Make custom bootscreen/bootlogo (image to rle)/(rle to image)
Thanks to:
- Riyal for giving me the idea to get into this.
- pvyParts because without him I'd only be "pulling Irises"...
Cheers!

Thank you very much. I've been looking for something like this.
Anyways, use VirtualBox instead of VMware. It's a thousand times better.

or try pendrivelinux,boot linux from windows..great tutorial,gonna try it
so everyone can be doomlord
question,if i manage to change boot image and repack the it back,is there any chance for me to "brick" the kernel?
Sent from my LT18i

Locked Bootloader
Hello Iridaki,
many thanks for your apports (this and the init.d script). I'm actually user from a Spanish forum called www.htcmania.com (you may have heard about thedr0idboy, which is a Neo developer) and we were trying to pack kernels in order to flash it in locked bootloader devices or at least try to create an Overclock module for stock kernel that can be flashed in locked devices.
Do you think we can use this to achieve this goal? I just hate Arc S with it's damn 1.4 GHz processor :S. It was released only a month after I got my Arc.
Many thanks for your time and your efforts!!
P.D: a girl developer!!!

rashid.fairus said:
so everyone can be doomlord
question,if i manage to change boot image and repack the it back,is there any chance for me to "brick" the kernel?
Click to expand...
Click to collapse
Nah, it takes a lot more to be DoomLord..!!!
If there are no errors in the cmd, boot.img should be OK.
By using flashboot boot command, the kernel is sent to the phone and it tries to boot it. It's not flashing it, so if it fails, it immediately goes back to previous kernel.
So don't worry! Imagine that until I found the correct script, I had tried more or less 10 crapernels (crappy kernels)!!!
iR¡[email protected]!* via Tapatalk

iridaki said:
Nah, it takes a lot more to be DoomLord..!!!
If there are no errors in the cmd, boot.img should be OK.
By using flashboot boot command, the kernel is sent to the phone and it tries to boot it. It's not flashing it, so if it fails, it immediately goes back to previous kernel.
So don't worry! Imagine that until I found the correct script, I had tried more or less 10 crapernels (crappy kernels)!!!
iR¡[email protected]!* via Tapatalk
Click to expand...
Click to collapse
looks like our themes and apps forum have a new section,kernel theming,,(iridaki,you have purple theme for apps and roms,how about kernel?)
Sent from my LT18i

A big thanks, iridaki!
I was looking forward to such thread.
I did also a lot of search on google too, but somehow I couldn't find any match.
I am an experienced Linux user, so that shouldn't be a problem for me.
I'll try everything this weekend.
Afaik, CWM is also stored in the kernel, so is it possible to modify it with the tool?
I don't want to have a step by step guide, just a reference would be great (of course if you know one).
Anyway, thanks for your great contributions in XDA.
Sent from my LT18i using xda premium

OMG... :-o Iris you are a genius.
Sent from my Arc S LT18i using Xda Premium App

glaudrem said:
Hello Iridaki,
many thanks for your apports (this and the init.d script). I'm actually user from a Spanish forum called www.htcmania.com (you may have heard about thedr0idboy, which is a Neo developer) and we were trying to pack kernels in order to flash it in locked bootloader devices or at least try to create an Overclock module for stock kernel that can be flashed in locked devices.
Do you think we can use this to achieve this goal? I just hate Arc S with it's damn 1.4 GHz processor :S. It was released only a month after I got my Arc.
Many thanks for your time and your efforts!!
P.D: a girl developer!!!
Click to expand...
Click to collapse
currently we cant use custom kernels on locked bootloader...
there is a way to make overclock module for stock kernel... i am looking into that possibility & i have contacted a few devs... i will work on it when i get time...
@Iris
there is a bug in the semc S1 bootloader... sometimes if the boot.img isnt of a correct size then the device will not boot... the workaround is to add a "filler" file (which is say 512KB file with junk data) to the ramdisk so as to increase the size of the final boot.img file...
thanks to jerpelea for this incredible tip... i must have wasted atleast 10-15 hrs trying to figure out why my kernel failed to boot

DooMLoRD said:
@Iris
there is a bug in the semc S1 bootloader... sometimes if the boot.img isnt of a correct size then the device will not boot... the workaround is to add a "filler" file (which is say 512KB file with junk data) to the ramdisk so as to increase the size of the final boot.img file...
thanks to jerpelea for this incredible tip... i must have wasted atleast 10-15 hrs trying to figure out why my kernel failed to boot
Click to expand...
Click to collapse
Great tip indeed!!! Added to the OP!
I haven't come across the issue yet because I am only editing some tweaks and the logo.rle but say someone uses a much smaller logo and deletes some scripts, would he need to use a filler file, even if it is for 20-30 KB?
THANKS!

iridaki said:
Great tip indeed!!! Added to the OP!
I haven't come across the issue yet because I am only editing some tweaks and the logo.rle but say someone uses a much smaller logo and deletes some scripts, would he need to use a filler file, even if it is for 20-30 KB?
THANKS!
Click to expand...
Click to collapse
size of logo doesnt really matter... just the final size of the boot.img matters...
btw the logo.rle must have correct permissions (644)

DooMLoRD said:
size of logo doesnt really matter... just the final size of the boot.img matters...
btw the logo.rle must have correct permissions (644)
Click to expand...
Click to collapse
Yes, but if the logo.rle is replaced with a smaller one in size, ramdisk size is reduced accordingly, isn't it?
Permissions are taken care of while unpacking/repacking.
Overall, this guide works, since I've sorted everything out, hasn't failed me yet!
dp94 said:
Afaik, CWM is also stored in the kernel, so is it possible to modify it with the tool?
I don't want to have a step by step guide, just a reference would be great (of course if you know one).
Anyway, thanks for your great contributions in XDA.
Click to expand...
Click to collapse
My initial response would have to be: I have no idea!
However, tell me what exactly do you want to edit. Images, colors, features?
I'll look into it, currently I have never been in involved with recovery.
theduke89 said:
OMG... :-o Iris you are a genius.
Click to expand...
Click to collapse
I have my moments.

Presumably, kernel.sin can be renamed to boot.img for splitting without problems, or am I missing something pertinent to SE?

LenAsh said:
Presumably, kernel.sin can be renamed to boot.img for splitting without problems, or am I missing something pertinent to SE?
Click to expand...
Click to collapse
NOOOOOOO!!
DoomLord has released a .sin unpacker. Unpack the kernel.sin with it, then repack it with my script.
iR¡[email protected]!* via Tapatalk

Found that previously, but the repacker doesn't work. I think the script he published is a hack of something else and may have errors.

LenAsh said:
Found that previously, but the repacker doesn't work. I think the script he published is a hack of something else and may have errors.
Click to expand...
Click to collapse
Well, no, the script is OK, it's just made to work with the particular unpacker I included in the package. You need to edit it a wee bit to work with the sin unpacker. If I get some time in the weekend, I'll look into it too.
iR¡[email protected]!* via Tapatalk

Magic, thanks Iris. I recall the unpacking is fine, it is just repacking that doesn't yield either a boot.img OR kernel.sin due to the mixed file names/folders etc. It's been a few months since I tried... forgive me. All I was doing at the time was taking a stock Neo kernel and making it insecure. Which is dead easy normally. done it plenty with other phones, but SE .sin files threw me.

iridaki said:
My initial response would have to be: I have no idea!
However, tell me what exactly do you want to edit. Images, colors, features?
I'll look into it, currently I have never been in involved with recovery.
Click to expand...
Click to collapse
Just to change the colors, rename options, maybe integrate some features into one option.
I have really tried to search a lot, here in XDA & Google, but I have no idea.

dp94 said:
Just to change the colors, rename options, maybe integrate some features into one option.
I have really tried to search a lot, here in XDA & Google, but I have no idea.
Click to expand...
Click to collapse
You would have to rebuild CWM from sources or so i believe. dont ask me how either as i've not a clue
LenAsh said:
Magic, thanks Iris. I recall the unpacking is fine, it is just repacking that doesn't yield either a boot.img OR kernel.sin due to the mixed file names/folders etc. It's been a few months since I tried... forgive me. All I was doing at the time was taking a stock Neo kernel and making it insecure. Which is dead easy normally. done it plenty with other phones, but SE .sin files threw me.
Click to expand...
Click to collapse
use this tool
http://forum.xda-developers.com/showthread.php?t=1262656
and then you will have a kernel and ramdisk and then it is just like any other boot img i had to edit it to make it unpack the ramdisk aswell. ( had to remove the ../ right after the gzip command )
basicaly use the file in that post instead of iridakis "split_bootimg.pl"
Pvy

I can change the boot logo now. Thanks very much.. I'm using doomlord kernel, but I love SE original boot logo. Finally I managed to change it. Thanks again. I just follow the instruction and it works. The reduce in size of boot.img didn't cause any problem at all... ;-)
Sent from my LT15i using xda premium

Partitions not mounting @boot

Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx

Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time

Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........

bump
please help

What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)

i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions

~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?

laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"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"
}

~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)

laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)

does that part help? i think it has to do with boot

~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site

laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?

~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..

laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does

~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat

hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please

Remove " Bootloader Unlocked" Warning 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"
}
Black Version of the logo
https://1drv.ms/u/s!Av6RWY-zSfSekyWGQi5mupY_9jvn
White Version of logo
https://1drv.ms/u/s!Av6RWY-zSfSekyaKccB9UqFgCU6U
This bin file will replace the "Bootloader unlocked" warning message with stock splash screens.
To use:
1: open adb CMD
2: type 'adb reboot bootloader'
3: type 'Fastboot flash logo logo_fix_*****.bin'
NOTE:::::: Replace ***** with White or Black as appropriate for your chosen logo download.
4: Restart and enjoy

Thank you for the mod, Added to Master index for more visibility.

I flashed the logo bin from the other stock files and I still have the unlocked warning.
sent via op5 and xda-app

byt3b0mb said:
I flashed the logo bin from the other stock files and I still have the unlocked warning.
sent via op5 and xda-app
Click to expand...
Click to collapse
Yes, this mod is cosmetic. It won't magically lock your bootloader. That warning is hard coded. These bin files are too just mock the locked state for those who are annoyed by it

I wonder if we can hex edit copy/paste an alternate png--as long as you used the correct start address? It is a png, right?

Uzephi said:
Yes, this mod is cosmetic. It won't magically lock your bootloader. That warning is hard coded. These bin files are too just mock the locked state for those who are annoyed by it
Click to expand...
Click to collapse
ya i know it wont re-lock it this actually does remove the warning, i stand corrected. flashing the logo.bin from the retail zip in the other thread only took away the t-mobile logo splash...

execute logo replacement in Android terminal
to execute logo replacement in root Android terminal (if downloaded to Download folder, otherwise change downloaded file location in flash section), type or copy/paste:
su
grep -q system_b /proc/mounts || echo "using slot a"
(or type to detect)
grep -q system_a /proc/mounts || echo "using slot b"
dd if=/dev/block/bootdevice/by-name/logo_a of=/sdcard/logo_a_backup.img
(or type to backup)
dd if=/dev/block/bootdevice/by-name/logo_b of=/sdcard/logo_b_backup.img
dd if=/dev/zero of=/dev/block/bootdevice/by-name/logo_a
(or type to zero)
dd if=/dev/zero of=/dev/block/bootdevice/by-name/logo_b
dd if=/sdcard/Download/logo_fix_black.bin of=/dev/block/bootdevice/by-name/logo_a
(or type to flash)
dd if=/sdcard/Download/logo_fix_white.bin of=/dev/block/bootdevice/by-name/logo_a
(or type to flash)
dd if=/sdcard/Download/logo_fix_black.bin of=/dev/block/bootdevice/by-name/logo_b
(or type to flash)
dd if=/sdcard/Download/logo_fix_white.bin of=/dev/block/bootdevice/by-name/logo_b

Veeery nice! I was waiting for it...! :silly:
Only one question... both version of the logo have no "warning message transparency" issue?
On my old Griffin only some colours were able to fully hidden the msg...

Fantastic job. Love the blacked out version.

Can't we just push this to system files and grant proper permissions or does it have to be flashed?

TheKnux said:
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
Click to expand...
Click to collapse
Definitely has to be flashed to logo.bin

As Joemoss states: it is on a separate partition than system

Amd4life said:
Fantastic job. Love the blacked out version.
Click to expand...
Click to collapse
Really. I can confirm black one is *fantastic* with Amoled and it doesn't have any "transparency" issue...

This bin file will replace the "Bootloader unlocked" warning message with stock splash screens.
To use:
Click to expand...
Click to collapse
THANKS! That warning screen has always annoyed me I flashed the black one. I love it. Looks "Oldskool" Like my Droid X back in the day

TheKnux said:
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
Click to expand...
Click to collapse
Well... If TWRP can access /dev/block/bootdevice/by-name/logo_b(a) then someone can make a flash able zip quite easily.
I remember on all my HTC phones TWRP could flash to that partition when s-off to remove their Dev splash warning and on some others it required to manually flash a hex edited bootloader, so it just depends

Fabulous! Replaced the T-Mobile image and removed the warning! Many thanks! This is the first device I've ever rooted. So glad I did and wouldn't be able too without all of you developing and teaching

Will this work with Flashfire/Flashify /etc? I don't have a pc, just a chromebook so don't have access to fastboot.

I'm about to release a new twrp with flashable boot logos

joemossjr said:
I'm about to release a new twrp with flashable boot logos
Click to expand...
Click to collapse
Sweet!

joemossjr said:
I'm about to release a new twrp with flashable boot logos
Click to expand...
Click to collapse
Any preview?
Don't forget a version for unbranded Z2s pal..!