URGENT: Build.prop deleting itself after each reboot - Android Q&A, Help & Troubleshooting

got an urgent and important question.. please urgent help required.!!!
I edited something in build.prop and restarted. phone goes blank after boot. Tried adb.. [build.prop not found] restored a backup of build.prop into system via adb but after reboot, same thing again and adb shows [build.prop not found again]..!! Can anyone help..?? Also didn't make nandroid backup..
Is there anyway to get the phone running again without losing any data..??
URGENT..!!

Are you either hitting fix permissions in recovery or using adb to chmod the build.prop after pushing it? If not this will happen.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Related

Can't Root with SuperTool, Read-Only...

Hey there! About 2 months ago I first rooted my HTC Legend and unlocked my bootloader and ugraded it to hboot 1.02
I installed cyanogenmod 7.2 and all worked great. I have CWM 5.0.2.8 installed too. And supertool worked for me (zergling rushes commenced . I was also able to use eclipse for android to view my root files via the computer.
Well I cant do this anymore. I can only see my root files via the phone using Root Explorer Lite which I downloaded from the play store.
And supertool is giving me errors of read-only file system (see attached screenshot) and says pushing Superuser.apk, so it appears on my phone, I also opened it but I don't know what im supposed to do in there??
I just want to be able to access my root files via my computer. do I have to use eclipse or is there another program? what am I doing wrong here?
ATM im using a workaround where I copy files to my SD card and then using Root Explorer Lite I copy for instance ringtones to the system/media/audio/ringtones folder and that works. But I need a simpler method like drag and dropping files into this folder via my computer. How can I do this?
Thanks for you help!
You can try qtadb.
Sent from my Legend using xda app-developers app
Curious as to actually know the need to use supertools when your already using a rooted rom?
I am so sure supertools was only needed to root a non rooted Rom, perhaps supertools stuffed it up....
Have you simply tried just using adb commands from cmd?
Perhaps your issue is the pc itself.
Maybe first is to try this:
Adb devices (proves phone and pc are connected).
Adb shell
Then type "su"
Then type "ls" (this gives file listing on device)
This is assuming you know anything about windows cmd, Adb and stuff like that.
Just some basics to get you started in trying to diagnose.
Hey, why not try restoring a nandroid backup you did earlier, you did do a backup yeah?
Sent from my HTC Desire HD using xda app-developers app
jazib360 said:
You can try qtadb.
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
thanks this actually worked! i dont even know how/why but it did
i tried other programs like Droid Explorer or Android Commander but it didnt let me copy files to system/media/ or wutever. and it would say my phone isnt rooted.
i tried the cmd promt as ranger said with adb shell
i did the su and ls thing and it works (displays dir/files list) but thats not the problem, the problem is when i type something like this:
chmod 777 media/
and it says it cant change permissions cuz its read-only file system, the same reason supertool didnt want to work. i wan my zergling rush!!!
seriously this is weird

[Q] Changing ownership / permissions

I use to have an issue with my wifi not turning on.. Fixed that problem then I had the issue of it not remembering new networks.. Fixed that too..
The problem is the fix I found is simply changing the permissions of a few wifi files. While that is not hard to do... Getting those changes to stick is the problem.
I've rooted my phone obviously and I've played around with Ubuntu in the past so I remember something like sudo su... Well just su because I already have root.. I have terminal emulator on my phone I just need to know how to make these permissions stick... Chmod or chown I don't remember..
Any help would greatly be appreciated
Sent from my PantechP9090 using xda app-developers app
Oh and I know this topic has probably been discussed before but haven't really found where it is at.
Sent from my PantechP9090 using xda app-developers app
I'm assuming upon booting up there is a file that tells Linux/android which files should have which permissions... I've looked through some files and haven't found anything.... I tried changing the permissions through terminal with su access... Restarted and still reverted back.
Sent from my PantechP9090 using xda app-developers app

[Q] SGPT12, modified build.prop, won't boot anymore!

hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
the problem was in the file permissions. i had to remove write permissions to the group. (rw-r--r--)
You can fix permissions using adb
Sent from my GT-S5830 using xda premium
the.fuzzy.guy said:
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
Click to expand...
Click to collapse
First of all DO NOT WIPE DATA / FACTORY RESET
This will remove adb access. Depending how far you can boot, do you get adb in recovery or normal. Can you use adb shell? If you can you can us adb shell chmod 644 /system/build.prop
EDIT:
Failing that try to install a zip. Sell my links for both current and older zips

[Q] Android won't boot after modifying system file

This is (nearly) my first post, so hi all !
Before I start with anything else: I searched a lot and found a lot of things, but I'm so newbie that I'm afraid to do anything because I don't quite understand what I'm about to do.
Oh, and I don't speak english natively so forgive me if I make any horrific mistakes :angel:
With all that said, let's begin with my problem...
I have a HUAWEI Y300-0100, and it comes with a funny feature: every time it can't connect to WIFI a popup message appears saying that if you switch to data plan charges may apply.
I am constantly switching between WIFI/no-WIFI zones so that message really bothered me, and I searched a way to disable it.
Presumably, the only way to do that is by modifying a system file called "build.prop". I already had my phone rooted so doing so wasn't very hard.
I used Jota+ to change a setting from "true" to "false" (ro.config.hw******), and saved the file in the root of the SD card. Then, with ES File Explorer, I renamed the "build.prop" in /system to "build.prop.bak" and copied there the "build.prop" I previously saved in the SD root.
All seemed to be fine, except that after rebooting my phone it could not get past the HUAWEI logo.
Android recovery mode seems to work, but I don't know how to use a lot of its options nor I want to do a Factory Reset if there's a better alternative.
Is there a way to modify system files before booting Android? I really would like to try to delete the "build.prop" file and rename the "build.prop.bak" back to "build.prop".
Does any of that make any sense? What do you recommend me to do?
Thank you very much for your help!
From within recovery open adb
adb pull /system/build.prop /some/location/on/PC
Now edit build.prop back to how it was
adb push build.prop /system
adb reboot
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
From within recovery open adb
adb pull /system/build.prop /some/location/on/PC
Now edit build.prop back to how it was
adb push build.prop /system
adb reboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your response!
I managed to restore the original build.prop, but the phone still doesn't boot.
..Maybe that wasn't the problem. I guess I'll factory reset...
--------------------------
After that it STILL doesn't boot. I have no idea what happened, I did nothing strange apart from editing that file :crying:
If you changed something in /system factory reset won't work
Try either fixing permissions in recovery or
adb chmod 644 /system/build.prop
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
If you changed something in /system factory reset won't work
Try either fixing permissions in recovery or
adb chmod 644 /system/build.prop
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Nothing fixes it... I give up.
Next time be sure to make a backup before you modify
For now wipe clean and install a new ROM or return to stock
Sent from my Nexus 4 using Tapatalk 2
Install a new rom
Sent from my GT-I9100G using xda app-developers app

[Q] Stuck in Boot Loop Because of vold.fstab

Anyone, please I need help. After I have rooted my friends' android tablet he asked me to swap the internal storage and the external. after editing the vold.fstab, I've restarted the device. And it just got stuck at the boot logo. I am new here at xda and i don't know how to do a nandroid backup before editing the vold.fstab file. i've tried methods like pulling the vold.fstab using adb, but no luck because permission denied. Please Help...:crying:
Which device are u using
Sent from my KAUSHDROID using XDA Free mobile app

Categories

Resources