I'm using a Huwei Pronto and a friend rooted my phone a while back so I factory reset. I was unable to connect to Google servers and I've tried everything I've seen so far.
I am once again rooted using kingroot
Device is running android 4.4.4 KitKat
Every file explorer I've tried has root access
Es file explorer, total commander, fx explorer, etc...
I've come to the conclusion that the hosts file in etc is the file at fault, as it has an extra line.
I couldn't edit or overwrite the file so I looked to forums and found that I needed to remount.
When I try to remount I get
Remount error: read only file system...
I've even tried commands to remount in terminal emulator but my device is not listed when I type adb devices
Pls help it has been 6 months. I just want to be able to use Google play again.
Related
Am trying to fix the ES File Explorer Root access issues by following the steps posted by Joker Fuel in one of the TP forum.
I cant get to delete the current apk under /system/app using any of the File Explorers. How do i get this file deleted ? Any help.
This is what am trying to accomplish:
OK guys, for u guys that are having issues Using ES File Explorer Root permission.
The Root does not work while the app is in /system/app.
so to get it working, u must delete the com.estrongs.android.pop-1.apk
couple ways to do it. u can download a free file explorer off the market and delete the file under /system/app
---------------------------------
reboot your new BUTTAH
download ES from the market
If I am understanding what you want to do correctly you need to remount /system as read/write so you can remove the file.
There are many ways to do this. I like to use RomToolbox, available on the market. Once installed you can open up "Scripter" and there will be a couple of pre-defined scripts, one to remote System is Read/Write.
After you run that script you can jump to the Root browser, one button above, and delete what you need from the /system/app directory.
Remember to remount your /system as Read-Only using the other script, or reboot when your done. It is a bit dangerous to leave it as Read/Write. Better safe than sorry
Thanks. gonna give it a try !
Titanium Backup works on Buttah. Downloaded through market. Then I was able to pull ES through that. Then re-install through market. Now root access and mountable system.
Hello. I am having a lot of trouble accessing root folders [/etc] to paste a new gps.conf. I was wondering if anyone might know why this is, or have a fix. I have searched for similar problems in the forums, and seemed to get some similar problems, but no specific answers.
Phone model: HTC Desire GSM
Android version: 2.3.7
Oxygen ROM 2.3.2-bravo
I have tried using root explorer (yes setting root and etc to r/w, not r/o) and ES explorer (turning on all the root access settings).
When I try to either paste a new gps.conf to the etc folder, it gives me no error messages, but will not overwrite the old file.
Any ideas are welcome
Try using terminal emulator:
Code:
su
cp /your/gps.conf /etc/gps.conf
Or using adb:
Code:
adb remount
adb shell "cp /your/gps.conf /etc/gps.conf"
RoberGalarga said:
Try using terminal emulator:
Code:
su
cp /your/gps.conf /etc/gps.conf
Or using adb:
Code:
adb remount
adb shell "cp /your/gps.conf /etc/gps.conf"
Click to expand...
Click to collapse
I tried this and it says it cannot copy - out of memory
Having searched for this issue, I found that it has nothing to do with memory, but simply that the user does not have permission to modify the contents of the folder. This can be changed using the chmod command, but I have no idea how to use the chmod command, it looks complex.
Any help is much appreciated
I don't use root explorer or but you should be able to use it to edit a folder's permissions.
I use total commander and all I do is navigate to the folder/file, long press it, click properties then permissions then enable write across the board. I imagine the process is basically the same for root explorer.
jr67 said:
I don't use root explorer or but you should be able to use it to edit a folder's permissions.
I use total commander and all I do is navigate to the folder/file, long press it, click properties then permissions then enable write across the board. I imagine the process is basically the same for root explorer.
Click to expand...
Click to collapse
Thanks, but I think you have to use chmod. For some reason root explorer / es file explorer, &c. cannot change this permission, because they do not have permission to change the permission.
Hey guys,
I'm having a problem with ES file explorer. After several days I managed to root my HUawei U8800 Ideos X5 (Android 2.3.5) and obviously one of the next steps is installing CWMR. Unfortunately I'm failing here too. I tried to copy the recovery.img to the .cust_backup/image, but it keeps to say copy failed. Root access was given and I checked all four boxes in root settings. Someone in a german forum told me to update the binarys in SU, which failed too (it says sth like copy su to /system -> failed!). I'm not even sure ES FE would work if the binarys would be current.
Is there someone who can help me? Any ideas?
I already tried the app Mount /system (rw / ro). It didn't work with this too.
Thanks a lot.
no ideas?
You must have the /system folder mounted for read and write, default is read-only.
Different folders in the file structure could be located on different file systems, the easiest way to be sure that you have read and write access were you want to put files, imho, is by using root explorer.
If you are rooted and ES have root permissions then the problem is that the folder is non-writable. I don't know the app you tried to use to mount the /system as r/w but it's easy to do in root explorer or through adb shell with a little bit of *nix knowledge (su and mount -o remount,rw).
Should work from terminal emulator app as well.
C:\Users\...>adb push C:\recovery.img /.cust_backup/image/
failed to copy 'C:\recovery.img' to '/.cust_backup/image//recovery.img': Read-on
ly file system
before I typed
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Doesn't work. adb etc. is installed.
I'm really desperate about this now, I think something is really wrong with my system partiture or something like that. I consider formatting it, the problem I obviously have is that without CWMR I have no clue how to do that and how to flash an OS after it. Does someone have ideas about the whole issue? Interesting facts about my device: Often I'm not able to flash a stock ROM, it stops somewhere in the middle of the process. Rooting works often, but not always with SuperOneClick or zergrush. At the moment my superuser app says "root app_63" in a red font instead of "root root" in a green font, at least I have current binaries at the moment, but this doesn't work always as well. Seems like I am pretty alone with all these problems, that's why I want to format /system...
Please help me! Thanks
Give root explorer a try!
Sent from my OC ed mind.!
Why would you think that would work? ES File Explorer does basically the same...
Dont EVER try to format /system or u r gonna end up completely bricked. Just take your phone to a service centre and see what can be done. If you are under warranty, replace the mobile.
Hope i helped .
Sent from my GT-S5360 using XDA-Developers App.
looking around for answers to Android Pay not working on MM, I found some answers. My problem was Google couldn't verify the device and I couldn't ad any cards. After a few steps I am now able to add cards and verified by Google.
adb shell
type su
chmod 751 /su/bin
or you can use root explorer and change to rwxr-x--x
Step 2
then
renaming xbin_bind folder
As far as working at the NFC machines haven't tried it yet.
EDIT: For some reason root explorer for ES File Explorer doesn't work anymore, the app Root Explorer does
Hello everyone,
I’ve a problem with my system folder as I can’t write to it anymore.
Phone: HTC Desire with Android 4.1.1;
rom: https://forum.xda-developers.com/showthread.php?t=2183281
My story: I wanted to try a model specific soft and I made a change of model in the build.prop in the system folder. Everything was ok, but when I edited back the build.prop with ES file editor, it saved the file as a blank file. I then moved the blank file to the SD card with success and tried to copy the build.prop from a backup I’ve done; and I get permission denied…
So far I’ve tried:
- Re-mounting the system folder
- Clearing ES file explorer data to give a SU access again
- Trying the same thing with Terminal Emulator but I’m not familiar with android command line
So now I’ve a phone without build.prop in the system and I suppose it will not be happy about it the next reboot.
My question: How I lost the capacity to write to the system folder, from a theoretical point of view, and how I can clean this mess as a personal matter. As the phone is still up I hope that it’s still possible to solve the problem without having to re-install everything.
If someone is interested by this, I will welcome any help.
Kuroneko
Try
mount -o remount rw system
In terminal.....And then try to copy with terminal itself...Use CP command
Thank for the help but sadly it didn’t make the trick.
I use Terminal Emulator
After several trials with the command I think that I’ve found the correct syntax but at the end it didn’t worked.
Working in the root folder where I put a copy of build.prop:
su
mount –o remount,rw /system
cp build.prop /system/build.prop
>can’t create “/system/build.prop”: Out of memory
I also tried to create a text file in the system folder with Total Commander without success.
I fear that there is a serious **** up in the system, probably with the file handling. Under windows (and dos) I could find my way but I’m not familiar with Linux system, and even less with Android. Under normal circumstance I would reboot the system but without a build.prop in the system directory I fear that it will go even worse.
Any other suggestion?
Kuroneko
PS: I’ve nothing again command line but with a 3.7” touch panel it’s far from fun…
This is due to HTC's read/write protection that is built into the boot.img. You might see if there is a custom kernel for your device that has this flag disabled.
Thank for your answer,
But I’m not sure that I follow you.
If the problem was due to an r/w protection of the boot image, how I was able to modify my build.prop, and later erase it?
If you could explain this it would help greatly as it means that I could re-boot without worry.