Is there a way to change that ugly ASUS boot splash logo screen whatever you wanna call it thingy? I'm sbkv2 so no nvflash.. but I'm rooted. Is there a file somewhere in /system/ that I can replace? Or?
Thanks for any help/guidance.
Not possible then?
To the best of my knowledge, you don't need nvflash to change the boot animation. Just get a new one, rename it to bootanimation.zip and place it in /data/local. Someone correct me if i'm wrong.
Saav said:
To the best of my knowledge, you don't need nvflash to change the boot animation. Just get a new one, rename it to bootanimation.zip and place it in /data/local. Someone correct me if i'm wrong.
Click to expand...
Click to collapse
I think he's talking about the splash screen, the one that appear before the bootanimation.
baseballfanz said:
I think he's talking about the splash screen, the one that appear before the bootanimation.
Click to expand...
Click to collapse
He is correct, I mean the splash screen,
I know it's gotta be possible! I just can't find an image in /system anywhere
The splash screen is in the bootloader/EBT. You can mod it and flash it through the staging partition. Whirly eyes has a thread in the dev section. I think it's much easier with nvflash since you can test it before writing it.
sent from my transformer
Thanks, I'll look for the thread, so I can do this with Sbkv2?
It should be possible, but I've never done it.
sent from my transformer
How would I go about flashing the new blob with the boot screen without NvFlash though, I have cwm I'm just a tad unsure and don't want to be accidentally flashing over something important... Thanks for the help
You can pack up just the EBT partition as a blob and flash it through the staging partition. It will only overwrite your recovery if you include an SOS partition in the blob. The relevant threads are in the dev section.
sent from my transformer
Awesome, so I can just flash certain sections, doesn't have to be all. Thanks for the help!
Okay, as far as which source to download, does it matter? Since I can't use NvFlash to extract mine I want to be extra careful.
I'm running AOKP Build 35 with Guevor v20 kernel or TestyMehIcs kernel.
I have a blob with just the EBT and the new screen made. It just says blob (not .EBT)
If I make this into a .zip and flash it, will it overwrite EVERYTHING or just .ebt? This is very important :/ I can't nvflash a brick and really want this to be clear. Should I rename it?
First off, there are no guarantees! As you said, without nvflash, you're screwed if you make a mistake, and it will be a real brick, not one of those, "help I turned off my tablet and I think it's bricked!"-type threads.
How did you pack the blob?
blobpack your_blob EBT blob_mod.EBT
You don't need to pack it up as a zip, you can just flash it through the staging partition. Not to sound condescending, but be sure you know what you are doing because the consequences are real. I truly think that it's great that you are heading down the Android! journey.
EDIT: I think I see where the confusion is coming from- most people think of the splash screen as the bootanimation. In this case, the splash screen is the Asus/nvidia logos without the spinning balls. If you change the bootanimation.zip, you will still see the splash screen.
Gah this is incredibly scary, damn Asus making Sbkv2 -_-!!
Sofar I havn't packed with blobpack, I've just used that spash image creator gui pointed to EBT then save as blob.
What I've done to this point:
Downloaded BlobTools.
Downloaded Latest .24 US
Unzip, Unzip, Copy blob
Use Blob unpack on blob
I did NOT get a blob.header for whatever reason? Or am I misreading something?
Found blob.ebt
Used This: http://forum.xda-developers.com/showthread.php?t=1232410&highlight=splash Splash screen patcher to open it.
Patched
Save as blob
I have a blob with no extention.
Did I do anything wrong? Now what?
Thanks!
Edit: Also the filesize of the blob before the patch and after is exactly the same. 1421KB
file extensions are a false indicator- what matters is the data format inside. A properly packed blob will start with msm-radio update, some blank space, and then some hex and text that indicates partitions and their size that are included in the blob. Take some blobs apart and see what's inside of them. Get a calculator and check the file sizes of the blobs inside. Then repack them to see if you get the same thing/order.
This is a screen of the EBT blob that was saved by the app, MSM-Radio-Update, some 0s, then a whole lot of gibberish.
{
"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"
}
That looks like a packed blob. I guess whirly eye's program packs it up for flashing. Notice the EBT part in the second line, and the fact that there aren't any other partitions like SOS, LNX, or APP.
sent while running with scissors
I unpacked just the EBT blob that I unpacked with blobunpack and opened it with his patcher then edited. Should be fine then I hope, if nothing messed up.
Scrolling through the rest, it just looks like EBT, I saw whirleyes left a watermark in quotes about the patcher before the image, and a section with the display text "cold-booting linux, unsupported bootloader, error, wipe data" (The options stuff) rest was blank or gibberish.
Is this primed to flash then? You said to flash through the staging partition, how would I go about this in Cmw Rouge xm recovery, do I need to pack a .zip, or what is the command to run?
Thanks majorly for all the help!
Related
You can display a "splash" screen of sorts upon boot. You just have to have a file named initlogo.rle in your root directory. The trick is that the root directory is overwritten each time you boot with the contents of your boot image (mtd2). There are instructions elsewhere on the forums for updating this image.
You can prove to yourself that this works by just copying logo.rle to initlogo.rle in your updated boot image and you will see the "G1" screen twice.
The hurdle I'm running into is generating my own images. There is a program called to565 that takes in an image and spits out the resulting image in the appropriate format (give it the -r flag to generate an rle) [edit, correct flag is -rle]. However, everything I generate with this just looks like random colored bars when I boot up (and sometimes at the bottom of the screen I see part of whatever was left in the framebuffer when I shut down). Supposedly to565 takes in a raw rgb888 file, and perhaps I'm not generating those properly. I tried saving to "raw image" from gimp but so far everything is just different variations on colored bars.
I may give up at this point, but I thought others might be interesting in picking up where I left off.
Huh. Interesting. I'll see if I can give it a whirl. Thanks for posting the info you've found so far
I took a quick look at the source of that to565 program. It looks like you need to use -rle instead of just -r. Did you try that?
JesusFreke said:
I took a quick look at the source of that to565 program. It looks like you need to use -rle instead of just -r. Did you try that?
Click to expand...
Click to collapse
You sir, are correct! I just did it with -rle and it works.
How to create a boot image:
1. put a properly encoded initlogo.rle in root directory
2. insert this line in init.rc in the boot: section (optional, this disables the stock android boot animation)
Code:
setprop debug.sf.nobootanimation 1
3. wrap it all up and flash it to mtd2
Attached:
1. A boot image with these changes made. To try it on your phone, first back up your mtd2 image (the boot image). Type the following in a root shell to back it up to your sdcard:
Code:
cat /dev/mtd/mtd2 > /sdcard/mtd2.img
Then, unzip boot-rc29-customlogo.img.zip it and stick it on your sdcard and type the following in a root shell:
Code:
cat /dev/zero >> /dev/mtd/mtd2
flash_image boot /sdcard/boot-rc29-customlogo.img
(when you do the cat, it will tell you "write: No space left on device," which is fine)
To restore your original boot image, do the cat and then flash_image your mtd2.img backup.
2. Samples of the raw image as well as the rle encoded version.
3. A nifty photo of this working on 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"
}
WOW awesome!! great job will test this out when i get back from the airport
i couldn't wait so i did it works perfectly. i just can't get rid of the first boot .img.(i see the instruction but i need further help) if this helps i have a vista 64 but, I'm also running VM to any operating system.
humble said:
i couldn't wait so i did it works perfectly. i just can't get rid of the first boot .img.(i see the instruction but i need further help) if this helps i have a vista 64 but, I'm also running VM to any operating system.
Click to expand...
Click to collapse
Yeah, actually I haven't found a way to get rid of the G1 logo on boot. If you change logo.rle on the root filesystem, it still shows that image. I'll post a longer guide to generating your own boot.img later tonight (although I posted a bunch of it in another thread already). You could always create your own boot.img and replace logo.rle to prove to yourself that it doesn't change that initial logo... but I've tried it. It must be somewhere else (including, perhaps, some on-phone memory that we can't access).
hmmm so i've done this correctly since the boot image works...however i no longer have WIFI access. Does anyone knoe whats going on? under settings it keeps saying turning wifi ON... but it doesnt.
EDIT: So i reflashed the original backup img and now its fine. I wonder where i went wrong?
mack said:
hmmm so i've done this correctly since the boot image works...however i no longer have WIFI access. Does anyone knoe whats going on? under settings it keeps saying turning wifi ON... but it doesnt.
Click to expand...
Click to collapse
Did you use the boot.img I posted or one of your own? I'm not having any trouble with wifi, and I'm booted with that one. Do you see anything in dmesg about wifi?
Edit: also, it looks like JesusFreke had some issues with wifi not working when he was doing custom boot images. Dunno the details but maybe it's related.
thanks alansj (sorry i miss read). and my wifi still works
alansj said:
Did you use the boot.img I posted or one of your own? I'm not having any trouble with wifi, and I'm booted with that one. Do you see anything in dmesg about wifi?
Edit: also, it looks like JesusFreke had some issues with wifi not working when he was doing custom boot images. Dunno the details but maybe it's related.
Click to expand...
Click to collapse
I used your img that you posted with the hackdroid...LOVED it by the way =)
Could it be i'm on RC19 firmware? I'm reading jesusfreke's post but i'm fairly new to the linux thing so i'm having trouble understanding.
anyway i guess i'll just stick to stock until something new comes a long...
Thanks Alansj
mack said:
Could it be i'm on RC19 firmware?
Click to expand...
Click to collapse
Good guess. You could first apply the RC29 via sdcard and then flash the boot image.
To apply RC29, download this file, put it on your sdcard, name it update.zip, then reboot your phone while holding down power+home and when you get the recovery screen press alt+L then alt+s.
will this work with 30
jriley60 said:
will this work with 30
Click to expand...
Click to collapse
The general process will work, but the boot image I posted is based on rc29. The two things in the boot img are a kernel and a ramdisk (which includes a few of the basic system files). I don't think there was a kernel update in rc30, but I think there were updates to init.rc and possibly adbd (haven't checked). So, flashing with that boot.img I posted would undo the changes in those files done by rc30.
The better approach would be to take the boot.img from the full rc30 release, add your own initlogo.rle, and reflash from that.
I will now go and write a more detailed tutorial on how to edit boot.img
that would be awesome. Thank you!
Kinda off-topic, but where did you get the font that you used in the logo? I'd like to make my own, and I was wondering if I could use it...
amgupt01 said:
Kinda off-topic, but where did you get the font that you used in the logo? I'd like to make my own, and I was wondering if I could use it...
Click to expand...
Click to collapse
I just pixel-edited the logo from the android site (had to invent a couple of characters)... no font.
jriley60 said:
that would be awesome. Thank you!
Click to expand...
Click to collapse
I just posted it here
alansj said:
I just pixel-edited the logo from the android site (had to invent a couple of characters)... no font.
Click to expand...
Click to collapse
Good work, man! Someone is actually working on the android logo font here: http://androidcommunity.com/forums/f37/new-android-ttf-logo-font-ver-1-0-a-6537/#post68847
Just FYI.
topdnbass said:
Well I noticed that nobody has really made any animated bootscreens.
I thought I would add to the community, so here are two that i've made..
You really need to try em because the pics don't show the animated android guy in the pics, and the videos look like crap
If you have an unthemed version of rc33/30 read the green text. Otherwise read the orange text under it.
Ok so the first one with the crazy colors is basically what you see in the pic except the colorful android disappears and reappears =).
{
"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"
}
http://www.youtube.com/watch?v=MDP3VvL10rQ (See it in action)
Color Animated Bootscreen
The second one i like to call Bloody Black!
The picture def doesnt do it any justice because the android is what makes it cool. Basically theres a black android that you can only see when theres a white glow behind it, and also it has red eyes so you only see the red eyes until the android is visible. It's a cool effect, just try it out lol.
http://www.youtube.com/watch?v=tGkRagArMRc (Check out a video of this one in action)
Bloody Black Animated Bootscreen
These 2 are the same as above except for the Hybrid 1.5 theme rc33/rc30 versions. (simply install the hybrid theme and then do this one afterwards..)
Bloody Black Hybrid Bootscreen
Color Hybrid Bootscreen
Installing is the same as usual. Rename the file update.zip, put it on your sdcard. Hold home + power and then hit alt+s once it loads up!
If you decide that you want to go back to the original version, just install the update below and you'll go back to the original one. (only if you have an unthemed version of rc33, otherwise just reinstall whichever theme you like, and thatll get rid of this bootscreen in the process)
Original Animated Boot Screen
Let me know how you like em!!
Click to expand...
Click to collapse
Hi guys!
I have a big problem. I just renamed a file from the orange text to update.zip and flashed my Phone!
I have JF 1.5, HardSPL, Root.
I have fastboot and it works on my PC.
When the bootscreen should come its just black and nothing comes. The first bootscreen works, but the second is black. He does not load anything and the phone doesnt start... What can i do?
pls fast Help thx
That update.zip isn't meant for ADP 1.5, it's for RC33. If you have a Nandroid backup, you could restore that. If not, just reflash the JF 1.5 update.
I decided to try it myself to see if it was as I though, and yes, it doesn't work with
1.5. I'm just checking which Nandroid images need reflashing...
Edit: Right, flashing boot back doesn't fix it, and I don't think you need to. Just flash the system image (assuming you have a nandroid backup) and it'll all go back to normal
The nandroid backup is on the sd card. How can i restore it? Is there a chance to connect to sdcard with my PC when the phone doesnt start?
To restore it, you need to have the Nandroid backup on your computer, so you'll need an SD card reader to do that (no USB file transfer without booting the phone).
Once you've got it on, you go into fastboot, and type "fastboot flash system system.img" (assuming fastboot is in the same folder as your Nandroid backup)
Mh oke thanks. I have no cardreader, is there another chance to help
my phone?
Someone have an idea?
I can't think of another way, sorry. Unless there is some other way that I don't know about, I think you're gonna have to buy yourself a card reader.
As long as the phone boots once you can then mount your sdcard right? So just flash any fastboot images that work, retrieve the images, and then flash them again. I've done this many times. So really you don't need a sdcard reader but it makes it a lot easier. Here are the official fastboot images you could use temporarily:
http://www.htc.com/www/support/android/adp.html
Thank you Peter and Doom. I bought a card reader and flashed the system.img.
I was pretty dumb
I did the same thing. Didn't realize it wasn't compatible. I am not too clear on what I am supposed to do. And the nandroid backup I did was before the 1.5 upgrade. Any help would be appreciated.
[Edit]
Ok, so reapplying JF 1.5 update cleared up the problem with no wipe necessary. AWESOME.
Phew... I was sweatin there. Anyone know how to change the bootscreen in 1.5?
cdi90 said:
The nandroid backup is on the sd card. How can i restore it? Is there a chance to connect to sdcard with my PC when the phone doesnt start?
Click to expand...
Click to collapse
use the recovery image and choose exit to console...
first:
mount -a
cd /sdcard/nandroid/HTXXXXXX/
flash_image system system.img
works like a charm....no computer or sd reader.
Hi all,
I have successfully flashed ROMS for my Gtab for over a month now. Tonight, though I have a problem. I decided to to NVFlash back to stock (which I have done successfully several times), so APX mode works. However, THIS time, the Gtab does what I believe is that Bootloop thing. I have read threads about it, but I don't quite understand what I do to fix it.
So I get into APX mode - then what? Again - Again, I have tried NVFlash and this time it will not boot into stock - It just loops from the Viewsonic screen to the G Tablet screen over and over again.
I appreciate being rescued from my disaster.
Thanks!
Mark
mlinder1958,
I am understanding you have nvflashed and are having boot loops.
If so, you can usually re-partition with ClockWorkMod and that normally will
fix it.
http://forum.xda-developers.com/showthread.php?t=844088
When you get CWM installed, reboot into recovery (CWM) with power/volume+. Go to the
advanced menu and partition. Take a few minutes--don't panic. The Fix Permissions.
Then Wipe Dalvic Cache. The go back to the Main Menu and Wipe Cache and then
Wipe/Reset Factory Data. The reboot and hopefully you will come up running right.
If not, the re-do the nvflash back to stock.
Hope this helps.
Rev
Hi Rev,
Thanks for replying.
Here is the problem. When I enter APX mode, I hear the PC (Windows 7) make its little beep sound and the gtab screen goes blank, but there is no dos prompt window opening in windows unless I run the gtablet .bat file. This is where I am confused. Since i am getting into apx mode, how do i move put recoery and update.zip back onto the gtablet since no indication (drive letter) of the gtablet appears?
Again, I can run NVFlash and the dos prompt appears, showing the progress and the gtablet black screen displays the nvflash info at the top.
I know I need to get CWM back on there. I just don't know how to do it from APX mode withou a drive letter appearing.
Thanks again.
Mark
mlinder1958,
I gave you the CWM link so you could download the correct CWM file.
Now we need someone to come along who can tell you how to use nvflash
to load CWM into your tablet. I have never used that procedure as I have
used my microSD card in /SDCARD2 whenever I have needed it.
I will see if I can find the procedure, but you need to be looking too. If you
can flash CWM on the tablet, then you can follow my repair process.
Rev
To fash CWM recovery with nvflash, you follow the same procedure as flashing back to stock but replace part9.img in the stock image with the .img file extracted from the cwm zip download rnamed to part9.img.
So I rename update.zip to part9.img?
mlinder1958 said:
So I rename update.zip to part9.img?
Click to expand...
Click to collapse
Unzip and extract the recovery.img - then rename THAT to part9.img (and backup the old file first, of course).
roebeet,
Oh man, what an honor!
Anyway, when I extract the zip it gives me the recovery folder and the update.zip file, which I am famliar with. Howewver, I see no recovery.img file. Or did I find/unzip the wrong file?
sorry for the long drawn out call for HELP
Mark
confirmed. I am confused. I cannot find any file called recovery.img after I unzip the CWM 08 zip file.
any help is appreciated.
Mark
The recovery.img is inside the update.zip... keep extracting ;-)
The recovery.img is inside the update.zip. It's a "file inside a zip inside a zip". I used to do this early on, but later started using rar files to make it less confusing.
No worries on the thread - you made me blush.
Roebeet and Rev,
I AM DE-BRICKED!
Thank you so much for your help.
Maybe a oughtta tone down my flashing for awhile : )
You guys ROCK!
Mark
Glad to hear! Many thanks to Rev for all the good advise!
Everyone,
Let's just all celebrate.
When I read a post from someone with a major or hard problem and sense the sadness,
it really makes me sad too.
It is so great to help someone and see that sadness become joy!! Anybody that
wouldn't like that has to be a rock head!!
Mark, now just ENJOY!!
Rev
Thank you everyone who responded to this thread. This also fixed my problem of a bricked/looping system.
when i tried to go back to power + vol + a triangle with "!" shows up. any remedy?
ramerco said:
To fash CWM recovery with nvflash, you follow the same procedure as flashing back to stock but replace part9.img in the stock image with the .img file extracted from the cwm zip download rnamed to part9.img.
Click to expand...
Click to collapse
Do you rename it part9.img or 09_SOS.img?
It seems as if there is no 'part9.img' and just the latter
Edit*Ah part9 is the one in the normal NVFlash and I am trying out nvflash_gtablet_46 to fix my issues
edit2* didn't work for me, a shame
I'm in the same boat as Citi is. Still a no go for me. I have even tried what was described in this thread to no avail:
http://forum.xda-developers.com/showthread.php?t=974422
Here is one thing that I am seeing that I also didn't see mentioned.
{
"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"
}
The "Can't Mount" error has been consistant for a while. Also something else I forgot was that when connected through USB to the PC, I can't see the device in My Computer. It is there and does allow an NVFlash though.
My gTablet is in the same boat after reflashing it after using VeganTab v7.0. I'm going to try the recovery.img rename this afternoon to get it out of the bootloop.
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
{
"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'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, it doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and if I find I have a bad nvflash blob file).
For other's info, I'd originally asked about re-running the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set. In preparation for recreating one, I moved the /sdcard/AndroidRoot folder to another location. I happened to reboot and noticed the AndroidRoot folder and its contents are automatically recreated upon rebooting. So for these files, there's no need to re-run the fastboot command for another set.
I did notice one "issue" viewing the /sdcard/AndroidRoot folder in Windows 7 after the initial reboot. While they display fine via my TF300T's File Manager, it took either disconnecting/reconnecting my usb cable or rebooting one more time for them to display correctly in Windows 7.
I still plan on re-running nvflash to create a new bricksafe.img, factory-config.img, and unlock-token.img set just to be extra safe.
wha2do said:
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and I find I have a bad nvflash blob file).
Can I rerun the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set? While I'm at it, I figure I should be able to rerun nvflash and create a new bricksafe.img, factory-config.img, and unlock-token.img... Is that possible and does it make sense?
Thanks!
Click to expand...
Click to collapse
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
Thanks for the confirmation. I dislike relying on an unverified backup only to find out too late that it's not valid or usable! And out of curiosity, you went through a recovery successfully? It'd be great if you had a link to the thread/post you followed.
I had missed one step after upgrading the jb bootloader (didnt force shutdown after upgrade, just let it load) and were stuck with official jb with no root or recovery, so i tried to use nv flash and messed up even more , post 3 in this thread helped me get the bootloader to work so I cound install TWRP again using fastboot.
I do not recommend testing it "just for fun" but it worked for me. Search for "nvflash restore" if you have any problems.
totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
I'm curious about your sizes matching mine; more specifically my unlock-token.img file size matching yours. Maybe fine if you used your unlock-token.img file when you did your recovery. If didn't use, might want to (if you still can) go back and recreate it and compare with your original...see below why.
Being OCD on backups, I created a new bricksafe.img, factory-config.img, and unlock-token.img and compared the files. I was a bit surprised to see factory-config.img and unlock-token.img were not exact copies of the original set created. Factory-config.img had some bits that varied, but was mostly the same. I'm figuring it's something "internal" as I haven't changed anything on my table between runs and is fine...
But seeing a large size change between the two unlock-token.img files, I went back through my logs, etc. Lo and behold, I had a typo and hadn't changed the partition from 14 to 7! So I had made duplicate backups of the factory-config partition by accident. The actual file size is 8,192 KB and not 5,120 KB.
That could have been a real problem down the road if ever I need to recover (assuming this file is vital to the particular recovery procedure). So if nothing else...the lesson to learn is always double check what you've done to make sure!
The boot logo which is a small partition, in mmcblk0p29 (/dev/block/mmcblk0p29)
We can modify this if you have unlocked your bootloader.
I wrote bootlogo_extract.exe / bootlogo_merge.exe to help things done in a more easy way.
1. backup your bootlogo
Backup your logo.bin by one of the following command, or use openrecovery (Thanks Skrilax_CZ)
Code:
dd if=/dev/block/mmcblk0p29 of=/sdcard/logo.bin.original
or
dd if=/dev/block/platform/msm_sdcc.1/by-name/logo of=/sdcard/logo.bin.original
Remember to adb pull out to your PC.
2. Extract image files
There are 2 bmp files in logo.bin, one for locked bootloader, one for unlocked bootloader.
Use the following command to extract, you will get two 540x540 bmp files, which can be directly open by double click.
Code:
C:\XT897 Photon Q 4G LTE\logo> [B]bootlogo_extract.exe logo.bin.original[/B]
bootlogo_extract for XT897, written by dove.
# Name start size
-----------------------------------------------------------
1. logo_boot 512 874800
2. logo_unlocked 875520 874800
extracting 1.logo_boot.bmp
extracting 2.logo_unlocked.bmp
done.
3. Edit or replace bmp files if you want
Use tools like photoshop or GIMP or ...
4. Merge 2 bmp files into logo.bin
Make sure you have 2 bmp files FLIPPED, 24 bit depth, BMP format, 540x540 !!
My tool will create a logo.bin automatically.
Code:
bootlogo_merge.exe locked.bmp unlocked.bmp
5. Flash back
Reboot to bootloader, then use moto-fastboot.exe to flash
Code:
moto-fastboot.exe flash logo logo.bin
Enjoy modifying you boot logo !!
Thank you for programming such an easy tool... But when trying to merge the BMPs I made, the command "bootlogo_merge.exe locked.bmp unlocked.bmp" doesn't produce a logo.bin in the folder. I have made sure that the file names and locations are correct, I've given administrator permissions to bootlogo_merge.exe, and I've even searched the whole hard disk for that logo.bin, but no success. Please look into this and tell me what have I done wrong, thanks
EDIT: Never mind, the BMPs saved by Photoshop is 2 bytes bigger. Re-saved using GIMP and everything's brilliant!
EDIT: Never mind, the BMPs saved by Photoshop is 2 bytes bigger. Re-saved using GIMP and everything's brilliant!
Click to expand...
Click to collapse
Photoshop will add 2 more bytes at the end of file, just delete them.
BTW, is there anyone who can share more nice boot logos ??
dove0rz said:
BTW, is there anyone who can share more nice boot logos ??
Click to expand...
Click to collapse
I'll share the simple one I just made for myself (it's a bootlogo, it doesn't have to be fanciful): LINK
Totally inspired by the stock screen protection film on Moto G, as seen here:
{
"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 how the boot logo looks on my own Photon Q:
great , thanks for sharing
AndyYan said:
I'll share the simple one I just made for myself (it's a bootlogo, it doesn't have to be fanciful): LINK
Totally inspired by the stock screen protection film on Moto G, as seen here:
This is how the boot logo looks on my own Photon Q:
Click to expand...
Click to collapse
broken link, i really want this boot logo though
ashtreylil said:
broken link, i really want this boot logo though
Click to expand...
Click to collapse
Surprised that this was bumped and wanted...
Anyway, here you go in the attachment. Unzip and you get the .bin file for flashing.
Note that this is for qHD screens only - if you have an Atrix HD or RAZR HD, tell me and I'll upload the 720p one.
Thanks I have the multicolor one that looks similar but I like this better since my photon is black and white themed
Sent from my PHOTON Q using XDA Free mobile app
Wheres the logo.bin output?
AndyYan said:
Thank you for programming such an easy tool... But when trying to merge the BMPs I made, the command "bootlogo_merge.exe locked.bmp unlocked.bmp" doesn't produce a logo.bin in the folder. I have made sure that the file names and locations are correct, I've given administrator permissions to bootlogo_merge.exe, and I've even searched the whole hard disk for that logo.bin, but no success. Please look into this and tell me what have I done wrong, thanks
EDIT: Never mind, the BMPs saved by Photoshop is 2 bytes bigger. Re-saved using GIMP and everything's brilliant!
Click to expand...
Click to collapse
"Never mind, the BMPs saved by Photoshop is 2 bytes bigger. Re-saved using GIMP"
Why does it matter if they are 2 bytes larger? How did you save them in GIMP differently?
dove0rz said:
Photoshop will add 2 more bytes at the end of file, just delete them.
Click to expand...
Click to collapse
Just delete what?
Ive tried editing/saving the BMP's in both gimp and photoshop. Heres what I get:
C:\photon>bootlogo_extract.exe logo.bin.original
bootlogo_extract for XT897, written by dove.
# Name start size
-----------------------------------------------------------
1. logo_boot 512 874800
2. logo_unlocked 875520 874800
extracting 1.logo_boot.bmp
extracting 2.logo_unlocked.bmp
done.
C:\photon>bootlogo_merge.exe locked.bmp unlocked.bmp
bootlogo_merge for XT897, written by dove.
why didn't the program output a logo.bin?
Logos Ascetic said:
"Never mind, the BMPs saved by Photoshop is 2 bytes bigger. Re-saved using GIMP"
Why does it matter if they are 2 bytes larger? How did you save them in GIMP differently?
Just delete what?
Ive tried editing/saving the BMP's in both gimp and photoshop. Heres what I get:
C:\photon>bootlogo_extract.exe logo.bin.original
bootlogo_extract for XT897, written by dove.
# Name start size
-----------------------------------------------------------
1. logo_boot 512 874800
2. logo_unlocked 875520 874800
extracting 1.logo_boot.bmp
extracting 2.logo_unlocked.bmp
done.
C:\photon>bootlogo_merge.exe locked.bmp unlocked.bmp
bootlogo_merge for XT897, written by dove.
why didn't the program output a logo.bin?
Click to expand...
Click to collapse
This is long obsolete - use the mighty MotoBootLogoMaker instead.
AndyYan said:
This is long obsolete - use the mighty MotoBootLogoMaker instead.
Click to expand...
Click to collapse
You're using the latest 2.4 version with your Photon Q LTE, without problems?
Logos Ascetic said:
You're using the latest 2.4 version with your Photon Q LTE, without problems?
Click to expand...
Click to collapse
I've long sold my PQ (for 3+ years already), but at the same time I've used it with a bunch of other Motos such as the XPure and G4 and it works well.