Hi
I am trying to root a cheap chinese tablet using A20 chip but cannot seem to edit the build.prop file even when tablet looks rooted ie ro.secure=0, am using insecure adb on tablet and adb shell shows #, etc.
I then retrieved /system into an img file on sdcard using dd and adb pull to get it onto a ubuntu PC, then mounted the img file as rw.
Even tho img file is mounted as ext4 rw, and I have root on ubuntu box (ie can see # and id shows uid=0, guid=0) I still cannot edit the build.prop file using vi as it says file is read-only when saving. buid.prop permissions are -rw-r--r-- so theoretically I should have no problem.
This must be a linux/file system type property when needs to be set/reset and is a little beyong my linux knowledge.
Any help, hints or direction to fix this would be appreciated.
TIA
Have you tried editing build.prop using a file manager inside Android? So you don't need a computer...
Gesendet von meinem One S mit Tapatalk
LS.xD said:
Have you tried editing build.prop using a file manager inside Android? So you don't need a computer...
Gesendet von meinem One S mit Tapatalk
Click to expand...
Click to collapse
yes, have tried many editors/root explorers on android device - did that all first, but with no sucess. only then decided to move image to PC
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
Hello guys,
I been trying in the little time I have to get rid of Fota file by using ADB but have not successfully been able to delete those files. I am not quite sure what is the process to do it but this is what I have been trying.
Open CMD
1- go to platform-tools folder on CMD
2- Type adb push c:\directory\fota_delta_dp1\ \data\fota\
3- repeat for second fota file.
It says that failed to copy c:\directory\file\ \data\fota\ since is read-only
How do I make it "writable" or what am I doing wrong,
I wanted to mention as well that my phone is rooted.
Find Root Explorer. Install it.
Change the file system to R/W.
Then, navigate to \data\fota and delete the files.
-Steve
sgyee said:
Find Root Explorer. Install it.
Change the file system to R/W.
Then, navigate to \data\fota and delete the files.
-Steve
Click to expand...
Click to collapse
Need to be rooted to use this method
Sent from my DAMN Galaxy 4G¡!
Success100 said:
Need to be rooted to use this method
Sent from my DAMN Galaxy 4G¡!
Click to expand...
Click to collapse
The OP said his phone was rooted.
-Steve
However you want to get root shell and do:
# cat /dev/null > /data/fota/fota_delta_dp1
# cat /dev/null > /data/fota/fota_delta_dp2
Well thank you for your advises. I ended up using "Super Manager" checked in setting "Use root function" went to the folder were i had the files alreadt unzipped and copy them over to /data/fota which replacea both of the fota files. Rebooted the phone and had 280mb of available storage.
When i get home i'll make a tutorial using Super Manager.
Sent from SGS4G
I installed Astro File Manager and I have a few questions.
1) When I look in the /data directory in the phone, it shows as empty. When I do a nandroid backup, and untar the result, I find numerous folders and files in data.tar and even find the original .apk files from the Market (/data/apps)
2) I found out my phone (obtained second hand from ebay) already has a custom ROM (InsertCoin) and expect is should already be rooted. So I tried Astro File Manager to edit the /build.prop where it says "screen capture=false" to switch it to true. Astro File Manager, is claimed to have root capability in this article
http://www.freeyourandroid.com/guide...dit-build-prop
But I find the Save button disabled and cannot write out the file. Why?
Is it possible or likely to have InsertCoin and NOT be rooted? How do I tell if my device is rooted?
Try es file explorer I don't think astro can access root files. Es can root explorer can to. Just go into settings and check the root access and mount /system I think is what it is.
And yes with a custom Rom you should be rooted.
You can check by downloading terminal emulator from the market then type su if super user pops up and asks to allow your rooted
Sent from my HTC Sensation XE with Beats Audio using xda premium
another useful tool is called root checker. downloadable on the maret. one click and it will tell you if your rooted. also give you the best way to root for your device if you arent.
and yes es file manager is good for re-writing files.
wadill said:
Try es file explorer I don't think astro can access root files. Es can root explorer can to. Just go into settings and check the root access and mount /system I think is what it is.
And yes with a custom Rom you should be rooted.
You can check by downloading terminal emulator from the market then type su if super user pops up and asks to allow your rooted
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
tk_xda said:
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
Click to expand...
Click to collapse
I use Root Explorer, it has an easy mount r/w option.
If everything else fails use ADB and Notepad++ on the PC.
In essence:
adb pull /system/build.prop AN_UNEDITED_FILE
Notepad++ to edit it, making sure EOL is set to UNIX
adb shell, su, "mount /system as r/w", cd /system, cp build.prop build.prop-
adp push AN_EDITED_FILE /system/build.prop
The mount r/w comand is:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I think that's it, I'm sure folks will correct me if I'm wrong.
tk_xda said:
I confirmed my device is rooted with the terminal emulator.
When I try to edit /system/build.prop (by choosing to use the text file editor) from es file explorer, it is still leaving the Save button disabled and I cannot write the file back out. I remembered to check root access and mount /system.
So, how do I edit /system/build.prop on a rooted device?
(And es file explorer shows me my /data directory.)
Click to expand...
Click to collapse
I just was able to change my build prop with es so I'm unsure why you cannot. I used the es note also and when finished I pressed the menu button and save was available.
Also this version of es file explorer I just used is brand new I've never used this update, it was included in the newest hd revolution sense 3.0.
I suggest just trying again. Possibly try another app or use the adb method if you think you can. Adb only looks hard really its just copy and paste.
I wish I had more advice but I can't replicate the same problem. Keep at it its just something simple were overlooking.
Sent from my HTC Sensation XE with Beats Audio using xda premium
wadill said:
I just was able to change my build prop with es so I'm unsure why you cannot. I used the es note also and when finished I pressed the menu button and save was available.
Also this version of es file explorer I just used is brand new I've never used this update, it was included in the newest hd revolution sense 3.0.
I suggest just trying again. Possibly try another app or use the adb method if you think you can. Adb only looks hard really its just copy and paste.
I wish I had more advice but I can't replicate the same problem. Keep at it its just something simple were overlooking.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
True regarding ADB, but it's guaranteed to work. The other thing is you can also do so much more with it.
As always YMMV.
Guys do you know some script to delete line on some files ?
For example dalvik.vm.heapstartsize=5m, value 5m on some roms is not same if I use this script :
HTML:
busybox sed -i '/dalvik.vm.heapstartsize/d' /system/build.prop
The line is not deleted :/
Please Help me guys
Just open the build.prop manually and search for the line. Then delete it. Make sure you are using a root file browser.
I suggest - Es File Browser.
Sent from my Nexus 5 using Tapatalk
TheArc said:
Just open the build.prop manually and search for the line. Then delete it. Make sure you are using a root file browser.
I suggest - Es File Browser.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I want delete line via recovery
Hi! Someone know how to push a file in /data/data/ without root?
I want to copy my savegame from my old phone to my new phone. With ADB push can't make this, because ADB want privilege (grant root permission)
Thanks in advance! [emoji2]
Inviato dal mio LG-H870 utilizzando Tapatalk
Using a custom recovery can help. TWRP - file manager - copy file to data folders.. this is possible way, if you have a twrp recovery. Otherwise you must build one or ask somebody to make it. You also can try to use the helium app from clockworkmod, which is able to backup and rewrite apps and data to new phone.
Gesendet von meinem VTR-L09 mit Tapatalk