Related
This is how i managed to install the Google Maps 5.7.0 ownhere/Brut.all MOD which enables Navigation in countries where originally you cnt use this app. this is a modified version that seamlessly replaces the original app.
i tried to follow the instructions provided in the original thread but i kept facing problems and errors like "Application not installed" when trying to install the app, and "remount failed: no such file or directories", among others.
i also dnt have the Maps app availble in the market in my country, i can only sideload it.
it took me few days of googling to finally make it work on my Galaxy Ace. i'm running a rooted stock 2.2.1
it's simple once you got the right instructions. but as usual, i'm not responsible if your phone just decides to go brain dead on its own
for this you need ROOT access, Superuser, ADB and Titanium Backup
in Titanium Backup, choose Maps and back it up (app+data).
in case things dnt work out, you can always use this backup to restore the original app and data.
in Titanium Backup, choose Maps and wipe data then uninstall.
in Titanium Backup, choose Street View, wipe data and uninstall.
use whatever way to place the maps5.7.0-ownhere.apk file in the root of your sd card.
(i dnt know what's the diffrence between maps5.7.0-ownhere and maps5.7.0-ownhere-testkeyresign. i used the first and it's working fine.)
now connect your phone to your computer and make sure you keep your screen on. that's very important for the next step to work.
launch ADB and enter these commands:
adb shell (in the next line, a $ will appear)
su (when you inter this, Superuser in your phone will prompt you to grant root access. confirm it. a # will appear in the next line)
mount -t rfs -o remount,rw /dev/block/stl9 /system (this will remount your system in Read/Write mode)
cp /sdcard/maps5.7.0-ownhere.apk /system/app/maps5.7.0-ownhere.apk
mount -t rfs -o remount,ro /dev/block/stl9 /system (remount system back in ReadOnly mode)
exit
exit
Maps should appear in your app drawer.
you can now reinstall Street View.
if anything is not clear enough, just ask
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Sent from your phone
is it working
an0nym0us_ said:
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Click to expand...
Click to collapse
that was the first thing that came to my mind when installing didnt work. i copied the file with root explorer but the Maps app didnt show up in the app drawer.
i only speak from my own experience, i'm no expert.
thank you for the contrbution
imranaryan said:
is it working
Click to expand...
Click to collapse
it is working on my phone
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.
Hi guys, having an odd problem.
I've made some nandroid backups (about three) via CWM Recovery, and I can't seem to browse to them, or delete them.
It's definitely taking up space, and I'm not sure what to do now.
A backup that I made straight to my external SD card however, seems to be browse-able, so I'm a bit confused now.
Attached are some screenshots from ES File Browser (with root access turned on).
The last screenshot is going to /storage/sdcard0/clockworkmod/ (same directory, but now I can't seem to see anything about "backups").
I've also tried to delete these backups straight from CWM Recovery, but CWM says that it can't access the folder.
Oddly enough, if I do another backup (straight to internal), it seems to put all the files in /sdcard/Clockworkmod/backups but never to be accessed again.
Anyone have any ideas?
Delete via Windows Explorer .
jje
JJEgan said:
Delete via Windows Explorer .
jje
Click to expand...
Click to collapse
Thanks for the suggestion, but nope, that didn't work. (Obviously tried that first).
The folder was shown as empty via Windows.
After a lot of digging and trying different things (including Root Explorer and Terminal Emulator), I've managed to delete it.
I'll post the instructions so other people who may have similar problems in the future can follow it.
First, you'll need ADB and you'll need to reboot into CWM Recovery.
Once you've gotten that sorted, boot into CWM Recovery and go to "mount and storage" and then select "mount /data".
This will mount the /data structure which we need to use.
Afterwards in CMD, use the following:
Code:
adb root
adb shell
After this, you should be logged in as ~ (root)
Proceed to go into the directory using the cd function. (PROTIP: Use the ls function to check where you're going.)
You need to get to ../clockworkmod/backup/
You'll find that you can finally access the /backup/ folder, and you'll then be able to delete the files. Please note that the below command will delete ALL the files within this folder.
Code:
rm -rf *
Afterwards, do
Code:
cd ..
to get back to the ../clockworkmod/ folder and then run the below code to delete the now empty /backup/ folder:
Code:
rmdir backup
no, to be logged in as root you need to type in "su"
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
EDIT:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
lalalalas said:
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
Click to expand...
Click to collapse
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
leadtk said:
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
Click to expand...
Click to collapse
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Quallenauge said:
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Click to expand...
Click to collapse
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
leadtk said:
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
Click to expand...
Click to collapse
From the guide, install using adb. http://forum.xda-developers.com/showthread.php?t=1871912
Originally Posted by surdu_petru
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /local/ ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
If you are a Linux user. http://forum.xda-developers.com/showpost.php?p=48731942&postcount=1
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
leadtk said:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
Click to expand...
Click to collapse
I do not know what i am doing wrong but when i type adb shell ..all i get is BUSYBOX v1.7.2 (2012-10-19 CEST) built in shell (ash) Enter help for a list of built in commands ...
I did have ics blue v04 rom on my tablet that i was trying to go from to 4.4.2 ..
I did this before and had the write problem . any help you can give would be appreciated
Hi,
I've been fighting with this for weeks, and I can't seem to get it work.
Situation:
I want to make my Xperia T (CM12.1) into a usenet download machine. I'm hoping to download local, and extract external to my share.
So far I've managed to mount the share, but anything I try won't give an App write permission. I've used ES File Explorer in Root Explorer mode to write, which works, but the specific app for usenet downloading doesn't need root, so it can't write to the share.
What I've tried:
Moving the App to system
Gave him all kinds of write permissions
Changed owner and group from system to root and vice versa
Used several kinds of mount commands
Used several mounting locations (folder on SD, folder in /mnt/remote dir, etc)
Adding the user id (uid) to the mount command, to target the mount for this specific user (which the basic terminal app gave me back as something like 1 and another said my uid was 2 for example, so that's wonderful...)
Adding the Domain of the user of the share
This is my mounting script:
Code:
su --mount-master
mount -o unc=\\\\192.168.*.*\\share1,username=Rubenos,password=*****,uid=1,gid=1,rw,nounix,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777 -t cifs none /mnt/network/share1
I'm executing this from the terminal app within CM.
What am I missing here?
Thx!
Bump
Hi. I've had the same issue on Nexus 5.
Looks like the root of the problem is SELinux. You need to flash an insecure kernel and disable SELinux enforced mode.
Obviously it's not a perfect solution and maybe someone will suggest a better idea how to fix it.