Database Info

HELP ME!!! build.prop file deletes itself upon reboot!!!

HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!

Machlev said:
HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!
Click to expand...
Click to collapse
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE

Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
no MD5 file found while installing via TWRP. Should I wipe /system?

Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
I wiped system and pushed an md5 file. Still fails with no reason.
I use this ROM -
https://cyngn.com/products/oneplusone/
(On the bottom)

What error are you getting?.. You could try another download (that one may be corrupt) or CM11 ROM, you should still be able to keep your app data as long as you don't wipe that partition.. You only need to wipe system/dalvik/cache..
Sent from my OnePlus ONE

Are you mounting /system with TWRP before doing that?
Also, dont move the file, try cp which works better with crosslink devices
And try chmod 755 /system/build.prop with adb while in recovery and check the build.prop isnt edited in Windows so EOL is Windows-like, then use Notepad++ to change to UNIX-type

easy, you copy pasted so permissions are not the same as the original
reflash system or rom
Sent from my A0001 using XDA Free mobile app

Yep. Permissions should be rw-r-r (or 644). If you don't know what you're doing don't mess around with system files.
Transmitted via Bacon

[SOLVED] TWRP backups: Delete failed

Hi
Despite several attempts with different file managers and TWRP versions I can't delete my TWRP backups. The only solutions I have is through the recovery mode or a terminal command (rm -rf /sdcard/...).
No issue to delete folders from other directories though.

Is this the same with new backups?

rootSU said:
Is this the same with new backups?
Click to expand...
Click to collapse
Yep

Primokorn said:
Yep
Click to expand...
Click to collapse
odd. i use root explorer, open twrps file, select backups, long press on the backup i want to delete, then press delete(and its gets deleted). what file explorer do you use?

Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?

rootSU said:
Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?
Click to expand...
Click to collapse
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.

simms22 said:
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.
Click to expand...
Click to collapse
I mean for @Primokorn not in general
Sent from my Nexus 5 using Tapatalk

@Primokorn try root explorer

I tried with root explorer, solid explorer and ES file. Nothing works with these apps.
Actually I already had this issue with old TWRP versions.
I manage my backups from the recovery mode now but that's really odd...
Maybe doing a new fastboot flash could fix it. Last time I had to use Flashify to upgrade because I didn't have a PC.
Then I'll try with adb if needed.

If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.

KJ said:
If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.
Click to expand...
Click to collapse
Yep. Better yet, flash a userdata.img I reckon

Problem solved after flashing userdata.img. Thanks guys.

I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP

iliass01 said:
I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP
Click to expand...
Click to collapse
It's too late for me to try but I keep this in mind. I took the opportunity to clean up my internal memory lol
BTW due to this issue ADB didn't work while being into recovery mode. Everything is fixed now.

[Q] Clockworkmod file in root of sdcard

I have a clockworkmod file in the root of sdcard. I can see it in ES File Explorer but I cannot see it when I connect the phone to my computer. I use clockworkmod recovery only by booting into it when I need to...not by flashing it.
Although it dissappears when I delete it in ES File Explorer, if I refresh the screen it is still there. Anyone know what this file is exactly and how to get rid of it for good?

I tried another app called File Manager by Gira.me. It shows this file as ...
Path: /storage/emulated/0/clockworkmod
Type: */*
Size: 0 B
Last modified: Unknown
Permissions: ---
MD5: Unknown
When I try to delete it it says "Not enough permissions". There must be some way to delete this file.

Boot cwm, adb shell, rm the file

beekay201 said:
Boot cwm, adb shell, rm the file
Click to expand...
Click to collapse
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.

xda6969 said:
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
Click to expand...
Click to collapse
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.

Aerowinder said:
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Click to expand...
Click to collapse
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.

xda6969 said:
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
Click to expand...
Click to collapse
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.

Aerowinder said:
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Click to expand...
Click to collapse
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.

xda6969 said:
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
Click to expand...
Click to collapse
Yes, you need to be rooted for restorecon command (su). A lot of people had troubles like yours when they moved to Lollipop (me too). Now that the recoveries have been updated, it's no longer an issue for most. You may still need to run the command, though. I suppose if you did a full wipe in stock recovery, it would fix the problem.
Your question about restoring app data with nandroid is vague and could be answered in a few ways. With your issue, the data partition is actually where the problem is, so I wouldn't recommend restoring the partition.
Instead, you might use Titanium Backup or something similar to back up only app data. But you need root for that.
Easiest solution is to root, fix issue, then, if you really want to, unroot. Don't need to wipe anything.

No longer able to copy files to /System

Recently had some issues with my device that caused me to to come back from a soft brick. Since then I have not been able to copy or replace files in the /System directory.
Items that have been tried and do not result in access:
Re-flash ROM (RR)
Taken back to stock image and then Re-flashed ROM (RR)
Flashed a new version of Magisk
Tried mounting the /system and making rw
Used RootExplorer and ES to change permissions to rw (chmod 777)
With all these, I try and overwrite files in system and they fail. Items with non conflicting names will appeared moved, but upon reboot all files are missing.
Ultimately what I am trying to do is move additional .ogg files into the media folder within system.
Any and all help appreciated.
Edit: Finally was able to mount /system and replace/add files after fully uninstalling Magisk and then flashing Magisk-v16.1(1610).zip

If I understand correctly, you can't modify /System with Magisk. With SuperSU, you can.

shopealope said:
If I understand correctly, you can't modify /System with Magisk. With SuperSU, you can.
Click to expand...
Click to collapse
yes you can modify /system with magisk. I do it all the time. Usually delete some aosp apps I don't need and they are in system/apps.

TWRP : SYSTEM partition not in backup list, how do i backup it?!

After unlocking phone & installing TWRP, i want to backup of course, but in the partition list, SYSTEM is not here! Never seen this before. Happens with any version of TWRP for the Realme 5 Pro. I may be missing something..? Let me know ASAP, thanks

Try Erase Partition Recovery and Flash TWRP again.
Command
fastboot erase recovery
fastboot flash recovery file-name-twrp.img
Click to expand...
Click to collapse

faisalxp said:
Try Erase Partition Recovery and Flash TWRP again.
Click to expand...
Click to collapse
Thanks but that did not change anything. When you go to BACKUP, do you see SYSTEM (just that, not SYSTEM IMAGE)? I noticed by going into file manager that system folder appear as "system_root" perhaps that's the issue..?
But then it should be the same for everyone, why it isn't i don't get it?! In mount section, SYSTEM is NOT ticked after booting recovery, but ticking it doesn't change anything unfortunately..

Yeah realme rename it to system_root

faisalxp said:
Yeah realme rename it to system_root
Click to expand...
Click to collapse
..? Not sure to understand your reply (=how is it helping me) : are you saying it is so for ALL Realme roms/devices? I read it's only for non-indian versions.. I need some guidance here :angel:

GoJo ^^ said:
Thanks but that did not change anything. When you go to BACKUP, do you see SYSTEM (just that, not SYSTEM IMAGE)? I noticed by going into file manager that system folder appear as "system_root" perhaps that's the issue..?
Click to expand...
Click to collapse
Have you previously tried to backup a System Image and try to open the backup file system_image.emmc.win with an Archive application like RAR or Zip ?
If so you will see that the System folder is inside the system_root folder so it can be concluded that System Image or system on twrp is the same as system_root or root. You can check attachment file.
I think the problem is with the twrp source or the developer, where the system image backup path leads to System_Root not /system_root/system.
If you only want to backup only the system partition you can use "dd" command on the TWRP terminal.
But then it should be the same for everyone, why it isn't i don't get it?! In mount section, SYSTEM is NOT ticked after booting recovery, but ticking it doesn't change anything unfortunately..
Click to expand...
Click to collapse
When you tick and mount the system partition on twrp, you will be able to edit all files and folders in system_root. for more details diferent tick and untick system, you check the file attachment.
GoJo ^^ said:
..? Not sure to understand your reply (=how is it helping me) : are you saying it is so for ALL Realme roms/devices? I read it's only for non-indian versions.. I need some guidance here :angel:
Click to expand...
Click to collapse
I try searching and not its not same for all device realme, one of the example : Realme X & XT using /system-root
I think it depends on the variant or type of device reality. bit the point its same System Image or system on twrp is the same as system_root or root

But "SYSTEM IMAGE" is +5GB, never seen such big parition on any phone.. It does contain system certainly, as well as other thing i do not need. I wish there was a way to backup just system like i did up until today on all other devices..

GoJo ^^ said:
But "SYSTEM IMAGE" is +5GB, never seen such big parition on any phone.. It does contain system certainly, as well as other thing i do not need. I wish there was a way to backup just system like i did up until today on all other devices..
Click to expand...
Click to collapse
Try this command on Terminal TWRP
Code:
dd if=/dev/block/by-name/system of=/sdcard/backup-system.img

anyone here facing backing up system image back up failed on fox and twrp ?