Database Users

[Solved][Q] Splash screen during first boot

As I mentioned in a previous thread, I've picked up a kitchen from a retired chef so as not to reinvent the wheel since most of the changes I'm looking to do are rather minor.
One thing that's been bugging me is a small splash screen that only appears during the first boot over the welcomehead. At first I thought it was a part of RunCC as it appears above the progress bars when RunCC runs, but I took out the whole packaged (replaced it with XDA_UC) and the splash still appears for about 5 to 10 seconds during the first boot before I get to windows.
I looked through the image files (*.png/*.bmp/*.gif/*.jp[e]g) but couldn't find it anywhere, so I'm guessing it's a resource inside a dll (or some other binary file) but I can't figure out which?
Sorry if this has been asked before but I couldn't find anything related to my question by searching.
Edit:
Some pics for clarification (sorry about the quality, I only have my laptop's webcam to take images with for the time being):
Animation/Welcomehead:
{
"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"
}
The splash in question:
In case you're wondering, it reads: "Nhathoa ROMs - Windows Phone" (check my sig for more info).
It appears for about 10 seconds and then it's replaced by the Microsoft copyright text:

Check for Wellcomehead.png it must be inside Operator package or some OEM folder.
EDIT: sorry maybe i didnt understand right, anyway:
1st Boot = Splash.nb
2nd screen Wellcomehead
3rd RunCC
Those are the sequence.

Actually, none of those is the one that I'm talking about.
I'll try to get some pics to better explain what I'm talking about.
Edit: First post updated with pictures.

I downloaded the Kitchen in your sig,i took the TD2 Kitchen 2008 and i found nothing.
Im pretty sure that the pics you posted before are the Splash Screen.
You can make a test for be sure, download this Topaz Splash Screen http://forum.xda-developers.com/showthread.php?t=589777 , or one that you like, and check if it will change and that words will disappear.

I also want to know what this is, I know which images it uses though.
This is what I know about it:
It runs on first boot after which is after splash.nb and then the HTC animation (<-- btw, anyone know how to remove this completely?).
It uses the normal welcomehead.png as the wallpaper.
It uses PB1.bmp to PB14.bmp for loading bars (although yours don't seem to have it :?)
It uses LogoMsg.bmp to display an overlay (I think this, in your case, is that "Nhathoa ROMs - Windows Phone" image)
Hope this is the same thing you're talking about, and I hope it helps
It uses

seeM_ZA said:
It uses LogoMsg.bmp to display an overlay (I think this, in your case, is that "Nhathoa ROMs - Windows Phone" image)
Click to expand...
Click to collapse
Yes! That's exactly the file I was looking for! Thank you veeery much!
I must have forgotten to search for *.bmp files under OEM and only looked in the EXT folder.
As for the loading bars, they don't appear when you don't cook RunCC (which is the case for me).
Oh, and about disabling the startup animation, making this reg entry point to a non-existing file can do the trick:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\HTCAnimation]
"StartupGif"="\\Windows\\imaginaryFile.gif"
After doing this change, the screen will show a black screen between the boot splash and the welcome head, or where the animation used to be.
Got that from the "BSB Tweaks" utility, but I ended up not using it. I didn't feel any difference in booting time.
I don't know if there's an alternative method.

old thread but BUMP
this is the original wm logo i have.
LogoMsg.bmp
is there any edited ones somewhere? cool ones?
thanks
Rn

[Tool] New tool for Unpack and Repack MTK boot.img

QURepack is a new tool for boot.img unpack/repack. You do not need to run cmd and write anything to this. Just run the QURepack.exe and click unpack and repack button for this. This tool is very easy to use and will help you to do this in short time.
{
"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: links removed.
Step 1. Download and Unzip
Unzip QURepack.zip. You will get two exe files bootimg.exe and QURepack.exe. Place your boot.img file there.
Step 2. Unpack
Run QURepack.exe and click unpack. It will start work and you will get unpacked files.
Step 3: Repack
Click repack button and it will create two boot.img file.
Step 4: New Boot File
Now click New Boot File and you will get a new boot file.
I made this tool for personal use and make easy to unpack/repack boot image. Anyone can use this tool for personal use. If anyone want to publish this tool to their blog or website then they need to take permission.
N.B. Do it at your won risk. I will not responsible for any kind of misuse and brick or damage of your phone.
Mod Edit: links removed.
Dev of QURepack
Mod Edit: links removed.
Special Thanks to:
Dev of bootimg

I don't have FB accaunt

Dreamer... said:
I don't have FB accaunt
Click to expand...
Click to collapse
It's a scam anyway

Jubbard said:
It's a scam anyway
Click to expand...
Click to collapse
Are you sure? I find this app without passcode on archive, but not try yet..
Some mans say what its works.

Dreamer... said:
Are you sure? I find this app without passcode on archive, but not try yet..
Some mans say what its works.
Click to expand...
Click to collapse
I'm sure it works. Because it's a GUI to the bootimg.exe tool (available for free from Github), which is a modification of the bootimg.py tool (available for free from another Github). The internet is full of "content gateways" where someone wastes their talent on building a do-nothing program instead of something useful, like a tool that allows easy repartitioning/editing of a mmcblk0.raw image.
bootimg.exe --unpack-bootimg boot.img
Click to expand...
Click to collapse
Sadly for some reason it requires the image being unpacked to be named "boot.img", when it's fully capable of unpacking any "ANDROID!" boot image for both Mediatek and Qualcomm.
I've used it to unpack boot and recovery for a Huawei Y536A1, boot factory laf recovery for a LGL16C, boot dfs dkernel recovery for an Amazon Kindle Fire HDX 7". I've never seen it fail to unpack a boot image yet.

Thread closed until non income earning links are submitted, and no password is required .

Samsung galaxy A5 boot splash

Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU

legitscoper said:
Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU
Click to expand...
Click to collapse
It's in param partition.

It is empty ;(
It is in dev/block/bootdevice/by-name/param
I have made dd if=/dev/block/bootdevice/by-name/param of=/sdcard/param
I opened it in hexview and it has almost only 00 everywhere
and has 10mb

It's because you have a raw image of that whole 10MB partition while maybe only 1MB is used.

It'll send you it

I can take a look at it when I get home in a few hours.

Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change 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"
}

Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?

legitscoper said:
Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?
Click to expand...
Click to collapse
I guess Odin would never allow the modified bootloader to flash. May be possible with the modified version of odin, I don't know..
I assume by the pictures I found that the background will be black by defauld no matter what.
There's no whole bootlogo, only the "Samsung galaxy A5" and "Powered by android" logos as small images.
Here I have extracted the "powered by android" logo from aboot. Only problem is I don't know what the file is named inside aboot.
If I name the new image something else than it should be and overwrite the old one, it would probably become bricked.
At best there would still be download mode.
Even if I did know the filename I would have to be precise in everything. Same resolution(304x81), same dpi(96dpi), same bytesize(6157 b), etc. and insert/overwrite at the exact same place. One faulty byte anywhere and chances are that the phone may never boot again unless you can get a jtag and reflash it.
It feels a bit risky just to change those two small images, and still be limited to only black background with new text at the same places as the original.

00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?

legitscoper said:
00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?
Click to expand...
Click to collapse
I would not try to change size or dpi in bootloader. I've made mistakes before when I modded param partition on another phone and it ends in no boot to system or recovery, or loop, and only download mode available. Param is like an image cache for bootloader, but here the images are inside bootloader which means that if something goes wrong it probably won't boot at all.
I think 00033.jpg was just what the program i used named it when it extracted the images.
That image was the second I found by searching for ffd8 which always is the beginning of a .jpg in hex, then make a search downwards for ffd9, which is the end of a .jpg. The first I found was the 5. It's a bit of trial end error when working in hex without knowing which image is what
The aboot I used was extracted from firmware.

And I will be unable to go to download mode it that "faulty byte" will occur?

I think thread is to close, I don't want to have that level of risk and with that limitations

tys0n said:
Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change it.
View attachment 4094675
Click to expand...
Click to collapse
Program name?

EASY UNLOCK AND 8.1 Developer Preview Install

First of all, thanks Deuces and Northmendo for the idea to help people.
I have created a pretty easy all in one that will install the lasted adb and fastboot system wide and fastboot flash unlock and unlock_critical. It will install the latest 8.1 developer preview for the Pixel 2 XL for you as well with all the necessary files included. I did not inlcude the lock and lock_critical function as most do not use it.
As the instructions state, please use a usb 2.0 port and and usb-c to usb-a cable that supports data. Also enabling debugging and oem unlock is a must.
It includes a menu driven batch file that is super easy to use.
For those that want to use this same batch file on the pixel 2 itself, please extract the zip from google and then extract the zip within the zip. Next pull the bootloader and radio img file from the root of the zip to the FILES folder included in this program. Then copy all the contents from the zip within the zip to the same FILES folder. It should contain about 22 files in total. We really don't need the android-info.txt file.
I will also be including a batch file with a semi empty FILES folder that does not include any Google related 8.1 files for those that want to download it quicker and copy their own contents to it for flashing. Like Pixel 2 owners that already have the 8.1 preview downloaded.
If anyone needs any help please feel free to ask. This post was rushed so please excuse my grammatical errors.
FOR PIXEL 2 and PIXEL???? ----NO IMG's inlcuded
http://www.mediafire.com/file/eksn04aiaeqvvia/PXEL_2_&_PIXEL_SAUCE_NO-IMGS.zip
FOR PIXEL 2 XL ---- IMG's included
http://www.mediafire.com/file/1wde39mj7ssbxb3/PIXEL_2_XL_SAUCE_V1.zip

Oh btw. In the credits they are listed as well as their profile page.
Forgot to mention your phone needs to be in the bootloader. Duh!
Sent from my Nexus 6 using Tapatalk

Great tool bro, thank you.

samteeee said:
Great tool bro, thank you.
Click to expand...
Click to collapse
No problem. I'll prolly update it to lock the bootloader and have some useful adb commands.
Sent from my Nexus 6 using Tapatalk

so we need unlock_critical
which they said we need only for non signed bootloader
did google not signed the bootloader img by mistake
or this is intentional for dev previews

You can install the Dev 8.1 ROM without unlocking though. Just go to Android's site and enroll your phone in the beta program like you would an iPhone, and it just sends it to you as an OTA and installs it without wiping or unlocking your phone...

abogrhen said:
so we need unlock_critical
which they said we need only for non signed bootloader
did google not signed the bootloader img by mistake
or this is intentional for dev previews
Click to expand...
Click to collapse
Not sure but it could be as it is a manual flash. Have you tried stock 8.0 flash with critical locked?
Sent from my Nexus 6 using Tapatalk

bryantjopplin said:
Not sure but it could be as it is a manual flash. Have you tried stock 8.0 flash with critical locked?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
i did not receved my pixel 2 yet
still using my nexus 6
but i will try first

I'm having issues flashing this. I ran the .bat file but when I choose "Flash All", I can get to this final screen where it says "THERE IS NO GOING BACK. PRESS ANY KEY TO CONTINUE" except nothing happens when I hit any key. Is this happening for anyone else?
{
"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"
}

Lumia 520 cannot flash partition

Hello there !
I have an issue where I want to go back to Windows from fastboot as explained in this post :https://forum.xda-developers.com/no...nt/restore-windows-phone-8-installed-t3608223 .
I have my TZ.bin and other necessary files, but when trying to flash them with the command "fastboot flash partition TZ.bin", I get this error message:
{
"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"
}
Is there someone here smarter than me who knows how to solve that ?

First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).

TBM 13 said:
First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).
Click to expand...
Click to collapse
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...

r0mDU19 said:
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...
Click to expand...
Click to collapse
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?

TBM 13 said:
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?
Click to expand...
Click to collapse
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !

r0mDU19 said:
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !
Click to expand...
Click to collapse
Sorry, but i don't remember.

TBM 13 said:
Sorry, but i don't remember.
Click to expand...
Click to collapse
No problem, thanks again for the advices ! :good:

Weirdly enough, my problem came back.
That prevents me from flashing anything at all.

r0mDU19 said:
Weirdly enough, my problem came back.
That prevents me from flashing anything at all.
Click to expand...
Click to collapse
Same problem than today, replace partition with the partition name (TZ in this case).