Boot sound?? - Android Software/Hacking General [Developers Only]

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:

Related

[SOLVED] Regarding Custom Boot Animation

I was wondering if it's safe to flash new ROM with a custom boot animation active?
I want to update my SynergyROM as it's gotten slow and clunky, though it's about 40 revision behind the times. I haven't messed with customizing my phone for months, however, and am a bit rusty. I downloaded the latest SynergyROM, made my backups, and was just wondering about this. In fact, I'm searching for my bootanimation.zip right now, not sure where I manually installed it... lol
Also, apparently there is a way to just flash boot images now? Anybody have a link to some solid info?
Thanks in advance!
Weioo said:
I was wondering if it's safe to flash new ROM with a custom boot animation active?
I want to update my SynergyROM as it's gotten slow and clunky, though it's about 40 revision behind the times. I haven't messed with customizing my phone for months, however, and am a bit rusty. I downloaded the latest SynergyROM, made my backups, and was just wondering about this. In fact, I'm searching for my bootanimation.zip right now, not sure where I manually installed it... lol
Also, apparently there is a way to just flash boot images now? Anybody have a link to some solid info?
Thanks in advance!
Click to expand...
Click to collapse
bootanimation.zip is in /system/media, so it'll get formatted when you flash a new rom anyways.
I'm assuming you're referring to bootanimations or splash screens, not boot.img's ..... But then again confused by what you're asking. Bootanimations just need to be put in a zip and the updater-script push it to /system/media. Splash screens there's a thread explaining how-to.
Sent from my SCH-I535 using xda app-developers app

[Q] New to rooting and XDA! So hi! :D few questions...

Alright, so I'm pretty new to all of this. I've read the threads here for probably 2 years, and finally decided to join because I rooted my phone. It's rather old to be honest my phone. It's a Samsung Galaxy Gio. Gt-S5660M (Canadian) (M). Well anyways due to it being a Samsung phone, and my phone having stock kernel. I believe that's how it is. Plus it having the stock rom, but bing rooted, the files for startup animations are called - "samsungboot.qmg" , They all have that suffix of .qmg . So its made trying to understand how to implant a new boot animation rather difficult. Should I root my phone to a different version in hopes that it changes the system files and no longer requires a qmg. File but rather can utilize a bootanimation.zip file instead? I could be completely off, mainly the reason I am assuming this is becausemost pre-made animations are built in a .zip format. Well any help would be much appreciated, I'd like to learn as much as possible about what is possible and can be achieved. Or how to change that animation would suffice. . Currently running GB 2.3.4 rooted. If any specs are needed I'd be glad to share. Even images of the system folders if it helps anyone in aiding me.
You have to use ODIN
You have to use ODIN, look for it on the search pane.-:silly::good::cyclops:
Alright, that would make sense!
TheMiracle said:
You have to use ODIN, look for it on the search pane.-:silly::good::cyclops:
Click to expand...
Click to collapse
But, still though, I will have to take a look into it, what exactly will I be doing in odin? Does it convert file format, or am I changing my phone's OS again? Having to use Odin is better than me being in the dark, but I'm just curious as to how it helps with my problem. Thank you for your reply however. Hopefully you can help me work through this. -.-
Everything You Need to Know About Rooting Your Android Phone
http://www.lifehacker.com.au/#!5789397/the-always-up+to+date-guide-to-rooting-any-android-phone
A beginners guide to rooting for Android
http://www.androidauthority.com/root-android-277350/
Well, my phone is already rooted... I had a rather specific question about getting a custom booting animation... And then wanted to know how exactly Odin would aid me with that.

we need safestrap for t337a!

AT&T locks us out, is safestrap the way in?...​
Total noob here. Will be researching how safestrap works. If anyone knows where I can find out how safestrap works please share. I am also going to try see if I can enlist help from devs who got it working on sgs5 and similar devices... has anyone tried safestrap for t337a?
Any help/info is appreciated
Already got a dev trying to port it for our 337a. [emoji106]
Hey guys. I have the t377a. Is there a root method for NK2? I have looked everywhere and have found nothing.
pre4speed said:
Already got a dev trying to port it for our 337a. [emoji106]
Click to expand...
Click to collapse
Happy New Year !
okay, i tried faking it with safestrap and so far it's booting me to my actual recovery....which is annoying.
scouring through hashcode's stuff on git and wondering if there's enough there to put together,
i got one boot to hang and was hopeful , adb logcat showed a dead stop at unable to find /sys/class/backlight blah blah
should be interesting ! yay.... :silly:
m
okay,
i've rounded up what source i could and after overcoming a VERY silly mistake on my part,
i am now trying to stitch a build together.
What i'm not certain of is if i can test it correctly on a device that isn't locked.
When/if/when i get it working and tested as far as i can take it, i will still need testers.
I am working from the hltexx device source since my initial mod attempts seemed to grab with that safestrap version.
The problem with that mod/test seemed to be that the recovery could find /data and /cache but, not /system.
My guess is that even though i can modify the *apk's configurations and repack it, the partition scheme and/or some of
the hardware specifics [display/backlight] are hard coded/built in to this particular build/binary.
Anyway, :silly:
m
moonbutt74 said:
okay,
i've rounded up what source i could and after overcoming a VERY silly mistake on my part,
i am now trying to stitch a build together.
What i'm not certain of is if i can test it correctly on a device that isn't locked.
When/if/when i get it working and tested as far as i can take it, i will still need testers.
I am working from the hltexx device source since my initial mod attempts seemed to grab with that safestrap version.
The problem with that mod/test seemed to be that the recovery could find /data and /cache but, not /system.
My guess is that even though i can modify the *apk's configurations and repack it, the partition scheme and/or some of
the hardware specifics [display/backlight] are hard coded/built in to this particular build/binary.
Anyway, :silly:
m
Click to expand...
Click to collapse
You know how to get ahold of me and you also know I'll test anything. I'm ready! [emoji106]

[Completed] HTC Vivid won't boot, possibly after build.prop change

Hello,
Pretty new to rooting, tried to root my HTC Vivid to install some apps which are "incompatible" with my device. Unlocked bootloader and rooted successfully by installing TWRP recovery and installing the supersu zip. After copying the build.prop file to another folder I proceeded to make some minor changes to the build.prop file with ES File Explorer. Essentially changing the model ID of the phone to another device to try to prompt Google Play to show the incompoatible apps, didn't touch anything boot-related or anything else. Phone was working fine at that point, rebooting ok, but Google Play still showed the apps as incompatible, so I temporarily brought back the old build.prop file by copy/pasting it from the folder I made. The system indicated the copy was made successfully, and I tried to reboot once more. That is where the problem started.
When the power button is pressed for a second or so, the phone vibrates once and shows the starting splash screen (HTC) as it did when working, and then the screen goes blank, although the LED backlight is still on (so phone has power). Nothing comes after, no "HTC quietly brilliant" logo nor the chime that indicates it's booting up. At that point it stops responding to any stimulus except the removal of the battery, at which point the LED backlight finally goes off. Waiting for ~10min solved nothing, still blank black screen with backlight on. Upon reinserting the battery, the phone once again responds to the power button, with the same results.
I can boot to recovery by holding down Vol down and pressing power, and there I get the usual options including Fastboot, Recovery, etc. I tried doing a factory reset. It gives a bunch of error messages along the lines of "can't mount emmc", then says it's starting the reset, and gives a successful completion prompt after half a minute or so. However, that seems to do nothing at all to fix the problem (tried 4x times, with SD card in and out).
The only change that comes to mind is the last replacement of the build.prop file I did, which should have just restored the original. Assuming the factory reset doesn't actually reset that file (where would it get a copy to do so?) perhaps it being broken is preventing me from booting after the reset. Just my theory though, and could be something else.
From what I understand I could try putting a recovery image on the micro sd from a PC, then doing a recovery rather than a factory reset from the TWRP menu to replace all the files, including the potentially problematic build.prop. However, I didn't make a backup of the system before this happened (learning experience) and have no such image. Could anyone perhaps point me to a clean image for the Vivid that I could download and flash to my phone with recovery? Or otherwise shed some light on what could be causing the problem? I also realize there are various unbricking tutorials online, but after many hours of this I'm a bit too exhausted to follow all of those just to see if they work or not.
Edit: Upon further research I realize I can try to flash a new rom to the Vivid, but no matter how much I search I can't find a working link for a stock ICS .zip. There is a RUU .exe file from HTC but my phone can't get past fastboot, so I'd need to do this with a zip file. Anywhere I can get a working one? I could also try a custom rom, I just have 0 knowledge of those so don't know which would be a safe bet.
Would appreciate any help, and hope the post isn't overly long. Tried to give as much info as I could. I already spent a ton of time on both the root procedure and trying to fix this and would really like to hear professional opinions before breaking anything else. Thanks for reading.
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
jd1639 said:
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
Click to expand...
Click to collapse
Thanks for the advice, I basically got into rooting from scratch a day ago, so many resources I don't know about. Trying to return to stock, but I need a rom of the stock in .zip form since the phone can't get past recovery, and having trouble finding that. Perhaps due to age of phone, but most links to those seem to no longer be functional.
rohanreddy277 said:
Actually u shouldnt have rooted with that zip file containing supersu u actually should have done it with kingo root. anyway, the best waty to revive it is to install cyanogenmod. download the version for ur device and google how to install cyanogenmod. this will give a new life to ur phone. hope it helps.
Click to expand...
Click to collapse
Right, I basically learned as I went along for this root, haven't even heard of kingo before. I was very careful, but apparently something still went wrong. Thanks for the suggestion, I'll try that mod and see if it works.
Edit: I'm only finding a nightly build for the Vivid on the CyanogenMod website, with no stable versions. Nightly build is dated two years ago, so clearly no stable versions coming. While I'm in no position to be picky, and I'll try it if needed, I'd rather not break what's still functioning in my phone. Any mods out there that are stable for the Vivid?
Edit2: the nightly cyanogen build seems to have brought the phone back online, but besides the different look and feel from what I'm used to, it doesn't seem to have Google Play... so I can't download anything. It also isn't seen by HTC Sync so I can't run the RUU from there, but I did successfully extract the rom.zip file using some instruction on this forum from the stock ICS RUU .exe. However, installing that from twrp recovery fails as it cannot open the zip, and an attempt to use the "fastboot flash zip rom.zip" command fails saying it's not allowed. Integrity of zip fail is tested to be ok with an archiver program. The zip file extracts properly, and I can flash things like boot.img and recovery_signed.img to the phone, yet system.img cannot be flashed (data length too large error). Not sure what to try next.
Thread closed.

The struggle... (64 bit recovery porting)

I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.
lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.
Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?
As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.
jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.

Categories

Resources