I installed Ginger Yoshi 1.5 on my Android Dev Phone 1 by following these instructions:
http://forum.xda-developers.com/showthread.php?t=1178665
I found that most things are working, but I cannot install CoPilot GPS (28MB)
Error 498 in Google Play seems to mean the /cache partition is too small. My cache partition is 27MB.
I tried redirecting /cache to larger place with Cache Fixer 1.1
The "Data" option doesn't succeed in expanding the cache.
The "Tmpfs" option successfully makes the cache bigger, but it makes Play force close when I try to install the app.
I Tried using CacheDownload2SD 1.7.1, but it doesn't do anything
I got a message saying my su binary should be updated. I don't know if that is related or not.
I tried updating the SuperUser su binary from 2.3.2-efgh to 3.1.1
su Binary Updater says "Make sure new su works... fail!"
When I try again, su Binary Updater says "Copying su to /system... fail!"
When I try yet again, su Binary Updater again says "Copying su to /system... fail!"
I used Root Checker to verify root access. The phone is properly rooted. I don't know if this issue is related
I've considered downloading an apk and manually installing it. That should work, but then Google Play wouldn't let me know when an update became available. Any ideas on how to solve the problem? Does anyone know why Cache Fixer and CacheDownload2SD dont' work? Can anyone see why the su binary won't update? I've spent all day clearing caches, rebooting, and attempting installs. Why does Google Play need to download to such a tiny partition?
@IMSargon if your /cache partition is too small then you need to use custom MTD.
HTCDreamOn said:
@IMSargon if your /cache partition is too small then you need to use custom MTD.
Click to expand...
Click to collapse
Thanks for that. I certainly have some more reading before I fully understand the topic. When I upgraded to Ginger Yoshi 1.5, I changed from DangerSPL to hboot-1.33.0013d which gives practically the same partition sizes, except /cache is 27MB instead of 30MB, which is why I didn't have this problem before.
So you're saying I can flash to this custom bootloader to increase my cache size (decreasing /system and/or /data accordingly), install the GPS app, then flash back for normal operation? It sounds like a risky proposition. Is there no way to permanently or temporarily redirect the location to which Play downloads APKs? Such solutions appear to exist (Cache Fixer, etc), but they don't seem to work for me (why?).
No, if you change partition sizes you will be wiping those partitions. Maybe a better option is to do it just once but bind mount to sdcard, see the link htcdreamon gave for more info on this
Sent from my Nexus 4 using xda premium
demkantor said:
No, if you change partition sizes you will be wiping those partitions.
Click to expand...
Click to collapse
This is a relief to hear. It sounded like they would just redefine the partition boundaries with the data in place and hope for the best. I was wondering how that worked. After re-reading, the instruction do call for wiping the partitions and re-flashing the ROM.
demkantor said:
Maybe a better option is to do it just once but bind mount to sdcard, see the link htcdreamon gave for more info on this
Click to expand...
Click to collapse
That would work, and it's something I'll seriously consider once I have a chance to read all the documentation. It seems to me, though, that I should be able to unmount and remount elsewhere the /cache partition on a live system from the command line. Any reason I should not attempt that?
If you want to resolve your problem then follow these steps
- Clean your Device Cache
- Erase Market Data
- Scan your Device for Viruses
- Restore Smartphone to Factory Settings
I also have tutorial like article where you will find all the solution steps to fix the error here is the link:
optimum-systems.com/2013/04/error-498-in-android.html
I hope you will resolve your problem
I tried making a folder under /sdcard, removing /cache, and replacing it with a symlink to the folder in /sdcard. That didn't work for a number of reasons. Firstly, mkdir was missing, which was a pain. I just made the directories with File Manager on the phone - I'll fix that later. Then it wouldn't let me change the ownership of the target directory on the sdcard, even though I was root. When I tried downloading my app, Play force closed.
My next idea was to put the folder in /sd-ext, which is my next largest partition. This is an ext4 partition on the sdcard. I created a folder there. Then I deleted /cache/download and created a symlink to my folder in /sd-ext. I didn't have any problems changing permissions this time. For whatever reason, Play did not force close, and successfully installed the app.
I'll write what I did here, but I'll pretend mkdir worked.
Code:
rm /cache/download
mkdir /sd-ext/download
chown system:cache download
ln -s /sd-ext/download /cache/download
chown -h system:cache /cache/download
I'd expect this setup to survive a reboot, so maybe you want to delete the symlink and remake the original folder to set things back to normal. If not, only apps that use /cache/download are effected, so you might as well leave it. Just clean that folder out every so often.
Related
I've been trying to figure out how to fix my phone and my knowledge of unix is terrible. I checked the adb logcat on my phone and the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. If not is it possible to delete this file and the phone will rebuild a proper version of it. It seems to be the root of what is causing my phone to go into a bootloop whenever I attempt to install a non-JF build. Thank you guys ahead of time.
The entire /system partition is always read-only, unless you tell your phone to remount it read-write.
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
But for your problem.. You shouldn't really need to manually tweak files in /system if you flash another ROM. The new ROM will replace that entire partition. Have you wiped? What ROM are you trying to flash?
Kudos for using logcat and trying to jump in yourself though.
Saiboogu said:
The entire /system partition is always read-only, unless you tell your phone to remount it read-write.
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
But for your problem.. You shouldn't really need to manually tweak files in /system if you flash another ROM. The new ROM will replace that entire partition. Have you wiped? What ROM are you trying to flash?
Kudos for using logcat and trying to jump in yourself though.
Click to expand...
Click to collapse
I've been unable to replace the ROM because I keep getting stuck at the T-Mobile G1 screen in a bootloop constantly running those errors. I've tried cyanogen, dudes, jachero and keep getting stuck in a bootloop. I had an earlier post here http://forum.xda-developers.com/showthread.php?t=536657.
Metatronx said:
I've been unable to replace the ROM because I keep getting stuck at the T-Mobile G1 screen in a bootloop constantly running those errors. I've tried cyanogen, dudes, jachero and keep getting stuck in a bootloop. I had an earlier post here http://forum.xda-developers.com/showthread.php?t=536657.
Click to expand...
Click to collapse
Interesting.. Doesn't sound fun. I remember your other thread - didn't chime in that time because I had no advice. Still not sure what could be causing it. Did you try the last bit of advice in that thread?
Also .. I'm no Android development expert, but just form my PC knowledge.. That logcat from the other thread could be explained by file corruption. And if you get similar issues on different ROMs, it points to your device. Bad blocks on the internal storage, or glitch in the memory controller. May be something that doesn't get utilized until one of the newer (and larger) ROMs gets written to that block.
That's all just a theory.. But if you can't get it running, is there any chance you can exchange it? To rule out the hardware.
is there a guide anywhere on this or could someone give me a rough guide?
Do I need to format the partitions I made on my SD to run Hero, when flashing to another ROM that uses APPS2SD like Soulife's Rogers? I'm getting untold weird problems with this ROM - syncing etc.
Also, looks like APP2SD might not be working - 45MB free space is this right?
(For the record, all I did was a 'wipe' and then flash - which didn't seem to get rid of most apps)
Thanks!
You need to wipe your ext partition before switching roms.
That will get rid of the apps that stayed.
Hmm.. I digg my double post even though I only clicked once. Thx xda
can you wipe with the 'repair ext filesystems' option in cyanogens bootloader?
didn't seem to work for me. :?
with adb:
adb remount
adb shell
rm -r /system/sd/*
reboot recovery
then flash the update
thanks!
when I do
rm -r /system/sd/*
I get:
cannot remove '/system/sd/*': No such file or directory
So I guess there's nothing there anyway? ... looks like it when I 'ls' the directory anyway... confused as to why my apps keep on showing up after flashing ???
what a minute I adb'd in when it was in bootloader mode would that effect what I see?
I have downgraded from JPK to JM8. When recovery runs I get an errormessage about "can not access /system/csc", not exact words but I think I've understood it right. I have checked it with ADB and I have permissions set to "drwxr-xr-x root root csc" and in /system/csc I have "-rw-r--r-- root root" on all files. It seems a little strange that my permissions are set to that in the folder. Are those permissions correct?
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Ok. Will do that. I'm looking for a reason to why I can't flash docs rommod onto my phone. I can't get any further than to the S on black background hearing bootsound but the phone doesn't boot up to a ui. Thought the message could be a clue to that problem
did you do a factory reset in recovery?
When do I have to do that factory reset? I have tried to do it after the slimmod flash. Should I do it before flashing the mod? Now I have oclf installed. Do I have to remove it before trying again?
I have done a clean install of JM8. Installed OCLF, rooted, installed RomManager and clockworkmod recovery. Pushed extreme superslim to internal sdcard. Rebooted into recovery. Did a factory reset and wipe of cache. Installed zip from sdcard. ONLY DIFFERENCE IS THAT MY CLOCK SHOWES TWO HOURS TO EARLY. What am I doing wrong?
Install fresh jm8 push docs update.zip to sdcard and apply it. Then install those rest...
Sent from my GT-I9000 using XDA App
At last! After to more resets and flashes I have Extreme Slim on my device and I really likes it. Big applause to doc. Happy HTC:ing.
mickeko said:
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Click to expand...
Click to collapse
I noticed with this you had to change the permissions for these foders using a program such as root explorer. Tick all boxes. Well, that's the only way I got rid of the error.
Also case sensative..
/system is usually mounted a read-only, you have to remount it like this from terminal emulator (rooted of course)
$ su
$ mount -o remount,rw /system
then run
$ mount
you should see /system mounted as 'rw'
When a system app is updated seems to store the old version on the systems folder and the new version on the SD card. Is there a way to merge the new version onto the system? Once merged there is only the system version like it was when the ROM first was installed. I thought I did this once before but don't remember how or what I used to do it.
you would need to remove the app from the system partition and then install the newer one in its place, if it wasnt this way when your phone got corrupt by a bad update and you had to do a factory reset then you would be stuck with the same corrupt apk. so unless you absolutely need dont bother, and if you do the easiest way would probably be through root explore or similar file manager.
Titanium pro does it but not worth the $5 or $6. Used to do it for free just not remember the apps name.
Sent from my HTC Magic using XDA App
you can always copy the apk over using terminal
put it at the root of your sdcard and type
Code:
su
mount /system -o remount,rw
cp /sdcard/updatedapp.apk /system/app/appyouwanttoreplace.apk
mount /system -o remount,ro
Careful though, you don't want to accidentally brick
Make sure the app works and if it's an important app you might want to do it from recovery because it may be running
in recovery you type the following in console (Amon_RA Recovery):
Code:
mount sdcard
mount system
cp /sdcard/updatedapp.apk /system/app/appyouwanttoreplace.apk
Make sure the app update works though, or else you'll get force closes
also may be a good idea to backup the original app with something like:
Code:
cp /system/app/blah.apk /sdcard/blah.apk.backup
Then if anything and you need to restore do this from recovery console:
Code:
cp /sdcard/blah.apk.backup /system/app/blah.apk
yes i really love console
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse