Develop Bugs

[FIXED!] - BuildOS producing Windows error on opening

I'm really sorry to be starting a new thread, but I've been racking my brains over this problem and haven't got anywhere yet. I know it's not the application so it must be something I've done, just not sure what!
Until today I have been able to use the BuildOS.exe in both Pandora and Core's kitchens without problem. Haven't tried using it for a few weeks, but with the new OS build today tried Pandora. Unfortunately, when I try to open BuildOS, it reports it has encountered a problem and needs to close. It offers the choice of reporting to Microsoft or not (reporting produces no suggested fixes).
Have uninstalled .NET Framework 3, 2, 1.1 and 1 and then re-installed them from Microsoft Update but at each stage the error message has been the same. I've also tried Googling for problems with BuildOS, but each just suggests installing .NET Framework 2. Searching for the error message codes didn't producing anything either.
I'm attaching the first screen of the error message but cannot work out how to copy and paste the actual error (it's unselectable).
If anyone has any ideas at all, I'd really appreciate them as I'm out. Thanks for reading this post and please don't flame unless they're REALLY funny!

The attachment doesnt really give much information..
Try print-screening the error and paste it into paint then cut out just the error and post it.. though im guessing it just says something lke unhandled exception or something like that..
You can also try looking around the system error logs in Control Panel\Administrative Tools\Event Log where you might find some details of the error.
have you installed or uninstalled anything in those few weeks?

the only thing I get from that log file is the mscorelib - .NET Framework...
Maybe try MS .NET Compact FW? I have 1.0 SP3 and 2.0 SP1...

Step by step
Lets try to isolate the problem:
Step 1: Try to use an older version of pandora, if its working something is wrong with your download of the latest version.
Step 2: You said that you haven't use the kitchen for some weeks. What have you installed and/or deinstalled since the last use of the kitchen? Maybe another program on your desktop computer is in conflict with .net or the kitchen.

Problem located, just got to fix it now!
Thanks for the suggestions guys, should've thought of the event viewer myself! D'oh!
The report viewer shows the problem is in my .NET 2 installation, so at least I know where to concentrate now.
Time for the big stick with the nail in it, I think!
Thanks again Sam and matt. I know you're both very busy and really do appreciate you taking the time to help.
EDIT: Sorry Gerald, your post showed up while I was typing. Thank you very much for the suggestion and bringing me back to sanity! Will try an older version first, just in case, and then going to play around with my .NET installations.

mattk_r said:
Maybe try MS .NET Compact FW? I have 1.0 SP3 and 2.0 SP1...
Click to expand...
Click to collapse
Uhh, in my world .NET CF runs on a device.

The problem continues...
Bugger - tried a shortcut and it didn't work! Copied the Pandora setup files and installed them on my laptop, only for that to come up with the same error message!
The laptop has very little installed on it and has only been up and running from a fresh install for two weeks. I've got basic drivers, AVG Anti-virus, Spybot and MS Office 2003 installed and that's about it. It's also completely up to date on MS Updates (I'm anal like that) so has .NETs up to 3.0 installed.
I also tried downloading Core's kitchen onto the laptop but again the BuildOS in that reports the same error.
The error shows under Event Viewer > Application as:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 14/08/2007
Time: 21:07:36
User: N/A
Computer: MINI-LAPTOP
Description:
EventType clr20r3, P1 buildos.exe, P2 0.0.0.0, P3 45fef3bf, P4 mscorlib, P5 2.0.0.0, P6 461eee3d, P7 331e, P8 119, P9 system.io.directorynotfound, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 62 00 75 00 69 00 .b.u.i.
0018: 6c 00 64 00 6f 00 73 00 l.d.o.s.
0020: 2e 00 65 00 78 00 65 00 ..e.x.e.
0028: 2c 00 20 00 30 00 2e 00 ,. .0...
0030: 30 00 2e 00 30 00 2e 00 0...0...
0038: 30 00 2c 00 20 00 34 00 0.,. .4.
0040: 35 00 66 00 65 00 66 00 5.f.e.f.
0048: 33 00 62 00 66 00 2c 00 3.b.f.,.
0050: 20 00 6d 00 73 00 63 00 .m.s.c.
0058: 6f 00 72 00 6c 00 69 00 o.r.l.i.
0060: 62 00 2c 00 20 00 32 00 b.,. .2.
0068: 2e 00 30 00 2e 00 30 00 ..0...0.
0070: 2e 00 30 00 2c 00 20 00 ..0.,. .
0078: 34 00 36 00 31 00 65 00 4.6.1.e.
0080: 65 00 65 00 33 00 64 00 e.e.3.d.
0088: 2c 00 20 00 33 00 33 00 ,. .3.3.
0090: 31 00 65 00 2c 00 20 00 1.e.,. .
0098: 31 00 31 00 39 00 2c 00 1.1.9.,.
00a0: 20 00 73 00 79 00 73 00 .s.y.s.
00a8: 74 00 65 00 6d 00 2e 00 t.e.m...
00b0: 69 00 6f 00 2e 00 64 00 i.o...d.
00b8: 69 00 72 00 65 00 63 00 i.r.e.c.
00c0: 74 00 6f 00 72 00 79 00 t.o.r.y.
00c8: 6e 00 6f 00 74 00 66 00 n.o.t.f.
00d0: 6f 00 75 00 6e 00 64 00 o.u.n.d.
00d8: 20 00 4e 00 49 00 4c 00 .N.I.L.
00e0: 0d 00 0a 00 ....
I know this now definitely isn't a WM6 problem but I'm adding this info in case one of the great XDA Dev minds knows the solution, and in case another user like me experiences the same problem - you're not alone and I'll update the thread when I find the solution!

Here's a stab at it (albeit a simple one). When using Pandora, do you have everything in the proper folder structure? The following applies:
(in this example, everything is thrown into a main folder "Pandora")
- Pandora (parent folder)
- BuildOS.exe (file)
- CreateROM.bat (file)
- pkgcommon.dll (file)
- OEM (sub folder)
- ROM (sub folder)
- SYS (sub folder)
- TOOLS (sub folder)
If you don't follow this hierarchy, Windows will shoot an error out at you.
Good luck!

Thanks Taurus, good suggestion. I've also got an inconsequential Readme.txt file in there too, but other than that - all present and correct!
Again, thanks for all your suggestions guys and once I find the solution I'll be sure to post it up.

You run buildOS from the command line, make sure you cd to the folder containing OEM/SYS/ROM and TOOLS .... THEN run buildOS from wherever it is by typing the full path into cmd, or even better add buildOS to the PATH variable .
so you need to follow this kind of procedure:
Code:
cd c:\ROMFOLDER (ENTER)
then...
c:\ROMTOOLSFOLDER\BuildOS (ENTER)
remember ROMFOLDER and ROMTOOLSFOLDER should be replaced by the paths you use.....its a PITA but thats how it runs.

Confused Stu said:
Thanks Taurus, good suggestion. I've also got an inconsequential Readme.txt file in there too, but other than that - all present and correct!
Again, thanks for all your suggestions guys and once I find the solution I'll be sure to post it up.
Click to expand...
Click to collapse
No problem. I just wanted to clarify what I meant, as I don't know if I was that clear.
I've attached a shot of everything the way it should look. Anyhow, it sounds like you have it right already, but I thought I'd just float that your way.

vp3G said:
Uhh, in my world .NET CF runs on a device.
Click to expand...
Click to collapse
It gets installed with VS Team Suite 2k5, probably since it has the CE mobile device emulators included.
Confused Stu - if you're still having trouble with .NET, let me know. I supported this stuff for M$, and know a few tricks to getting it cleaned up and installed.

Only common factor - interface between keyboard and chair!
OK, I've spent this evening wiping and rebuilding my laptop. It's got XP SP2 on it, then added the laptop drivers, the Kitchen and ran all the Microsoft Updates until only the .NETs were left.
Tried running BuildOS with no .NETs installed, and it came up with a message telling me the application wasn't in the correct state and re-installing it might help.
Installed .NET 1 (same message on trying to open BuildOS), then installed the updates for .NET 1 - same message. Installed .NET 2 and immediately got the original error I was getting on my home PC and other laptop! Went on to install the updates for .NET 2 and finally .NET 3 - but the same error kept coming up.
I've now got this same error coming up my Home PC (self-built), my Dell laptop, and my newly rebuilt Medion one! I've got no common files besides the MS Updates and no common components. Beginning to think maybe it's just plain personal!
Matt - if you can help at all with my .NET problems, I'd be ridiculously grateful. Alternatively, if anyone can suggest another avenue I can try please post it up - I'm almost out of ideas!
I've got another fresh install going on at work (Dell desktop this time) so tomorrow I'm going to try installing only .NET 1 and .NET 2 - not even any other MS Updates. Then if i install the updates one at a time I might be able to work out the problem one. Still not sure why I'm the only person affected by this though?

First of all, you are not alone, have a look at:
http://www.google.at/search?hl=de&q...time+2.0+Error+Reporting+Event+ID:+5000&meta=
Now for the bad news: I checked the first ten posts or so, they recommend to debug the code. But as its running on other machines without any problems it must be something within your .net installion.
man, this is strange.

I had a similar problem with BuildOS but with me it happened anytime I tried to add a package to the OEM folder.
Have you made any changes to anything from the Kitchen?
Matt said that you can't just add a package because its signed ( or something).

FIXED!!!!
Allan1 - you're a star!!!!
I've just deleted out the OEM (and SYS) folders, unzipped the v6 kitchen again and it's worked perfectly! Looks like my problem was I was unzipping the v6.1 (beta) OEM over the top of the existing OEM and that was causing my problems.
Don't I feel like a complete doughnut!
Sorry for wasting everyone's time, and THANK YOU very, very, very much for everyone's help and suggestions on this. It's really touching that so many people were willing to try to help me out.
Now commence the "what an idiot" flaming if anyone wants to - it's justified!

No probs!!

allan1 said:
I had a similar problem with BuildOS but with me it happened anytime I tried to add a package to the OEM folder.
Have you made any changes to anything from the Kitchen?
Matt said that you can't just add a package because its signed ( or something).
Click to expand...
Click to collapse
good looking out...just encountered this problem in HYPERCORE....driving me insane why it wasn't working cuz I just built 3 .nb's in the last few hours.
thanks alot

Samsung i900 Omnia rom backup help

Hi to all the Samsung experts, I currently have a Samsung i900 and am looking for a way to extract my rom and create a flashable format. I have used pdocread to extract 3 .raw files but am not sure how to proceed from here. Can anyone advise? Thanks.

Hoping that the i780 istruction can be used for the omnia, the relevant posts are here..
http://forum.xda-developers.com/showpost.php?p=2237280&postcount=10
http://forum.xda-developers.com/showthread.php?t=393490

Thanks, I have read those threads, problem is you apparently need a flashable .bin to start with which in this case I do not so am looking for a way to use the .raw files only. Do you know if that is possible?

efjay said:
Thanks, I have read those threads, problem is you apparently need a flashable .bin to start with which in this case I do not so am looking for a way to use the .raw files only. Do you know if that is possible?
Click to expand...
Click to collapse
No you don't need the bins, you can start from the raw files.
Just look at the famusc kitchen and read the included instructions.

Ok here is a way to dump the nb file and then dump its contents.I have already done that, including xip
Use itsutils and following command in dos window :
psdread -1 0 0xDISKSIZE os.nb
Then use imgfs tools or tazio tools to dump, and further processing.
We need now how to flash back the custom os.nb to omnia
still searching for sd card flashing combinations

@The Solutor: I have read the famusc kitchen docs and it explicity states you need an existing .bin PDA rom. However there are a few commands in there that may be worth checking out.
@hdubli: I will try the command you suggested later today. What are the tazio tools? And dont Samsung phones use .bin files to flash rather than .nb?

You don't need the bin.
Here step by step:
- Downlad and install the kitchen
- Copy Part02.raw into the kitchen folder
- Open cmd and type: ImgfsToDump Part02.raw (This will create dump folder)
- Execute RecreateBin.exe
You got your bin file!!!!

mievalt said:
You don't need the bin.
Here step by step:
- Downlad and install the kitchen
- Copy Part02.raw into the kitchen folder
- Open cmd and type: ImgfsToDump Part02.raw (This will create dump folder)
- Execute RecreateBin.exe
You got your bin file!!!!
Click to expand...
Click to collapse
Do you mean RecreateBin.bat? There is no RecreateBin.exe and looking at the contents of the .bat file I dont think it will work as it makes reference to i780 files which I dont have and most likely wont work with the Omnia.
imgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative

yes it is the .bat file sorry.
I780 should just be name of the files that you get at the end...
I can't say if it works you just have to give it a try...
But that would be the way we do it with our i780 roms...
Try and report. You should get a i780.bin file.... otherwise it should stop with an error.

I have a Samsung Omnia German version and would like to get the english version. Anybody know where to find the WWE ROM and CID unlock or what i need to install it?

any luck
Any luck on cooking a samsung i900 Rom

JesperRas said:
I have a Samsung Omnia German version and would like to get the english version. Anybody know where to find the WWE ROM and CID unlock or what i need to install it?
Click to expand...
Click to collapse
What does ur version read?
My one read i900XXHE4. I am also looking for way to upgrade to i900DXHG4

anyone manage to extract the rom?
or is there anyway i could extract those dll in the roms?
would like to try reverse it see if can extract the data for the accelerometer

Link
Here is the Link
For the update

any body can backup the rom G2 and previous and let us flash it? i sooo want the old rom back.. G4 fully sucked with too many issues on it..

What is the build info on G4?
I can dump the rom but you will have my serial #

silencer22 said:
anyone manage to extract the rom?
or is there anyway i could extract those dll in the roms?
would like to try reverse it see if can extract the data for the accelerometer
Click to expand...
Click to collapse
it looks like a .bin file and oddly enough executing it changed all my Atom .nb0 files to 'open with' USDL4...
Do kitchen tools exist or Perhaps somebody could be commisioned to make tools for us, I'd be up for that!

whats the go on creating a flashable rom? i tried to flash chinese G8 rom and i regretted it.. now i cant flash it back to WWE G4 rom. =( anyone here able to make flashable rom or F8 or G2 WWE roms? pls pls pls..

I tried to back up my i900 Omnia ROM and get this:
C:\12>pdocread -l
128.46M (0x8076000) DSK1:
| 1.47M (0x179000) Part00
| 2.58M (0x295800) Part01
| 124.40M (0x7c66800) Part02
90.44M (0x5a70000) DSK2:
| 90.43M (0x5a6f000) Part00
0.00 (0x0) DSK5:
| 0.00 (0x0) PART00
15.00G (0x3c0000000) DSK3:
| 15.00G (0x3bffffc00) Part00
STRG handles:
handle 6698a06e 15.00G (0x3bffffc00)
handle a698a026
handle c6cc2472 90.43M (0x5a6f000)
handle 06e0479a124.40M (0x7c66800)
handle 26e04776 2.58M (0x295800)
handle 26e0472e 1.47M (0x179000)
disk 6698a06e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a698a026
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c6cc2472
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 06e0479a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 26e04776
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 26e0472e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C:\12>psdread -1 0 0xDISKSIZE os.nb
remote disk 1 has 65772 sectors of 2048 bytes - 128.46Mbyte
SerialNr: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CopySDCardToFile(remote, 1, 0x0, 0xd, os.nb)
ERROR: ITReadSDCard - The parameter is incorrect.
C:\12>pdocread -w -d FLASHDR -p Part00 0 0x179000 Part00.raw
ERROR: ITTFFSGetInfo - The device is not ready for use.
WARNING: using default 512 bytes for sectorsize
CopyTFFSToFile(0x0, 0x179000, Part00.raw)
ERROR: ITReadDisk: outbuf==NULL
- The device is not ready for use.
Any thoughts?

I am improving :
C:\12>psdread -1 0 0x8076000 i900XHHG4.nb
remote disk 1 has 65772 sectors of 2048 bytes - 128.46Mbyt
SerialNr: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CopySDCardToFile(remote, 1, 0x0, 0x8076000, i900XHHG4.nb)
but I am waiting more than 30 min and no activity. How long does it take to copy 128MB?

[DEV] Oem channel Id Modifier

Hi everydbody,
i'm working on a software to change oem and channel id for windows store (8.0, maybe 8.1...)
i've managed to see surface pick, or lenovo pick on my asus vivotab, but i don't know other oem channel ID.
in order o make a database, i need help !
could you go to: (win+R)
%localappdata%\Packages\WinStore_cw5n1h2txyewy\AC\Microsoft\Windows Store\Cache\0
and post in reply this file with your pc model in comment :
0-Channel-https∺∯∯next-services.apps.microsoft.com∯browse∯6.2.9200-1∯670∯Channel.dat
this file doesnt contain any personal data, juste channel and Oem ID
thanks!

feherneoh said:
09 AA 98 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Lenovo B560
Click to expand...
Click to collapse
Hi ferneoh
thank you, if you replace 09 AA 98 by 97 C5 98 for exemple you willhave access to samsung picks.... but i can't download from oem store for now...

My Surface RT only have file "0-Channel-https∺∯∯next-services.apps.microsoft.com∯browse∯6.2.9200-1∯670∯Channel∯Surface%20RT.dat"
ฺู™  0 0 0 0 1 0 9 8 9 4
That all from it.

That file is a binary data file. Opening it notepad doesnt represent the actual data (although it does attempt to parse it as plain text anyway).

I'd love to be able to use this to install Nokia's proprietary apps onto my Surface... please make this happen!

Anyone looked into this, yet?

Xperia open bootloader: What is this TA / bootloader update protocol?

While looking for a way on linux to update my bootloader to use a real recovery partition, I found this little gem:
munjeni said:
Here is aditional trick to install openbootloader without needs for emma:
Code:
//===========================================================
// Rhine S1 Boot Config Data
//
// Config Data Description: http://metadoc.sonyericsson.net/?DOCS=1/15935-5/FCP1191274 PA2
// Honami
//
//
//
// Created: 20150417 1730
// Author: Magnus Strandh, 23048553
//
// Specification document: 8/159 35-LXE 108 010, Rev PA4
// Format:
// [TAPartition<HEX8>]{1}
// [UnitID<HEX32> UnitSize<HEX16> Data<HEX8>{UnitSize}]{n}
//===========================================================
02
// this enables recovery mode (aka installs openbootloader)
0000084f 0054 1A CE 28 00 01 00 06 05 00 02 02 51 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 05 00 05 83 02 00 10 02 00 05 85 0A 00 02 00 A9 09 BE BA A9 09 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01
000008fd 0001 00
Click to expand...
Click to collapse
I would like to understand more about this protocol. Was it created by Qualcomm? Sony/Ericsson?
What tools use this protocol? I understand that Androxyde's FlashTool is supposed to do the right thing when it finds this in a .ta file packed within an .ftf file, but FlashTool is huge, and I don't like the idea of reading all of its source code just to find the parts that relate to this protocol.
The Config Data Description URL above is broken; metadoc.sonyericsson.net no longer exists. Is the referenced document still available somewhere? Is there any other documentation?

I just tried my luck googling Markus Strandh at Ericsson and found this profile at LinkedIn. Job desription says
Senior Sw Architect at Sony Mobile Communications
Click to expand...
Click to collapse
. So he might as well be the author of the document. And if he is he might know where to find that file you're looking for.
In case you don't have a LinkedIn account let me know

Thanks. I don't do LinkedIn, but I might try to find his contact info once I know a little more.
I'm hoping someone here (@munjeni? @Androxyde?) can chime in with which programs are known to apply these files.

I found munjeni's newflasher today. The source code is far easier to understand than Flashtool, and although it doesn't answer all my questions, it does help reveal how these bootloader config files are supposed to be applied to a device. Nice.

[MOD] Custom Boot Splash Generator - Create Your Own

You can customize your Boot Splash Picture
(This is the first picture you see when you boot up your device, before the boot animation starts. The one you also see before booting into recovery.)
I have done this for every device I owned so far, plus a few I did't own. Until now they have all been HTC devices. Today I added the Xiaomi 9T Pro / K20 Pro.
If you have your bootloader unlocked and have a custom recovery (tested only on twrp-3.3.1-15-raphael), you can create you own custom boot splash using this Boot Splash Creator tool.
How to do it:
Upload a picture to the online boot splash zip generator (http://jobiwan.net:81/bootsplash-9tpro). (If your picture is not 1080x2340 it will be resized while retaining proportions.)
It generates and downloads a flashable .zip file,
Flash the resulting .zip file in recovery.
Alternatively, you can take the logo.img file from the cache directory inside the .zip file and flash it in fastboot:
fastboot flash logo logo.img
Disclaimer:
You have unlocked and rooted your device, and flashed custom recoveries, so by now you should know that you have nobody to blame but yourself.
Anyway: This tool is provided as is, with no warranty whatsoever. If you brick your device, I will feel sad for you but I will not be responsible.
How it works:
I took the logo.img file from a firmware zip. This is a 24M file that contains 4 bitmaps:
The MI logo
The fastboot logo
The MI logo with unlocked at the bottom
System has been destroyed logo
Each one is 1080x1920, 24bpp.
This tool converts your picture into a 1080x2340 bitmap and replaces the raw image data in the original logo.img file with the raw image data from your picture.
It replaces bitmaps 1 and 3, the MI and MI unlocked logo's. Fastboot and Destroyed logo's remain original.
Then it puts this patched logo.img file into a zip with an updater script that puts it into the logo partition. This .zip file gets sent back to your browser.
Back to stock:
The attached .zip files are recovery flashable. They contain the stock boot splashes for raphael and raphaelin respectively. (I put the original logo.img files in them.) So if you ever want the stock splash back, you can flash this.
('extracted-bitmaps.zip' is not flashable. It contains the original logo's as .bmp files.)
Share & Enjoy!
If you create any cool splashes, that others might like, please post them in this thread with a pictures and zips.
-Jobo
Update Oct. 16, 2019: Online tool now generates 1080x2340 plash images.

Nice

Can I use this on K20 Pro Raphaelin?

Anonda said:
Can I use this on K20 Pro Raphaelin?
Click to expand...
Click to collapse
[edit:]Yes you can. See post below this one.[/edit]
I can not say for 100% sure, because I do not own a raphaelin device to test with.
However, I strongly believe that you can do it. Here is why:
I looked at the logo.img files from a raphael and raphaelin firmware zip.
They are not the same: They have the bitmaps at different offsets. But the structure is the same. They both have the signature and index at the same offset (0x4000 or 16k) and the addresses of the bitmaps are int he same place in the index.
This is from V10.3.3.0.PFKEUXM:
Code:
00004000 4c 4f 47 4f 21 21 21 21 05 00 00 00 ef 05 00 00 |LOGO!!!!........|
00004010 f4 05 00 00 ef 05 00 00 e3 0b 00 00 ef 05 00 00 |................|
00004020 d2 11 00 00 ef 05 00 00 00 00 00 00 00 00 00 00 |................|
00004030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
It has the bitmaps at 0x0005000, 0x05f4000, 0x0be3000, 0x11d2000
This is from V10.3.5.0.PFKINXM:
Code:
00004000 4c 4f 47 4f 21 21 21 21 05 00 00 00 3b 07 00 00 |LOGO!!!!....;...|
00004010 40 07 00 00 ef 05 00 00 2f 0d 00 00 3b 07 00 00 |@......./...;...|
00004020 6a 14 00 00 ef 05 00 00 00 00 00 00 00 00 00 00 |j...............|
00004030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
It has the bitmaps at 0x0005000, 0x0740000, 0x0d2f000, 0x146a000
After confirming this, I felt confident / brave / stupid enough to flash the logo.img from the raphaelin firmware into my raphael. When I rebooted, it showed the Redmi logo and everything was fine.
So since flashing the raphaelin logo in a raphael device is safe and works fine, I would think that the reverse is also true.
If you or anyone with an Indian K20 have done this, please report back.
-Jobo

touch of jobo said:
I can not say for 100% sure, because I do not own a raphaelin device to test with.
However, I strongly believe that you can do it. Here is why:
I looked at the logo.img files from a raphael and raphaelin firmware zip.
They are not the same: They have the bitmaps at different offsets. But the structure is the same. They both have the signature and index at the same offset (0x4000 or 16k) and the addresses of the bitmaps are int he same place in the index.
This is from V10.3.3.0.PFKEUXM:
Code:
00004000 4c 4f 47 4f 21 21 21 21 05 00 00 00 ef 05 00 00 |LOGO!!!!........|
00004010 f4 05 00 00 ef 05 00 00 e3 0b 00 00 ef 05 00 00 |................|
00004020 d2 11 00 00 ef 05 00 00 00 00 00 00 00 00 00 00 |................|
00004030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
It has the bitmaps at 0x0005000, 0x05f4000, 0x0be3000, 0x11d2000
This is from V10.3.5.0.PFKINXM:
Code:
00004000 4c 4f 47 4f 21 21 21 21 05 00 00 00 3b 07 00 00 |LOGO!!!!....;...|
00004010 40 07 00 00 ef 05 00 00 2f 0d 00 00 3b 07 00 00 |@......./...;...|
00004020 6a 14 00 00 ef 05 00 00 00 00 00 00 00 00 00 00 |j...............|
00004030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
It has the bitmaps at 0x0005000, 0x0740000, 0x0d2f000, 0x146a000
After confirming this, I felt confident / brave / stupid enough to flash the logo.img from the raphaelin firmware into my raphael. When I rebooted, it showed the Redmi logo and everything was fine.
So since flashing the raphaelin logo in a raphael device is safe and works fine, I would think that the reverse is also true.
If you or anyone with an Indian K20 have done this, please report back.
-Jobo
Click to expand...
Click to collapse
Raphael logos work on raphaelin without any issues!
Regards,
acervenky

acervenky said:
Raphael logos work on raphaelin without any issues!
Click to expand...
Click to collapse
Thanks for confirming. That's good to know.
I have added a zip with the stock logo for raphaelin to the original post.
-Jobo

Here is a boot splash plus boot animation that go well together.
They are the same style and the first (and last) frame of the animation is the same as the splash.
The boot animation is not recovery flashable. You have to manually copy it to /system/media/
-Jobo

Do you have the raw files of the 4 bitmaps inside the original logo.img of K20 Pro? Because I can't extract it and I want to get the original bitmaps/stock logos and start edit on it. Thanks

ispiyaakoe said:
Do you have the raw files of the 4 bitmaps inside the original logo.img
Click to expand...
Click to collapse
Yes. I have added them as an attachment to the first post, in 'extracted-bitmaps.zip'.
Inside the .zip are 8 .bmp files. euX.bmp are from European firmware, inX.bmp are from Indian firmware.
Interestingly, the bitmaps in the Indian firmware are not all the same size.
The 'normal' logo's are 1080x2340 while the 'fastboot' and 'destroyed' logo's are 1080x1920.
I think I will change my online tool to generate 1080x2340 splashes instead of 1080x1920.
Edit: Done. Online tool now generates 1080x2340 plash images.

Thank you very much! You are awesome.

There is a crop up and down at 1080p images. Other than that is working properly!!! Thx!

pikachukaki said:
There is a crop up and down at 1080p images. Other than that is working properly!!! Thx!
Click to expand...
Click to collapse
I have updated the online tool to generate 1080x2340 images instead of 1080x1920. This fills the entire screen.
(It also no longer distorts the image when stretching. It now scales the image proportionally for best fit and puts it on a 1080x2340 black background.)
Originally I made them 1080x1920 because that's how they are in the PFKEUXM firmware.
Only after looking into the Indian K20 Pro firmware did I find out that it also works with full 1080x2340 bitmaps.

Here is Google black boot logo + black android 10 bootanimation. Bootanimation is only for AOSP ROMs.
Thanks and credit to @touch of jobo for his tool.

Xiaomi Bunny pics
I took the images from this set: http://vkclub.su/en/stickers/xiaomi/
..and converted them to boot splash zips.
(On that site, it says the Author / Illustrator is 'Xiaomi'...)
It is the same creature that we have on our stock fastboot logo. I think they were originally meant as emoticons. Some of them have some text (in what seems to be Russian) in very dark grey. I first overlaid the images on this same dark grey color and then turned that dark grey into black. This gets rid of the text.
Attached to this post are:
The 16 images where I put the original pictures on a black background,
The original pictures in originals.zip
The flashable bootsplash zips are inside zips-000-007.zip and zips-008-015.zip
I put the 16 bootsplash zips inside 2 new zips to get around the 20 attachments per post limit.
This means they are fairly large. You can also just download individual pictures and run those through the tool.
(So just to clarify: Those 2 large zips are not flashable. They each contain 8 other zips that are flashable.)

gianton said:
Here is Google black boot logo + black android 10 bootanimation.
Thanks and credit to @touch of jobo for his tool.
Click to expand...
Click to collapse
Bootanimation does not work. Tested on my K20 pro

omkar1997 said:
Bootanimation does not work. Tested on my K20 pro
Click to expand...
Click to collapse
Forgot to mention bootanimation is only for AOSP ROMs.

IdrisMC said:
Can you flash both on LOS 17?
Does the splash also include the google bootloader image?
Click to expand...
Click to collapse
Yes that's what I'm using with LOS 17. Flash both in recovery (mount system first).

Silhouette of trees against winter evening sky
I took this picture about 10 years ago. Since then I have used it as a wallpaper on every computer and phone I used. I think it goes really well with a dark theme.
Now I made a boot splash and boot animation based on this picture. They are the original 9T-Pro splash and animation, but with this photo as the background.
By default, the lock screen takes the center of the wallpaper (when you select 'Apply Both'), which is the same cut-out I use as the background for the splash and boot animation.
Attachments:
bootsplash-9tpro-trees.zip
This is a recovery flashable zip that replaces your boot splash.
bootanimation.zip
This zip is not flashable You have to put it in /system/media/
(This is an external link, not an attachment. The file was too large to attach.)
trees-wall.jpg.zip
This is the full resolution wallpaper 3120x2340 (zipped)
trees-boot.jpg
This is a picture of the boot splash.
trees-small.jpg
This is a small, lower quality version of the picture inside trees-wall-jpg.zip. Just as a preview.
Enjoy,
-Jobo

Thanks for this tool, it's amazing
Sent from my raphael using XDA Labs

What are the odds of working on Mi 9T (Davinci)?
PS. Tested and it works like a charm S2