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
Related
Is it possible to make an update.zip file that replaces the build.prop file, or any way to replace the build.prop file without doing a full restore?
I did it using adb commands.
Well I tried using adb shell to swap the file, but when I ran su I got "[1] + Stopped (signal) su"
So I guess I'm going to be forced to do a nadroid restore of my system
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Sent from my GT-I9000 using Tapatalk
Boot loop
Clienterror said:
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Click to expand...
Click to collapse
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
You could just reflash your current ROM and it should replace it.
korockinout13 said:
You could just reflash your current ROM and it should replace it.
Click to expand...
Click to collapse
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
P
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
Actually there is a potential option... can you get into recovery? And does your recovery have a file manager? If so go into mounts and mount /system. Then use the file manager in recovery and you should be able to access build.prop. copy it to your SD and then you should be able to mount your SD to your computer through recovery.
Edit: when you mount /system make sure you mount the SD as well or you won't be able to copy to it while you're in the recovery file manager.
Sent from my SGH-I897 using xda app-developers app
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
remuscat said:
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
Click to expand...
Click to collapse
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
remuscat said:
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
Click to expand...
Click to collapse
BWolf56 said:
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
Click to expand...
Click to collapse
From what I'm reading he doesn't even have a captivate. He's using some Chinese tablet.
Sent from my SGH-I897 using xda app-developers app
I just applied Daoist's CWM stock ROM update (should still be rooted, right?). It came up first time.
Then, I modded my build prop (set dpi to 120 because I like it that way). But maybe I screwed up the file name in Root explorer, because now I'm in a boot loop and if I try ADB PULL /system/build.prop it says "file not found."
I can't get SU through adb, so can't push build.prop to /system. ADB remount returns an error. permission denied. Transformer won't boot, so I can't do anything from it.
I CAN get to cwm, and have been trying to create an update.zip that will just copy build.prop to /system, but everything I have tried quits with "install aborted" message.
What can I do?
restore a nand and dont try and **** with it again, lol. no but really, restore a nand and then copy your build. prop and make a flashable zip and place on your sd card in case it happens again, so you can just flash it in cwm.
Resolved..
Well, why go back when you can go forward?
I went ahead and installed the Prime ROM. Looks like it is eating all my currently installed apps.
Y'all should know, though, that if your system can't find a build.prop it won't start. You can ADB to it and have a rudimentary set of commands, but your ability to significantly alter anything in your file system will be prohibited.
Lesson learned.
glg
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
mrevankyle said:
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
Click to expand...
Click to collapse
That is true. I had backups. But without a build.prop, the virtual machine won't start. There is no way to do a file operation to replace the backup. At least none that I found. I had to flash the whole system.
glg
So I edited build.prop and bootlooped my phone. I would like to restore the file without reflashing it because it takes a good deal of time. I know that ES file explorer automatically makes a .bak file of any system file it modifies, so I have a /system/build.prop.bak in there. Basically I would like to rename /system/build.prop to build.prop.bak2 and rename build.prop.bak to build.prop. I think you can do ADB in CWM so I just need help on how to do this.
EDIT: I am very familiar with the Windows command prompt and have used the linux shell a couple of times, so it shouldn't be that hard for me to understand this.
EDIT2: Never mind I did it another way. Basically I backed up the bootlooped system in CWM, ODINd tweaked 2.0, modified /system to what I normally do and then restored /data from that backup.
JihadSquad said:
So I edited build.prop and bootlooped my phone. I would like to restore the file without reflashing it because it takes a good deal of time. I know that ES file explorer automatically makes a .bak file of any system file it modifies, so I have a /system/build.prop.bak in there. Basically I would like to rename /system/build.prop to build.prop.bak2 and rename build.prop.bak to build.prop. I think you can do ADB in CWM so I just need help on how to do this.
EDIT: I am very familiar with the Windows command prompt and have used the linux shell a couple of times, so it shouldn't be that hard for me to understand this.
EDIT2: Never mind I did it another way. Basically I backed up the bootlooped system in CWM, ODINd tweaked 2.0, modified /system to what I normally do and then restored /data from that backup.
Click to expand...
Click to collapse
Nice save! Good to learn something.
Sent from my SCH-I510 using xda premium
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.
Hello
i installed layers and applied a theme and performed a reboot and the device is stuck . any ideas ?
Hello,
please reflash your ROM.
No need to reflash your ROM, OP. Reboot to recovery (a custom one, of course), and either by using adb shell or twrp's built in file manager, remove what you will from /system/vendor/overlay.
a hammerhead wrote this.
beekay201 said:
No need to reflash your ROM, OP. Reboot to recovery (a custom one, of course), and either by using adb shell or twrp's built in file manager, remove what you will from /system/vendor/overlay.
a hammerhead wrote this.
Click to expand...
Click to collapse
What of there's no /system/vendor/overlay/, just /system/bin/? Also, I see just /vendor in the root. It contains firmware and lib folders. Also, I have /sdcard/Overlays and it contains Backup folder(which is empty) and vividcolorwhite.zip. Nothing more.
drago06 said:
What of there's no /system/vendor/overlay/, just /system/bin/? Also, I see just /vendor in the root. It contains firmware and lib folders. Also, I have /sdcard/Overlays and it contains Backup folder(which is empty) and vividcolorwhite.zip. Nothing more.
Click to expand...
Click to collapse
vividcolorwhite.zip: is this the overlay that's giving you grief? delete/move it.
drago06 said:
What of there's no /system/vendor/overlay/, just /system/bin/? Also, I see just /vendor in the root. It contains firmware and lib folders. Also, I have /sdcard/Overlays and it contains Backup folder(which is empty) and vividcolorwhite.zip. Nothing more.
Click to expand...
Click to collapse
You have to mount your system partition. Just boot into twrp recovery, go to mount, mount system. After you mount the system partition you should be able to see all the system folders.
Mr.FREE_Bird said:
You have to mount your system partition. Just boot into twrp recovery, go to mount, mount system. After you mount the system partition you should be able to see al the system folders.
Click to expand...
Click to collapse
THANKS! This is exactly what I was looking for.