DISCLAIMER:
1) You are doing this at your own risk.
2) Educate yourself first and try this ONLY if you feel comfortable with modifying with your phone.
3) If you break your phone it is not my fault nor is it my responsibility to fix your phone.
Things could go wrong but they shouldn't if you follow the directions and have some general knowledge of Android.
##############################
Go from this:-------------------------------------------------To This:
{
"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"
}
----------
##############################
Things needed:
ADB/Fastboot knowledge - HERE and HERE
RGB565Converter v0.3c - Thanks to DeToX-cz!
UPDATE: You must have the engineering bootloader flashed for access to splash1. Follow the steps here to flash the S=OFF bootloader. -Thanks to jcase
Instructions:
Find an or create an image (.png, .bmp, .jpg, or .gif -- 320x480 is preferrable)
Open RGB565 Converter
Ensure that "To RGB565 (binary)" tab is selected
Click "Open Image", select your image
Click "Convert to RGB565" (RGB565 Converter will make your image 320x480 if it is not already)
CLOSE RGB565 CONVERTER
Reboot phone into Fastboot using this command: adb reboot bootloader
OR Button combo: SEND/CALL + END/POWER
Flash image using this command: fastboot flash splash1 <your_image_name>.rgb565
Reboot phone using this command: fastboot reboot
OR fastboot oem powerdown if not then remove your battery
View the results of your hard work.
Enjoy!
As of right now there is no way to read the splash1 partition to back it up short of some kind of kernel mod to partition splash1 from NAND as a new MTD. At least that's how I understand it, please correct me if I'm wrong.
You must flash the S-OFF BOOTLOADER for this to work.
You can use the RGB565Converter tool to flash your image successfully without needing to type commands.
Below is another method used to keep your phone from rebooting unexpectedly during the process:
joshw0000 said:
I tried using the "Flash Splash1" button that someone had posted earlier and I almost **** myself. I think my phone tried to load the file I originally used to root it. I was getting really nervous so I pulled the battery and, to my relief, it powered on and it booted normally. I'm sure that method works but I'm scared of it now.
I tried the original instructions and it rebooted my phone before I was ready so I did this in the command prompt (this was mentioned on the first page of posts):
cd C:\android-sdk-windows\tools
adb shell
su
reboot bootloader
fastboot flash splash1 <copy and paste file name here>
fastboot reboot
Of course this will only work if you've downloaded the program, converted your picture and placed it in the tools directory of SDK.
Worked great for me. I couldn't be happier!
Click to expand...
Click to collapse
didnt seem to work for me, but im not rooted, ill try this with my brothers rooted phone in a bit and repioret back
Wow that worked great! Thanks
Reboot phone into Fastboot (Power down, hold Send press and hold Power)
Click to expand...
Click to collapse
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
ch4sethe5un said:
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
Click to expand...
Click to collapse
no, Hold Call button and end button to get into fastboot
and this is ONLY FOR ROOTED PHONES
thanks
thanks i will try it out. Im using ivan's 0.7
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
ch4sethe5un said:
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
Click to expand...
Click to collapse
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
there should be an option to go to HBOOT menu and then into recovery and reboot from there.
I used this one:
Great tutorial. Thanks!
Here's mine if someone likes it they are free to use it.
+1 rep (if only we could do that). I was looking for something like this. Thanks!
t2noob said:
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
Click to expand...
Click to collapse
I did a battery pull myself too lazy to go into recovery from hboot. My phone did not explode after doing a battery pull so it "should" be safe however do so with caution.
moved thread by request of OP.
Best regards,
Flar
Ive learned that battery pull is the easyiest way,
As a fan of FFXIII, I could not pass up the opportunity to do this.
[Taking Requests also ]
Maybe we should come up with a thread so people can post all boot images and animations in one place, no?
Just remember to convert it like mentioned in the first post
Here is one(as a fan =] ):
Was just thinking about changing and found this. Thanks.
Awesome!!!
Thanks for the tutorial.
Worked great!
Related
I merged all the bootscreens from the original boot screen thread in development. Over taking "aron4588" as the thread creator of this one. His original post is in 12.
Sorry "aron4588"
This is updated with the latest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
(Driver for 1.5r2)
If you have the "new spl" you're going to need the new usb drivers
(http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565 You dont get a splash2 option with the "NEW SPL"
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Go to the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Files updated 1/4/08
Credit to JF for all app to make this possible
OR get Boot Screen Flasher 3000 by dom2684 & Octoberriot
to build the file yourself go to the root android source directory (mine is linux, but it looks like this "/home/ryan/android_source"), your's might look something like "C:/Source Codes/android/" or whatever. Once you navigate to that directory (via the command prompt... just go to start > run > and type in 'cmd' and hit enter, then use the 'cd' command to get there... e.g., "cd C:/Source Codes/android/"), once there, simply type 'make' and hit enter and it will start building everything, it might take a few minutes to complete. Then just go into the 'out' directory, then it's under "host/windows-x86/bin" (i'm not sure about the windows-x86 part, it might just be windows or something like it, i'm just assuming based on mine), once in that folder you'll have the fastboot as well as all of the other binary files ready to go. Then you can just type fastboot w/e w/e and it'll work just fine.
Here's my updated bootloader 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"
}
It's kind of difficult to see, my camera sucks... it's my fraternity letters with the crest in the background. Here's the image i used for it:
Here's what I finally settled on.
Take 2...
I found this one on google, I think it suits me
Ok, before i go dual booting my system , as i have Vista x64 now. I want to know if i can use ubuntu x64 for this process or would it be best to use the 32 bit version.
Here is the boot image I put together that i want to use. Still futzing with it but this is the general idea.
Stock Boot Logos
For anyone that wants a copy of the stock images, for instances of RMA/repair.......Here they are.
The file contains both UK and US logos
Thanks to JesusFreke and Tobes, for the rip coding and the UK logo
Custom Boot Screen
Just sharing the boot screen I'm using. Made by me on PS. Enjoy.
Yes, you need to convert the picture.
Just in case here is the raw file.
Sure, I can provide the base image. On mine however, I customized it with some of my information, such as my name, etc. That way if it ever gets stolen, the thief will be reminded of it everyday
Stericson
infernix said:
“It won't work,” droned Marvin, “I have an exceptionally large mind.”
Click to expand...
Click to collapse
I really liked this idea, so I found the image at deviantart, and made a copy of your boot image, and for anyone else, I've attached the splash.raw565 file (zipped) to this post.
Cheers guys, and happy new year!
-- michael
Domo for android
[HOW TO] Install Custom Boot Images/Post images here
CAN I GET A STICKY I THINK THIS THREAD HAVE HELP ALOT OF PEOPLE AND I NEVER BEEN STICKY BEFORE LOL
This is updated with the lastest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Goto the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Files updated 1/4/08
Credit to JF for all app to make this possible
I was able to, here is mine:
It didnt work for me
brandenk said:
It didnt work for me
Click to expand...
Click to collapse
To the OP, you can grab that file from the SDK tools folder and include it in the zip.
Ok, so I downloaded this: http://graha.ms/androidproxy/AdbWin.zip
I put those 2 files in the fastboot folder and it worked! Thank you aron4588!!!
And here is a mirror to your file with those two files added: http://www.4shared.com/file/78814404/36e59544/Boot_images.html
Success
I was able to do it, but quick question.
How many splash images can I have?
I was able to flash 2 over and it boots the first one (splash1) and then the second one (splash2)
How far can I go with this?
MMTest97 said:
I was able to do it, but quick question.
How many splash images can I have?
I was able to flash 2 over and it boots the first one (splash1) and then the second one (splash2)
How far can I go with this?
Click to expand...
Click to collapse
You can only do 2 images.
Here's mine
How long does this take to send? It's been "sending" for over a minute now
Yanked the battery, restarted the whole process and it worked. Very nice tutorial!
I played a little today and did Amon-Ra recovery for our Swift
This enables us
Partition your sd card to swap, ext2, fat32
Backup NAND + ext
Backup BART
Screen
Files update.zip require slightly different syntax for the script updater-script
Files are available http://forum.android.com.pl/f200/
DOWNLOAD
recovery_ra1.7swift.img
what is it swift?
angelsanges said:
what is it swift?
Click to expand...
Click to collapse
codename lg gt540 Optimus
Good job! Thanks man.
Sent from my GT540 using XDA App
How to install?
Is like clockworkmod: rom with fastboot and then fastboot flash recovery recovery_ra1.7swift.img
bluepower said:
How to install?
Is like clockworkmod: rom with fastboot and then fastboot flash recovery recovery_ra1.7swift.img
Click to expand...
Click to collapse
Yes installation by fastboot
Thanks a lot and wonderful job
so is this better than the clockwork recovery?
will this overwrite clockwork recovery if I already have that installed?
and the most important question:
DOES THIS WORK WITH PS3 JAILBREAK? I heard someone did it with this recovery, I want this to happen with the GT540!!!
I had clockwork now i have amon ra, it will overwrite clockwork when you install it
I've been trying to put this info my phone. But I have a problem.
Phone is ruining in fastboot mode, am typing command in cmd am pressing enter, then my PC reboot :/
Does somebody had the same problem?
__________
Written with Tapatalk on GT540
ZduneX25 said:
Phone is ruining in fastboot mode, am typing command in cmd am pressing enter, then my PC reboot :/
__________
Written with Tapatalk on GT540
Click to expand...
Click to collapse
Why you do that?
- Put your phone on fastboot mode
- Link it to the pc and turn on adb command
type:
fastboot flash recovery recovery_ra1.7swift.img
and you're done
I did this... I wrote I did. After ENTER the command my PC doing a reboot by itself, before apply recovery in my phone.
{
"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"
}
Is it working now? If it doesn't, download this: http://www.mediafire.com/?07qod3dg208mb30
Then, put the amon ra file in that folder.
- Put your phone on fastboot mode
- Link it to the pc and turn on adb command
type:
fastboot flash recovery recovery_ra1.7swift.img
you can try this method too (i use it)
1) copy recovery_ra1.7swift.img to sdcard
2) download/install some terminal into your phone.
3) run terminal and write :
Code:
#su
#flash_image recovery /sdcard/recovery_ra1.7swift.img
(or when it's not working:)
flash_image recovery recovery_ra1.7swift.img ;
flash_image recovery "/sdcard/recovery_ra1.7swift.img"
also you can to it in adb shell(connected into PC):
Code:
#su
#adb shell flash_image recovery /sdcard/recovery_ra1.7swift.img
or
Code:
#su
#adb shell
#flash_image recovery /sdcard/recovery_ra1.7swift.img
Hope this helps. (for me, it helped, because my computer freezes when using "fastboot flash" commands. )
Am reinstalling SDK and will check.
@hani93 thanks for this tut, it can be very helpful for me, cos my PC freezes too :/
ZduneX25 said:
Am reinstalling SDK and will check.
@hani93 thanks for this tut, it can be very helpful for me, cos my PC freezes too :/
Click to expand...
Click to collapse
no problem.
it should work.
(i googeld it for 4-5 days :S)
now i'm always using this method
I don't have to use fastboot with you method I guess, am I right??
ZduneX25 said:
I don't have to use fastboot with you method I guess, am I right??
Click to expand...
Click to collapse
that's right
just copy recovery image to sdcard (root dictionary) , install some terminal app( in market "terminal emulator" ) and enter commands...
and after that.. when you enter it . and terminal says "flashing recovery" ..or something, and then ends(with new command line)..
something that:
Code:
#su
#flash_image recovery /sdcard/recovery_ra1.7swift.img
flashing recovery...
#
make reboot and hold on home+power, and recovery comes up.
No way, so don't I need rom with fastboot to get recovery?? I just flashed my phone about 2 days ago with ROM+Fastboot to get recovery via fastboot (I lost some data - all angry birds saves).
And you are saying that I could use your method on my previous ROM without Fastboot, am I right??
ZduneX25 said:
No way, so don't I need rom with fastboot to get recovery?? I just flashed my phone about 2 days ago with ROM+Fastboot to get recovery via fastboot (I lost some data - all angry birds saves).
And you are saying that I could use your method on my previous ROM without Fastboot, am I right??
Click to expand...
Click to collapse
yeah...
i'm not sure. that it works with rom what's without fastboot..
but. for me it worked xD
My phone is soft bricked, I tried flashing to the stock rom using odin but the phone fails to boot up once the flash has finished it just stays on the 'Samsung Galaxy S III GT-I9305 screen, I can get the phone into download mode but not recovery mode, could anybody please help?
You have two phones ???
see your identical post .
Have you tried after flashing in odin to boot to stock recovery and do a factory reset?
trippy202 said:
Have you tried after flashing in odin to boot to stock recovery and do a factory reset?
Click to expand...
Click to collapse
Yep, nothing happens, just stays on the boot up screen
bump
bluereus said:
bump
Click to expand...
Click to collapse
Do a factory reset then re flash a stock rom
Raistlin1158 said:
Do a factory reset then re flash a stock rom
Click to expand...
Click to collapse
I can't do a factory reset though can I? All I can do is enter download mode
Ok, inside the zip of the rom you flashed, there is a file called boot.
On your desktop, drag out the boot.img.
It's an easy way to get fastboot and adb access without having to download android sdk. Extract the folder to your desktop. put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd. Then change the directory of the prompt so that it aims to the ADB-Fastboot folder. Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot. On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Raistlin1158 said:
Ok, inside the zip of the rom you flashed, there is a file called boot.
On your desktop, drag out the boot.img.
It's an easy way to get fastboot and adb access without having to download android sdk. Extract the folder to your desktop. put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd. Then change the directory of the prompt so that it aims to the ADB-Fastboot folder. Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot. On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Click to expand...
Click to collapse
This is all I have in 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"
}
If anyone can sort this out for me I'll happily throw you a fiver on paypal
bluereus said:
If anyone can sort this out for me I'll happily throw you a fiver on paypal
Click to expand...
Click to collapse
Unzip the zip then unzip again to split up the rom, You don't need to pay as we are all here to help each other :good:
Raistlin1158 said:
Unzip the zip then unzip again to split up the rom, You don't need to pay as we are all here to help each other :good:
Click to expand...
Click to collapse
I've got this far, where is the ADB-Fastboot folder? (sorry)
And I'd like to as a thank you, it'd be £25+ to send it off for repairs
Any chance you could do this for me on teamviewer or something tomorrow? I'm really out of my depth here (like you couldn't tell)
bumping
come on guys
Put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd.
Then change the directory of the prompt so that it aims to the ADB-Fastboot folder.
Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot.
On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Raistlin1158 said:
Put the boot.img inside the folder called ADB-Fastboot.
Now open up cmd.
Then change the directory of the prompt so that it aims to the ADB-Fastboot folder.
Then type "adb reboot bootloader" so your phones goes into bootloader.
It should boot into a mode called fastboot.
On your phone's screen, you should see "Fastboot usb" in red.
Then type "fastboot flash boot boot.img" Then once it finishes flashing, you can either reboot to see if it gets passed the screen or reflash the rom and then try rebooting again.
Click to expand...
Click to collapse
What is the ADB-Fastboot folder?
bluereus said:
What is the ADB-Fastboot folder?
Click to expand...
Click to collapse
Create a folder called ADB-Fastboot
Put the boot.img inside the folder called ADB-Fastboot. then follow the instructions... :good:
Raistlin1158 said:
Create a folder called ADB-Fastboot
Put the boot.img inside the folder called ADB-Fastboot. then follow the instructions... :good:
Click to expand...
Click to collapse
By 'change the directory of the prompt what exactly do you mean?
In CMD you have to open the folder you created ie ADB-Fastboot
So type cd ADB-Fastboot , you are changing the directory to the one you created.
Then follow the other instructions.
Without being rude you do not seem to have sufficient knowledge to dabble with you phone....
Once you get it going I would not play with it till you have read a bit more and watched a few videos to bulk up the level of competency,
{
"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"
}
Black Version of the logo
https://1drv.ms/u/s!Av6RWY-zSfSekyWGQi5mupY_9jvn
White Version of logo
https://1drv.ms/u/s!Av6RWY-zSfSekyaKccB9UqFgCU6U
This bin file will replace the "Bootloader unlocked" warning message with stock splash screens.
To use:
1: open adb CMD
2: type 'adb reboot bootloader'
3: type 'Fastboot flash logo logo_fix_*****.bin'
NOTE:::::: Replace ***** with White or Black as appropriate for your chosen logo download.
4: Restart and enjoy
Thank you for the mod, Added to Master index for more visibility.
I flashed the logo bin from the other stock files and I still have the unlocked warning.
sent via op5 and xda-app
byt3b0mb said:
I flashed the logo bin from the other stock files and I still have the unlocked warning.
sent via op5 and xda-app
Click to expand...
Click to collapse
Yes, this mod is cosmetic. It won't magically lock your bootloader. That warning is hard coded. These bin files are too just mock the locked state for those who are annoyed by it
I wonder if we can hex edit copy/paste an alternate png--as long as you used the correct start address? It is a png, right?
Uzephi said:
Yes, this mod is cosmetic. It won't magically lock your bootloader. That warning is hard coded. These bin files are too just mock the locked state for those who are annoyed by it
Click to expand...
Click to collapse
ya i know it wont re-lock it this actually does remove the warning, i stand corrected. flashing the logo.bin from the retail zip in the other thread only took away the t-mobile logo splash...
execute logo replacement in Android terminal
to execute logo replacement in root Android terminal (if downloaded to Download folder, otherwise change downloaded file location in flash section), type or copy/paste:
su
grep -q system_b /proc/mounts || echo "using slot a"
(or type to detect)
grep -q system_a /proc/mounts || echo "using slot b"
dd if=/dev/block/bootdevice/by-name/logo_a of=/sdcard/logo_a_backup.img
(or type to backup)
dd if=/dev/block/bootdevice/by-name/logo_b of=/sdcard/logo_b_backup.img
dd if=/dev/zero of=/dev/block/bootdevice/by-name/logo_a
(or type to zero)
dd if=/dev/zero of=/dev/block/bootdevice/by-name/logo_b
dd if=/sdcard/Download/logo_fix_black.bin of=/dev/block/bootdevice/by-name/logo_a
(or type to flash)
dd if=/sdcard/Download/logo_fix_white.bin of=/dev/block/bootdevice/by-name/logo_a
(or type to flash)
dd if=/sdcard/Download/logo_fix_black.bin of=/dev/block/bootdevice/by-name/logo_b
(or type to flash)
dd if=/sdcard/Download/logo_fix_white.bin of=/dev/block/bootdevice/by-name/logo_b
Veeery nice! I was waiting for it...! :silly:
Only one question... both version of the logo have no "warning message transparency" issue?
On my old Griffin only some colours were able to fully hidden the msg...
Fantastic job. Love the blacked out version.
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
TheKnux said:
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
Click to expand...
Click to collapse
Definitely has to be flashed to logo.bin
As Joemoss states: it is on a separate partition than system
Amd4life said:
Fantastic job. Love the blacked out version.
Click to expand...
Click to collapse
Really. I can confirm black one is *fantastic* with Amoled and it doesn't have any "transparency" issue...
This bin file will replace the "Bootloader unlocked" warning message with stock splash screens.
To use:
Click to expand...
Click to collapse
THANKS! That warning screen has always annoyed me I flashed the black one. I love it. Looks "Oldskool" Like my Droid X back in the day
TheKnux said:
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
Click to expand...
Click to collapse
Well... If TWRP can access /dev/block/bootdevice/by-name/logo_b(a) then someone can make a flash able zip quite easily.
I remember on all my HTC phones TWRP could flash to that partition when s-off to remove their Dev splash warning and on some others it required to manually flash a hex edited bootloader, so it just depends
Fabulous! Replaced the T-Mobile image and removed the warning! Many thanks! This is the first device I've ever rooted. So glad I did and wouldn't be able too without all of you developing and teaching
Will this work with Flashfire/Flashify /etc? I don't have a pc, just a chromebook so don't have access to fastboot.
I'm about to release a new twrp with flashable boot logos
joemossjr said:
I'm about to release a new twrp with flashable boot logos
Click to expand...
Click to collapse
Sweet!
joemossjr said:
I'm about to release a new twrp with flashable boot logos
Click to expand...
Click to collapse
Any preview?
Don't forget a version for unbranded Z2s pal..!
Hello
I have a Kindle Fire HD 7 2nd gen and it is stuck on the "Kindle Fire" logo. I bought a factory cable and get a 'fastboot' screen when connected to my Windows laptop. But in ADB no devices are listed and when I try the command 'fastboot -i 0x1949 getvar product' it says ' <waiting for device>' What can I try next? Any help would be great
Thanks in advance
check the device manager of PC, then maybe you will see a warning devices. install the attach files.
Finally someone replied. I looked in Device Manager and saw something in yellow called "Tate-PVT-08". So Windows was not recognizing the Kindle. I installed the Kindle ADB drivers from rootjunkysdl.com and now "fastboot -i 0x1949 getvar product" gives me "Tate-PVT-08"
My guess it is working now, but when I try to flash boot, recovery, and system img's from the KFRT here it does nothing and I'm still stuck in "Kindle Fire" logo/bootloop. What is the problem ? Is this thing hard bricked ?
Yes. I also have similar issue:
during I'm running the "fastboot -i 0x1949 flash system system.img"
My thread
I feeling that's should be a root problem. Since during I'm running (adb shell su -c reboot fastboot) there shown a pop windows on the KFTT.
shall ask the permission
with my understanding, that should be can mount -o remount rw /system. to get rw privilege to reflash system.
But, nothing..
and sdcard, no data can be removed or deleted. Read only..
I read your thread and if you had root (I did not) that may be the issue or else try a new USB 2 port or computer. But I need to ask where you got bootloader.img from ? I found out boot.img is only the kernel and ramdisk, so it is likely the bootloader is damaged.
seskanda said:
I read your thread and if you had root (I did not) that may be the issue or else try a new USB 2 port or computer. But I need to ask where you got bootloader.img from ? I found out boot.img is only the kernel and ramdisk, so it is likely the bootloader is damaged.
Click to expand...
Click to collapse
a long story. Before, I rooted it to remove some initial software from official version. then, turn it down a long time, about 2 years. Last week, I'd like to reboot it to check. Then, I found the system looks like to read only on lastest time. Even login system to remove any software, after reboot. they would be back. I tried to flash the img, such as boot, recovery, system and so on. you can check.
{
"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"
}
except kfhd7*.img . I reflashed them one by one, except system, other should be OK.
I tried "adb shell mount -o remount rw /system" or "chmod 669 " but doesn't work.
looks I have to click the allow the "shell" privilege as same as I ran "adb shell su"
I tried to hold the root to run all commands....
That is a lot of partitions in this screenshot, where did you find and get them from? The ones of interest are bootloader, crypto, dfs, dkernel, efs, idme, and xloader. Most of these I have no clue what they do and are for. Other than the obvious like boot and bootloader. I think xloader has something to do with the bootup process too. I'm not able to use ADB at this point, only fastboot, and that only takes img files, and system is a folder in the firmware .bin files from Amazon. There is no easy way to convert that into a system.img
seskanda said:
That is a lot of partitions in this screenshot, where did you find and get them from? The ones of interest are bootloader, crypto, dfs, dkernel, efs, idme, and xloader. Most of these I have no clue what they do and are for. Other than the obvious like boot and bootloader. I think xloader has something to do with the bootup process too. I'm not able to use ADB at this point, only fastboot, and that only takes img files, and system is a folder in the firmware .bin files from Amazon. There is no easy way to convert that into a system.img
Click to expand...
Click to collapse
where did you find and get them from? From Website. Yes, official way only the bin file. But if you'd like to write the KFTT with fastboot to flash. only img. files.
There is no problem on the img files. only I can't flash. There should be a way to format /system as re-partition something like that. Or a way to reset chip of memory.
03300209 said:
where did you find and get them from? From Website. Yes, official way only the bin file. But if you'd like to write the KFTT with fastboot to flash. only img. files.
There is no problem on the img files. only I can't flash. There should be a way to format /system as re-partition something like that. Or a way to reset chip of memory.
Click to expand...
Click to collapse
I see and which website might that be? But what i meant is where did the website get the partitions from. Yes hope to find out how to turn a System folder to an img
If you look up some commands for fastboot there is a format option but not sure if it will work for you. I'd try it anyways just to see the errors. That will be quite hard to do
seskanda said:
Finally someone replied. I looked in Device Manager and saw something in yellow called "Tate-PVT-08". So Windows was not recognizing the Kindle. I installed the Kindle ADB drivers from rootjunkysdl.com and now "fastboot -i 0x1949 getvar product" gives me "Tate-PVT-08"
My guess it is working now, but when I try to flash boot, recovery, and system img's from the KFRT here it does nothing and I'm still stuck in "Kindle Fire" logo/bootloop. What is the problem ? Is this thing hard bricked ?
Click to expand...
Click to collapse
I am stuck in a similar bootloop as you describe. I can only get the device to power on for a second. It shows the Kindle Fire Screen, the fastboot screen, then it shuts back down. I tried this with the OEM cable, a third-party cable, and a fastboot cable. I also tried all three cables in my PC over USB 2 and Windows constantly sends a notification saying USB device not recognized.