Database Develop

Nexus One Splashscreen Scaled for G1/Magic

BIG LOGO
{
"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"
}
DOWNLOAD: http://www.megaupload.com/?d=7RXNL18L
DOWNLOAD: http://www.mediafire.com/?3nymonjmmuj
LITTLE LOGO
DOWNLOAD: http://www.megaupload.com/?d=GHAP5YFE
DOWNLOAD: http://www.mediafire.com/?1an13t2yqta
How to flash:
fastboot flash splash1 <filename>
fastboot reboot

Nice.
Thanks !!

rgb556?
hey maxisma, whats the file type opened with ?

I was hoping that someone would make this, thanks!

Yeah, I also just get a .txt file downloaded. Should it be renamed to .zip and flashed from recovery?...or ...?

bert269 said:
Yeah, I also just get a .txt file downloaded. Should it be renamed to .zip and flashed from recovery?...or ...?
Click to expand...
Click to collapse
don't change the filename. he has instructions at the bottom of the post. boot into fastboot and type in the commands. everything is how it should be. rgb565 is the correct file type.

Is this animated or not?

idbl_fanatic said:
Is this animated or not?
Click to expand...
Click to collapse
it's a splash screen. it replaces the tmobile g1 screen when you first boot up your device.

grandomegabosses said:
it's a splash screen. it replaces the tmobile g1 screen when you first boot up your device.
Click to expand...
Click to collapse
Oh ok, so it's not the 2nd screen that comes up, darn it! Oh well.

is it possible to use console or terminal?

s0mep00p said:
is it possible to use console or terminal?
Click to expand...
Click to collapse
not from anything i've read. fastboot is your friend.

why the hell is it keep on saying cannot find <file name> when i try to do fastboot for splash screens!!! i made a folder on the desktop with the name "fastboot" and even made a folder with the same name on the root of the sd card. fastboot works and it recognizes my device. if you can help send me a email at [email protected]

Thankyou so much Maxis!

Thanks for the image

AndroidNoobie said:
why the hell is it keep on saying cannot find <file name> when i try to do fastboot for splash screens!!! i made a folder on the desktop with the name "fastboot" and even made a folder with the same name on the root of the sd card. fastboot works and it recognizes my device. if you can help send me a email at [email protected]
Click to expand...
Click to collapse
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.

david1171 said:
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.
Click to expand...
Click to collapse
And fastboot has to be in the same folder as the .rgb565 file

david1171 said:
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.
Click to expand...
Click to collapse
thanks man. I love you (no homo)

Somebody backed this up perhaps? Download links aren't working..

[GUIDE] How to get back the stock kernel of Nexus 5 (LMY47I)

Hi everybody,
This is my second post at XDA and as an answer to my first post (List of Lollipop 5.1 custom kernels for the Nexus 5) This post guides you how get back the stock kernel (LMY47I).
Always remember: You flash at your own risk! This post is only for the Lollipop build LMY47I!
There are two ways to get the stock kernel back, the first with a custom recovery like TWRP or CWM and the second with FASTBOOT (UNLOCKED BOOTLOADER is imortant)
1. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the Kernel.zip file! Copy it to your phone, then switch to the custom recovery navigate to the Kernel.zip file and flash it. Now reboot the phone. The stock kernel was succesfully flashed.
2. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the boot.img! If you haven't downloaded the Android SDK yet download it now! Switch to folder where you installed the SDK and navigate to "platform-tools". Copy the boot.img file into it. Now reboot your phone into FASTBOOT (Bootloader) with POWER Button + VOLUME DOWN and connect your phone to your PC wait until the drivers are installed if you get an error install the latest Google drivers. Open CMD navigate to "platform-tools" and type: "fastboot flash boot boot.img". Reboot your Phone and disconnect the USB-Cable. The stock kernel was succesfully flashed.

Error
Can't flash the zip, says "Unable to execute"

falcon.prj said:
Can't flash the zip, says "Unable to execute"
Click to expand...
Click to collapse
What is the name of the .zip that you tried to flash?

some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?

Wakamatsu said:
What is the name of the .zip that you tried to flash?
Click to expand...
Click to collapse
Kernel.zip
And the problem was with TWRP, sorry
and thanks!

iamelton said:
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Click to expand...
Click to collapse
Nope. So this thread is kinda pointless. You need to reflash your rom after hellscore, code blue, elementalx and probably franco (not used franco since kitkat)
From hells thread -
{
"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"
}
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

[Boot Logo][Flashable] Android 6.0 Marshmallow

Hii guys .. here am created boot logo of android marshmallow for Moto X Style ​
Instructions:
1.Download the flashable zip file from the link
2.copy that into sdcard/internal storage
3.reboot to recovery
4.flash the zip file
5.Reboot your device
{
"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"
}
Downloads: http://d-h.st/bjXA

Sweet! Any chance for one with a Black background?

Shouldn't this be about 1440px high?

When I tried flashing this I had errors and it failed in twrp. Redownload and same issue.
Sent from my XT1575 using Tapatalk

BlackHoleSlam said:
When I tried flashing this I had errors and it failed in twrp. Redownload and same issue.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I am having the same problem

It no work...

For those who can't flash the zip, you could try extracting the logo.bin and flash via fastboot:
Code:
fastboot flash logo /path/to/logo.bin
Disclaimer: The fastboot command works, but I haven't tested it with the logo.bin file provided from the zip in this thread.

Stryder5 said:
For those who can't flash the zip, you could try extracting the logo.bin and flash via fastboot:
Code:
fastboot flash logo /path/to/logo.bin
Disclaimer: The fastboot command works, but I haven't tested it with the logo.bin file provided from the zip in this thread.
Click to expand...
Click to collapse
I will attempt to flash later in the evening to test.
Update: flashed successfully with fast boot. Looks great

flash logo.bin via cmd
mfastboot flash logo logo.bin

[email protected] said:
flash logo.bin via cmd
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Did you test the file you posted?
You shared a flashable zip file so is it working?

@[email protected] ... It's a sorry thing to see when a member of your apparent experience on XDA resorts to plagiarism to open a new thread. The reason your flashable zip doesn't work is because you have copied the "Meta-Inf" file word for word and comma for comma from the original by @caitsith2 who pioneered flashable zips for boot logos. Not only have you failed to give him/her due credit for the work but you have also been ignorant enough to copy/leave in the three "dummy commented out" lines from his original. If you had an ounce of original thought in your being you would have seen that there was no way this "updater-script" was going to work.
Unlike you I have taken note of the requests by posters to this thread and have incorporated your "image" into a new flashable zip which works. As usual flash through custom recovery.

Oh looks awesome...thanks.

metpolds said:
@[email protected] ... It's a sorry thing to see when a member of your apparent experience on XDA resorts to plagiarism to open a new thread. The reason your flashable zip doesn't work is because you have copied the "Meta-Inf" file word for word and comma for comma from the original by @caitsith2 who pioneered flashable zips for boot logos. Not only have you failed to give him/her due credit for the work but you have also been ignorant enough to copy/leave in the three "dummy commented out" lines from his original. If you had an ounce of original thought in your being you would have seen that there was no way this "updater-script" was going to work.
Unlike you I have taken note of the requests by posters to this thread and have incorporated your "image" into a new flashable zip which works. As usual flash through custom recovery.
Click to expand...
Click to collapse
No. i made this bootlogo just using bootlogo maker tool. And ik flashable zip is not working and I am busy with mokee anyways thanks for fixing.

I did the procedure but it was upside down

eduluzamba said:
I did the procedure but it was upside down
Click to expand...
Click to collapse
@eduluzamba ... I don't wish to bang you on the head about this but I must point out that 268 people have downloaded this logo and you are the first to state that this particular problem exists.
Might I suggest that you delete the logo and re-instate the original, I presume you backed it up before installing this one, then re-download this logo just in case it was corrupted in the download and flash it again through recovery.
You might also look back at the post by @Stryder5 on page 1, he suggests the alternative method of flashing using ADB Fastboot.
I hate to state the obvious but presumably your device is the MXPE.

Sorry is that after I saw that the logo is for the bike x style and the bike x force

Root Unlocked Mi A2 without fastboot

Hello,
I have a mi A2 device that I unlocked it and flashed TWRP on it. I flashed TWRP on both slots and everything was ok.
After that, my USB board or charging board damaged for unknown reasons and the repairman could not fix it, Also, its charging board is very rare in my area and I can't find it.
So, my phone is never detected by PC but it can be charged, and I can't use fastboot commands.
A few days ago without knowing that DotOS has dedicated recovery, I flashed it with TWRP on slot A, and now I can't use TWRP on slot A anymore. But I think the TWRP is still installed on the slot B.
I really need root my device, so please help me.
1- Is there anyway to change slots without fastboot?
2- Can I install TWRP from anyway other than fastboot?
I tried to install TWRP zip file from DotOS recovery but it does not accept any file except DotOs official updates.
I can use adb commands with wireless debugging feature in android 11.
DotOS recovery options (Advanced option Does not include a useful option, just include reboot options and view logs)
{
"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. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash

LR7875 said:
1. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash
Click to expand...
Click to collapse
DotOS not include recovery.img in zip file, but it installed recovery too.
Does this solution still works?
DotOS zip file:

Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img

LR7875 said:
Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img
Click to expand...
Click to collapse
Not works, can't flash

So can you boot into system

And did you adb sideload?

LR7875 said:
And did you adb sideload?
Click to expand...
Click to collapse
I can't use adb sideload in recovery, because of damaged usb, I can boot system but can't use sideload command in system

Where to get vbmeta.img, and did I use the correct boot img?

Hi,
I don't have a vbmeta.img at hand, but I have a "vbmeta_a" and "vbmeta_b" partition checked by the command written in the install instructions.
So how can I continue with this?
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
So the question is where do I get vbmeta.img from?
And just to be sure:
I'm on LineageOS18.1, unlocked bootloader. The install instructions of Magisk tell me to patch a "boot image". But which one?
The LineageOS installl instructions mention a "vendor boot img", this one: https://wiki.lineageos.org/devices/sake/install#flashing-the-vendor-boot-partition
Is this correct?
Or otherwise, where to get the boot image out of https://download.lineageos.org/sake ? I just see this inside the zip:
{
"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"
}
Or is boot image = recovery image? LineageOS does provide a recovery image:
that is flashed into boot partition like this:
fastboot flash boot <recovery_filename>.img
So is this the one I need to take to patch?

Ok, I found out that you actually can extract the boot.img from the payload.bin using this instructions: https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas
So now I have a boot.img from there. Is this the correct one?
I am still a bit puzzled because LineageOS install instructions let me install the recovery into the boot partition, acting as a de-facto boot image:
fastboot flash boot <recovery_filename>.img
Yes, they actually let me do this and it worked fine, see https://wiki.lineageos.org/devices/sake/install#temporarily-booting-a-custom-recovery-using-fastboot
So then which should I choose? <recovery_filename>.img? boot.img? Or sake_vendor_boot.img? It's so confusing...
And I found out that boot.img and the <recovery_filename>.img are actually almost the same files. Only like a few ~50 bytes differ. So in LineageOS terms, <recovery_filename> is actually a boot image.
But still sometimes a few bytes can make a difference between working phone and brickwall. So I will still wait for a conformation which one I should choose.
Also still open question about vbmeta.img?

Mario545 said:
where do I get vbmeta.img from?
Click to expand...
Click to collapse
usually inside rom.zip :

loopypalm said:
usually inside rom.zip :
Click to expand...
Click to collapse
Yes, indeed, thanks. After extracting the payload.bin, a vbmeta.img was present.
But, and maybe I am a bit overcautious here, what is the purpose of flashing the unmodified stock vbmeta.img again? I mean I didn't see any instructions to acutually modify the vbmeta.img. Did I miss something?

Mario545 said:
Yes, indeed, thanks. After extracting the payload.bin, a vbmeta.img was present.
But, and maybe I am a bit overcautious here, what is the purpose of flashing the unmodified stock vbmeta.img again? I mean I didn't see any instructions to acutually modify the vbmeta.img. Did I miss something?
Click to expand...
Click to collapse
use the one present in custom roms
vbmeta is flashed to prevent the system from restoring the default recovery

It worked! I didn't brick my phone! Thank you so much for your answer.
To summarize, if you are on ASUS Zenfone 8 + LineageOS 18.1, and you are confused which image to patch:
Recovery image NO!
Vendor boot image NO!
boot.img extracted from the LineageOS zip by following https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas YES!
And this extraction process also gives you the vbmeta.img you need to flash (unmodified!).

Mario545 said:
ASUS Zenfone 8
Click to expand...
Click to collapse
twrp is available for that phone
no need to complicate the simple tasks ^......^