I seem not to be able to flash a new boot logo for my mido. I've tried to flash splash.img and other zip files from xda and nothing seems to work.
Related
I use the LG GT540
As the title says i can't flash any boot images
expect swiftdroids boot .img
Everytime i go onto recovery the swiftdroid boot image
comes up for about 1 sec and then the recovery menu
comes up!!!
I also tried flashing different CWMs but the same!!
My normal boot image does come up if i don't go to
recovery!! (It is the android boot image)
Cause of this i can't flash any type of boot .img
expect the swiftdroid's boot .img
Anyone know how i can get rid of this??
I am using SuperFast Froyo so its got nothing to do
with swiftdroid!!
I did go to data/local/
but nothings there so i went into data/local/tmp
and nothings there too. (used root explorer)
Eit: I have tried to delete recovery and flash it again
and the swiftdroids boot animation doesn't come up now!!
But when i try and flash a boot .img it only some of the rom's
boot .img flash!!!
Please help!!
Any help will be appreciated!!
Thank you!!
????
Sent from my GT540 using Tapatalk
anyone????
Why you need to flash boot.img?
Accidentally sent from my Google Nexus S using XDA Premium
Try some cool colorful boot logos. Images cropped to 540x960px. Highlights - NVIDIA logo, Flash Player logo, CM7, Google, HD video, Linux, Navigator, Motorola
Enjoy the X'mas Release
Instructions:
1. Download the attached *.zip files
2. Extract and find the *.bin files
3. Use fastboot to flash the boot logo to your device
-- Reboot device to fastboot
-- Open Command Prompt and type
fastboot flash logo *.bin
fastboot reboot
or Make a CWM Recovery zip and flash it.
Special thanks to thewarhawk, NFHimself, Ka4yan and Devbro. you guys made it a hell lot easier! Does anyone know how to remove the text "unlocked" from the boot screen??
Standard Disclaimer: Don't telegraph me if your device is bricked!
thx .i gonna try it
thanks more to come!!!
Not to be a stickler, but shouldn't the fastboot command be "fastboot flash boot <filename>.bin" ?
I might be wrong but I thought fastboot commands run on the structure of
fastboot flash <partition> [ <filename> ]
Again, correct me if I'm wrong, I just don't want anyone to be confused (as I am obviously )
EDIT: Nevermind, is "logo" the partition? If it is, my bad.
well...we are not dealing with boot image, but just boot logo ! you are right if we are flashing a new boot image to our device, might be like this
fastboot flash boot boot.img
and recovery, fastboot flash recovery recovery.img
it clearly specifies the partition! but here we flash the logo, boot logo! correct me if im wrong!
edit: yea yea sounds like partition!! though its just logo
Well, it seems no one is having any issues so more than likely you are right.
I'm definitely no expert.
njarun said:
well...we are not dealing with boot image, but just boot logo ! you are right if we are flashing a new boot image to our device, might be like this
fastboot flash boot boot.img
and recovery, fastboot flash recovery recovery.img
it clearly specifies the partition! but here we flash the logo, boot logo! correct me if im wrong!
edit: yea yea sounds like partition!! though its just logo
Click to expand...
Click to collapse
live4nyy said:
Well, it seems no one is having any issues so more than likely you are right.
I'm definitely no expert.
Click to expand...
Click to collapse
IS THERE ANY OPTION TO CONVERT CWM FLASHABLE ZIP TO ODIN FLASHABLE . AS WHILE CHANGING THE BOOT LOGO I THINK (NOT CONFIRMED) MY PHONE HAS BRICKED..... AND SO BECAUSE OF THE PROBLEM OF BOOT LOGO, I AM NOT ABLE TO BOOT INTO RECOVERY MODE TO CHANGE LOGO. SO A HELP IS NEEDED TO RECOVER MY PHONE. I THINK IF MY BOOT LOGO AGAIN GETS RECOVERED MY PHONE WOULD GET STARTED..... AS I M NOT ABLE TO BOOT INTO RECOVERY BUT CAN BOOT IN DOWNLOAD MODE..... SO ANY ONE HAVE ANY IDEA TO CREATE ODIN FLASHABLE FILE OF BOOT LOGO. I WOULD BE VERY THANKFUL TO EVERY REPLIES THAT COULD HELP ME...!!!
Boot Logo cannot be the cause of soft-brick.
If you flash wrong image as boot logo, then you wont see the logo, but will be able to boot to system.
Easiest way out : Flash stock
follow CORPHISH
I tried to upgrade magisk to latest from magisk manager and device boot loop at Tmobile logo. I can get into download mode, fast boot, and twrp recovery.
However, I do not wanna to reinstall the kdz from download mode .So, flashing the stock boot img from fastboot will fix it ?
Please attach stock boot img or magisk patched boot img . Thanks
I just installed havoc os using pe recovery and after setting up the phone I am unable to boot into recovery I also tried to install recovery again but then I cannot bot into os
Note: I tred TWRP but if I install Havoc os through it i cannot boot it just keeps loading
If I try to boot into recovery it just shows redmi icon
You are probably installing recovery incorrectly.
Did you use "fastboot boot recovery.img" for the first boot recovery?
Then upload the recovery to the ramdisk.
If even that would break the boot, you would still have to flash boot from Havoc.
StaryMuz said:
You are probably installing recovery incorrectly.
Did you use "fastboot boot recovery.img" for the first boot recovery?
Then upload the recovery to the ramdisk.
If even that would break the boot, you would still have to flash boot from Havoc.
Click to expand...
Click to collapse
StaryMuz said:
You dont need to install ramdisk for pe recovery or I am wrong
Click to expand...
Click to collapse
muneeb rizwan said:
I just installed havoc os using pe recovery and after setting up the phone I am unable to boot into recovery I also tried to install recovery again but then I cannot bot into os
Note: I tred TWRP but if I install Havoc os through it i cannot boot it just keeps loading
If I try to boot into recovery it just shows redmi icon
Click to expand...
Click to collapse
When You flashed the rom and reboot you will stuck on havoc os logo.
so to fix this go back to TWRP and format data then reboot havoc will boot up.
summary:
Flash havoc > format data > reboot.
You're wrong.
On our phone, recovery is part of boot.img.
If you require a different recovery than the one stored in boot.img, you must boot your own recovery to ramdisk and then it will work in parallel with the other boot.
Otherwise it will overwrite boot.img and the system will not start.
StaryMuz said:
You're wrong.
On our phone, recovery is part of boot.img.
If you require a different recovery than the one stored in boot.img, you must boot your own recovery to ramdisk and then it will work in parallel with the other boot.
Otherwise it will overwrite boot.img and the system will not start.
Click to expand...
Click to collapse
ok thanks for the information