Hi
I have Sony tablet S. I have been editing build.prop file then accidentally the build.prop and build.prop.bak file :crying: from /system/ folder. I do have copy of build.prop file on my computer but I am not able to push to the same location as before. It gives me error: failed to push read-only system. If I do ADB shell and su then I get [-] ui connection time out. Hence because of this, the tablet is not working properly. It shows the SONY label on start then goes black but in on state.
Please guide me if there is a way I can put back the file and start using my tablet.
Related
I am trying to install TapNTap keyboard in Vegan Ginger. (yeah, I know but I want to anyway). I need to copy two files to /system/app and system/lib. I presently have the files stored in /mnt/sdcard/download. I have terminal emulator installed and when I su I appear to get root (prompt changes to #). I was able to create an empty directory in /. When I try to copy the file to /system/app I get a message that it is a Read-only file system. When I do an ls -l the permissions show drwxr-xr-x for the directory. The owner is root and the group is root. It would seem that as su I should be able to copy the file there. Possibly it is mounted as RO. I tried to use a remount command but it failed. I'm not well versed in that so I may have done something wrong. Long and short - how do I get the file copied into the directory?
http://lmgtfy.com/?q=remount+system+rw+android
So I tried to get the build.prop file from my tablet but it says that there is none? So I ran adb pull /system and it all goes through fine but then it ends saying:
"Pull: /system/build.prop -> ./build.prop
Cannot create '.\build.prop': No such file or directory"
What is up with that?
Hello everybody,
I have a "problem" with /system/bin/ and bin folders (however, the phone works just fine, hence those quotation marks :angel.
Let's stick with /system/bin/: Inside I have the files that should be there, but there is also another bin folder with exactly the same files inside and another bin folder inside ... and so on, about 20 times/levels(?) nested.
Not sure what it is ... some hardlink problem?
The same is in /bin/ folder.
ES File Explorer says that there are about 7000 files/ 230 MB in the first nested bin subfolder.
I tried the following:
1. Delete the nested bin folders from ES File Explorer (root access granted) - unsuccessful ("can't delete ...")
2. From CWM: format /system/ + Factory reset + wipe + ROM reflash
3. Search the forum for this issue - maybe I can't search properly, but found nothing ... sorry
As I said, the phone works fine. But I think that it is not good to have such a mess inside the system folders.
I didn't try complete reflash (ftf file) ... I'm trying to avoid doing everything from scratch .
Can you help me, please?
Thanks a lot,
J.
Phone: Sony Ericsson Live With Walkman WT19i, unlocked bootloader (the Sony way), MESA Kernel 3.6 stock, Real ICS lite r4.
Update: It's a chain of symlinks. The depth of the chain is 40 (counted in DroidExplorer).
What else didn't work:
mount /system in TWRP, then starting file editor, deleting bin (even with chmod)
All attempts to delete the symlink via PC file managers (e.g. Droid Commander)
Solution {rooted phone):
It was a symlink in system/bin pointing to self,
1. Install Android Terminal Emulator (free at Google Play)
2. Start it
3. Then
Code:
# su
(allow root access)
Code:
# mount -o remount, rw /system
# cd /system/bin
# rm bin
That's it
I have installed stang5litre rom some time ago via flashfire since I am on of1. Recently I wanted to make a build prop edit to add apn settings and the damn buildprop app cleared the build prop leaving it empty, which I did not realize. I then rebooted and now you can guess I cant reboot. I have looked into a flashable zip with the build prop included but it has not worked. I get package footer is wrong and signature it wrong despite me signing the flashable zip. So what can I do?
I have full ADB access and can push sideload updates my issue is the footer and signature issue. Is there a way to sideload the buildprop without getting these errors? Can I flash the org verizon buildprop from there rom to make this boot? Any ideas?
I believe I have an almost solution, see below.. The problem is my device is unauthorized when I try to do adb devices. This is while allowing the device to boot in without the screen coming on. I can not see the dialog to allow me to confirm adb access. Is there another way?
Here are the steps to restore the build.prop settings.
1. Download android developer kit.
2. Connect tablet to (in my case I used a Mac) computer via USB Cable.
3. Boot tablet to "blank" screen.
4. Open Terminal and enter the following commands.
* cd /path/to/adb
* ./adb root #runs adb as root.
* ./adb devices #lists all connected devices, confirm your device is listed. If it is not, try disconnecting and reconnecting the USB Cable.
* ./adb shell #allows you to run a remote shell interactively.
* su #enters su.
* mount -o remount rw /system #mounts /system as rw.
* cd /system #puts you in the system directory of your device.
* ls -all #lists all the files in your devices /system directory. Look for a backup file of build.prop. If one exists, look at it's contents with less.
* less build.prop.bak #shows the contents of your backup build.prop file (the name of this file may very).
5. If you have a backup of your build.prop (and its' contents are correct), you can restore it using the following commands. If you do not have a backup, you will have to edit the file using vi (see step 6).
* mv build.prop build.prop.bad #renames build.prop.
* mv build.prop.bak build.prop #restores your backup of build.prop (replace build.prop.bak with your backup file name. If there is a space in the name, type \ before the space and hit tab. It should auto complete).
* exit #until you are back to your computers adb directory.
6. If you don't have a backup of your build.prop file, you will have to edit it with vi.
* vi build.prop #edits the file using vi (you will have to google how to edit this file with vi if you don't know how; I'm not doing a tutorial on vi ).
* exit #until you are back to your computers adb directory.
7. Reboot your device! You should be back in business!!!
8. Enjoy!
I'm screwed arnt I? I tried just about everything I could find for days since I posted this. Without USB debugging enabled I can not recover my data. Not with ADB, not with Kies, not with odin, NOTHING. My phone is rooted but that does not seem to matter now. I tried every recovery app out there including dr.fone and nothing can get it back. I guess I just have to reflash to stock and loose it all uh?
as shown in the attached screenshot i am using Miui 10.2.3 and when I connect the phone to the laptop and run adb shell I am unable to overwrite the hosts file as i do not have write permissions.... When i attempt to give write permision to /etc it fails.