Hello. I have been trying to locate and extract the image file that is used for the boot image for the brief seconds before the boot animation.
This is the image with the custom unlocked padlock , the Samsung Galaxy Note 4 banner, and the powered by android footer.
I've been trying to extract my param.bin in order to get the logo.jpg however if had failure I have found posting of others logo.jpgs but they do not have the unlocked padlock. Here is the image I have found if anyone could help me if the full resolution image that I am looking that would be awesome.
chugs said:
Hello. I have been trying to locate and extract the image file that is used for the boot image for the brief seconds before the boot animation.
This is the image with the custom unlocked padlock , the Samsung Galaxy Note 4 banner, and the powered by android footer.
I've been trying to extract my param.bin in order to get the logo.jpg however if had failure I have found posting of others logo.jpgs but they do not have the unlocked padlock. Here is the image I have found if anyone could help me if the full resolution image that I am looking that would be awesome.
Click to expand...
Click to collapse
you are asking for trouble champ. that splash screen isnt the bootloaders splash. that is secondary program loader. if anything gets ****ed up there the phone is gone . you would lose download and recovery . it would truly be a brick
mojoswagger1980 said:
you are asking for trouble champ. that splash screen isnt the bootloaders splash. that is secondary program loader. if anything gets ****ed up there the phone is gone . you would lose download and recovery . it would truly be a brick
Click to expand...
Click to collapse
Well what I'm doing is making a normal boot animation but I want seamless fade from that unlocked padlock image. I'm not looking to change the splash but I am looking for the full 1440x2560 image that the phone already uses, that way I won't have issues with the placements shifting in between frames.
chugs said:
Well what I'm doing is making a normal boot animation but I want seamless fade from that unlocked padlock image. I'm not looking to change the splash but I am looking for the full 1440x2560 image that the phone already uses, that way I won't have issues with the placements shifting in between frames.
Click to expand...
Click to collapse
It's not an image file . Rather it's not an image file in the way the bl and recovery are . It's not part of the ROM at all it would be there with no os installed it is an embedded partition known as the secondary program loader . But cryptic warning aside I have no idea ......I dont even see it on the device tree which implies it is on a chip that doesn't require kernel support to operate . Good luck man . You are looking a chip that must have voltage regulator of its own i.e transistor or fuse
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
mojoswagger1980 said:
It's not an image file . Rather it's not an image file in the way the bl and recovery are . It's not part of the ROM at all it would be there with no os installed it is an embedded partition known as the secondary program loader . But cryptic warning aside I have no idea ......I dont even see it on the device tree which implies it is on a chip that doesn't require kernel support to operate . Good luck man . You are looking a chip that must have voltage regulator of its own i.e transistor or fuse
Click to expand...
Click to collapse
PS. Supposing you do find it would most likely require JTAG to interact with
---------- Post added at 01:39 AM ---------- Previous post was at 01:27 AM ----------
mojoswagger1980 said:
It's not an image file . Rather it's not an image file in the way the bl and recovery are . It's not part of the ROM at all it would be there with no os installed it is an embedded partition known as the secondary program loader . But cryptic warning aside I have no idea ......I dont even see it on the device tree which implies it is on a chip that doesn't require kernel support to operate . Good luck man . You are looking a chip that must have voltage regulator of its own i.e transistor or fuse
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
PS. Supposing you do find it would most likely require JTAG to interact with
Click to expand...
Click to collapse
BTW I think the idea is epic. I just think u would need Samsung to hop on board to make it happen . If it's even possible . Android isn't live boot . Those screens represent various stages of the load process dub "bootstrap". Though I fail to see how grafix are essential to the load .....I mean technically if u had no screen at all it should load. But there may be a noticeable delay as it switches fro secondary program to bl to rom
mojoswagger1980 said:
It's not an image file . Rather it's not an image file in the way the bl and recovery are . It's not part of the ROM at all it would be there with no os installed it is an embedded partition known as the secondary program loader . But cryptic warning aside I have no idea ......I dont even see it on the device tree which implies it is on a chip that doesn't require kernel support to operate . Good luck man . You are looking a chip that must have voltage regulator of its own i.e transistor or fuse
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
PS. Supposing you do find it would most likely require JTAG to interact with
---------- Post added at 01:39 AM ---------- Previous post was at 01:27 AM ----------
BTW I think the idea is epic. I just think u would need Samsung to hop on board to make it happen . If it's even possible . Android isn't live boot . Those screens represent various stages of the load process dub "bootstrap". Though I fail to see how grafix are essential to the load .....I mean technically if u had no screen at all it should load. But there may be a noticeable delay as it switches fro secondary program to bl to rom
Click to expand...
Click to collapse
I ended up with a copy of the padlock. The custom and the padlock are veriZon only images. I was able to extract the logo. And it is a change able image. It's alot of work to inject a replacement but I wasn't trying to. I was able to finish the boot animation I'll have it posted soon.
chugs said:
Hello. I have been trying to locate and extract the image file that is used for the boot image for the brief seconds before the boot animation.
This is the image with the custom unlocked padlock , the Samsung Galaxy Note 4 banner, and the powered by android footer.
I've been trying to extract my param.bin in order to get the logo.jpg however if had failure I have found posting of others logo.jpgs but they do not have the unlocked padlock. Here is the image I have found if anyone could help me if the full resolution image that I am looking that would be awesome.
Click to expand...
Click to collapse
Mmblck017 (lol watevs that's close to correct) on partioning table is sys boot image .
Related
I accidentally used Crossix's Custom Build.prop for HC on my A100. I'm running ICS. Had I read his thread on it, I wouldn't have a problem. But I found it through someone else's post and they made it sound as though it worked on ICS too. Right now my tab is stuck in an infinite boot loop and the power button/volume button combo does not work for recovery.
Can anyone help? Or am I needing to now buy a new one?
Thanks in advance.
No you don't need to buy new one so calm down.
But some more info is needed.Do you have unlocked bootloader and custom recovery?
If not (that's is more likely) you will need update.zip on external sd card for Power+Vol combination to work.And this update script can contain only build.prop that to be flashed.
Here comes the good part.If the above is true this zip will do the job.
Good Luck!
I have the same problem stuck in infinite bootload loop although my down+power works and I can go i nto fastboot mode. I downloaded the zip file but it wont open says the file is corrupt or encrypted. Can someone help me? Also cant get adb running on my pc followed all directions and cant get commands to work...
---------- Post added at 06:21 PM ---------- Previous post was at 06:19 PM ----------
Also my bootlaoder is unlocked...
Maybe I'm doing something wrong?
@ Zleto,
Unfortunately, it didn't work. Unless I'm doing something wrong? I have ICS rooted with Crossix's SD Swap Mod. Could that be why it isn't working? You are correct, I do not have unlocked bootloader or custom recovery.
Thanks for the help!
Hi All.
I have a Samsung Galaxy S4 Mini LTE (GT-I9195) which displays a White Screen when powered on.
The only thing that I can see is the SGS4 splash screen at boot and after that the screen turns to White. When I try booting into Recovery Mode, The splash screen pops up saying "RECOVERY BOOTING" and afterwards, the screen turns white. I can, however, boot into download mode which leads me to think that this is a software problem
I have opened up the entire phone and ran an inspection on the parts and they seem to be fine. I have tried flashing the JB software using a guide posted on this forum but it failed as I'm stuck on Bootloader v2 (Curse you Samsung) from the update to KK some time ago which makes it impossible to downgrade the OS.
Another thing to note is that the device responds to touch as I have an assistive light widget and it turns on when I tap the place in which I have it on my homescreen.
The phone is not under warranty anymore as my carrier only has a 1 year warranty for phones purchased from them and I would like to try and fix it myself instead of having to pay a sum of money to get this device working again.
I have spent several hours searching and have basically landed myself back at step 1 - with a non-working device.
I appreciate any and all help provided with this issue and will try and provide more information if needed.
Thanks!
Why don't You try to flash it with 4.4.2?? If You can see splash and nothing after that it's not related with screen but firmware or memory. Boot Your phone in download mode and flash it with Odin to stock 4.4.2. If it doesn't help Your eMMC can be fried. Unfortunately it's common issue in S4 Mini but the first time I've heard about white screen with fried eMMC. Anyway good luck.
Chamelleon said:
Why don't You try to flash it with 4.4.2?? If You can see splash and nothing after that it's not related with screen but firmware or memory. Boot Your phone in download mode and flash it with Odin to stock 4.4.2. If it doesn't help Your eMMC can be fried. Unfortunately it's common issue in S4 Mini but the first time I've heard about white screen with fried eMMC. Anyway good luck.
Click to expand...
Click to collapse
Thanks so much for the quick reply.:good:
I will try doing so. Could you please provide me with a link to download from, I would really appreciate it.
http://www.sammobile.com/firmwares/database/GT-I9195/
You need to register to download but it's free. Choose Your country and then You will see all available files.
Chamelleon said:
You need to register to download but it's free. Choose Your country and then You will see all available files.
Click to expand...
Click to collapse
Okay Thanks Man. I'll let you know how it goes:good:
Chamelleon said:
You need to register to download but it's free. Choose Your country and then You will see all available files.
Click to expand...
Click to collapse
Okay, so after getting around to downloading the files for my country (I chose the South Africa (Vodafone)) and trying to flash that, I'm now recieving an error near the end saying invalid ext4 image while flashing some hidden.img (something like that) file. After some googling, I found that I need to Flash a new Partition Information Table (PIT) with the OS because of different file sizes, however, I am unable to find that PIT file. What do I do now?
First try to flash different file. For example choose stock GB without any brand. Sometimes branded flashes are corrupted.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
When I will be in my service center today I'll look on server for PIT file. I should have some.
Hello there!
Didn't saw my problem in the forum so i m posting here. The problem:
I have a bootloop, yeah not quite original, but the bootloop is due to my boot animation (never heard of that problem, i m quite new with zenfone). I've made a personal boot animation which is probably too big 62Mo in 2 parts (part0 and part1).
I m quite sure the problem comes from here because I was working on my boot animation, the only manipulation i made is replacing bootanimation.zip in /system/media/ . The previous one was quite similar to the problematic one, it was just a bit lighter (52 Mo), and the only change i made is adding some png to the file part1.
On my screen the firs part (part0) of bootanimation.zip plays normaly (a bit slow but ok) then the second part (named part1 in bootanimation.zip) begin to play and block at 55%. Then i got a white screen and reboot. Then animation again, block at the same time, white screen and restart the second part of the animation, block, white screen, 2nd part etc...
I would looove to erase bootanimation.zip from /system/media/ but it's impossible from adb or from adb shell (root permission denied in both case - root and su didn't work- )
So my plan was a factory reset but a factory reset does not reset bootanimation.zip
So my second plan is to reinstall the frimware but i'm not even sure this will work...
pls help...
Go to the section on unlocking the boot loader download the black splash screen and flash through fastboot, should fix your problem
Sent from my Nexus 7 using Tapatalk
It'll work.
jimchee said:
Go to the section on unlocking the boot loader download the black splash screen and flash through fastboot, should fix your problem
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Hi thanks for the answer!
But what does unlocking the boot loader will do? And the black splash screen?
My plan was to open a terminal with my device connected with fastboot and send fastboot flash "UL-Z00A-2.20-40.139-user.zip"
Then update from adb ; adb sideload UL-Z00A-2.20-40.139-user.zip; factory reset; pray...
The point is when i rooted my phone i did it through a "one click method" (yeah i was younger and stupid) i dont realy know if it had unlocked my boot loader...
2nd point I can't get root privilege when I m in adb shell I dont know if the method for unlocking the boot loader will work.
You don't need to unlock the boot loader just flash the black splash screen, that is the boot up image, nothing else in that section is important at this point
Sent from my Nexus 7 using Tapatalk
---------- Post added at 02:01 PM ---------- Previous post was at 02:00 PM ----------
You won't need to reflash the whole rom that way
Sent from my Nexus 7 using Tapatalk
jimchee said:
You don't need to unlock the boot loader just flash the black splash screen, that is the boot up image, nothing else in that section is important at this point
Sent from my Nexus 7 using Tapatalk
---------- Post added at 02:01 PM ---------- Previous post was at 02:00 PM ----------
You won't need to reflash the whole rom that way
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
you have my thanks sir!
My phone has started. It's no more rooted, do i have to root it again to erase my problematic file or is there another method?
Not enough information, what did you do to get it to start? Did you flash the splashscreen? Give me the steps you used
Sent from my Nexus 7 using Tapatalk
Hi all,
I apologize if opening a new thread as first post but I did that after an extensive research and I noticed the questions in the sticky are 4 days old.
I purchased a soft bricked Asus Zenfone 2 ZE551ML Z00AD for fairly cheap as I needed a decent dual-sim phone.
Initially it was just stuck on the first asus screen and nothing more - not even spinning wheel. It would not go in recovery mode with vol+ and power, nor vibrate.
Tried to adb / fastboot but even when adb was listing the device ok, fastboot would just say "Waiting for device"
Leaving the phone connected to PC I noticed it was rebooting by itself after a few minutes and leaving it alone for about 15 mins it went in a TWRP 3.0.0.0 screen - was probably installed before....
From there I wiped everything and managed to install latest image that I downloaded from Asus site - UL-Z00A-WW-2.20.40.183-user.zip by using an SD card. Nothing else installed
The phone booted up just fine after this - I had some troubles with the Asus Cover screen going on/off every second but I managed to turn it off - proximity sensor and light sensor tested ok. It is not rooted now.
I have a few problem though and I need your expertise and advice.
1. There is absolutely no sound from it. Speaker test in normal and Safe mode stays silent. There is sound through the headset.
2. I does not detect any SIM card in either Slot 1 or 2
2. Screen never goes off unless I press the power button - display set to 1 min and lock to swipe.
3. Storage only shows 16Gb while it should show 64GB
Given the issue described I would suspect this is still a firmware/software issue but I would like someone with experience to confirm and hopefully advise a few steps.
Thanks!
Can you get into bootloader now?
Sent from my SM-T710 using Tapatalk
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
I agree that this sounds like a software issue and if it was my phone I would take the following steps.
1. hard reset
2. Download the pre rooted software that shakalaka provides, you'll find it in the thread for flashing from cn to ww in this forum it also gives all instructions for downloading, prep & flashing.
3. Flash through bootloader everything but the bootloader
4. Reboot and it should work fine, this is the procedure I have always had to follow whenever my Zenny won't find the Sim card.
5. Let us know how that worked for you?
Sent from my SM-T710 using Tapatalk
yes I can - TWRP is still active - I installed an older firmware from Asus website - 139 but the cover flicker is much worse and I got it stuck on now
I have to reload it again
Thanks for the tip = I will try that as well if older firmware fails too
Edit - older firmware did not fix anything - trying your route next
EDIT2 - after another 3h on 2 PC's still cant make fastboot to work. I will try tomorrow on another one
What are you getting with fastboot? Error msg? You need to flash .183, if you want to flash earlier you have to change the boot loader to earlier edition
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 12:39 PM ---------- Previous post was at 12:39 PM ----------
Forget term it will not help you it is part of the problem
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:39 PM ----------
Not term, twrp
Sent from my ASUS_Z00AD using Tapatalk
so far I tried:
UL-Z00A-WW-2.20.40.183-user.zip - the only one usable with the original problems - sound, SIM, storage space, screen
UL-Z00A-WW-2.20.40.139-user.zip - Asus cover flicker makes it aamost imposible to reach the normal screen
UL-Z00A-WW-2.12.40.11-user.zip - not booting - stuck at first android screen then rebooting itself until it goes in TWRP
cm-13.0-20160512-NIGHTLY-Z00A.zip - won't install from TWRP
things got worse though
Used xFSTK - and after a few unsuccessful tries I got stuck on the TV 4 color screen with no bootloader anymore and cannot reach fastboot anymore and TWRP is gone. FW will load in xFSTK but not the OS image - seems problem is more common - and the issue is that there is no proper file with signature for my Z00AD available anywhere.
I tried Asus Flash tool as well - there are only 3 raw images I was able to find but none will match the device and it will not show up.
Also tried Intel Flash tool - That will see the phone but could not find any flash.xml for it.
Now I don't have any way to use adb and will have to wait until a proper droidboot_dnx.img.POS_sign.bin or .raw image is released somewhere...
If I find any other solution I will post it here
I do not understand why you continued to try to flash a zip through twrp, I specifically told you that it would not work and you have now made fastboot, you're only way to solve this problem, inaccessible. If you have any hope of rescuing now it will have to be with flashing the raw image, but frankly I think you have little possibility of that working now.... situations such as yours can almost never be solved with recovery, you almost always have to use fastboot, so good luck, I have no other solutions and you are likely in need of a new device.
Sent from my ASUS_Z00AD using Tapatalk
@jimchee I am also having a "no sim-no sound error". My device is YU YUREKA +, Tried to flash it with custom rom 'firehound' but didn't got any luck with the issue.
Jimchee what do you suggest(please answer in little detail as i am kinda noob when it comes to this) I flashed using twrp
Thanks in advance
Don't know that device at all and never heard of that rom so I have no advice for you sorry
Sent from my LG-D693n using Tapatalk
I received my Mi A2 Lite yesterday (yay!). I have unlocked the bootloader and have rooted. I opted not to install TWRP since backups can't be restored. The only issue I have is with the unlocked bootloader...when I boot up I get the warning message that the system has been unlocked. Is it possible to edit the logo.bin with a different image so I (we) don't need to see that anymore? I am coming from a long use of several Moto phones where I could easily create a new logo.bin with a custom picture to hide the unlocked bootloader warning. I used a program called Moto Boot Logo Maker. It appears to be catered to the Moto line but may work with the Xiaomi. If anyone can provide the stock logo.bin I can try editing it. Or at least tell me how to extract the logo.bin from my phone. I tried extracting it with Terminal Emulator but it failed saying the location didn't exist. So what I need to find is the location.
Thanks!
inside stock rom there's a file called splash.img, that i think is the bootimage, but i'm not sure the warning can be removed, i think only the bootimage could be modified.
Also take care of what you are doing because flashing splash may brick your phone in a way that only edl mode can fix.
Let me know if you find a way
I found this for the Xiaomi Mi A1. I replaced image #5 with the same Android One image that starts off the boot animation. I then resized all the images to 1080x2280 to match our device, and had to compress image #2 smaller for the program to run...but it completed without errors and gave me a splash image! I am hesitant to flash it though - the path for most devices appears to be:
/dev/block/bootdevice/by-name/splash
The path for splash image I found is:
/dev/block/platform/soc/7824900.sdhci/by-name/splash
I have included the resulting splash image for anyone brave enough to try. It is NOT flashable. It will have to be done manually through adb or Terminal Emulator.
I haven't been brave enough to flash my "new" splash.img yet. I have extracted the stock splash.img from the stock firmware download and am hoping/trying to find a way to extract/view the files/pictures on it before proceeding. I haven't had any luck using winiamge or other similar programs. Anyone have an idea to open/view the splash.img?
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
mn1968 said:
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
Click to expand...
Click to collapse
Lol success!?
mn1968 said:
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
Click to expand...
Click to collapse
I have already seen that, it happens when spash image is wrong(i think on all qualcomm devices).
ncar123 said:
Lol success!?
Click to expand...
Click to collapse
I said "Kind of"
mac12m99 said:
I have already seen that, it happens when spash image is wrong(i think on all qualcomm devices).
Click to expand...
Click to collapse
Wrong how? What would be needed to make it right?
I have replaced many logo.bin on Moto phones (qualcomm variants). It is easier though with Moto though since there is tool designed specifically for editing Moto logos. The tool I used from the Mi A1 may need to be tailored for the Mi A2 Lite but that is beyond my capability.
Does anyone know any more about how to do this? I found that when I flashed the splash.img from post #3, aside from booting with a black screen with the Linux penguin, it also messes up the image on the fastboot screen (which is nothing special as it is). That being said, fastboot still functions with ADB, just the image on the phone is messed up. I wound up reflashing the stock spash.img and am dealing with the unlocked bootloader message.
mn1968 said:
Does anyone know any more about how to do this? I found that when I flashed the splash.img from post #3, aside from booting with a black screen with the Linux penguin, it also messes up the image on the fastboot screen (which is nothing special as it is). That being said, fastboot still functions with ADB, just the image on the phone is messed up. I wound up reflashing the stock spash.img and am dealing with the unlocked bootloader message.
Click to expand...
Click to collapse
Did you manage to get any further on this? I'm considering to flash your image and get the Linux pinguin, it's better than the warning screen.
Embeeweezer said:
Did you manage to get any further on this? I'm considering to flash your image and get the Linux pinguin, it's better than the warning screen.
Click to expand...
Click to collapse
No. I kind of gave up on this. Maybe one day I'll try again.
mn1968 said:
No. I kind of gave up on this. Maybe one day I'll try again.
Click to expand...
Click to collapse
Yeah, its very annoying. I dont like that super bright white boot animation screen. I would just prefer and easily color invert :good:
I found this on Motorola One forum, it should work with A2 Lite. I didn't test it tho, I don't have unlocked bootloader.
I am using splash.img from
https://translate.googleusercontent...JrhgOvxxsyFr7imjXOCYKUEm6Y9lTRw#entry83388689
Flashed via fastboot, works on Oreo as well.
locovibe said:
I found this on Motorola One forum, it should work with A2 Lite. I didn't test it tho, I don't have unlocked bootloader.
Click to expand...
Click to collapse
I am 99.9% certain that won't work. Moto phones use a logo.bin. The Xiaomi uses a splash.img. FInding a program to edit the splash.img is the problem.
Chrono Leggionaire said:
I am using splash.img from
https://translate.googleusercontent...JrhgOvxxsyFr7imjXOCYKUEm6Y9lTRw#entry83388689[/url]
Flashed via fastboot, works on Oreo as well.
Click to expand...
Click to collapse
Your link goes to a 400 error.
Sorry, it should be fixed now.
Check post #83
Chrono Leggionaire said:
I am using splash.img from
https://translate.googleusercontent...JrhgOvxxsyFr7imjXOCYKUEm6Y9lTRw#entry83388689
Flashed via fastboot, works on Oreo as well.
Click to expand...
Click to collapse
Could you upload it here please ?
Can't download (4PDA 404 error)
No problem, credits to search0123 from 4pda.ru
deleted