Can anyone develop a boot logo (without the Unlock and signature verification warning) and boot animation without the use of TWRP? I'd love it if someone could point me to a how-to if they can't produce such a thing, please and thank you!
This would be awesome. Hopefully someone can figure it out. This was possible on the Nexus 5X but not the 6P, for some reason.
I fear with the latest SafetyNET update triggering with as little as an unlocked bootloader that this won't be possible for some time. However if there is a developer willing to tackle this, I'm willing to donate to the cause, as I'm sure others would be too. I know that many other people would love have black boot logo and the error gone as well.
Kalveitt said:
I fear with the latest SafetyNET update triggering with as little as an unlocked bootloader that this won't be possible for some time. However if there is a developer willing to tackle this, I'm willing to donate to the cause, as I'm sure others would be too. I know that many other people would love have black boot logo and the error gone as well.
Click to expand...
Click to collapse
How do we create a bounty? I have no clue. I'd throw in a dollar or two.
Well I tried changing the hex code in system\media\bootanimation.zip from white to black but that didn't do the trick. It basically just "removed" any animation whatsoever and booted up with a static white background and Google logo.
I would love someone to look into this more.
Anyone have any ideas on this?
Happened to me once. I rechecked the permissions 644 after I placed the files once again in solid explorer and there it was- not correct. Changed permissions, rechecked, permissions stood there, rebooted and it worked.
I wonder if the developer of the Weta ROM @Mentalmuso can assist. One of the main reasons I use this great ROM is to get the black boot logo (just the boot image, not the starting BL unlock warning). This way, I have a visual indicator of which slot I'm booting into. If it's black, it's slot A.
Here's one.
[BootAnimation] Darkish & Black Stock
mrZoSo said:
Here's one.
[BootAnimation] Darkish & Black Stock
Click to expand...
Click to collapse
You know, thanks for this. Actually, this thread points to another link and I used it to create my own flashable zip.
Related
Bootloader version I9020xxka3
Baseband version I9020xxkd1
Lock State - Unlocked
I followed the steps given on XDA forum to root my phone I was able to unlock the boot loader. But that's it. It doesn't go beyond it.
After selecting recovery, it did reboot but got the google screen with unlock icon.
Then splashed a installer screen, as if phone wants to install something and couldn't find it. Screen splashes an Exclamatory mark with in a triangle.
Now when I boot my phone it doesnot go beyond the google screen.
We all know, a lot of people have been facing this issue but how do we resolve it?
Is my phone useless or is there a way out? If we have genius devs who can rewrite the android platform I'm sure some dev can find a fix to this also.
I couldn't find a solution anywhere. But I brought my phone back to life.
Before you think of a root or ROM mod make a Nandroid back up.
SO here's the deal.
Why would it not work for me or you when root works for entire world?
It's sweet and simple, files we used were corrupted or USB drivers we are using, just don't fit.
So I looked around for best version of files we need like recovery.img or boot.img and repeated the process. If files are in good shape, it will work second time.
It's important you use same USD drivers which you used to find your way to get bricked else you'll keep getting "<Waiting for device>"
If nothing works (which I doubt) adb programming can push back the soul into the phone.
Heck, it ain't I-Phone ---- It's Opensource. Android doesn't die.
Hope it makes sense to a lot of people who be in a similar situation.
Okay, so here's my dilemma. Unlike most other people I want boot sound enabled on my ROM's. I have spent countless hours searching every forum and post, trying everything that is suggested. Nothing seems to work. The only breakthrough I've came across the last several months is that while running a ROM with boot animation support and a stock kernel I am able to achieve both custom mods. What I'm shooting for is to be able to do the same with a custom kernel. I'm relatively new to this but through process of elimination I have concluded that the coding for this lies in the boot image. Maybe I'm wrong but it seems that way.
Listed under the features in almost every single ROM the developer usually puts "muted boot sound" my question is, how do I un mute the sound? Is there a simple fix, possibly a script that I can run or does it involve pulling apart the boot image and editing code? If it has to do with the boot image could somebody possibly tell me what code needs to be edited. I have no problem decompiling and recompiling boot images, I'm just not sure what part of the code needs to be added. Any help would be extremely appreciated! I'll keep my fingers crossed!
Sent from a Shaftamle Galaxy S3
Shaftamle said:
Okay, so here's my dilemma. Unlike most other people I want boot sound enabled on my ROM's. I have spent countless hours searching every forum and post, trying everything that is suggested. Nothing seems to work. The only breakthrough I've came across the last several months is that while running a ROM with boot animation support and a stock kernel I am able to achieve both custom mods. What I'm shooting for is to be able to do the same with a custom kernel. I'm relatively new to this but through process of elimination I have concluded that the coding for this lies in the boot image. Maybe I'm wrong but it seems that way.
Listed under the features in almost every single ROM the developer usually puts "muted boot sound" my question is, how do I un mute the sound? Is there a simple fix, possibly a script that I can run or does it involve pulling apart the boot image and editing code? If it has to do with the boot image could somebody possibly tell me what code needs to be edited. I have no problem decompiling and recompiling boot images, I'm just not sure what part of the code needs to be added. Any help would be extremely appreciated! I'll keep my fingers crossed!
Sent from a Shaftamle Galaxy S3
Click to expand...
Click to collapse
see my post in andybone's mod thread. you need an edited volumedb in system/etc folder where the volume is raised. i think they just set the volume level in the db to 0 and the file i posted raises it so you can now hear sounds. confirmed to work on CR6.2 by myself. oh and you will need a PowerOn.ogg in system/media/audio/ui folder... hope it helps!!:highfive:
[NOTE] I should've posted this in the i9300 forums, not the Verizon ones.
Hey all,
I've been having some major issues with my i9300 recently. Probably due to my ridiculous stupidity when I erased the /data folder from my main storage on the phone (don't ask why - I don't know).
I've tried to flash a new ROM using various recovery methods however it just throws error messages at me.
I can boot the device into download mode however I've also tried to flash ROM's via this method and they still don't work. When I try to boot into recovery mode, the screen just appears with black and white stripes all over it and I cannot read any text or see anything that may be below it.
Any help or suggestions will be greatly appreciated and I may even donate $5 to the people who help me fix it.
Thanks,
Luke G
Hey guys and guyettes!
I somehow managed to put my One mini into a boot loop!
None of the options on the fastboot menu do anything other than turn the screen black and then go back to the boot menu... If anyone has any ideas on how to fix this it would be greatly appreciated!
And before anyone asks for whatever reason, no it is not rooted!
Things I've tried:
- Using ADB and SDK to unbrick it
- Hard resets, recoveries and factory resets
The last thing I did before it started the loop was install King of Thieves (a game).
Before the loop it ran out of power so I plugged it in and it went to the menu like it usually does then it just started too loop!
Thanks for any suggestions
~James
I'm currently chasing the same thing on my wife's phone. This is the 2nd time this has happened. (the first time was replaced by factory warranty). The ROM and everything is completely stock so I'm trying to unlock the bootloader using the HTC dev tools and I can flash the Unlock_code.bin but the screen never prompts me to actually unlock it... I'm hoping someone has a tried and true way of fixing this.
iceterminal said:
I'm currently chasing the same thing on my wife's phone. This is the 2nd time this has happened. (the first time was replaced by factory warranty). The ROM and everything is completely stock so I'm trying to unlock the bootloader using the HTC dev tools and I can flash the Unlock_code.bin but the screen never prompts me to actually unlock it... I'm hoping someone has a tried and true way of fixing this.
Click to expand...
Click to collapse
I have the bootloop menu which suddenly appeared for no apparent reason seeing as I haven't rooted the phone. It's an annoying problem that I see many people have except most people I see haven't quite got the same problem as myself...
Same issue...
I have a customer's phone, having the same issue. The customer brought it to me like this and I thought I would try to repair it. He is mentally challenged and so I really wanted to help him. But it's doing exactly what the OP stated. I even tried the same things before I found this thread. Unlocked the bootloader (but it did not actually bring up the screen to unlock the bootloader, the WinDroid Universal Toolkit simply stated it was unlocked). And yes, I did acquire the unlock.bin or whatever it was called.
So the phone will do nothing but reboot. I'm not sure how it got this way or if it can be fixed. That is why I am here.
Any ideas?
Thanks!
Da
PAinguINx said:
So the phone will do nothing but reboot. I'm not sure how it got this way or if it can be fixed. That is why I am here.
Any ideas?
Da
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=57727218&postcount=1365
probably this is the case
Hello I'm a student here for learning purpose. I've been messing around with custom ROM for over 3 years now and came across GrapheneOS and I liked it on my Pixel 4a due to its secureboot feature and others. So my question is can how can I use a custom boot amination in it? Since its non rooted and everything. Can it be done if so It would be a great help since I would like to use my own logo as I'm a game developer and I would like it very much. I've tried using flashing commands, tried changing it from file manager(not happening since dont have root access), magisk not working, twrp cant flash it. Is there any other way to do it? Thank you in advance.
Changing Android's boot animation always requires phone's Android got rooted.
More info here:
How To Change Boot Logo (Splash Screen) for Android Smartphones - AndroidFist
Splash Screen or Boot Logo on Android smartphone is crucial. But in case you are bored with the same old image, you can change it and here's how to do it.
androidfist.com
jwoegerbauer said:
Changing Android's boot animation always requires phone's Android got rooted.
More info here:
How To Change Boot Logo (Splash Screen) for Android Smartphones - AndroidFist
Splash Screen or Boot Logo on Android smartphone is crucial. But in case you are bored with the same old image, you can change it and here's how to do it.
androidfist.com
Click to expand...
Click to collapse
Yes I gathered that. So is there there a way to root this ROM. I also found a rooted version of GraphOS but the link is no longer supported. Another question... Can I change another Custom rom to secure boot... like LineageOS suppose, after I change the Logo? Revoke all access like similar to graphOS lets say.
jwoegerbauer said:
Changing Android's boot animation always requires phone's Android got rooted.
More info here:
How To Change Boot Logo (Splash Screen) for Android Smartphones - AndroidFist
Splash Screen or Boot Logo on Android smartphone is crucial. But in case you are bored with the same old image, you can change it and here's how to do it.
androidfist.com
Click to expand...
Click to collapse
Hello I found the source code on GitHub:
GitHub - GrapheneOS/device_google_sunfish: Pixel 4a device sources.
Pixel 4a device sources. Contribute to GrapheneOS/device_google_sunfish development by creating an account on GitHub.
github.com
I don't need step by step explanation can just redirect me to the correct thread where I can find how to change the boot image and compile it successfully. Thank you.