[Q] Read only storage - Nexus 4 Q&A, Help & Troubleshooting

hi
i installed ubuntu touch using dual boot. it has a bug that moves the sdcard content to a nested 0 folder. for example :
before ubuntu touch data was located at : /data/media/0 or /sdcard/
after installing it goes to : /data/media/0/0 or /sdcard/0/
i've installed it twice though so my files are at /data/media/0/0/0/ or /sdcard/0/0/ :|
android still considers /data/media/0 as its sdcard root though. every thing located at /data/media/0 has become read only and i'm getting the 'No external storage' when i launch the gallery app . i've already tried clearing the cache but it didn't work.
any ideas ?

backup your files and format data(stock recovery,or using android itself or using fastboot format userdata)

i know how to do that but i was hoping for a less 'factory reset' method :} but it doesn't look like i have much of a choice

MTN_HD2 said:
i know how to do that but i was hoping for a less 'factory reset' method :} but it doesn't look like i have much of a choice
Click to expand...
Click to collapse
maybe the permissions are wrong(or the owner)?

i did #chmod 775 and #chown media_rw:media_rw on all the folders in /data/media/0 and the 0 folder itself. it got better (i can rename,delete) but still can't access gallery and camera even after reboot.
ah screw it . i'm just gonna do the factory reset ... i figure its gonna take less time than messing with everything trying to fix it

Related

[GUIDE]Moving Dalvik-Cache to /Cache -Viewpad 7 Tested

Moving Dalvik-Cache to /cache
Notes:
If you want to move the Dalvik-Cache to /cache you will needed to the following:
1. A Viewpad7 or another branded device (such as: Cherry Mobile Superion, Commtiva Linx N700, Olivepad VT-100, Spice MI700, and Camangi FM600..........)
2. Already got the root permission (For running a set of command)
3. ADB or Terminal Emulator (For running the command)
4. Root Explorer(Optional - if you have a lot of patience for typing)
Steps
1. Build a file call "install-recovery.sh" into the /etc (Path: /etc/install-recovery.sh) With 711 Permission. (Or you can build it in your computer and put it in the sdcard then copy it using Root Explorer.
Code:
#!/system/bin/sh
chmod 771 /cache
2. Move your dalvik-cache and Create Symbolic Link
(You may experience some program FC (Force Close), but never mind)
Code:
mv /data/dalvik-cache /cache/dalvik-cache
ln -s /cache/dalvik-cache /data/dalvik-cache
You've done the action!
If you got a LOT of FC after move the dalvik-cache.
Please go to /(Root) to check the permission of the /cache it may be become 770.
Remarks:
I think it is able to do the same things to a SD Partition or A2SD.
However I have try it. (Because I still haven't install the Custom Recovery.)
If you have any problems. Please leave a message here.
If you want to forward this message. Please provide the source URL in your message.
DISCLAIMER: I cannot be held liable for anything you do to your Viewpad 7 (or equivalent device).
[DISCLAIMER Copy from lakehousetech thanks for your DISCLAIMER.]
Will this still works, after reboot ?
Yes It will be. The install-recovery.sh scripts will be automatically run everytime you boot up the viewpad 7
i found a more efficient method, moving dalvik chache to sd card partitions... using rom manager and link2sd..
wazzzuuuup2 said:
i found a more efficient method, moving dalvik chache to sd card partitions... using rom manager and link2sd..
Click to expand...
Click to collapse
Hah same here And it works great
Could either of you guys who are using ROM Manager/Link2SD provide instructions for how you set that up? Thanks!
Edit, a few days later. Disregard, figured it out on my own. For anyone else interested...
If you're one a Windows based machine, download this, and use it to create an ext2 partition on your SD card. Personally, I copied the contents of the SD over to my computer before I did so, then copied them back after I was done. With link2sd, you can just adjust all the "user" apps to link to the SD, and set it up so it does likewise on install of new apps. Very easy.

[ROM] malata_t8_smba_9701_cm9_3g

PIMPUP_ICS_MALATA T8​​​​​
DISCLAIMER NOTE
ITS NOT MY RESPONSIBILITY FOR DAMAGE WILL CAUSED FLASHING THIS ROM
HTML:
features
all cm9 twaeks ,screenshots,lockscreen widgets,theme,dsp,developers option
superbass beats with autovolume and working dsp manager
supercharger script
ntfs driver support
cifs support
walkman player with working youtube tweaks
floatting touchscreen
brightness & backlight stage improve
large battery levels over 3 days to wifi sleep
deep sleep without sod
3g and wifi support for most networks
latest gapps inverted with gmail.4.2 pinch to zoom and slice to delete
chrome browser working with flashplayer
DOWNLOADS
download nvflash:http://www.mediafire.com/?n513xv6dr28ppmw
download rom :http://www.mediafire.com/download.php?fl4dwihc172jztv
download gapps inverted:http://www.mediafire.com/download.php?fl4dwihc172jztv
INSTRUCTIONS
FIRST MUST GO TO OTA 20110524 FROM MALATA SITE AND DO DATA FACTORY RESET/WIPE CACHE
GO APX MODE AND RUN NVFLASH
GO CWM 5.5.0.4 DO DATA FACTORY RESET
FLASH PIMPUP 16 ROM AND REBOOT
CHECK IF GTALK APP HAVE BEEN INSTALL AND
REBOOT TO CWM 5.5.0.4 AND FLASH GAPPS
GO ADVANCE AND FIX PERMISSIONS REBOOT
MUST HAVE A COPY OF FAT32.IMG TO THE ROOT OF SD CARD
OPEN TERMINAL TYPE SU TO GET PERMISSION
TAKE MOUNT 1 COMMAND FROM ATTACHMENT AND PASTE TO TERMINAL
WAIT UNTILL MESSAGE THAT : ... bytes transferred in ..... secs AND PASTE MOUNT 2 COMMAND
NOW YOU HAVE UNLOCK YOUR INTERNAL MEMMORY
DONE!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
[/IMG]
IF YOU LIKE MY JOB BUY ME A BEER​
[/CENTER]
STEP 2
WARNING!
MAKE BACKUP FROM CWM BEFORE PROCCED
pimpup edition
new pimpup 7 update
Download from here
http://www.mediafire.com/?31toc9d0mybzzh3
Changelog
Added supercharger
Added ips matrix settings
Added 0db noise text when plug headset
And other usefuell things...
New invert gapps include new gmail 4.2 with pinch to zoom and swipe to delete
Make a backup before procced with tittanium app
To install will do fully wipe and will loose all apk!!!!
To install must do
Download from here
http://www.mediafire.com/?ywow63lwivf4i18
1 copy new gapps to sd card
2 go cwm mount system and format system
3 do data factory reset
4 flash new pimpup rom
5 boot first time and check if talk app has been installed
6 reboot to cwm and flash new gapps
7 wipe dalvik cache
Done
New dark theme with ics color its something that worth
The difficult was talk apk so proceed step by step otherwise will loose talk apk
Have fun!!!
Pimpup
download from here
http://www.mediafire.com/?24cymzxexec9kwd
changelog
the most amazing pimp script added
superbassbeats
float touchscreen
wifi and 3g devices support
if 3g doesnt work return to ote and make wipe data cache
first boot takes longer
wifi user turn off data
update 1.5
download from here
http://www.mediafire.com/?zwj1tfypabfubss
changelog
added new overclocking script
added original latest walkman player from sony with you tube tweaks
update 1.4
download from here
http://www.mediafire.com/?cz6x3y9x3lkad6c
changelog
added latest ics browser
added new kernel modules
ntfs support!!!
cifs support
sound improved
wifi improved
fingerprint improved
added latest busybox
added google music player for usb play
apollo removed
compitible with more games ie gameloft
update fix 1.3
download from here
http://www.mediafire.com/?6i2kuwyk2dnv2y6
changelog
cpu sleeper.apk added
http://forum.xda-developers.com/showthread.php?t=1745132
this is earlier kernel(than drh kernel) based to this tweak but for reason does not work properbly
enable service and boot this will fix sleep and rotate bug
work perfect with init.d tweaks i have added
added new build.prop as stand alone rom
if you want right mount after enable memmory i have attachment
right voldstab
unrar and
with root explorer paste at etc and give rw permission
reboot
not overheat fix
try it the pure aosp built in with cm9 tweaks
last fix
the main system has update with better comands
the plus of kernel built is that commands is straight from boot
whyberg did it an gave us that tweks you will receive from update
the update use half daemons so the steps should be from the begining
first rom then update
plus
no sleep reboots
wifi steady
wifi & 3g both working
With download mode
fast !!! Very Fast!!!!and stable
Best perfomance
dont use supercharger or root apps will wipe dalvik cache
you will receive phone error take backup before update
neuro friend should take update
kernel and rom are same
same problems same solves
have fun[/COLOR]
the third step is unlock memmory
ihave add two txt at attachment files for mount sdcard
you must have a copy of real-fat32.img from nvflash folder to the root of sdcard
open terminal type su
copy paste comands
and reboot
And all this is done, I needed a customized mode ADB on a PC connected to the tablet PC, tablet inserted into MicroSD card, and file real_fat32.img, abandoned to the root of MicroSD (see attach). So:
1. Enters the ADB (I have Win XP, I went through Start -> Run -> Cmd)
2. Run ADB - consistently serving team "ADB devices" (get the code connected device - it will not need, just confirmation. Device is connected), and "ADB shell" - to turn on the console.
3. Serve command "mount", the screen falls list mounted devices, the end will be a line like / dev/block/vold/179: 9 / mnt / microsd ..... (In fact, we need only the inscription / mnt / microsd)
4. Write the command "dd if = / mnt/microsd/real_fat32.img of = / dev/block/mmcblk0p7" (this command overwrites the disk image to 4.77 GB while a malfunctioning device / dev/block/mmcblk0p7. ​​So we are making the proper recording of the file system on the device sdcard, which after flash unfortunately incorrect. And a self-memory sdcard becomes 4.77 GB. Dubbing lasts for some time, with no message is not displayed, but you must wait for the final completion message recording. come out on the screen something like: ... bytes transferred in ..... secs (....... bytes / sec))
5. Sdcard install command - mount-t vfat / dev/block/mmcblk0p7 / mnt / sdcard
6. Reboot your tablet.
And it's all
PS If you suddenly reboot internal memory again not read correctly - download tablet mode CWM, look in the engineering menu "format emmc" (not to be confused with the sdcard - in the engineering menu sdcard - this card MicroSD, and emmc - internal memory), and then check that the internal memory is available - consistently perform in the engineering menu command "mount emmc" and "unmount emmc" - both teams have performed well
Step 3 post taken from 4pda/forum assistant07 author​
Thanks for that.. one rom and one update in two days.. Great !
I've been trying it and except for the low memory space, this is very great ! I wil install the update as soon as it is downloaded but even without update, the rom was work quite nicely..
I've just finished downloading and installing your update.. Nice... The tablet now wake up much faster from the sleeping mode.. And it seems it boot faster as well.. Good update... Well done, really happy with it...
Does 3G and camera work?
cociuba said:
Does 3G and camera work?
Click to expand...
Click to collapse
No camera
No hdmi
No mic
All others work great
cociuba said:
Does 3G and camera work?
Click to expand...
Click to collapse
I never use the 3G, so i dont know if it is working.. But the camera isnt.. But to be honest, I never really used the camera on this tablet. The quality of it isnt great.... So, it wasnt a no-go for me not to have it working.. And the same goes for 3G. I'm always using wifi to connect on internet.
Honestly, i tried all he different roms that's been going on that site in the recent years, and before any ICS rom came out, i never kept any of them. After playing a little bit with them, i'd always reverted back to the stock version. There was always something i didnt like, something that bothered me... It was either the status bar, the display, the orientation problem..
But since geowolf1000 shared with us this new CM9 rom, i havent even thought once about reverted back to the old stock rom.
In my opinion, if the camera not working isnt a problem for me, just give it a try, you may like it...
The only drawback that may refrain you from flashing that rom, maybe, for the moment, the limited memory space allocated to new apps. there is only 250 Mb....
So, if you want to install large apps, it will be full quite quickly. And this is, in my opinion, the only drawback of that rom.
But like i said in another post, if you only use your tablet to surf internet, to go on youtube, read your mails, watch movies, maybe read comics, books or magazines, that rom will be a delight to use, promise.
On mine, I've install the following apps : Adobe Flash Player, Better Keyboard, Google Currents, Digi Clock widget, Dropbox, Facebook, Freecell, Maps + Street View, Mx Player and its codec, Perfect Viewer and its PDF plugin, Adobe Photoshop Touch, Solid Explorer, Wallbase, Wifiwidget and Youtube app...
And so far, I've used 200 MB and i've got 52 MB free....
i think now download problem has been fix
update with new fix
when start only once turn off and turn on wifi anf signal change color
Do anybody has downloaded stock ROM for our devices?
It seems file:
ht*p://112.5.164.225/tablePC/T8_nvflash_emmc_WCDMA_20110524.rar
on malzata.com download page is offline/deleted.
kedziu said:
Do anybody has downloaded stock ROM for our devices?
It seems file:
ht*p://112.5.164.225/tablePC/T8_nvflash_emmc_WCDMA_20110524.rar
on malzata.com download page is offline/deleted.
Click to expand...
Click to collapse
Hope this helps :
https://dl.dropbox.com/u/33159207/T8_nvflash_emmc_WCDMA_20110524.rar
dont hezitate to post bug
The reboots remain?
Cociuba the 3g working?
Did you download from 3g?
I am to 2ond day with 3d update and all working smoothlie
If reboots remain go to advance of wifi menu and trigger never of wifi sleep mode
It reboot every some times like wifi scan interval
Trigger never so at sleep time and that will disable scan
I hope that update been usefull
Thanks
I've just have a question :
Where can we find real_fat32.img ? is it the same one as the real_fat32.img in the T8_nvflash_emmc_WCDMA_20110524.rar archive or is it another one ?
obeguin said:
I've just have a question :
Where can we find real_fat32.img ? is it the same one as the real_fat32.img in the T8_nvflash_emmc_WCDMA_20110524.rar archive or is it another one ?
Click to expand...
Click to collapse
Yes is rhe same
I am still fighting with flashing new ROM..
i have'nt problems with AOSP 4.0.4 ics rom for malata t8(smba_9701)mcc expect problem with META-INF - the same what had obeguin member. After change META-INF flashing was OK and system also works perfect.
Now i am trying to flash NEURA rom and i have problems during the installation process. I will try to describe as detailed as i can.
go APX
nv flash T8_nvflash_emmc_WCDMA_20110524 (download_EMMC_512)
start the system and do 'privacy options' - 'factory data reset' (system is rebooting..)
go APX
nv flash xdownload.WIFI (i have version 3G but with 512MB memory, xdownload.3G - is not working with my tablet)
go recovery 5.5.0.4 and wipe cache partition
--Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
Cache wipe compleate.
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
reboot recovery 5.5.0.4
install zip from sdcard - choose zip from sdcard - cm9-20120610-u«UNOFFICIAL.zip
-- Instaling
E:cant mount /cache/recovery/last_install
E:filed to open last_install: no such file or directory
Finding update packege..
opening update package..
instaling update
install from sdcard complete.
all process take 20sec (realy fast)
next gapps-ics-20120317-signed.zip
wipe data
--wiping data..
formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p6
formating /cache..
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
formating /sd-ext
formating /sdcard/.android_secure..
data wipe complete.
reboot and stack on nvidia splash screen...
could anybody tell me where i am making fault?
kedziu said:
I am still fighting with flashing new ROM..
i have'nt problems with AOSP 4.0.4 ics rom for malata t8(smba_9701)mcc expect problem with META-INF - the same what had obeguin member. After change META-INF flashing was OK and system also works perfect.
Now i am trying to flash NEURA rom and i have problems during the installation process. I will try to describe as detailed as i can.
go APX
nv flash T8_nvflash_emmc_WCDMA_20110524 (download_EMMC_512)
start the system and do 'privacy options' - 'factory data reset' (system is rebooting..)
go APX
nv flash xdownload.WIFI (i have version 3G but with 512MB memory, xdownload.3G - is not working with my tablet)
go recovery 5.5.0.4 and wipe cache partition
--Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
Cache wipe compleate.
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
reboot recovery 5.5.0.4
install zip from sdcard - choose zip from sdcard - cm9-20120610-u«UNOFFICIAL.zip
-- Instaling
E:cant mount /cache/recovery/last_install
E:filed to open last_install: no such file or directory
Finding update packege..
opening update package..
instaling update
install from sdcard complete.
all process take 20sec (realy fast)
next gapps-ics-20120317-signed.zip
wipe data
--wiping data..
formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p6
formating /cache..
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4
formating /sd-ext
formating /sdcard/.android_secure..
data wipe complete.
reboot and stack on nvidia splash screen...
could anybody tell me where i am making fault?
Click to expand...
Click to collapse
download again from here
http://www.mediafire.com/?dyjec4wzyskivsd
geowolf1000 said:
the third step is unlock memmory
And all this is done, I needed a customized mode ADB on a PC connected to the tablet PC, tablet inserted into MicroSD card, and file real_fat32.img, abandoned to the root of MicroSD (see attach). So:
1. Enters the ADB (I have Win XP, I went through Start -> Run -> Cmd)
2. Run ADB - consistently serving team "ADB devices" (get the code connected device - it will not need, just confirmation. Device is connected), and "ADB shell" - to turn on the console.
3. Serve command "mount", the screen falls list mounted devices, the end will be a line like / dev/block/vold/179: 9 / mnt / microsd ..... (In fact, we need only the inscription / mnt / microsd)
4. Write the command "dd if = / mnt/microsd/real_fat32.img of = / dev/block/mmcblk0p7" (this command overwrites the disk image to 4.77 GB while a malfunctioning device / dev/block/mmcblk0p7. ​​So we are making the proper recording of the file system on the device sdcard, which after flash unfortunately incorrect. And a self-memory sdcard becomes 4.77 GB. Dubbing lasts for some time, with no message is not displayed, but you must wait for the final completion message recording. come out on the screen something like: ... bytes transferred in ..... secs (....... bytes / sec))
5. Sdcard install command - mount-t vfat / dev/block/mmcblk0p7 / mnt / sdcard
6. Reboot your tablet.
And it's all
PS If you suddenly reboot internal memory again not read correctly - download tablet mode CWM, look in the engineering menu "format emmc" (not to be confused with the sdcard - in the engineering menu sdcard - this card MicroSD, and emmc - internal memory), and then check that the internal memory is available - consistently perform in the engineering menu command "mount emmc" and "unmount emmc" - both teams have performed well
Click to expand...
Click to collapse
Ok, i managed to install ADB and used ADB.
I install real_fat32.img onto my SD card. And then, to the root of the internal memory - recognized asSD card on the malata -
then, I run the following command :
mount
dd if=/mnt/microsd/real_fat32.img of=/dev/block/mmcblk0p7
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
reboot
I didnt see any differences.. I even rebooted in recovery mode, Format emmc and still, no differences...
I mean, the internal memory is still recognized as SD card, and vice versa.. And still only have 250 MB for my apps..
What was it supposed to do ?
You have nvflash whyberg kernel
Download from 1page again and nvflash neuro kernel
Neuro kernel has 1.9 capacity
Follow step again
geo I've followed yours instruction and everythink is working fine. thanks!
I am wondering if we can add mounting sdcard to initr.d?
now I need to type in console:
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
every time I boot android.
kedziu said:
geo I've followed yours instruction and everythink is working fine. thanks!
I am wondering if we can add mounting sdcard to initr.d?
now I need to type in console:
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
every time I boot android.
Click to expand...
Click to collapse
Ooooooohhhhhh.. It goes back to normal, each time you reboot the tablet ?
Maybe that's why it wasnt working then. Because each time, I was trying to reboot the tablet but when i checked my memory, it wasnt working. There was always a problem.. I never checked my memory before reboot.. Only after rebooting and i couldnt understand why it was working...
So, tonight i'll check what happen before rebooting...
And to run the command at each reboot.. I think there may be a solution but I havent try it...
But on google play, there is an app call smanager ( it stands for Script manager ) and it is an applictaion to execute scripts at boot..
So, i think it should be possible to run the command at boot...
save line below in text file, no file extension
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
use play store app: "smanager" free, to run script on boot + su
Click to expand...
Click to collapse
But I havent try yet, but i will try it tonight...
smanager is working fine
you need to create text file with lines:
#!/system/bin/sh
mount -t vfat /dev/block/mmcblk0p7 /mnt/sdcard
save and get permisions to execute.
in smanager you have to give attributes boot and su.
Just for know
Last update can be stand alone rom
Nothing change and don't need to do it again
If ever need to update again only last after kernel,now you know my rom .
You can restore
Ok

[MOD][SCRIPT] Get More Storage by Relocating Dalvik Cache!

DISCLAIMER: YOU AGREE TO TAKE FULL RESPONSIBILITY FOR YOUR DEVICE IF YOU PROCEED.
The original thread (http://forum.xda-developers.com/moto-g/general/mod-save-data-space-cache-partition-t2942765) was getting to cluttered up with development and testing so I decided to start a new thread with the "finished" product. The original thread will be renamed to Q&A/Development. We might even ask for the old thread to be closed down. (up to @Bert98, the thread's creator.)
Moto G's internal eMMC card has a ~600Mb partition called /cache, which is not used since the apps' cache is stored in /data, so the latter fills up and the first one stays empty.
Owning a 8Gb model, having 600Mb not available for storage really bugged me, because my phone's memory (/data partition) was always full because it's a 5.7Gb space shared between apps and microSD files.
Now, it may not work for you if:
a) you have A LOT of apps installed.
And by "a lot", I mean more than 90-100 apps, but if you have a 8Gb model, you probably don't
b) you're running ART (this is default in lollipop and newer)
Since ART uses a lot more space than dalvik, the space in the /cache partition probably won't be enough. When I was running ART, it used 1Gb more than dalvik.
Original post by @Bert98
Click to expand...
Click to collapse
This was tested on my moto g 16GB which is running RetailUS_4.4.4 kitkat with CWM recovery. The custom ROM procedure was tested on the same phone but with cm11 Nightly installed.
Prerequisites:
1. You must have "adb root" functioning. If you don't head to this thread: http://forum.xda-developers.com/showthread.php?t=1687590 and there is a free download link at the bottom of the post.
Download and install the apk on your phone. Open up adbd insecure (the new app) and grant it superuser rights PERMANENTLY. Check the box that says "enable insecure binary" and make sure to check the box
that says "enable at boot."
2. You must have a recovery that can accept adb shell commands.
3. Root Access Duh?!
4. A windows machine capable of running batch files.
5. A decent text editor, notepad will work but notepad++ is strongly recommended. (Only needed if you are using STOCK ROM procedure)
Please, please make a nandroid backup before you continue!!!!
Stock ROM procedure:
Read the directions very carefully and then read them again, before continuing.
1. Download the cachemover_v1.3.zip from: LINK REMOVED DUE TO SCRIPT ISSUES.
2. Extract the contents.
3. Connect device to PC and navigate to the extracted folder.
4. Double click/Run the cachemover_Stock.bat
5. Follow the onscreen instructions until you get to the part where it says to edit a file.
6. About halfway through the script it will pull a file called "init.qcom.post_boot.sh" to the folder.
7. Open it with a TEXT editor and navigate to about line 487 (Might be different for 8gb model). Look here for a better understanding: https://www.dropbox.com/s/jr5lyl5s5i2jtpg/where to paste code.PNG?dl=0
8. Start a new line and paste this code in the file: (Refer to the image above for help)
Code:
chmod 655 /cache
chmod 655 /cache/dalvik-cache
chmod 655 /cache/dalvik-cache/*
9. Make sure to save the file in the same folder as the cachemover_Stock.bat
10. Press any key to continue on the script and let it do its thing.
11. It will reboot several times and land you on the home screen/lock screen.
12. If the script hangs after a reboot, you need to unlock the device to reestablish a connection with your computer.
13. There might be one or two force closes but once you close the notifications they will not come back.
Custom ROM procedure:
USE THIS FOR ROMS THAT DO NOT REMOUNT OR CHANGE PERMISSIONS OF /CACHE ON BOOT
1. Download the cachemover_v1.3.zip from: https://www.dropbox.com/s/bzj34g4q1s61ojz/cachemover_v1.3.zip?dl=0
2. Extract the contents.
3. Connect device to PC and navigate to the extracted folder.
4. Double click/Run the cachemover.bat
5. Follow the onscreen instructions.
If anything goes wrong:
Go to recovery, wipe cache, then wipe dalvik-cache and reboot. This should get your device back to how it was.
(If you used STOCK ROM procedure)
The script made a backup of the "init.qcom.post_boot.sh" file to /sdcard/init_backup
You can restore the shell script to /system/etc/ via shell commands or by using a root browser. To restore permissions:
Code:
chmod 740 /system/etc/init.qcom.post_boot.sh
chown root:root /system/etc/init.qcom.post_boot.sh
Custom ROM procedure already has a restore script!
I am currently working on an auto restore script for stock and that will be relased soon, hopefully! :good:
Changelog:
v1.0 - First stable release. Does not work on STOCK ROM.
v1.1 - Added a restore script.
v1.3 - Added support for STOCK ROM. There are still a few bugs.
How it works?!?!
Coming soon...
Huge thanks to @Bert98 and @dd043
Hit the thanks button if it worked! I went through about 50 factory resets, and reflashed the ROM about 25 times, and put about 10 hours of work into this script! Really motivates me for future projects. :laugh:
Thanks for your help man and effort.
I encountered a problem, everything works up until my device boots in CWM to fix permissions, then just sits there doing not alot I don't even see the option in my CWM.
Any ideas? cheers
Sent from my XT1032 using XDA Free mobile app
When it reboots to cwm unplug the cable and replug it, if it hangs just type these commands manually from a command window.
chmod 655 /cache
chmod 655 /cache/dalvik-cache
chmod 655 /cache/dalvik-cache/*
reboot
If this does not work you may ned to go into mounts & storage in the cwm menu and click mount /cache. Then try the commands again.
I'm having some issues on stock.
I thought 0655 fixed everything but no, I can't install any app after moving the dalvik-cache to /cache. I tried chmoding 0777 on the new cache folder, on /cache itself, to no avail.
Code:
E/dexopt cannot open '/data/dalvik-cache/[email protected]' for output
Anyone can confirm it's not only my device? And/or can help find a fix?
Also does someone knows how to execute commands on a particular init step? Real init.rc scripts can do:
Code:
on post-fs-data
mount -o bind /cache/dalvik /data/dalvik-cache
It there was a way to achieve the same from post_boot/init.d we could mount -o bind /cache/dalvik /data/dalvik-cache and all permissions issues would disappear as well as the need for symlink.
You have a typo in the threads title. Just a heads up.
Vuciz said:
You have a typo in the threads title. Just a heads up.
Click to expand...
Click to collapse
Thanks for letting me know!
dd043 said:
I'm having some issues on stock.
I thought 0655 fixed everything but no, I can't install any app after moving the dalvik-cache to /cache. I tried chmoding 0777 on the new cache folder, on /cache itself, to no avail.
Code:
E/dexopt cannot open '/data/dalvik-cache/[email protected]' for output
Anyone can confirm it's not only my device? And/or can help find a fix?
Also does someone knows how to execute commands on a particular init step? Real init.rc scripts can do:
Code:
on post-fs-data
mount -o bind /cache/dalvik /data/dalvik-cache
It there was a way to achieve the same from post_boot/init.d we could mount -o bind /cache/dalvik /data/dalvik-cache and all permissions issues would disappear as well as the need for symlink.
Click to expand...
Click to collapse
Let me try and do that right now... Ill get back to you if it does!
My script works on stock btw... But the mount way seems a bit easier and might cause less errors than my way.
Try it please.
skyguy126 said:
Let me try and do that right now... Ill get back to you if it does!
My script works on stock btw... But the mount way seems a bit easier and might cause less errors than my way.
Try it please.
Click to expand...
Click to collapse
Yes I've tried your script, all went well but the result is the same. The script itself works nicely btw
Applications present before moving cache work perfectly, but I can't install anything new. I suspect it might be my device but before wiping everything I'd prefer feedback from others :fingers-crossed:.
I cannot install new apps as well. The mount command you showed me has the same effect too. I honestly don't know anymore, the sym link did not allow the install of new apps nor did the mount command you sent me. Correct me if I am wrong.
Edit: Going through all the init files on my phone to see which one remounts /cache at boot.
Why does the init.rc get overwritten at boot. Is it because the kernel (boot.img) is the one that copies it over? I have found by changing the perms/locations in this file and init.target.rc you can achieve what this mod is trying to acomplish.
I don't see the mount cache command in CWM strange
I've managed to get back to normal, thanks for everyone's help though, I will keep and eye on the thread
Sent from my XT1032 using XDA Free mobile app
non-windows version?
Thanks for this tool. It's a great idea and our Motos really need it.
However, I have a problem - I do not own a windows license (os x and ubuntu user) and I would prefer not to spend $120 just to use it for this script. Pirating is out of the question for me.
I was wondering if there is any chance of having this script written for linux and/or mac. If impossible, is there a LEGAL way of running windows in a virtual machine? Something like a trial or similar?
If you know how just convert it to shell script for osx and Linux. I give you permission to do this but you may not take credit or rehost your creation.
Ok so I have the kernel extracted and we could modify and flash that, but I believe that it's not really necessary. There are a lot of risks to flashing kernels and I am not willing to take it. So is there a way we can modify dalvik so it creates it's cache in /cache instead.
skyguy126 said:
Why does the init.rc get overwritten at boot. Is it because the kernel (boot.img) is the one that copies it over? I have found by changing the perms/locations in this file and init.target.rc you can achieve what this mod is trying to acomplish.
Click to expand...
Click to collapse
Yes the init.rc is in the boot ramdisk. I don't think it would be worth the trouble to rebuild a boot.img. The moto g is fairly unbrickable but it's quite a lot of work to setup an environment to rebuild an image :/.
Too bad for the mount command, I was sure it was working but maybe I had changed something else and don't quite remember the steps to reproduce
We could possibly implement a shell script toggler for when we need to install new apps, but I'm afraid it'd become annoying fairly quickly: I noticed the issue initially because google play services decided to update itself, failed, and broke all google apps. As far as I know this autoupate can't be disabled.
Thanks for trying!
dd043 said:
Yes the init.rc is in the boot ramdisk. I don't think it would be worth the trouble to rebuild a boot.img. The moto g is fairly unbrickable but it's quite a lot of work to setup an environment to rebuild an image :/.
Too bad for the mount command, I was sure it was working but maybe I had changed something else and don't quite remember the steps to reproduce
We could possibly implement a shell script toggler for when we need to install new apps, but I'm afraid it'd become annoying fairly quickly: I noticed the issue initially because google play services decided to update itself, failed, and broke all google apps. As far as I know this autoupate can't be disabled.
Thanks for trying!
Click to expand...
Click to collapse
How about making a simple apk that toggles this feature. Something like when you click the icon it doesn't even open but gives a little notification of success. Something like that. I myself am not experienced with apks but I can put together a shell script for the apk.
skyguy126 said:
Ok so I have the kernel extracted and we could modify and flash that, but I believe that it's not really necessary. There are a lot of risks to flashing kernels and I am not willing to take it. So is there a way we can modify dalvik so it creates it's cache in /cache instead.
Click to expand...
Click to collapse
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
dd043 said:
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
Click to expand...
Click to collapse
Ill try it. I don't mind doing a bunch of resets because I am using my moto g as a test bench anyway. My daily driver is the OnePlus One
dd043 said:
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
Click to expand...
Click to collapse
EDIT: Unfortunately it didn't work. I don't know if I modified the installd file correctly. The program I used is HxD.
Is there a way we can force dalvik to start after the directories are created. And change dalvik to create it in /cache.

Weird folder issue

I've been having this weird issue with folders on my N4 for a while now. Just for background, I'm using SimpleAOSP r11 with CWM 6.0.4.7 though I just switched recoveries because I think that was the issue.
Anyways, sometimes when I update my phone, my old folders on /data/media gets put into another location. Like the folders would be there but there would be nothing. Instead there would be an additional /0, /legacy, and /obb in /data/media that would contain the old folders with content. Is there any way to remerge these folders through adb? I thought I saw a post on a topic that I follow but I couldn't find the post when I looked through. Also any idea why this happens?
Sent from my bacon
stab244 said:
I've been having this weird issue with folders on my N4 for a while now. Just for background, I'm using SimpleAOSP r11 with CWM 6.0.4.7 though I just switched recoveries because I think that was the issue.
Anyways, sometimes when I update my phone, my old folders on /data/media gets put into another location. Like the folders would be there but there would be nothing. Instead there would be an additional /0, /legacy, and /obb in /data/media that would contain the old folders with content. Is there any way to remerge these folders through adb? I thought I saw a post on a topic that I follow but I couldn't find the post when I looked through. Also any idea why this happens?
Sent from my bacon
Click to expand...
Click to collapse
If your'e getting weird /0 changes, follow this:
Also, CWM is a bit outdated, PhilZ CWM is an updated + improved CWM, try it out. The latest build says experimental but it's perfectly safe, confirmed by multiple users : http://forum.xda-developers.com/showpost.php?p=58065887&postcount=424
Got "No SDCard" error?
This is because 4.4.x seems to point to: storage/emulated/0 & L points to: data/media/0
Solution:
- Mount system in TWRP/CWM
- Wipe system, dalvik, data, cache
- Unmount system
- Install ROM
- Factory reset
- Reboot
- Go back to recovery & flash SuperSU (link above).
- Reboot
Still not resolved? try:
Open terminal and type
su
restorecon -FR /data/media/0
or type
su
restorecon -r /data/media/0/*
Click to expand...
Click to collapse
Source info : http://forum.xda-developers.com/showpost.php?p=53956158&postcount=2

Apps Cannot Access Internal Memory after TWRP Recover

Background:
Trying out ROMs here and there, making backups along the way in TWRP. Turn out I had my favorite ROM from the start, so clean all the slates and performed a restore to Hybrid X Series 1.07. Everything is as it was...almost.
Apps are complaining about not being able to download to internal memory, there not being enough space, etc (there's plenty). Switching the download directory of these apps to the extSdCard is my current workaround.
What I've tried:
Fix Permissions from TWRP
Repair partition /data from TWRP using e2fsck
recursive busybox chown to 1001 on /data/media
restorecon on /data/media/0
This Fix Script Also found a similar flashable ZIP which did the same thing, but to no avail
None of these seem to have any effect. Also, trying to change permissions from Root Browser works on /sdcard, but not on any subfolders. Error returned is "Changing permissions was not successful. Please note that some file systems do not allow permission changes."
Any thoughts
funkeywoookey said:
Background:
Trying out ROMs here and there, making backups along the way in TWRP. Turn out I had my favorite ROM from the start, so clean all the slates and performed a restore to Hybrid X Series 1.07. Everything is as it was...almost.
Apps are complaining about not being able to download to internal memory, there not being enough space, etc (there's plenty). Switching the download directory of these apps to the extSdCard is my current workaround.
What I've tried:
Fix Permissions from TWRP
Repair partition /data from TWRP using e2fsck
recursive busybox chown to 1001 on /data/media
restorecon on /data/media/0
This Fix Script Also found a similar flashable ZIP which did the same thing, but to no avail
None of these seem to have any effect. Also, trying to change permissions from Root Browser works on /sdcard, but not on any subfolders. Error returned is "Changing permissions was not successful. Please note that some file systems do not allow permission changes."
Any thoughts
Click to expand...
Click to collapse
First off, this is an ownership issue, not a permissions issue
Second, chown 1001 gives ownership to Radio, not System. Chown to 1000 for System ownership
I never did find a solution to this problem. In my attempts to correct the problem, I ran chown on the entire /data partition by accident. The ROM booted, but everything crashed. After this, I just decided to salvage what little I might be able to save and move on with life.
The problem even persisted through wipe/reinstall of the ROM.
Finally, as a last resort, I had flash the stock version through Odin and start over from scratch.

Categories

Resources