Develop Bugs

Can't edit main.conf file

Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175

neomagik said:
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
Click to expand...
Click to collapse
As we don't have write access to /system on a normal booted desire, you have to do all your work in recovery-mode.

I can get into recovery mode ok but how do I edit the file I want from there?
The options I have are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off

Extract the file out of the rom, change it, than push it back to the rom.
You can do that from ADB shell while your phone is in recovery.
You can find commands how to backup files and push/delete them back to ROM on this forums, or you can search it on internet.

dont forget to mount /system
adb shell in a new terminal screen
then mount /system

I can't figure out what I'm doing wrong.
I've tried the method suggested by allla and ivicask ie, using adb commands in recovery mode and I get the same result as using root explorer, the file appears to have copied successfully it reboots but the original file is back again
I've also tried vastlopers method and after lots of reading found that the device needs to be booted normally to 'remount' however when I try to push the file now it says "Directory not empty"
It seems to me that this adb method is just a long winded alternative to root explorer, none of which get the desired result.
Please help?

Bump. Bump.

I've now tried adb file explorer but can't figure out how to install Busybox on my device.
I'm out of ideas. Someone must know how to edit/overwrite the main.conf file.

I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?

neomagik said:
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
Click to expand...
Click to collapse
Yes it is. It's also written in the root tutorial!

Messed up build.prop, phone won't boot, can I push build.prop via adb?

My phone is on 4.1.2 still, and I had edited the build.prop to not update to 4.2 (after hearing all the problems). Now that 4.2.2. is out i decided to update, I tried restoring the build.prop file that i had as a backup of 4.1.2. I guess I must've changed some text without realizing.
Now my phone is stuck, it gives me the Google Logo with the unlocked sign, and then it disappears...and where there should be a boot animation...black. Nothing. Stays like that.
Any way I can push the build.prop via the computer using abd or something?

Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.

So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app

bodh said:
Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.
Click to expand...
Click to collapse
Yes, you need to 'cd /system' before typing the commands to change permissions and ownership, as you have them.
Sent from my Nexus

ksc6000 said:
So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)

Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
Then you should go to your own forums, as 99% of the info here wont do you any good

Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you pbootlease guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3

ksc6000 said:
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
Click to expand...
Click to collapse
Thanked you buddy !!

[Q] How to make stock ROM support INIT.D

hi guys, a friend of mine is asking me if there's something i can do to make her cp a bit faster/ smoother running stock rom (gb 2.3.6) since he don't want to use any custom rom. her cp
searching the thread, i was able to read some info that some was able to flash mod/ tweaks on stock roms to at least improve its performance. so i'm planning to install andrenaline engine or crossbreader on it but, as far as i know, flashing them requires ur rom, aside from of course being rooted, have cwm, etc., to support init.d which stock roms don't have. (corect me if i'm wrong)
i'm a bit in doubt doing this in the fist place, so any guide/ help or suggestions to make this init.d thing work is really really much appreciated. thnx in advance!
info i got (xda forum) about making stock rom support init.d Enable Init.d for Any Phones w/o Need of Custom Kernels

here, this link provide init.d support;
http://forum.xda-developers.com/showpost.php?p=32716432&postcount=3
flash zip_init.zip.
copy zip_init.zip to sd-card,
boot to cwm, mount /system, mount /data then flash zip_init.zip
check for test.log in /data if it is there or not, no test.log not working.
it work on my stock rom.
also flash adrenoboost v0.7 will boost perfromance from stock 5000 to 7000 (antutu benchmark).
adrenoboost link;
http://forum.xda-developers.com/showthread.php?t=2167228

saintsoh said:
here, this link provide init.d support;
http://forum.xda-developers.com/showpost.php?p=32716432&postcount=3
flash zip_init.zip.
copy zip_init.zip to sd-card,
boot to cwm, mount /system then flash zip_init.zip
check for test.log in /data if it is there or not, no test.log not working.
it work on my stock rom.
also flash adrenoboost v0.7 will boost perfromance from stock 5000 to 7000 (antutu benchmark).
adrenoboost link;
http://forum.xda-developers.com/showthread.php?t=2167228
Click to expand...
Click to collapse
thnx for the reply bro. about the adrenoboost, i think its main purpose is to boost the performance of Adreno 205 GPU or similar gpu but my friends device doesn't have gpu.

i didnt know tat.
anyway i think after mount /system, u should also mount /data (just in case).
it work on my sgw without mount /data but then i saw check /data for test.log which makes it necessary or not?
i'm not sure, just be on the safe side mount /data.

saintsoh said:
i didnt know tat.
anyway i think after mount /system, u should also mount /data (just in case).
it work on my sgw without mount /data but then i saw check /data for test.log which makes it necessary or not?
i'm not sure, just be on the safe side mount /data.
Click to expand...
Click to collapse
okay, i'll try that and hope it'll work
EDIT: sad, it didn't work

just learn something new when i reverted back to stock and re-install zip-init for init.d support.
when flash zip_init.zip and reboot, cwm will ask to "disable recovery flash" - select "NO".
(note: if select "yes", it will give a false positive, 'install-recovery.sh' will not have execute permissions and init.d support will not work).
after troubleshoot found out the install-recovery.sh is not in execute permission (rwxr--r-- instead of rwxr-xr-x).
by correcting the 'install-recovery.sh' permission, init.d support will work again.
ps;
must install busybox app (do a normal install).

saintsoh said:
just learn something new when i reverted back to stock and re-install zip-init for init.d support.
when flash zip_init.zip and reboot, cwm will ask to "disable recovery flash" - select "NO".
(note: if select "yes", it will give a false positive, 'install-recovery.sh' will not have execute permissions and init.d support will not work).
after troubleshoot found out the install-recovery.sh is not in execute permission (rwxr--r-- instead of rwxr-xr-x).
by correcting the 'install-recovery.sh' permission, init.d support will work again.
ps;
must install busybox app (do a normal install).
Click to expand...
Click to collapse
i got busybox installed, but i'm having status 0 error in CWM. in troubleshooting guide, it says replace the update-binary in zip-init.zip with a working update-binary of your phone and i don't how to do it

dec0der said:
i got busybox installed, but i'm having status 0 error in CWM. in troubleshooting guide, it says replace the update-binary in zip-init.zip with a working update-binary of your phone and i don't how to do it
Click to expand...
Click to collapse
update-binary is in the zip file, just download the latest which is the v2 and re-flash again.
if still doesn't work, try get help from init.d support thread.
i didn't get it working on the first time twice but somehow get it work again again.

saintsoh said:
update-binary is in the zip file, just download the latest which is the v2 and re-flash again.
if still doesn't work, try get help from init.d support thread.
i didn't get it working on the first time twice but somehow get it work again again.
Click to expand...
Click to collapse
it was v2 of zip_init that i use and i think i re flashed it 5x already and still getting that error anyways, thnx 4 ur help bro, godbless!

dec0der said:
it was v2 of zip_init that i use and i think i re flashed it 5x already and still getting that error anyways, thnx 4 ur help bro, godbless!
Click to expand...
Click to collapse
superusers app needed for terminal emulator, fx explorer(root access), busybox and script manager apps installed for root access.
use script manager, look for install-recovery.sh in /etc or system/etc (both r the same directory).
touch su n boot icon, su will turn green n boot will turn blue. reboot.
or
use fx explorer to set file permissions if u do not know linux commands.
google play search for fx explorer app and fx root addon (enable root access).
use root folder, look for install-recovery.sh in system/etc.
touch tool menu below and mount read-write then u can change file permission.
or
if u r familiar with linux commands, u can use terminal emulator to change file permission.
check install-recovery.sh permission is rwxr-xr-x, not other like rwxr--r--.
how2check in emulator, type n press enter:
ls -l etc/inst* ↵
how2change file permission, type n press enter:
su ↵
cd etc ↵
mount -o remount rw /system ↵
chmod 755 install-recovery.sh ↵
exit ↵
exit ↵
done, there shouldnt be any error, reboot.
if not re-flash zip_init.zip, reboot, select "NO" to disable flash recovery.

saintsoh said:
superusers app needed for terminal emulator, fx explorer(root access), busybox and script manager apps installed for root access.
use script manager, look for install-recovery.sh in /etc or system/etc (both r the same directory).
touch su n boot icon, su will turn green n boot will turn blue. reboot.
or
use fx explorer to set file permissions if u do not know linux commands.
google play search for fx explorer app and fx root addon (enable root access).
use root folder, look for install-recovery.sh in system/etc.
touch tool menu below and mount read-write then u can change file permission.
or
if u r familiar with linux commands, u can use terminal emulator to change file permission.
check install-recovery.sh permission is rwxr-xr-x, not other like rwxr--r--.
how2check in emulator, type n press enter:
ls -l etc/inst*
how2change file permission, type n press enter:
su
cd etc
mount -o remount rw /system
chmod 755 install-recovery.sh
exit
exit
done, there shouldnt be any error, reboot.
if not re-flash zip_init.zip, reboot, select "NO" to disable flash recovery.
Click to expand...
Click to collapse
busybox was installed correctly as i can see the folder bin/ xbin. it's rooted already so superuser was in there and i used root explorer file manager. i can't find install-recovery.sh in /etc or system/etc which maybe means that it was not working

dec0der said:
busybox was installed correctly as i can see the folder bin/ xbin. it's rooted already so superuser was in there and i used root explorer file manager. i can't find install-recovery.sh in /etc or system/etc which maybe means that it was not working
Click to expand...
Click to collapse
1) phone is rooted,
2) superuser app installed,
3) busybox app installed,
4) root explorer file manager app installed,
5) no install-recovery.sh in /etc or system/etc?
6) no test.log in /data?
7) re-flash zip_init.zip, reboot, select 'NO' to disable flash recovery?
8) no init.d directory in /etc?
9) in etc/init.d directory, there should have two files 00test n 08setperm. in /etc should have install-recovery.sh file.
10) u dont have these three files?
flashing cant write on system directory, means manufacturer locked the system.
unless u can find way to break the lock.

saintsoh said:
1) phone is rooted,
2) superuser app installed,
3) busybox app installed,
4) root explorer file manager app installed,
5) no install-recovery.sh in /etc or system/etc?
6) no test.log in /data?
7) re-flash zip_init.zip, reboot, select 'NO' to disable flash recovery?
8) no init.d directory in /etc?
9) in etc/init.d directory, there should have two files 00test n 08setperm. in /etc should have install-recovery.sh file.
10) u dont have these three files?
flashing cant write on system directory, means manufacturer locked the system.
unless u can find way to break the lock.
Click to expand...
Click to collapse
1-4 yes, all done
5-10 don't have those files coz i got status 0 error flashing zip_init.zip v2 in CWM
if thats the case, maybe i'll try to flash different stock firmware 1st

dec0der said:
1-4 yes, all done
5-10 don't have those files coz i got status 0 error flashing zip_init.zip v2 in CWM
if thats the case, maybe i'll try to flash different stock firmware 1st
Click to expand...
Click to collapse
try manually put in those files in their respectively directories.
unzip n try putting those files in their respective order.
create a init.d directory in /etc then put those two files 00test n 08setperm into it.
put the install-recovery.sh in /etc, set all permissions to rwxrwxrwx.
(upload manager doesnt allow .sh file, rename install-recovery.sh.txt to install-recovery.sh)
done, reboot n see it works or not.

saintsoh said:
try manually put in those files in their respectively directories.
unzip n try putting those files in their respective order.
create a init.d directory in /etc then put those two files 00test n 08setperm into it.
put the install-recovery.sh in /etc, set all permissions to rwxrwxrwx.
(upload manager doesnt allow .sh file, rename install-recovery.sh.txt to install-recovery.sh)
done, reboot n see it works or not.
Click to expand...
Click to collapse
okay, i'll try that. thnx

GT-I9082 completely stuck on logo

i will say what i did
first i got this from my friend and android ver is 4.2.2 and phone hang with him and storage have bug its say app use 11.5 gb and free is 500 mb and there nothing in storage
i found in forum here i can upgrade rom from 4.2.2 to lollipop by cm12 rom
i follow the steps to make it, first make root and recovery cwm but found phone already rooted i don't know by who but any way try to install cwm i can't by all ways
i try use odin but need first to go download mode to this, i press on vol down + power + home and what i found is factory mode and chinese language
search and i found i must change it by efs folder and i cant found it by root explorer or any other app
but i use EFS Professional and it cant detect the phone in backup, but when i press on device inf its say phone model is GT-I9500
and any other app in phone too detect it as GT-I9500 ?????????!!!!!!!!
i search in system to find what file make it GT-I9500 and found it was build.prop
i try to edit and correct the info and replace it ((i was take copy and it in attach))
by the way i replace it by adb shell and that what i did
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
chmod 777 /system/app
exit
exit
adb push build.prop /system/build.prop
and its done now, must restart to make this file work
and until this moment its stuck at samsung logo , don't forget download mode not working just recovery is working until now its old one not cwm
are any chance to make this phone alive again?any help?

[SOLVED] Editing build.prop file / bootloop / disable OTA

I fixed it myself and hope the advice can help someone:
A) Some of the mistakes i made during editing of the build.prop file
0. While bootlooping constantly hold volume down+power, it WILL boot to the bootloader after some time!
1. Don't use adb shell then adb pull/push, you don't need the shell here! Just use "adb pull /system/build.prop", notepad++ and "adb push build.prop /system/build.prop" to update the file, then set permissions again with "chmod 644 build.prop" and then "ls -l" to make sure the permissions of build.prop show -RW-R--R--
2. To use adb, get into fastboot->recovery and watch out that /system is mounted
3. Use the UniversalADBDriverSetup.msi to install drivers, then check check and check again that you change the drivers used to the ADB ones, not my htc, not android device. Different states of the phone sometimes activate different drivers (IE i plugged my bootloader phone in, changed drivers, got into recovery, had to change drivers again!)
4. Make a .bak file before you change anything inside android!
5. Avoid AROMA Filemanager, every time i tried to type something my keyboard got stuck and i had problems closing it. Without being able to remove the battery this is a huge risk.
B) Regarding OTA:
To disable the OTA updates i installed the app "MyAndroidTools" and disabled Service->System->Update/Upgrade(german: Aktualisierung)->UpdaterCheckIntranetService
Old Stuff:
Update: Got fastboot connecting, but adb not.
New main question: How to choose the rom i am going to flash?
Device Carrier Region Type Kernel Android Size Description
Device is clear, but Region i get TW and TW Wifi. My android Version before was 4.4.2 and i had the ota upgrade to 1.60.xxxx. Is it safe to not know what carrier, region and type i have and just chose Region TW, Type CRC, Android version 4.4.2 1.54.xxx?
Desire 816 hTC Asia TW CRC 3.4.0 v4.4.2 155 MB 1.54.709.2
Can i use the latest android one instead?
Desire 816 APTG TW MR 3.4.0 v4.4.2 156 MB 1.63.500.1
TLTR: reboot loop after rooting and tampering with the build.prop file, can get into bootloader/recovery, usb drivers wont work, how to edit build.prop/reflash stock with zip/add new build.prop?
My Phone as i remember: TW international HTC 816 single sim android 4.4.2
PC win 7 x86 ultimate
Here is what i did before the bootloop:
Rooted the phone with this instruction: https://www.youtube.com/watch?v=vhUBLhdgSPU
Quote: 1. HTC Sync Manager 2. Install ADB Fastboot 3. Unlock Bootloader 4. CWM Auto-Install via ADB Fastboot / Bootloader 5. ALL IN ONE SuperSU .zip file for Internal Storage (Includes Busybox, Init.d Installer, & Write Protection Removal)
Then i wanted to hide the over the air update by modifying the build.prop with root explorer->Jota Text Editor
(renamed it to build.prop.bak first)
I couldn't save it in /system with Jota so i moved it to the location (editing or savind with wrong permissions caused the loop)
rebooting started the bootloop, every 4 minutes it will start again.
i could enter recovery mode holding down and power for some minutes.
then adb and htc sync didn't detect my phone.
i tried using a file explorer [CWM-APP][1.91] AROMA Filemanager + TERMINAL :: 130903 :: Open Source
from http://forum.xda-developers.com/showthread.php?t=1646108 to rename the file, but the keyboard just hangs and produces garbage. Now my two build.prop files are named somewhat similar to jkdfh(ZG and $§BKGddddd, not build.prop and build.prop.bak
after barely closing the filemanager i am trying to get adb to work to change the filename for good
i boot in recovery and into hboot usb, connect the phone and try adb commands
i am now stuck, as none of the usb drivers i tried work.
i did a recovery->wipe data/factory reset and recovery ->wipe cache partition
i tried 15 sec adb drivers, i tried naked usb adb drivers, right now uninstalling every driver then reinstalling htc sync, reinstalling adb 15 sec 1.4.3 version of the drivers. Didn't find the ADB Driver entrys, so i searched and insalled universaladbdriversetup.msi, activated the "android adb interface" driver, have my phone in "fastboot usb mode", windows recognizes it, htc sync pops up but doesn't find a phone, adb still says device not found...
If i can't get the drivers to work, is there an option to not use usb to flash a stock rom from the sd (install zip)?
How do i decide what stock rom i need, how do i prepare it to be flashed as zip?
Please point me into the right direction.

I think I get it?
So I have a Droid 4.
I'm really bad at the jargon here, so if I may, I'll break it down and ask for explanations like I'm five.
My situation: I've been digging all over the internet for hours trying to figure out how to repair my broken build.prop file, which I edited in hopes of making the Droid 4 Compatible with Cricket Wireless. I am now stuck in Bootloop.
My options: I can easily get into the Android System Recovery menu.
@Kakmnesu: As I understand it, I need to:
1.) "update system from ADB" in the recovery menu.
2.) Run the ADB Command line.
3.) Enter "adb pull system/build.prop". This will, as it were, pull the file out so that it might be replaced.
4.) Have a backup copy of the clean build.prop on the external SD card.
5.) Enter "adb push system/build.prop". This will place the CLEAN build.prop from the SD card into the place of the old one and get rid of the old one completely.
What I don't know:
If my understanding of Item 5 is correct.
How can I tell if /system is mounted, and what do I do if it isn't?
What does setting the permissions do, and do I need to do that?
Any help is appreciated.
@sd_shadow, I've been trying to understand your posts and have been gathering what I think I might need should I have to overhaul the whole OS and start clean: I've noticed in your Droid 4 Repository that you have two files:
cdma_maserati_9.8.2o-72_vzw-18-2_1ff.xml
and
VRZ_XT894_9.8.2O-72_VZW-18.8_CFC.xml.
What is the difference between these, and do I need them both, should I need to just clean everything out?
Thanks so much for any of your help

ninthtale said:
So I have a Droid 4.
I'm really bad at the jargon here, so if I may, I'll break it down and ask for explanations like I'm five.
My situation: I've been digging all over the internet for hours trying to figure out how to repair my broken build.prop file, which I edited in hopes of making the Droid 4 Compatible with Cricket Wireless. I am now stuck in Bootloop.
My options: I can easily get into the Android System Recovery menu.
@Kakmnesu: As I understand it, I need to:
1.) "update system from ADB" in the recovery menu.
2.) Run the ADB Command line.
3.) Enter "adb pull system/build.prop". This will, as it were, pull the file out so that it might be replaced.
4.) Have a backup copy of the clean build.prop on the external SD card.
5.) Enter "adb push system/build.prop". This will place the CLEAN build.prop from the SD card into the place of the old one and get rid of the old one completely.
What I don't know:
If my understanding of Item 5 is correct.
How can I tell if /system is mounted, and what do I do if it isn't?
What does setting the permissions do, and do I need to do that?
Any help is appreciated.
@sd_shadow, I've been trying to understand your posts and have been gathering what I think I might need should I have to overhaul the whole OS and start clean: I've noticed in your Droid 4 Repository that you have two files:
cdma_maserati_9.8.2o-72_vzw-18-2_1ff.xml
and
VRZ_XT894_9.8.2O-72_VZW-18.8_CFC.xml.
What is the difference between these, and do I need them both, should I need to just clean everything out?
Thanks so much for any of your help
Click to expand...
Click to collapse
very little difference in the 2, only need one, either should be fine, but 18.8 is newer and should be better.
But you really should post in the Droid 4 section, and if you want reference this thread and/or mention Kakmnesu
the HTC Desire 816 and the Moto Droid 4 are very different devices, and the fixes may be very different.
---------- Post added at 01:02 PM ---------- Previous post was at 12:50 PM ----------
Cricket uses AT&T GMS network?
may need to see http://forum.xda-developers.com/showthread.php?p=25219819#post25219819

Got it. Thanks! I'll move to that thread because it still didn't work.. :\

After flashing CM-12, Both SIM are not working. Flashed stock L firmware but still problem is there... any solution?

Kakmnesu said:
[...]1. Don't use adb shell then adb pull/push, you don't need the shell here! Just use "adb pull /system/build.prop", notepad++ and "adb push build.prop /system/build.prop" to update the file, then set permissions again with "chmod 644 build.prop" and then "ls -l" to make sure the permissions of build.prop show -RW-R--R--
[...]
Click to expand...
Click to collapse
My issue was a bit like yours, only on my One M7. I screwed up the build.prop (replaced the ViperOne one with a Generic M7 one) and got stuck into a black screen after splash screen. The dreaded soft brick. I don't have ADB on my computer, but thankfully I had a copy of the original build.prop in my internal storage. However I couldn't get it to work after using TWRP to copy the file to /system/ multiple times.
I tried -everything- until a google search guided me to your post. The instructions in bold did the trick. You, sir, have saved me a lot of trouble