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
Related
{
"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"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot
Video Tutorial
Video Tutorial Thanks @wwjoshdew
Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?
CWM 6.0.4.7
OP Updated
Feb/2 OP updated
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
I was on 6.0.4.6 and i used flashify to update. Worked fine.
hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!
OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew
recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us
updated.
Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.
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
Sometimes the latest version of TWRP is in ".img", so some people use an older version instead, which is in .tar, so they can flash it with ODIN. The thing is that the ".tar" version is just the ".img" compressed XD, so I'm going to show you how to "convert" .img to .tar.
// TUTORIAL
1 - Download and install 7-zip
2 - Download the latest TWRP .img
3 - Open a file explorer, rename the downloaded file to: recovery.img
4 - Right click on the file > 7-zip > Add to archive...
5 - In this screen you can change the file name and, most important, in "Archive format" choose "tar"
6 - Open ODIN and flash the new file as always
Note: maybe other .img files (I mean other than the TWRP recovery) works too.
// SCREENSHOT
This is how the final file should look:
{
"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"
}
// Other stuff
[MOD] Centered clock in status bar [6.0.1][.ZIP][SM-N910C]
You can try this too to convert the .img to a "tar.md5": http://forum.xda-developers.com/showthread.php?t=2446269
is this method for MM build? (N910C)
Edited.
genova88 said:
is this method for MM build? (N910C)
Click to expand...
Click to collapse
It doesn't matter the version I guess.
The TWRP that I show in the screenshot is the one I'm using right now on MM (SM-N910C).
Thanks
Zawnaiminn said:
Thanks
Click to expand...
Click to collapse
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
joe535 said:
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
Click to expand...
Click to collapse
I have the same query. But seems that none exists!
Sorry for the resurrection but I wasted time trying to use this and wanted to say something.
I tried to use 7zip to create a .tar file for Odin and it didn't work for me personally. SeaFargo also says that 7zip .tars are not compatible with Odin.
SeaFargo's response is over at "[Script][Tool] how to create a tar.md5 file from img For Odin" by mkh.mourad. First page. New user here so I cannot post external links.
what about covert odin flashable files to twrp flashable files ?
joe535 said:
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
Click to expand...
Click to collapse
1st Extract Images from twrp
2nd Add Image files to this zip:
https://mega.nz/file/R4AggZjK#mVwpFp9lFtctNA51NubD1hr-Wm-zMREdJVLI3LXY4Yc
A S Ovin said:
I have the same query. But seems that none exists!
Click to expand...
Click to collapse
No need flashable zip, just extract by 7zip and flash images in twrp.
jjgvv said:
No need flashable zip, just extract by 7zip and flash images in twrp.
Click to expand...
Click to collapse
Can someone confirm this? It almost sounds too easy.
prkfsz said:
Can someone confirm this? It almost sounds too easy.
Click to expand...
Click to collapse
Sorry I mean:
1.Extract tar by 7zip or winrar
2. fastboot flash recovery C://recovery.img for recovery image and fastboot flash system C://system.img for system image which C:// recovery.img and C:// system.img should be replaced by the directory of the image
3.reboot and enjoy!
Remember delete meta inf folder
joe535 said:
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
Click to expand...
Click to collapse
just decompress it.
BOOTLOADER MUST BE UNLOCKED
DON'T TRY AND FAIL/BREAK YOU LOCKED DEVICE
Splash screens for Nokia 6.1 Plus
New screens will be added and updated by the contributors
{
"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"
}
More Previews
Download Splash
Instructions:
METHOD 1
via adb
unzip and place image file into platform-tools folder
reboot to fastboot
fastboot flash splash_a splash.img (replace splash.img with the respective img file name)
fastboot flash splash_b splash.img (replace splash.img with the respective img file name)
fastboot reboot
METHOD 2
via TWRP
Download zip
Unpack zip
1. boot to TWRP
2. Copy splash img
3. Select install
4. Select install image
5. Select splash.img
6. Select splash ( in partition box )
7. Swipe to flash
press home select reboot change slot repeat step 3-7
finally reboot system
tool used to work with img files by @GEEKiDoS
Contributors:
@D-Mi
@Sanju0205
@iamy7j
@joshclaudio
Amazing, Thanks
Is there a tutorial on how to make custom splash.img files for a given device? I want to modify the splash screen on my Nokia 7 Plus but can't find any tutorials or splash files.
thebob97x said:
Is there a tutorial on how to make custom splash.img files for a given device? I want to modify the splash screen on my Nokia 7 Plus but can't find any tutorials or splash files.
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/no...ol-splash2boot-logo-partition-editor-t3946992
Where splash screen image is stored?
Volski_ said:
Where splash screen image is stored?
Click to expand...
Click to collapse
It's located here - root/dev/block/by-name
But in case you need to extract run this commands in terminal emulator
su
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
@D-Mi The link for the tool is broken. Can you upload the tool or DM for me. Thanks in advance!
The25thMe said:
@D-Mi The link for the tool is broken. Can you upload the tool or DM for me. Thanks in advance!
Click to expand...
Click to collapse
Download tool here
can i also use a gif
D-Mi said:
Download tool here
Click to expand...
Click to collapse
Amazing work, can I use this to extract files from my splash.IMG of realme5 snapdragon chipset sir?
{Mod edit: Quotation fixed}
rockh3x said:
can i also use a gif
Click to expand...
Click to collapse
No splash.img is static part if you want to edit animation part of your phone's boot sequence you should change/edit bootanimation. Basically you can use any 30second video and turn it into a bootanimation.
Adamant12 said:
Amazing work, can I use this to extract files from my splash.IMG of realme5 snapdragon chipset sir?
{Mod edit: Quotation fixed}
Click to expand...
Click to collapse
I guess not these two phones have different resolution.
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 ^......^