Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU
legitscoper said:
Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU
Click to expand...
Click to collapse
It's in param partition.
It is empty ;(
It is in dev/block/bootdevice/by-name/param
I have made dd if=/dev/block/bootdevice/by-name/param of=/sdcard/param
I opened it in hexview and it has almost only 00 everywhere
and has 10mb
It's because you have a raw image of that whole 10MB partition while maybe only 1MB is used.
It'll send you it
I can take a look at it when I get home in a few hours.
Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change it.
{
"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"
}
Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?
legitscoper said:
Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?
Click to expand...
Click to collapse
I guess Odin would never allow the modified bootloader to flash. May be possible with the modified version of odin, I don't know..
I assume by the pictures I found that the background will be black by defauld no matter what.
There's no whole bootlogo, only the "Samsung galaxy A5" and "Powered by android" logos as small images.
Here I have extracted the "powered by android" logo from aboot. Only problem is I don't know what the file is named inside aboot.
If I name the new image something else than it should be and overwrite the old one, it would probably become bricked.
At best there would still be download mode.
Even if I did know the filename I would have to be precise in everything. Same resolution(304x81), same dpi(96dpi), same bytesize(6157 b), etc. and insert/overwrite at the exact same place. One faulty byte anywhere and chances are that the phone may never boot again unless you can get a jtag and reflash it.
It feels a bit risky just to change those two small images, and still be limited to only black background with new text at the same places as the original.
00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?
legitscoper said:
00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?
Click to expand...
Click to collapse
I would not try to change size or dpi in bootloader. I've made mistakes before when I modded param partition on another phone and it ends in no boot to system or recovery, or loop, and only download mode available. Param is like an image cache for bootloader, but here the images are inside bootloader which means that if something goes wrong it probably won't boot at all.
I think 00033.jpg was just what the program i used named it when it extracted the images.
That image was the second I found by searching for ffd8 which always is the beginning of a .jpg in hex, then make a search downwards for ffd9, which is the end of a .jpg. The first I found was the 5. It's a bit of trial end error when working in hex without knowing which image is what
The aboot I used was extracted from firmware.
And I will be unable to go to download mode it that "faulty byte" will occur?
I think thread is to close, I don't want to have that level of risk and with that limitations
tys0n said:
Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change it.
View attachment 4094675
Click to expand...
Click to collapse
Program name?
Related
Hello, I'm newbie there. First, I would like to congratulate with all staff of xda! I've an HCT Tattoo from four days and I immediately read the guide to flash fyodor ROM for upgrade my HTC from 1.6 to 2.2! It's was simply, beacause guides are carefully written step by step!
But when I search How to change the Splashscreen, I didn't find nothing for HTC Tattoo, only for other HTC... Is there a way to change the annoying "Fastweb" Splashscreen with another?
Thanks in advance...
Greetings
Leo
Not Development related moving to General
Do you mean boot screen? Look in themes and apps.
No, not BootScreen... I didn't need to change the animated Logo of Android... I need to change the SplashScreen, the image before "Droid" text and animation...
Sorry for my bad English ^^;
Nobody knows ?
I think nobody still understand what do you mean.
LeoVINTAGE said:
I need to change the SplashScreen, the image before "Droid" text and animation...
Click to expand...
Click to collapse
if you mean the image when turning the device on, it's still bootscreen. I have no idea where else could be the thing you call splashscreen.
Try describing the "splashscreen" on your phone, maybe i can see what you mean.
Ihaveatattoo said:
Try describing the "splashscreen" on your phone, maybe i can see what you mean.
Click to expand...
Click to collapse
Oh you all.....
Splash screen - the screen at the very beginning when you turn on your Phone. In tattoo's case, it would be stylized text "Tattoo". I.e. it "splashes" and is static (screen)
after Splash screen comes
Bootanimation - usually an animation that shows during OS boot process.
You can consider bootanimation the screen when like Windows loads up
{
"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"
}
and splash-screen when BIOS loads up.
bladez said:
Splash screen - the screen at the very beginning when you turn on your Phone. In tattoo's case, it would be stylized text "Tattoo". I.e. it "splashes" and is static (screen)
Click to expand...
Click to collapse
Is there a way to do this? To change the splashscreen? Or is it not possible?
revive
Hi, there.
I revive this old thread cuz i'm currently looking of a way to change the splash screen of the tattoo. The screen that display "tattoo" logo before bootanimation.
I'd like to further customize my little phone, but i don't find threads explaining how to do it. I found methods for Wildfire which seems close enough to tattoo resolution. I found how to create a .nb file or .img file containing the new splash image 320x240 but i don't know where to put it.
I'm asking for help on how to change the splash on tatoo. Or simply where is stored the normal splash file on the tattoo/click phone.
Thx in advance.
It's not possible, as it requires full S-OFF.
Well, thanks for the reply
I guess there wont be an S-off for tattoo as they did for wildfire
As I mentioned in a previous thread, I've picked up a kitchen from a retired chef so as not to reinvent the wheel since most of the changes I'm looking to do are rather minor.
One thing that's been bugging me is a small splash screen that only appears during the first boot over the welcomehead. At first I thought it was a part of RunCC as it appears above the progress bars when RunCC runs, but I took out the whole packaged (replaced it with XDA_UC) and the splash still appears for about 5 to 10 seconds during the first boot before I get to windows.
I looked through the image files (*.png/*.bmp/*.gif/*.jp[e]g) but couldn't find it anywhere, so I'm guessing it's a resource inside a dll (or some other binary file) but I can't figure out which?
Sorry if this has been asked before but I couldn't find anything related to my question by searching.
Edit:
Some pics for clarification (sorry about the quality, I only have my laptop's webcam to take images with for the time being):
Animation/Welcomehead:
{
"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 splash in question:
In case you're wondering, it reads: "Nhathoa ROMs - Windows Phone" (check my sig for more info).
It appears for about 10 seconds and then it's replaced by the Microsoft copyright text:
Check for Wellcomehead.png it must be inside Operator package or some OEM folder.
EDIT: sorry maybe i didnt understand right, anyway:
1st Boot = Splash.nb
2nd screen Wellcomehead
3rd RunCC
Those are the sequence.
Actually, none of those is the one that I'm talking about.
I'll try to get some pics to better explain what I'm talking about.
Edit: First post updated with pictures.
I downloaded the Kitchen in your sig,i took the TD2 Kitchen 2008 and i found nothing.
Im pretty sure that the pics you posted before are the Splash Screen.
You can make a test for be sure, download this Topaz Splash Screen http://forum.xda-developers.com/showthread.php?t=589777 , or one that you like, and check if it will change and that words will disappear.
I also want to know what this is, I know which images it uses though.
This is what I know about it:
It runs on first boot after which is after splash.nb and then the HTC animation (<-- btw, anyone know how to remove this completely?).
It uses the normal welcomehead.png as the wallpaper.
It uses PB1.bmp to PB14.bmp for loading bars (although yours don't seem to have it :?)
It uses LogoMsg.bmp to display an overlay (I think this, in your case, is that "Nhathoa ROMs - Windows Phone" image)
Hope this is the same thing you're talking about, and I hope it helps
It uses
seeM_ZA said:
It uses LogoMsg.bmp to display an overlay (I think this, in your case, is that "Nhathoa ROMs - Windows Phone" image)
Click to expand...
Click to collapse
Yes! That's exactly the file I was looking for! Thank you veeery much!
I must have forgotten to search for *.bmp files under OEM and only looked in the EXT folder.
As for the loading bars, they don't appear when you don't cook RunCC (which is the case for me).
Oh, and about disabling the startup animation, making this reg entry point to a non-existing file can do the trick:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\HTCAnimation]
"StartupGif"="\\Windows\\imaginaryFile.gif"
After doing this change, the screen will show a black screen between the boot splash and the welcome head, or where the animation used to be.
Got that from the "BSB Tweaks" utility, but I ended up not using it. I didn't feel any difference in booting time.
I don't know if there's an alternative method.
old thread but BUMP
this is the original wm logo i have.
LogoMsg.bmp
is there any edited ones somewhere? cool ones?
thanks
Rn
***TLDR: I edited build.prop, and now it looks like my /system/ folder has been deleted, phone won't boot. Will I be able to save my phone? or do I have to re flash it and start from scratch?
I was trying to get a patched Google Wallet working on my rooted S4 I9505OXAAMDE, and supposedly the app wouldn't open on most devices, so I changed some device details in the build.prop file in the /system folder.
The only things I changed are these values:
ro.product.model=GT-I9505
ro.product.name=jfltexx
ro.product.device=jflte
to
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
I did this on the S4 with a text editor (after changing the system folder to being RW instead of RO), and then I rebooted my S4. It gets up to the point where it says "Samsung Galaxy S4 i9505....", then goes to a black screen and just hangs there. At this point I can't do anything. I can't turn the phone off then on again with the power button, nothing shows up on the screen. The only response I can get is that the blue notification LED turns on for a bit after I press some buttons.
After that, I put the phone in recovery mode (using Phil's Touch Recovery mod, or something by that name), and tried to ADB pull the my backup build.prop (called build.prop.bak) from the system folder; adb tells me "remote object does not exist". I then tried pulling a copy i put in the /sdcard/ folder, and that worked. So I had the proper build.prop on my pc (with the i9505 settings), and i then pushed it to /system/build.prop. All should have been good at that point, but when I try to boot I get the same problem.
I then installed a recovery file manager http://forum.xda-developers.com/showthread.php?t=1646108 and had a look around in that. According to it there were only 2 things in the /system/ folder; an empty folder called "bin" and the build.prop that I pushed there earlier. From what I remember when I originally edited the build.prop file, there were heaps of folders and files in /system/.
So it seems like something, for some reason deleted my /system/ folder Now I'm guessing I can just flash the stock firmware again (got that downloading now), but I don't want to lose all my apps and such. Is it possible to keep my old setup after flashing? (I don't plan on wiping/resetting anything during the flash)
I also read somewhere that maybe i have to mount/remount (i have no idea) the system folder, and then it might appear again, but I have no clue honestly.
Anything I can do? I really don't want to start with a completely fresh phone, I wanna keep my old setup.
Thanks
EDIT: I tried running "adb remount", and it says "remount failed: success" I don't know what that means, but I was hoping that the /system/ folder isn't lost, that it was just unmounted at some point and hidden in a different location.
Any ideas?
goraax said:
Any ideas?
Click to expand...
Click to collapse
is it entering into download mode????
tush1114 said:
is it entering into download mode????
Click to expand...
Click to collapse
Yep, about to flash stock firmware now, out of options. I just hope it doesn't delete stuff.
Re flashing fixed it, and i didn't lose any files. Just a couple of messed up settings etc, easy to fix. Gotta re-root it though.
goraax said:
Re flashing fixed it, and i didn't lose any files. Just a couple of messed up settings etc, easy to fix. Gotta re-root it though.
Click to expand...
Click to collapse
You better have an efs backup if youre gonna do more similar advnetures. Triangle Away doesn't work on S4 yet so Samsung wont fix the phone for you if you screw it up without major $$$.
SilentRazor said:
You better have an efs backup if youre gonna do more similar advnetures. Triangle Away doesn't work on S4 yet so Samsung wont fix the phone for you if you screw it up without major $$$.
Click to expand...
Click to collapse
Triangle Away is confirmed working on S4 9505.
Sent from my GT-I9505 using xda premium
HANDSY said:
Triangle Away is confirmed working on S4 9505.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Also for me
{
"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"
}
After unlocking my 996, I'm met with the unlocked warning screen:
{
"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've seen several other devices fix this with a flashable zip or img file to overwrite or mask the warning. I've yet to see anyone mention it in regard to the V20.
Any help?
Other devices being something besides LG...
That image is in aboot, and you can't modify aboot.
runningnak3d said:
Other devices being something besides LG...
That image is in aboot, and you can't modify aboot.
Click to expand...
Click to collapse
5X is an LG phone: https://forum.xda-developers.com/ne...gdata-tool-t3240052/post63826602#post63826602
It may have been BUILT by LG, but it is still very much a Google phone and they specify the software that goes on it. For the Nexus series Google used the reference implementation of the boot loader.
If you find an imgdata partition on the V20, please be sure and let me know
-- Brian
runningnak3d said:
It may have been BUILT by LG, but it is still very much a Google phone and they specify the software that goes on it. For the Nexus series Google used the reference implementation of the boot loader.
If you find an imgdata partition on the V20, please be sure and let me know
-- Brian
Click to expand...
Click to collapse
Fair point. Thanks for the insight.
Yes, I miss being able to replace this goofy screen as well, I replaced the same bootloader unlocked warning screen on my Moto G4 with this awesome Motorola Developer Edition screen - on that phone it was a simple fastboot command or alternatively a zip you could install via TWRP
I decided to take a look at this again. raw_resources on the V20 is the equivalent partition to imgdata on the Nexus 5X. However, the format is not compatible with the tool that was linked above.
On the 5X they used bitmap images, and on the V20 they decided to use RLE images.
If someone wants to spend some time with a hex editor to figure out the new format, this is doable.
-- Brian
runningnak3d said:
Other devices being something besides LG...
That image is in aboot, and you can't modify aboot.
Click to expand...
Click to collapse
unless you can decrypt the whole aboot which is unlikely.
aboot is not encrypted, it is signed. But as I stated above, I was wrong. The images aren't in aboot directly. They are in raw_resources which is read by aboot. raw_resources isn't signed.
runningnak3d said:
I decided to take a look at this again. raw_resources on the V20 is the equivalent partition to imgdata on the Nexus 5X. However, the format is not compatible with the tool that was linked above.
On the 5X they used bitmap images, and on the V20 they decided to use RLE images.
If someone wants to spend some time with a hex editor to figure out the new format, this is doable.
-- Brian
Click to expand...
Click to collapse
you are talking about this right ?
http://www.fileformat.info/mirror/egff/ch09_03.htm
That is correct. RLE has no header like BMP or JPEG, so you have to know where it starts and where it ends if you have several images contained in one file -- which is what raw_resources is.
There is an index, but since I don't mind the nasty warning, I am not going to waste my time figuring it out
I am sure that it is probably something like:
Name
Beginning offset in raw_resources
End offset in raw_resources
Animated
Frames
blah blah blah
If someone wants to take this on, I will be more than happy to give some input, but at the end of the day solving LAF is far more important to me...
-- Brian
runningnak3d said:
That is correct. RLE has no header like BMP or JPEG, so you have to know where it starts and where it ends if you have several images contained in one file -- which is what raw_resources is.
There is an index, but since I don't mind the nasty warning, I am not going to waste my time figuring it out
I am sure that it is probably something like:
Name
Beginning offset in raw_resources
End offset in raw_resources
Animated
Frames
blah blah blah
If someone wants to take this on, I will be more than happy to give some input, but at the end of the day solving LAF is far more important to me...
-- Brian
Click to expand...
Click to collapse
Thank you very much for checking into all of this. That's amazing feedback.
Hello there !
I have an issue where I want to go back to Windows from fastboot as explained in this post :https://forum.xda-developers.com/no...nt/restore-windows-phone-8-installed-t3608223 .
I have my TZ.bin and other necessary files, but when trying to flash them with the command "fastboot flash partition TZ.bin", I get this error message:
{
"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 there someone here smarter than me who knows how to solve that ?
First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).
TBM 13 said:
First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).
Click to expand...
Click to collapse
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...
r0mDU19 said:
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...
Click to expand...
Click to collapse
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?
TBM 13 said:
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?
Click to expand...
Click to collapse
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !
r0mDU19 said:
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !
Click to expand...
Click to collapse
Sorry, but i don't remember.
TBM 13 said:
Sorry, but i don't remember.
Click to expand...
Click to collapse
No problem, thanks again for the advices ! :good:
Weirdly enough, my problem came back.
That prevents me from flashing anything at all.
r0mDU19 said:
Weirdly enough, my problem came back.
That prevents me from flashing anything at all.
Click to expand...
Click to collapse
Same problem than today, replace partition with the partition name (TZ in this case).