Database Info

Chinese "QsHTC" Launcher and more

Hello guys! I have in my hand a chinese "FG8" cellphone which has an "HTC" Launcher. I dont see any posts about it, so I will share.
QsHtcLauncher.apk
https://sites.google.com/site/ernestovillarreal/home/QsHtcLauncher.apk?attredirects=0&d=1
QsWidgetHTCClock.apk
https://sites.google.com/site/ernestovillarreal/home/QsWidgetHtcClock.apk?attredirects=0&d=1
I can't install them on my Dell Streak, but, hey, you can try it.
The ODEX files are on: test.neto.mx

Don't work on my sgs2

So yeah.. it installs. but nothing more...

this want low resolution display (320x240 or 400x240 or 480x320 ) so low end / mid end devices

This is weird, I've tried in my cell phone too without success... Do you think we need any special file???

it's possible, somethings like framework.res or other device's specific files

is ther anyway to know? I can get those files

netomx said:
The ODEX files are on: test.neto.mx
Click to expand...
Click to collapse
so where is it? i mean the odex file
edited: my bad, found it. thanks

Can you upload all apks&odex and framework files?

Ill get the phone tonight and will try to make a system image.

Here is a dump of the system and data partition. Symlinks may not work ;-)
http://www.multiupload.com/SSWKLFWPEW

ThauExodus said:
Here is a dump of the system and data partition. Symlinks may not work ;-)
http://www.multiupload.com/SSWKLFWPEW
Click to expand...
Click to collapse
How did you manage that? I was looking how to dump the partitions without success!

I found an update archive and unpacked it

ThauExodus said:
I found an update archive and unpacked it
Click to expand...
Click to collapse
I have just founded them too.. but I dont seem to locate any frameworks... it is weird :S

[ROM][SD-Boot]CM9 (4.0.4 ICS) Based on munjeni {WIP}

CANCELLED! GOT A NEW PHONE
Tried so many methods , non worked , I'd keep trying until one works , then I could port hTC Aria's CM10 to hTC HD MINI and redo all this again so that we can have 4.1 on our devices. Till then , I'd love it if munjeni or schlund helped me with the process , because it seems that the kernel extracted from boot.img needs modification , and that every OS needs its own initrd , I hope someone can help.
Update:
I found the required file's details , I have the ramdisk , I have the system.ext2 , what I'm missing is the required kernel , 3.0.1 , I just need a download link to that kernel, can't seem to find any.
Hi,
So I recently got into Android Development and so far , everything is good.
What I'm doing is using munjeni's CM9 ROM as a base for me to get the boot.img and the files in the folder /system/.
I tried to use iPlasm's CM9 ROM but I got some extraction problems , which I'll look into later.
I'm also using the initrd found in Shlund's posts , and the original HD Photon (Froyo 2.2).
I compared the two initrds and found out that the Froyo one was smoother and had lots of unnecessary stuff and that the CM7 one is better , but it may freeze , so I'm going to test both for maximum results.
To-Do:​-Ability to Extract zImage from boot.img Done
-Extract system files Done
-Put System Files into system.ext2 Done
-Use shlund's both kernels and see which one works.
-Create a system.ext2
-Extend Data.ext2's size to allow higher storage on higher SD cards.
If you are willing to help on this project...then please help me with these:
I need an empty system.ext2 in ext3 format (so I can put the system files inside).
Or I need someone to be able to empty the system.ext2 that I have which I got from the Froyo 2.2.
Problems :​Currently I'm facing these problems that may get fixed later:
Cannot delete bin and xbin from system.ext2 , which leads to files to be read when they are not needed.
No empty system.ext2 file present.
Cannot Modify the initrd to increase the space , looking forward to use this code:
When using the kernel from munjeni (extracted) all what happens is G1 logo appearing and nothing else.
Bases :​
zImage from mujeni's CM9 from boot.img
iPlasm's boot.img
initrd from either schlund's CM7.2 or shlund's Froyo 2.2
/system/ from munjeni's CM9
HARET_PHOTON7227.exe from PhotonAndroid Developement
Startup File from schlund's Startup.
All help appreciated
I found a 200mb system.ext2 , however , whenever i put files in it , the next time I mount it I loose everything I put inside , but everything deleted remains deleted. -_-

Glad to see you're trying to do some,
You should not try cm7 kernel with CM9, You're trying to make CM9 SDcard version so forget about cm7 kernel (you may do only for comparing)
please, try the munjeni's boot.img from (update 04.Jun. for rom 24.May.2012) or mine, because the munjeni's rom (24.May.2012) boot.img is older kernel. the new one includes bluetooth fix (NOT Handset Car).
what i see in system.ext2 i don't think you should empty or even use them, it should be writing in command (terminal) that will create those files into EXT2 file.
here is an example: http://forum.xda-developers.com/showthread.php?t=1055923
You can collect more informations in HTC HD2 forums which include SDCard versions,
Have fun,

Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?

thethiny said:
Will try that , because the kernel from munjeni showed me .T...Mobile and then did nothing. hopefully yours work
I just tried your way iplasm , and guess what , I get the same splash screen G1 TMobile.
any thoughts?
Click to expand...
Click to collapse
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.

iPlasm said:
Sorry to say that, this htc mini is not my phone, so I'm so limited to work on it. especially going back to windowsmobile for testing sdcard again. :silly:
Let me say, are you still using both these together froyo and merging them with other? don't do that.. this won't work. froyo things with other ROMs won't work!
You should do one ROM for it's settings, don't catch another things, for example froyo or things.
just those files be their,
1- HARET.exe
2- STARTUP.TXT
and begin to do, and choose the only one ROM you want to make it SDCard version,
about splash screen, it means you didn't applied them correctly, because none of these bootscreen include t-mobile,
I remember the cotulla's version was include AT&T splash screen.
Click to expand...
Click to collapse
I found the problem , I'm using a new system.ext2 created by me , I put the /system/ files of yours inside , then I took the kernel from your rom , and then I used schlund's initrd (because I compared it to the original initrd and found that the only differences were in :
1-splash screen
2-mounting the sd or mounting the ext/sd
3-order of command execution)
so I found out the Cotulla (the original creator of the init inside the initrd.gz ) has put a G1 .T...Mobile splash screen , and when the kernel is loaded , it is loading it as rom , not as sd boot so it launches the splash screen instead of launching the android bootloader , I'll have a look and see and luckily munjeni will reply to the pm I sent him (he helped me with creating the system.ext2 and the initrd)

thethiny said:
Hi,
may you help me with something?
I have a ramdisk (initrd.gz)
and a kernel (boot.img)
and an zImage (kernel main)
however , I cannot seem to be able to extract the zImage , but I did extract the boot.img and the initrd .
In order for me to make it SD Boot , I should allow SD boot from zImage , but I can't open , do you think you can do that for me?
Click to expand...
Click to collapse
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,

iPlasm said:
look, zImage is Kernel, you're doing to open Kernel.. zImage isn't an Archive file. so You don't need to edit or open zImage
Boot.img contains RAMDISK & Kernel, RAMDISK=intrd.gz, Kernel=zImage
You will need to extract the Boot.img from CM9, and convert them to initrd.gz and zImage,
Click to expand...
Click to collapse
ok I already did that , but the zImage extracted from CM7 , doesn't match the zImage from CM7 SD Boot (same ROM , same Dev , diff size).
So I wanna extract the zImage so I can modify the Boot section to SD Boot.

it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android

iPlasm said:
it's not easy to edit kernels, just a Q: have you tried from extracted cm9 two files the kernel & ramdisk and rename them to zimage and initrd.gz to SDCard and see results?
and if you really want to modify zimage (needs unpacking and repack), click here: http://lmgtfy.com/?q=Modify+zImage+Android
Click to expand...
Click to collapse
Yes I tried , also I'm a Windows User , so I use Cygwin , and none of the commands above worked! I tried using Ubunty 12 and I get error at line 12

[Q] Is there any APK to exact the boot.img in the phone

I want to unpack the img but don't want to use in my pc(too confused).
so I want to unpack by the phone,
thank you

ytyyutianyun said:
I want to unpack the img but don't want to use in my pc(too confused).
so I want to unpack by the phone,
thank you
Click to expand...
Click to collapse
I don't think there is. Maybe I'm wrong too.
Basically all these boot.img tools are written in shell/bash and is made specifically to run in Linux distros.
Anyways there is an Android app called, Complete Linux Installer that lets you install any Linux OS in your phone. But I doubt whether boot.img tools work, as it needs various library files for it to work.
On a side note, I guess it would be more complex to do it in phone rather than in PC, if there is some way for it to work.

coolsandie said:
I don't think there is. Maybe I'm wrong too.
Basically all these boot.img tools are written in shell/bash and is made specifically to run in Linux distros.
Anyways there is an Android app called, Complete Linux Installer that lets you install any Linux OS in your phone. But I doubt whether boot.img tools work, as it needs various library files for it to work.
On a side note, I guess it would be more complex to do it in phone rather than in PC, if there is some way for it to work.
Click to expand...
Click to collapse
Thank you for your reply, but do you feel strange that the IMG is created by the recovery, so it is rational that there is a tool about IMG building. then why there is no apk. I mean some professional can extract just from the CWM recovery, I think.

need root
if you wanna get boot.img i think you must be rooted.

k0tsompakos said:
if you wanna get boot.img i think you must be rooted.
Click to expand...
Click to collapse
yes, I root, so I can use the recovery to back and restore,

I think any app that can access zip files in the internal and external memory can extract boot.img.
Like ASTRO File Manager and stuff...

recovery?
You wanna install a rom?
or recovery??
or we speak about boot.img? (Boot img is the boot animation when you turn on your phone.)

k0tsompakos said:
You wanna install a rom?
or recovery??
or we speak about boot.img? (Boot img is the boot animation when you turn on your phone.)
Click to expand...
Click to collapse
Nooooo
boot.img is the kernel (zImage + Ramdisk packed into an image file) that lies in the /boot partition
@ OP - If you want to extract boot.img itself, there are various methods and from CWM recovery like you said. I thought you were mentioning about how to unpack the contents of the boot.img say like zImage, Ramdisk and other files.

0ops
0ops yeah... :silly:
Searching for 1 minute and found this tool :good:
--> [TOOL] Boot.img tools [unpack, repack, ramdisk] <--
( I do not send link cause i am new here and can't :angel: )
It works. Have a nice day

k0tsompakos said:
0ops yeah... :silly:
Searching for 1 minute and found this tool :good:
--> [TOOL] Boot.img tools [unpack, repack, ramdisk] <--
( I do not send link cause i am new here and can't :angel: )
It works. Have a nice day
Click to expand...
Click to collapse
Yes, that's the tool and it works :good:
But as OP mentioned, he wanted to do it within phone, I highly doubt though.

coolsandie said:
Yes, that's the tool and it works :good:
But as OP mentioned, he wanted to do it within phone, I highly doubt though.
Click to expand...
Click to collapse
It could be done using this post http://forum.xda-developers.com/showpost.php?p=20227868&postcount=1124 and a hex editor from play store on your phone. But would be even more fiddly than on pc I would imagine, unless your phone has a largish screen. It could be done though.
If editing the ramdisk, you would need to unpack and repack after editing, which usually requires linux. I recently found http://forum.xda-developers.com/showthread.php?t=2036528 for PC, but have not had a chance to try it yet, seems best solution for OP

coolsandie said:
Yes, that's the tool and it works :good:
But as OP mentioned, he wanted to do it within phone, I highly doubt though.
Click to expand...
Click to collapse
thank you coolsandie, the android is based on linux, isn't it, and if I can, I can install busybox.and using the terminal like Android Terminal Emulator, but I do not know the procedure. like you, it's more complex,

Robbie P said:
It could be done using this post http://forum.xda-developers.com/showpost.php?p=20227868&postcount=1124 and a hex editor from play store on your phone. But would be even more fiddly than on pc I would imagine, unless your phone has a largish screen. It could be done though.
If editing the ramdisk, you would need to unpack and repack after editing, which usually requires linux. I recently found http://forum.xda-developers.com/showthread.php?t=2036528 for PC, but have not had a chance to try it yet, seems best solution for OP
Click to expand...
Click to collapse
it's good tool, it can unpack the boot.img, but as to the kernel, I don't know how to unpack. but this tool add to my favorite, thanks Robbie.

OK, I find the app, names: yaffs, the author I don't know because I found in the search engine. so I also cannot find the course
then the app,

[I9305] boot.img Splash Screen

Hello.
I'm trying to customize the Boeffla Kernel (I9305 port) with a custom splash screen.
I've worked out that I need to use a initlogo.rle file at the root of the ramdisk, however I can't get the image to display properly.
I've atached two images, the first image is what the splash screen is supposed to look like, the second image is a photo of my phone showing how the image turns out.
Any assistance would be greatly appreciated

That typically happens when you're using the wrong size to convert the image. Make sure you're using 720x1280 and not any other resolution

CNexus said:
That typically happens when you're using the wrong size to convert the image. Make sure you're using 720x1280 and not any other resolution
Click to expand...
Click to collapse
I did use 720x1280, so it is the correct size (the image have been been reszied for the forum)
Is there a certain way the mage should be saved (Index, RGB etc?)

djb77 said:
I did use 720x1280, so it is the correct size (the image have been been reszied for the forum)
Is there a certain way the mage should be saved (Index, RGB etc?)
Click to expand...
Click to collapse
What are you using to convert the image to an RLE file?

I'm using the app from this thread here
The only thing I can guess is maybe this app might not be the right one

Still having trouble with it.
I don't want to give up on this, even if it takes me a while. I'm sure it can't be that complicated

BUMP
Any help at all? I'm still stuck with the same issues

Questions:
Is there a initlogo.rle there that you're trying to replace ?
If yes, can you provide both rle files?

There is no file I'm replacing just inserting it. The res is 720 x 1280
Sent from my GT-I9305 using XDA Premium HD app

Can you attach the initlogo.rle that you created?

You can use the same image in the OP
Sent from my GT-I9305 using XDA Premium HD app

That's a PNG, i need the RLE you used to create that double image error.

daedric said:
That's a PNG, i need the RLE you used to create that double image error.
Click to expand...
Click to collapse
Here you go...I had to zip it because the forums don't like RLE images

I'll need to check it at home... but i suspect the rle might be badly encoded.
How did you make it by the way?

daedric said:
I'll need to check it at home... but i suspect the rle might be badly encoded.
How did you make it by the way?
Click to expand...
Click to collapse
Using a PNG to RLE converter that I found on XDA. I dare say that somehting was encoded bad for this to happen.
If I knew exactly how it was to be encoded (or had the right encoder) I would be right hopefully.
It's just that I would probably want to create more splashes in the future, and even though I'd be grateful if this file was fixed, I'd also like to know how to make them properly in future

Here lies the catch: RLE is a means of encoding anything.
IF my memory doesn't fail me, you need a RAW file encoded in RLE. Now, you might need a RGB565 RAW file...
Take a look: http://forum.xda-developers.com/showthread.php?t=1516711

daedric said:
Here lies the catch: RLE is a means of encoding anything.
IF my memory doesn't fail me, you need a RAW file encoded in RLE. Now, you might need a RGB565 RAW file...
Take a look: http://forum.xda-developers.com/showthread.php?t=1516711
Click to expand...
Click to collapse
Still seem to be having the same issues.
Is it possible since there was no initlogo.rle there that it isn't properly supported by the kernel?
I know that it does show something when I put one there, but maybe there's something that needs adding to show it properly.

I've been digging the source code looking for logo loading code... and i suspect we MIGHT be missing something, i'm failing to find this instruction: load_565rle_image

daedric said:
I've been digging the source code looking for logo loading code... and i suspect we MIGHT be missing something, i'm failing to find this instruction: load_565rle_image
Click to expand...
Click to collapse
So it might not support that format at all by stock. It's weird how it does read that file though.

djb77 said:
So it might not support that format at all by stock. It's weird how it does read that file though.
Click to expand...
Click to collapse
You should pm DerTeufel1980. He's managed to accomplish adding a splash screen to his kernel for the Note II.

[Guide] Change Xiaomi MIX 2S (polaris) boot logo

Sagit Logo Generator for Xiaomi MIX 2S
Thanks @wangchuanyes for test! https://github.com/moonheart/sagit-logo-gen/issues/1
First download this File View attachment sagit-logo-gen-MIX2S.zip
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM .
Source: https://github.com/moonheart/sagit-logo-gen/tree/MIX2S
Thanks @huhu2207 for advice (binwalker).

Nice tool !!!!! Awesome
Do we have limit about size(in mb) or size (in pixels) ?

thiefxhunter said:
Nice tool !!!!! Awesome
Do we have limit about size(in mb) or size (in pixels) ?
Click to expand...
Click to collapse
up

thiefxhunter said:
Nice tool !!!!! Awesome
Do we have limit about size(in mb) or size (in pixels) ?
Click to expand...
Click to collapse
Yes. You should keep the original image height and width, and color depth. If you see file size reduced after saving, it's okay as long as you do not change pixels and color depth.
I recall, for example, 01.bmp extracted is around 20M but after you save it it's just around 5M. Feel safe, it's correct.
The newly generated logo binary file should be 19.5M, according to my memory. I don't have that file on hand now.
And if you broke it, you'll end up with a strange bootloader UI (with volume keys to select different modes), but don't worry, just flash a correct logo.bin and you'll make it running again.

EraserKing said:
Yes. You should keep the original image height and width, and color depth. If you see file size reduced after saving, it's okay as long as you do not change pixels and color depth.
I recall, for example, 01.bmp extracted is around 20M but after you save it it's just around 5M. Feel safe, it's correct.
The newly generated logo binary file should be 19.5M, according to my memory. I don't have that file on hand now.
And if you broke it, you'll end up with a strange bootloader UI (with volume keys to select different modes), but don't worry, just flash a correct logo.bin and you'll make it running again.
Click to expand...
Click to collapse
Alright , thank you again for that awesome explanation . Have a nice week !

Anyone has a "Mix" logo just like the boot animation?

Hi , i don't know why
But whenever i flash the logo.img created by your program.(even when using images you provided)
It always booted into a weird bootloader interface.
i'm on miui 9.6 china.
Wonder if anything has to do with this?
Can you help fix it?
Thanks!!!

Hello,
I will use this to remove the "unlocked" message at boot.
It's possible to simply copy 01.bmp to 03.bmp then recompile the image? (I ask due to size of 01.bmp is higher than 03.bmp)
Thanks

bartito said:
Hello,
I will use this to remove the "unlocked" message at boot.
It's possible to simply copy 01.bmp to 03.bmp then recompile the image? (I ask due to size of 01.bmp is higher than 03.bmp)
Thanks
Click to expand...
Click to collapse
I'd like to do that as well, "unlocked" seems so damn wrong to be displayed

evronetwork said:
I'd like to do that as well, "unlocked" seems so damn wrong to be displayed
Click to expand...
Click to collapse
I've created this Mix2s image (https://mega.nz/#!51UDyQoT!3b9sL2j4dNDW8WUNck39xVfNNuClqED2rZGw7kU5ZQs) using the files from OP to remove the "unlocked" message on boot splash.
You can use it if you want...

bartito said:
I've created this Mix2s image (https://mega.nz/#!51UDyQoT!3b9sL2j4dNDW8WUNck39xVfNNuClqED2rZGw7kU5ZQs) using the files from OP to remove the "unlocked" message on boot splash.
You can use it if you want...
Click to expand...
Click to collapse
Ready to use file? hmm
So it's just "fastboot flash logo xiaomi_mix2s_logo_image_removing_unlocked_message.img"
How safe is this? did you use the very same file?

Of course, I have used the same file that I've uploaded to my mega and is working fine. You can use it or generate using the op generator, but in any case I'm not responsible if you brick your device, blah, blah, blah...
evronetwork said:
Ready to use file? hmm
So it's just "fastboot flash logo xiaomi_mix2s_logo_image_removing_unlocked_message.img"
How safe is this? did you use the very same file?
Click to expand...
Click to collapse

Nice, ill put my contact information to make it harder to sell if it gets stolen or lost

Any chance this can be updated for the new format? New logo won't overwrite the bootloader splash.

xumixu said:
Nice, ill put my contact information to make it harder to sell if it gets stolen or lost
Click to expand...
Click to collapse
Great idea, so:
Fastboot, boot image etc ...with details, orange fox(instead of twrp) with pin locked and rom locked displaying personal info
This won't be an easy sale if stolen(hopefully not)