I treid to edit this file to get better video/photo/audio quality a while back but when I did edit it and rebooted I was stuck in a boot loop.
I want to give it a go again but do not want to end up in a boot loop again if I can help it.
Is there settings I should not edit or permissions I need to set etc to stop a boot loop? What causes the bootloop in the first place? I would of thought that editing this file would stop the camera from working and not the whole phone but hey what do i know
Can anyone provide some insight?
Cheers
most likely permission error
permission should be rw-r-r (read,write for root, read for group, read for global) or 644 depending on what you are used to
anyway, before you make changes, backup system in TWRP then do your stuff
in case something went wrong, simply restore system and no probs
Related
Hi guys,
unfortunately I cannot post in developers forum, because I am a new member. Therefore I have to ask here:
I am running ICSunday Final Rom with LafreeV2 script.
After installing the permissions of the script are automatically set on rw-r-r. But in another forum I read, that the script has to be executed for working - i.E. the permissions have to be changed to rwxr-x.
That sounded rational for me, so I changed the permissions like that - but after rebooting I got stuck on Android-Screen! (in the end I restored a Nandroid backup...)
Can anyone tell me, how the permissions are set right and why my phone did not boot again after changing them?
Thanks in advance and greetz,
Sarah
Hi everyone,
I'm using a cheap Android 4.0.3 tablet. It is a pre-rooted device and i am
able to browse the file system. I have read somewhere that the initlogo.rle
file is the encrypted logo. So I tried to replace/delete it to no effect. It
seems to be regenerated.
I also tried to set a constant/property in init.rc to try and disable the
boot logo and also no effect, the init.rc file seems to be regenerated as
well.
Is there a standard/effective way to replace this manufacturer logo?
Or at least disable it?
Many thanks in advance, I've searched through other posts but they
were mostly left unanswered or not applicable to my situation.
prokofiev said:
I also tried to set a constant/property in init.rc to try and disable the
boot logo and also no effect, the init.rc file seems to be regenerated as
well.
Click to expand...
Click to collapse
The init.rc file is located in the ramdisk and not writable from the booted system,
so you have to extract-edit-store-repack it from there.
prokofiev said:
Is there a standard/effective way to replace this manufacturer logo?
Or at least disable it?
Click to expand...
Click to collapse
There are lots of how-to-edit-your-boot-logo, just use the search button. "editing initlogo.rle" is a good start.
However... If you want to disable a boot animation easily, I would go for the /system/build.prop file.
This contains some of the system settings/properties.
Add the following line:
Code:
debug.sf.nobootanimation=1
Then save, close and reboot. Hopefully, you'll notice a difference. Good luck!
Thanks, editing build.prop disabled the bootanimation, so that was great.
However it does not disable the manufacturer logo display, which I
wanted to disable in the first place. It would have been great to find
something like a
debug.sf.nobootlogo property though.
I've browsed through a lot of posts, articles suggesting the
extract-edit-store-repack approach, but it's just far too much
trouble for me to go through just to turn the logo off.
Also, it's my first device, so still worried about bricking.
Well, it took me some time to get interested in digging deeper into Android hacking.
Anyway...
If you want to get further with Android development, I would advise you to unlock the bootloader - but remember to make a complete backup of your device. Nandroid or nanddump are preferable and can be performed, since your device is rooted.
Sent from my Xperia Arc via Tapatalk 2
Hi guys, before I start I'll say that I have searched all over the internet and here on the forums and I couldn't find my particular issue. Well the thing is that I edited the line in my build.prop "ro.build.version.codename=REL" to "ro.build.version.codename=L" so I could get the material design on the Google Now Launcher pulled from a Android L build here's the thread I got that app: http://forum.xda-developers.com/android/apps-games/app-android-lollipop-apps-launcher-apps-t2912905
I did that and now my device will boot up normally then I will reboot by itself then show the boot animation then repeat the same process again and again until I force the phone to recovery or fastboot.
By the way my device is the LG Optimus G (E970) running GEE 3 ROM 1.2 and TRWP 2.6.3.0 and I have a backup of the original build.prop on my PC. I don't want to lose my data and apps since I forgot to make a backup (silly me).
I would like to know if there is a way to push the build.prop file on my PC to my phone so I could just replace it, or create a flashable zip.
Please help me, and thanks in advance.
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
question
AntonyOrtega said:
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
Click to expand...
Click to collapse
how were you able to do it when you couldnt get past booting.
Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
positivehxcgo said:
Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
Click to expand...
Click to collapse
Sounds like you are on 4.5.3 but lost root. Might try to reroot using Kingroot although I believe that involves a reboot. Pretty sure your device will not restart (effectively brick) without build.prop. You really need to get adb working to expand beyond those options. Keep your device on charge to prevent a shutdown due to low battery.
I absolutely would not attempt a 3.2.8 rollback. There is an outside chance a factory reset from stock recovery would restore a generic build.prop if none is found. It generally will not repair or replace a damaged file and involves a reboot which could be fatal. This becomes an last resort option imo.
If you device was purchased from Amazon it may still be under warranty. Sometimes that is the best/only path. Good luck.
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
positivehxcgo said:
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
Click to expand...
Click to collapse
You will probably need to root via adb which is challenging and by no means certain. Take a look at this thread for ideas. You may want to reach out to @myotai as he faced a similar problem.
Hi There
I have been a long time Hacker of largely MTK devices. So I wanted to ask a question and see if there's anything I am missing here:
I have an Android 8.1 device, I have rooted it using Magisk no problem and I have successfully changed the bootanimation.zip and also the audio files. I have been able to release the rooted OS, get the OS back to a released state with the changes as I have simply kept the removed dm-verity flags that Magisk uses on the OS.
However, I am unable to change the build.prop at all.
If I copy the build.prop file from the device, edit it on the PC, and save it back it bootloops. If I edit it, roll back all the changes and re-copy it back to the device it is fine.
I noticed the original build.prop permissions are RW (Chmod 600). I tested the above chmodding to 600 and 644 and it makes no difference. If it has changes in it, it fails, if not it works!
So something somewhere is maybe checking the build.prop against an original and not liking it.
Is there anyone on here that could help shed some light on this at all?
Bump...Anyone?
So an update to this is that I have now successfully removed DM-Verity from this device. I have also managed this on many other devices. I prove this by installing all kinds of changes on the device.
So I can pretty much do anything with this device, almost like pre-Android 5.1, however whenever I edit the build.prop at all it bootloops.
What I have tried so far:
I have tried all kinds of permissions on the file
I have duplicated the /vendor/build.prop in an attempt to get round possible build.prop variety issue.
I have removed the /vendor/build.prop
I have replaced system/prop with original build.prop but still edited (and changed back) from my PC and the device boots OK.
So it looks like somethiung is looking up the build.prop file and checking something. Almost like a DM-verity for the build.prop.
Really out of ideas now. i can literally unlock/change anything MTK now except for this issue.
Any help is much appreciated.
Oh i forgot to mention, this is a systemless and not TREBLE OS.
I usually change /system/build.prop and have never had an issue up through Android 10. I know this is elementary and no intention to offend anyone - but are you sure the file is being saved with unix-style line endings.
File-permission must be set to 644.