[Recovery] Customization Engine version 2.0 - Color,Background,ProgressBar Mod !!! - Nexus One Android Development

Hey,
Versions supported for colormod :
MAGIC/HERO/DREAM - 1.7
Nexus - 1.7 For 1.7.0.1 amonra recovery, refer to this Link
Versions supported for noncolormod :
All recoveries, even koush's except you wont see the difference cuz he never calls on the png's
Thanks to amon_ra for his recovery and thanks to all those he thanked
Script is based on the dev kitchen by dsixda. I removed everything that was not needed for this task.
Requirements : Device drivers properly installed
Windows Operating System
Instructions :
1. Download the 7z file and extract.
2. You will get 3 folders and 2 batch files.
3. Run either batch.
INFO:
Noncolormod just allows you to change background image and progressbar
Colormod batch does what the noncolormod does + allows you to customize the colors inside the recovery
Guys 2 tips :
1. If image is layered please flatten it in photoshop or edit in paint.
2. Use this tool to configure a range of colors. Just grab the decimal values and feed in the script.
FYI: This will not work with Koush's recovery as he ignores the background png
PS : Donot ask for assitance from amonra if you are using the repackaged recovery image produced by this script. He WILL ignore u
PS : I AM NOT RESPONSIBLE IF YOU ARE NOT CAPABLE OF FOLLOWING INSTRUCTIONS. I EXPECT A DECENT LEVEL OF UNDERSTANDING/TECHNICAL ABILITIES FROM THOSE WHO ARE USING THIS SCRIPT.
----------------------------------------------------------------
Update
*Added menu with additional properties
*Can now flash/boot recovery from menu
*Added option for size check
*Allows customization of progressbars
*Keyboard-console fixed for G1 users
*Text-color customization
*Updatescript color customizable
*ProgressBar height adjustable
*A LOT MORE STABLE
*Thanks to amonra no more trackball issues should occur on Hero
----------------------------------------------------------------
Future Updates Expected:
Will bring this to the droid, cliq and desire
Will try to see what else i can make user-optional
Preview :
{
"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"
}
Heres the background for those who asked:

sweet,cant wait to try!

Care bears or nothing at all.

B3astofthe3ast said:
Care bears or nothing at all.
Click to expand...
Click to collapse
Well you are certainly entitled to your opinion. I just feel that Android is all about customization and the recovery should be no different.

One that I made ... if I get more time I will upload more
*** EDIT ***
This one looks really good with the green text. If your looking to try one out use this one as your first test. The mod is stunning!

Thats pretty nice, did you have any problems getting this to work ?

Daneshm90 said:
Thats pretty nice, did you have any problems getting this to work ?
Click to expand...
Click to collapse
No works great and the pic I uploaded looks fantasic in the recovery.
This option should have been here long ago!
What about text color? Any plans for your mod?
*** EDIT ***
Here are more:

Yea i was going to look into that, i hope it would be a simple hex edit, if not, i can always compile a couple of them with different colors and make a batch where the user selects which color they'd like. I will also be adding options to change the image that appears when flashing a rom, the loading bars, etc,etc....

Daneshm90 said:
Yea i was going to look into that, i hope it would be a simple hex edit, if not, i can always compile a couple of them with different colors and make a batch where the user selects which color they'd like. I will also be adding options to change the image that appears when flashing a rom, the loading bars, etc,etc....
Click to expand...
Click to collapse
Would the size increase effect the phone in a negative way down the road?
Like limited space for the recovery? What size is the area parition this expands to?
Also, what about the font size? any way to increase this at all?
I love this mod BTW

great job, works really well and very easy to do

Very nice, Was getting tired of stock recovery look on my N1
www.youtube.com/user/exclusivegslick

1wayjonny said:
Would the size increase effect the phone in a negative way down the road?
Like limited space for the recovery? What size is the area parition this expands to?
Also, what about the font size? any way to increase this at all?
I love this mod BTW
Click to expand...
Click to collapse
You cannot go over the space acquired for ur recovery. Im not too sure but i think its 5mb. If you do cat /proc/mtd you will see your partition and sizes. Not sure what units its in but i remember if my png's are too big in size, then it fails to flash. This is no different than flashing a recovery when an update comes out. Obviously the more you flash the shorter your lifespan of your devices cause nand has a certain number of write cycles.

Daneshm90 said:
You cannot go over the space acquired for ur recovery. Im not too sure but i think its 5mb. If you do cat /proc/mtd you will see your partition and sizes. Not sure what units its in but i remember if my png's are too big in size, then it fails to flash. This is no different than flashing a recovery when an update comes out. Obviously the more you flash the shorter your lifespan of your devices cause nand has a certain number of write cycles.
Click to expand...
Click to collapse
Great information, 5MB cause I saw it shoot up about a meg in size and have flashed a 4.* MB file already but was asking out of curiosity.

The background is static through all the menus but wiping the data / factory & flashing.
I wiped the dalvik-cache and the image stayed but when i wiped data/factory the image went away, background went black.
Then the black background stayed until reboot of the recovery but upon reboot the picture was here
It does this for flashing a rom and wiping, pretty much anything with the status bar.

Its not a bug, if u look a a couple of posts above i mentioned it. When you flash/wipe something a different image is called. Next update will have modifications for that as well.
FYI: Due to partition size limitations. By adding the option of customizing the flash_rom/wipe background, you have to make sure your size doesnt go over limit.

Daneshm90 said:
Its not a bug, if u look a a couple of posts above i mentioned it. When you flash/wipe something a different image is called. Next update will have modifications for that as well.
FYI: Due to partition size limitations. By adding the option of customizing the flash_rom/wipe background, you have to make sure your size doesnt go over limit.
Click to expand...
Click to collapse
Ah I missed that post , good stuff. Cant wait for the update!
Cheers
** EDIT **
You should update your first post like the G1 post and include some screens. Just a thought...

Ok so the recovery partition is 5.2MB. Update will come out in a matter of hours. I will try to see if i can put a size restriction in the batch file that checks for this.

Re: Recovery Background Changer
Update available : Added menu's with more options

the file is corrupted; when i download from the OP link and try to extract, it gives me error saying the file is corrupt; i get this message from WinRAR:
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygpng12.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygpopt-0.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygpq.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\lib\gtk-2.0\2.10.0\printbackends\cygprintbackend-file.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\lib\gtk-2.0\2.10.0\printbackends\cygprintbackend-lpr.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygreadline6.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygreadline7.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygsasl2-2.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\lib\sasl2\cygsasldb-2.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygserf-0-0.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygsigsegv-2.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: CRC failed in other\bin\cygSM-6.dll. The file is corrupt
! C:\Users\Desktop\RecoveryChanger.7z: Error - operation failed

Re: Recovery Background Changer
hmm let me reupload then. sorry about that.

Related

[10 Apr][DL Desire v5.xx][Always FASTER][kernel:freak]

{
"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"
}
V4.31.44.12
v4.32.44.12 applied with theme from he_stheone64.
Important note:
I create the Desire Series together with freak, and also got a lot of help from many technical experts, so, please thank them as well if you like the build.
This thread is for discussing the SD builds only.
All the releases please check: http://forum.xda-developers.com/showthread.php?t=962600.
Please discuss the NAND builds at: http://forum.xda-developers.com/showthread.php?t=913597&page=457
Before flash or install new builds:
1. DON'T expect it will work out of box.
2. DON'T expect it will be as light and fast as Gingerbread.
3. DON'T expect that some legacy problem will disappear
4. Reboot your phone at lease twice after flashing or installing, after 1st boot into setting screen, long press the right button to recall the boot menu, reboot. Can not use /Update_DL method to install app before 3rd reboot.
5. For this version, due to the base has been changed throughly, can not use previous data.img or ext4, remove existing data.img and set data_img=1 to let system generate one for you, or set format_ext4=1 to format your ext4 if you are using ext4
6. DON'T set any config for 1st installation except data_img=1(for data.img) or format_ext4=1(for ext4 user). if your have tmous phone, no need the config.txt.
7. For SD or magldr, if 1st installation failed, must delete the system.ext2 file under /Desire_DL to let system convert it again.
8. Use Windows notepad create a file named config.txt, save it under /Desire_DL, only need to put the necessary config inside it, say:
data_img=1
Important Release Note
This build is another endeavor by freak and me to improve the performance of our build, now, besides our existing optimization methods: squashfs, ext4, etc, this build has been added in the following features to improve it performance furthermore:
1. AUFS + SquashFS.
this is the 1st android version that can support the aufs+squashfs, we
even worked with the author of aufs to make it usable to android.
a lot of innovations within this build from the technical perspective,
for users, the benefit of it are:
a. high performance
b. despite of squashfs is used to reduce the size of file system, user
still be able to change any file directly with the power of aufs.
c. a lot of frequent accessed files are squashed and loaded into ram
to improve the performance.
2. RE-Odexed.
there flood a lot of misleading messages on xda of odexed, same as
squashfs. Odex can actually improve system performance, and at the
same time, reduce the whole system's size(because the odex is
optimized dex), and odex build has less chance of system crash that
lead to wipe the davlik-cache. an odex build doest not generate the
davlik-cache which is odexed.
3. Re-Engineering Sense:
All the apps and framework were re-compiled and reduced the size to get the lowest RAM consuming and Highest performance.
4. Merged DesireZ and DesireHD into one.
Merged the advantage features from both DesireZ and DesireHD into one build.
Please refer to this thread for download and detail info of v5.xx
DOWNLOAD
DL Desire v4.31.44.12
Light themed with power notification and battery percentage.
DL Desire v4.32.44.12
Themed with he_stheone64.
Converted system.ext2 for DL.Desire.v4.31.44.12, thanks mamdouhn
part 1
part 2
part 3
DL.Desire.v4.32.45.13 SD only with DLZ_update_20110307-2034
part 1
part 2
part 3
Note: you are always appreciated if you can help upload the converted system.ext2 for SD/MAGLDR, how to do:
after your system successfully boot into sense, and feel the performance is great, delete the system.img and data.img, zip the /Desire_DL folder and upload it, for some ppl have problem of converting the system.ext2 from system.img.
Click to expand...
Click to collapse
How to config SuperInit v4.4(advance user)
Bugfix and enhancement
Upgrade to v4.32.45.13 and v4.31.45.13 (yes, we upgrade the SuperInit and kernel together.)
How to ask for help:
1. First, make sure you ask at the proper place, this thread is only for ask the question related to the NAND, please ask questions related to SD or MAGLDR at http://forum.xda-developers.com/showthread.php?t=881937
2. Please indicate the following information when asking for help:
a. your phone modal: EU or TMOUS modal.
b. your loading mode: NAND, SD or MAGLDR
c. Please post the content of init.log(this file is on the root of your sdcard).
3. Please be patient and polite.
4. We(myself and freak) will only answer question that follows the above rules, thanks!!!
Naming convention
1. the 1st digit is for the build base, say DesireZ v4.xxx, is for the v4.0 base which based on the HTC RUU 1.85.
2. the 2nd field is for the subversion, normally, x.0 means the first relase which should based on a totally new base, and from x.0 till x.3, there will be a lot fix and testing, if you want a stable version, DON'T use it, and the build will be stabilized after x.4.
3. the 3rd field is for the init version, currently, our init is at v42, which is also not a stable version.
4. the 4th field will be used for the kernel, currently, freak is working on it, and will have the 1st kernel soon.
Video
v2.1
v2.6
Thanks happyendin21 for recording this wonderful video, which demonstrate my build v2.1 and v2.6
Older SD version:
DL DesireZ v1.0
DL DesireZ v0.3n
For version before v3.0
- extract "desire_z" folder on the root of your SD card
- Run "CLRCAD.exe" then "haret.exe"
[/COLOR][/B][/QUOTE]
Special thanks to
wingmann, E Lin, D69K, McNiceGuy, vlad48, RicarduZonta, akshan, Alexei, Kam,
adeeb, Shane Grosser, Kenneth Davis, Muhammad, Joe, parzifal, F-bone,
TruePlaya, Eric, kajos, b0nni....
[/SIZE]
Click to expand...
Click to collapse
Thanks to
- Cedesmith, Cotulla, ownhere, melethron, ocm, Rajko, LeTama, Hastarin, NetRipper, Markinus, gauner1986, Takaaki, iamgpc and others I may forgot.
Click to expand...
Click to collapse
Ah, fresh meat
Hmm Downloading.
all cedesmith fans must try this , please make changelog for next update
Thank you so much
its rebooting on the HTC screen
It works but wifi DHCP is not working (setting it to static IP works just fine) and HTC twitter (peep?) is missing?
Some screens please...
Sent from my HTC HD2 using XDA App
The Rom is excellent
really fast
so far everything is working apart from being unable to connect to WiFi ( stuck on Obtaining IP address.... )
Any Solutions ??
shahzads said:
its rebooting on the HTC screen
Click to expand...
Click to collapse
This build will not create the data.img automatically, hence, you have to supply a data.img file,recommend to use the one I listed above.
Screen Shots
WiFi do not work.
Thank you ,i like this ROM
Wow This one out of the blue
I am flabbergasted by this rom vast stable
Speechless
only minor and yes i am about to say this again Wifi doesnt work
dandiest said:
This build will not create the data.img automatically, hence, you have to supply a data.img file,recommend to use the one I listed above.
Click to expand...
Click to collapse
thanks for telling us that can you please put this info on the 1st post too
Renegade_Rulez said:
It works but wifi DHCP is not working (setting it to static IP works just fine) and HTC twitter (peep?) is missing?
Click to expand...
Click to collapse
same issue here, how do i set it to static ip? do we have to enter in the APN? i thought it was auto
Renegade_Rulez said:
It works but wifi DHCP is not working (setting it to static IP works just fine) and HTC twitter (peep?) is missing?
Click to expand...
Click to collapse
Yes, I removed the twitter and some other applications, if needed, I can put the pkg here, you just put it under /system/app.
ajax0666 said:
I am flabbergasted by this rom vast stable
Speechless
only minor and yes i am about to say this again Wifi doesnt work
Click to expand...
Click to collapse
Believe it's the problem for the file permission, I only managed to fix the pppd due to I don't have wifi here, maybe will try to fix it later.
I will be visiting this forum often to see the progresses of this build.
Other thing i came accros was that titanium backup cant get root permission
dandiest said:
Yes, I removed the twitter and some other applications, if needed, I can put the pkg here, you just put it under /system/app.
Click to expand...
Click to collapse
Yes, please post the twitter pkg.
Thanks

[ROM][R800X][2.3.3]-Cola- Geared Towards Speed

Made for locked bootloader R800x. I haven't tested this on anything else
Use at own risk
This ROM is made for gaming.
(archive is 54 megabytes)
this is stripped down and geared to speed. No fancy UI. No lag causing effects.
App drawer opens and closes in 1 fraction of a second.
{
"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"
}
Banners to show your support. Feel free to use
Features:
Based on 2.3.3 R800X Stock ROM
------------------------------------------------------------------------
Code:
numerical battery bar
fast photo gallery
host file edited to block advertisements
Script manager integrated
Hard to kill launcher
Supercharger script integrated and activated to run on boot
CWM Recovery Pre-installed
All bloatware removed.
boot animation replaced
optimized for speed
optimized file size
removed camera shutter sounds, removed video shutter sound
remove lag causing elements
file manager built in
usb debug and unknown sources turned on
Install guide:
-Make sure your battery is atleast 50% for saftey reasons.
-Make sure you are rooted & have CWM Installed
- Extract Cola_X.X.X Archive File
-Place Cola_X.X.X Folder inside clockworkmod/recovery/ located on your SD card. (If the folders dont exist create them)
-Reboot phone and push down on volume button till Recovery screen comes up.
-Select - "Backup and Restore" option with volume rocker and hit HOME.
-IMPORTANT: Make a backup of your current ROM incase you want to revert later.
-Hit back to main menu of recovery and select wipe cache partition.
-select -Backup and Restore/ Restore / Cola_X.X.X then hit HOME
-Wait for the files to finishing flashing and REBOOT SYSTEM NOW option.
Click to expand...
Click to collapse
Known Bugs:
ROM breaks with factory data reset. do not perform it.
just restore nandroid if you need to clear data / restart fresh
Hope you Enjoy.
If you have any questions just ask here I will try to help.
If you have any suggestions to make ROM faster or smaller please let me know.
Future plans:
Integrate latest market into rom
Integrate other tools and spare parts
Optimize for more speed
New Version Cola6
http://www.sendspace.com/file/heowpx
second download location.
http://tinyurl.com/6uwywwf
1.0.2 changelog:
Integrated persistant supercharge script (faster multi task and such)
Integrated Script manager
Added hard to kill launcher
Removed unnecisary files for lower size
Fixed app drawer problem
Lowered archive size.
1.0.3
changelog:
added numerical %' battery bar
removed 3d photo gallery (creates lag) replace with low memory/ low size photo gallery
removed other file systems not needed
fixed few minor bugs
total archive size reduced to 56 megabytes
1.0.4 changelog:
integrated latest market.
made archive smaller (54mb)
1.0.5 changelog:
fixed google talk error that was making rom unusable.
​
Thanks, I feel bad for r800x owners they need more stuff.
Sent from my R800i using Tapatalk
Clienterror said:
Thanks, I feel bad for r800x owners they need more stuff.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
You're welcome
If you have any improvements please let me know.
Please upload some pictures of this room.
And thank you
New pictures coming soon.
If you do a factory data reset you will loose super charge and hard to kill launcher properties
Also it will remove home button binding in /system/usr
If you need to reset do it from CWM not in privacy options.
Awesome! Will try this out this weekend.
TheAugust said:
Awesome! Will try this out this weekend.
Click to expand...
Click to collapse
cool! hope you like!
Can someone upload as zip instead of 7z
doua27 said:
Can someone upload as zip instead of 7z
Click to expand...
Click to collapse
I would help but I'm not at the computer right now.
Just use winrar or 7zip if your on windows
both are free
does this optimises the battery?
Hogwarts said:
I would help but I'm not at the computer right now.
Just use winrar or 7zip if your on windows
both are free
Click to expand...
Click to collapse
Thanks but I'm not at a computer too but I want to test it right now lol
Nice ROM mate, how about making the same for R800i too?
Magnumutz said:
Nice ROM mate, how about making the same for R800i too?
Click to expand...
Click to collapse
I would but I don't have a 800i to test with
sorry!
Also tomorrow I'm adding percentage battery for
Ease of use / function
Trancicted said:
does this optimises the battery?
Click to expand...
Click to collapse
Yes and no.
Ill add a script tomorrow that will improve battery life
But yes it already does because of low memory use
I have an R800i, so it won't work with mine?
Trancicted said:
I have an R800i, so it won't work with mine?
Click to expand...
Click to collapse
Well the R800x uses CDMA instead of Gsm so you wouldn't have phone service lol
other than that I don't know.
You could test for me. I'm sure the phone wont work tho. Just make a backup before you flash
Can over clock on this rom
nick4nick said:
Can over clock on this rom
Click to expand...
Click to collapse
Not yet. but I hope we can soon.
It's setup to be very fast tho. probably the fastest that it can be without overclocking.
I just added images and other new information to the first page.
Here is one I just added
The next update coming is going to integrate new market into rom
You know what would be missing in there aswell?
the T-Mobile Theming Engine >_<
Thanks for your hard work

[Converter] Web Converter Creates Rezound PH98IMG.zip 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"
}
I wrote a web converter that takes a properly sized image (720x1280) converts it into a IMG file and packages it up into a zip file which you can download, rename to PH98IMG.zip, place on your External SDcard and flash via the bootloader.
YOU MUST HAVE S-OFF for this to work!
This is also ONLY for the Rezound.​
How it works.
o You create an image.
o Image must be 720x1280 in size
o Image must be in png, jpg or gif format
o UPDATED WEBSITE: You go to the converter website: http://droid.tnet.com and upload your image
o It converts the image into a downloadable zip file for you to use.
What the converter does
o checks that the image uploaded is the right type
o checks that the image is the correct dimensions
o converts the image to a IMG file
o adds the new IMG file to the android-info.txt file into a template directory
o zip's the contents up using a unique ID
o Presents you with the ability to download the file.
What you need to then
o After you download the file. rename it to PH98IMG.zip
o Place it onto your external sdcard of your Rezound
o Enter into bootloader mode and flash it
When you reboot, the new splash screen will be displayed.
Reference:
The contents of the android-info.txt file is:
modelid: PH9810000
cidnum: VZW__001
mainver: 2.01.605.11
hbootpreupdate:12
Like ANYTHING YOU FLASH... You are responsible for your own devices. These should be fine to use, but make sure you have backups in case!
UPDATED! Website Converter Page: http://droid.tnet.com
This will change soon, but I will update it in this post when I do.
Additional Functions Planned
In the works....
o Upload an IMG file and convert it back to a jpg, png or gif.
o Ability to download just the splash1.img screen from already processed screens.
o Perhaps support for other phones...
Updates
2012-04-29
o Change filename formats for better sorting and to allow additional features.
o Turned on Hot Link Protection. Some users were hotlinking to the thumbnails on the Gallery.
Previous
o Added ability to download previous processed splash files
o Updated website to provide more details and new capabilities.
2012-05-11
o Over 200 Flash Screens generated with more than 100 in the gallery to view/download
CLICK FOR GALLERY OF IMAGES PROCESSED
2012-06-10
o Added EVO 4G LTE Version of this tool
Great work!
you can also pull the splash out of the zip file and flash with fastboot if you want:
fastboot flash splash1 splash1.img
Sounds great plan on trying this out tomorrow. Thanks.
Sent from my Rezound
FANTASTIC!!!!!!!!!!! This definitely helped me after 4 hours of infinite fail
Is there any chance you can make this into a non-site based app/script for windows. Sorry if that is asking too much.
I will be donating asap.
Thanks again
Think I will try this out tonight...thinking Rush's Starman would look killer..
Sent from my Rezound
abby_nitewolf said:
Is there any chance you can make this into a non-site based app/script for windows. Sorry if that is asking too much.
Click to expand...
Click to collapse
There already is a windows script. It is called SplashFlasher. It is included in a post: http://forum.xda-developers.com/showthread.php?t=1006999
Careful if you use it because it includes code to wipe your Internal SDcard. The android-info.txt in his script includes
Code:
DelCache:1
DelFat:1
which should be removed if you are going to use it. I based the web converter on and found that out while testing (Thanks con247).
I was using that script until I built the web converter. The web interface is really a lot easier... just create the image, and upload and it is all done without any errors. The script does have the ability to flash the splah1.img file to the phone though.
thank you!!!
This is awesome. I will definitely try it out. Not sure on showing what others have done though. For instance, currently there is one that looks to be someone's kids on there. It's a good idea, but I could see it as posing a problem down the line.
zalez said:
Not sure on showing what others have done though. For instance, currently there is one that looks to be someone's kids on there. It's a good idea, but I could see it as posing a problem down the line.
Click to expand...
Click to collapse
Think there are more pro's than cons there... gives people ideas of what they may want and for others to participate that don't have any graphic skills.
I've been watching it and have already removed a few that were not appropriate. They also roll off after 20, The current page is a temp page with the real site in the process of being built.
The full site will have an option for the poster to check off whether the image/zip can be public or not after conversion along with a number of additional options such as downloading just the splash1.img file, and converting an img file back to png, jpg or gif.
Currently, all resulting files are pretty anonymous with so unless they include names, nobody would know who created what. Same idea as http://www.acme.com/licensemaker/licenses.cgi
Thanks for the tool.....made it a breeze to quickly make this....
Sent from my Rezound
This saves so much time. Awesome work!! Thank you!!!
Updated Link to New Website
UPDATED Links in OP to the new website. This is a more general website that will have other tools and tips in the future. It has had the Web Generated added to it along with details instructions on how to use the zip file in the bootloader with screen captures and more.
New Website: http://droid.tnet.com
Awesome tool!!! It doesn't get any easier or BETTER than this.
Great work... and THANK YOU!
Actually it does... Should be adding the ability to create recovery flash splash pages this weekend.
Via Rezound using XDA Premium
Great job on this, i just did mine....
Thanks!
I hate maintenance lol
Sent from my ADR6425LVW using Tapatalk 2
evilstewie23 said:
I hate maintenance lol
Click to expand...
Click to collapse
Yup.... it really had to do with the mail system, not the generator, but since the generator sends me an email when it does something, I needed to take it offline. The email allows me to make sure someone hasn't uploaded something objectionable that might be in the gallery.
Rebuilt the entire mail system from the default one installed by the system to the same one I use on larger mail servers to get ready to do some other stuff. Took a lot longer than I thought it would as I am not as familiar with that OS platform.
Someone (perhaps you?) just made a Bulls logo, I added a slightly different non-squeezed version. It is in the gallery.
krelvinaz said:
Yup.... it really had to do with the mail system, not the generator, but since the generator sends me an email when it does something, I needed to take it offline. The email allows me to make sure someone hasn't uploaded something objectionable that might be in the gallery.
Rebuilt the entire mail system from the default one installed by the system to the same one I use on larger mail servers to get ready to do some other stuff. Took a lot longer than I thought it would as I am not as familiar with that OS platform.
Someone (perhaps you?) just made a Bulls logo, I added a slightly different non-squeezed version. It is in the gallery.
Click to expand...
Click to collapse
Ya it was me. Thanks man I tried for no joke, 2 hours to get it unsmooshed but it didn't work. Thanks for this converter I really appreciate it and so do many others
Sent from my ADR6425LVW using Tapatalk 2
Update 2012-05-11
o Over 200 Flash Screens generated with more than 100 in the gallery to view/download
CLICK FOR GALLERY OF IMAGES PROCESSED
thankkkkkkkkkkk youuuuuuuuuu =)

[WIP]LOGO.bin File Format and Modding

I haven't had enough to get a One now, but I'm pretty interested in the phone. Yesterday I saw a thread on Chinese forum, saying that LOGO.bin contains the image shown in fastboot mode, and thus everyone can choose his preferred image (like CM's) even if he uses ColorOS. So I tried to extract the bitmap from LOGO.bin and replace it with my own picture.
Now I've succeed PARTIALLY in identifying the BIN file format and extracting the images. There's no enough time to dig into replacing the pictures though, but I think it won't be hard.
Here is what I find, for those "aggressive" themers and ROM devs who want custom boot splash screen:
The BIN file starts with the following structure:
C:
struct SPLASHHEADERINDEX {
char magic_code[8]; // = { 'S', 'P', 'L', 'A', 'S', 'H', '!', '!' };
int img_width;
int img_height;
int reserved; // What's this? I haven't figured that out.
int img_offset[6];
char padding[468]; // The header is 512 bytes. Thanks [user=5757424]@chillstep1998[/user] !
};
Right after this structure, the raw data of boot splash image begins. Every pixel is described by 3 bytes in B-G-R order. The pixels begin at the upper left corner and then stored in the order of left to right & up to down. You can read (img_width * img_height * 3) bytes and write them into a BMP file. NOTE that BMP files require 4-pixel alignment for every horizontal row (Google that for details, otherwise you will get a "Broken image" info in image viewers) In order to avoid this problem, I wrote a simple program in VB.NET and used Bitmap.SetPixel and Bitmap.Save to solve it.
This is the VB code for this procedure. (I can't do GUI programs in C++...)
Code:
Dim bmp As New Bitmap(img_width, img_height)
Dim color As Color
For y = 0 To img_height - 1
For x = 0 To img_width - 1
b = fs.ReadByte 'fs is the FileStream of BIN file. Already sought to correct offset.
g = fs.ReadByte
r = fs.ReadByte
If b = -1 Then b = 0
If g = -1 Then g = 0
If r = -1 Then r = 0
color = color.FromArgb(r, g, b)
bmp.SetPixel(x, y, color)
Next
Next
There are some zeros after (img_width * img_height * 3) bytes. I don't know what's for...
Then let's look at the other images. Their offsets are in the img_offset array of SPLASHHEADERINDEX. They have headers like this:
C:
struct SPLASHHEADERNONINDEX {
char magic_code[8]; // "SPLASH!!" without \0
int img_width;
int img_height;
int reserved; //Still don't know
char padding[492];
};
Right after the structure is the raw data. Process that as mentioned above.
The image at img_offset[0] is the one shown in fastboot mode
[1] is AT current test (original Chinese: AT电流测试. What's AT?)
[2] is RF test
[3] is WLAN test
[4] is charging
[5] is low battery warning
Previews for new images are coming soon...
However: there is one bug: the images extracted are "mis-placed". You need to move 0x0 to 164xHEIGHT (163xHEIGHT maybe) area to the right side of the image to get the correct pic. The images extracted from ColorOS' LOGO.bin are listed as follows:
SPOILER:
[0]
{
"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"
}
[1]
[2]
[3]
[4]
[5]
Boot splash
Does anyone know the cause of this mis-place problem? Although that can be solved easily in the code, but it's not very reliable. Maybe it's related to the "reserved" member?
Since the format is rather simple, modding and repacking will be easy. When I get some free time I'll make a tool for this...
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
dlhxr said:
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
Click to expand...
Click to collapse
Can't come up with any reason why there should be signature check for logo, especially when we can use home-made modem fimwares and kernels without any problem... But it's worth considering since there's "reserved" member. ColorOS gets 0x00 0x00 0x00 0x00 and CM 0x00 0x00 0x00 0x01 in boot splash's "reserved" int. Haven't checked other 6 images though.
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
treChoy said:
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
Click to expand...
Click to collapse
Wow I didn't notice it before... This thread is revealing secrets of the magic and pushing it further
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
updateing said:
Wow I didn't notice it before... This thread is revealing secrets of the magic.
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
Click to expand...
Click to collapse
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
treChoy said:
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
Click to expand...
Click to collapse
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
updateing said:
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
Click to expand...
Click to collapse
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
treChoy said:
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
Click to expand...
Click to collapse
I have once seen somewhere that you can find specific .hex file (e.g. MPRG8960.hex for MSM8960) to download into the phone by QPST Service Programming. Then the phone will boot into mass storage mode, where computer will recognize the phone as a removable disk drive. Now the whole internal storage is "mounted" on the computer and you can use dd to restore then.
(Google'd and it says only QHSUSB_DLOAD need the hex file. QHSUSB_BULK should be mounting the internal storage to computer automatically and dd will be available. Not sure about that. Example: http://forum.xda-developers.com/showthread.php?t=2582142&page=1)
yeah the header is 512 bytes. Now the images are all correct :victory:
Flashing a bad LOGO.bin did send me to the QHSUB_DLOAD mode and I tired rebooting holding down all three buttons. It did seem to work but after a bit it seemed to just boot on its own. Then I just used an adb shell to run dd commands to flash the proper .bin and all has been well since then
Still have been to busy with our newborn to look into anything deeper but between this thread and the one by @chillstep1998 and treChoy and other it looks to be all good!
Glad all is coming together on this end, keep up the great work all
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
m9j_cfALt said:
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
Click to expand...
Click to collapse
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
updateing said:
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
Click to expand...
Click to collapse
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Reive said:
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Click to expand...
Click to collapse
I don't have a OPO to test, all these analysis are theoretical. So I may not be able to help. Sorry...

Themes / Apps / Mods [DEV] Kernel Flasher

{
"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"
}
Kernel Flasher is an Android app to flash, backup, and restore kernels.
Features
Flash partition images and AK3 kernel zips
Backup and Restore kernel partitions
Mount, Map, and Resize vendor_dlkm
Save dmesg, logcat, and ramoops
Check for kernel updates
Notes
When making a backup of the active slot, to save time, it is assumed that the kernel on disk is the same as the running kernel. The Check Kernel Version button can retrieve it from disk prior to backup.
Depending on the method used, the updated contents of vendor_dlkm may not be immediately available for backup after flash or restore. This can be resolved by unmounting, unmapping, then remapping it.
AK3 helper modules are not backed up.
Credits
@osm0sis for AK3, feedback, and general guidance
@eng.stk & @Freak07 for feedback, advice, and encouragement
@phhusson for lptools
@topjohnwu for Magisk and libsu
Latest Update
2023-02-20 v1.0.0-alpha13
Hi, great app!
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Nezorflame said:
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Click to expand...
Click to collapse
That is already done in my own personal test version of the app, but I haven't had a chance to clean it up and get it released. I'll make an effort to get that done this evening.
I've got several other enhancements planned, but most of my focus has been on Hashtree Patcher lately, though I think that is nearly wrapped up. I'll try to get the installation log issue fixed asap, then I'll work on the rest over the next few days.
I pushed a new build that resolves the installation log issue. Here is the full changelog:
added option to backup AK3 zips
disabled flash and restore on inactive slot
added save ramoops button
added stderr to AK3 logs
added .log file extension to log files
filtered ui_print and progress in AK3 logs
sorted backups
Click to expand...
Click to collapse
I also added a list of planned and potential features to the OP. If you've got some interest in seeing any of them or anything I may have missed in a future build, feel free to note it here. If the list gets to be too big of a pain to maintain here, I may request that they go to the issue tracker, instead. Note that I don't currently plan to add kernel tweaks to the app.
Edit: There was a bug in the v1.0.0-alpha03 build that caused it to crash frequently. This has been fixed in v1.0.0-alpha04.
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
eng.stk said:
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
Click to expand...
Click to collapse
I have that checksum too but it's not working, maybe it's minimum Android 12?
Edit: Yep! Can the minimum API be lowered to support Android 11?
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
osm0sis said:
I have that checksum too but it's not working, maybe it's minimum Android 12?
Click to expand...
Click to collapse
Yes, I was playing with the new Splashscreen API, which requires Android 12, and I don't have an Android 11 device to test on, so I just set minSdk to 31. I'll see if I can get it to build against something lower.
I pushed a new build that will hopefully work on Android 11. Here are the changes:
lowered minSdk to 30
added vbmeta to raw partition backups
fixed vendor_dlkm map and mount
Click to expand...
Click to collapse
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
capntrips said:
I pushed a new build that will hopefully work on Android 11. Here are the changes:
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
Click to expand...
Click to collapse
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
osm0sis said:
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
Click to expand...
Click to collapse
I pushed a new build that hopefully fixes the issue. It now makes it to the point where it requires root to continue on an Android 11 AVD. I assume if it makes it to that point, the rest will work as expected. Anything beyond that, and I'll have to root the AVD to test it (though I did see an article about that a few weeks back, and it seemed simple enough).
Now works on lineage 18.1 Sony xz2 slot a/b device
A few random thoughts/ideas while testing on my 8T :
Got some errors trying to backup on my 8T since there's no vendor_boot, so I guess some logic will be needed for whether they exist.
Probably the feature should be like "backup slot" and save init_boot, boot, vendor_boot, dtbo, recovery, vendor_dlkm and vbmeta from the chosen slot if any of them exist.
If vendor_dlkm doesn't exist on an older device it doesn't make sense to show "Not Found" all over the place, nor offer to allow me to map it, it should hide those messages/buttons and just only show boot or whatever other partitions exist on the device.
If the reboot button had a ... to reveal an advanced reboot menu (menu items like the Magisk app) that would be excellent!
Magisk/RebootEvent.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk/XSU.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Overall looking really good! Exciting to see a well written free alternative.
osm0sis said:
A few random thoughts/ideas while testing on my 8T
Click to expand...
Click to collapse
All good ideas. Probably good enough to check by path for the existence of a partition, rather than finding and parsing fstab. My next two weeks are brutal, but I'll see if I find some time to fiddle with it in there.
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
shoey63 said:
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
Click to expand...
Click to collapse
The backup format is very basic. You could easily drop the image you want into the backup folder and create the properties file. I'll take a look at adding something to simplify direct flashing in the next few revisions. I'm out of pocket through the weekend and will probably need a few days of catch-up when I get back.
----- posted in error ------
can I flash an uncompressed boot.img file with this app? the github only mentions flashing an AK3 zip file, so I was curious
sorry, I see the other reply. I'm hoping this app gets this feature in a future update soon. making a video about this app right now
Doesn't open up on Pixel 6. Anyone has a similar problem?
radekmazur said:
Doesn't open up on Pixel 6. Anyone has a similar problem?
Click to expand...
Click to collapse
Does it throw an error message? If not, is there anything in the logcat?

Categories

Resources