I've been trying to figure out how to fix my phone and through using the adb logcat 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. Any ideas?
Metatronx said:
I've been trying to figure out how to fix my phone and through using the adb logcat 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. Any ideas?
Click to expand...
Click to collapse
try
Code:
adb remount
What would the syntax be for remounting the core.jar and is it possible to do in terminal? Thank you especially for the quick response\!
From your other thread..
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.
May have been asked before, but I tried searching and didnt find much luck.
I think my SDCard slot finally gave up, it just will not be read (tried two different 8gb cards that both worked fine on the computer). On Cyan 4.2.9.1.
Anyway, is there a way to flash the phone without the sdcard? I was trying to think how that would be possible, but I think its not right?
Just looking for a quick def. answer so I can know if i need to go phone hunting . Or do something different , which would be much better.
Appreciate it .
Happy holidays btw
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
pjcforpres said:
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
Click to expand...
Click to collapse
I didnt really think of adb, yeah that might work. Maybe someone knows them?
Maybe
adb shell recovery flash location/zip ?
Tried the canned air, didnt change. Good thinking though.
And lastly, I did debate which place, but I was thinking I saw a utility here or I am looking for the command lines and thought maybe alittle more technical than a general question? It will fall shortly anyway (hopefully after the commands ) or get moved/deleted.
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
persiansown said:
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
Click to expand...
Click to collapse
Thats a pain, and I dont think there are many of those out there...
No adb commands? Ive been searching but it seems scarce
EDIT:
Ok I tried my idea anyway,
adb shell recovery flash update.zip
And it just hangs (no errors though)...probably missing something?
Are you able to warranty your phone for the bad SDCard Reader??
If so, I started this thread and came up with an answer, but it will bring you back to fully stock cupcake
http://forum.xda-developers.com/showthread.php?t=560254
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
bildo said:
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
Click to expand...
Click to collapse
That is the better answer, thanks for continuing. If you just left that first sentence I would have said re-read my problem, I cannot use my sdcard (the normal way rom is flashed).
As for the fastboot, I will look into that. I appreciate it, thanks.
Im getting
No android-info.txt
No android-product.txt
In the package when i try to do this command while in fastboot:
fastboot update update.zip
I found android-info in the update file from htc, but I cannot resign right now. Im also guessing it will still yell about the android-product.txt anyway, so any ideas where to get that file?
If all you're trying to do is flash a .img (system.img, userdata.img, recovery.img) and you have a developer, or hardspl, you can flash using fastboot.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
haykuro said:
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
Click to expand...
Click to collapse
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
jackslim said:
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
Click to expand...
Click to collapse
Well you're cache partition should have 30720K (about 30MB)
the last cyanogen rom was 37 MB =[
my other recommendation for you is to push the updates to your sdcard through your phone. (just re-read your post and noticed the SD card is functional in your phone)
Code:
adb push update.zip /sdcard/update.zip
then just proceed as usual.
@theslam08
Your signature say's your using the "Danger SPL" Judging by that you could reflash your spl from fastboot to the hard spl
Code:
fastboot flash hboot spl.bin
Then use the method described above by Haykuro pushing updates to /cache with adb
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
theslam08 said:
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
Click to expand...
Click to collapse
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
haykuro said:
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
Click to expand...
Click to collapse
Excellent, that seemed to be the trick (after going back to HSPL because yeah, I didnt have enough room with haykuro's). Though some bugs with that.
I got it to copy once after making that partition mount, and I was able to see the update file. I updated, and everything went well (even though I wondered how in the middle of the update it says formatting cache, yet it still worked).
Now, I went to put on a theme file and it says out of room. I hit 'update from sdcard' in recovery and it says E: No zip files found or something like that, just no files. So if it gets 'wiped' how is there no space? Is there a manual format I should do?
And I dont think this has happened to anyone yet, so thanks for going through this , im sure others down the road will find it helpful.
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
akapoor said:
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
Click to expand...
Click to collapse
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
theslam08 said:
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
Click to expand...
Click to collapse
Ah, okay - now it makes sense. I didn't understand the purpose at first.
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.
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