Related
I'm enjoying the new roms that are coming out, each one is better than the last, and I've tried just about every one of them. That being said I am still having a few problems with the g1. When I boot using (home+power) I see this at the top of the screen "E:can't open /cache/recovery/command" I've tried updating to cyanogens newest recovery console and it didn't change anything that I could tell, I can't even alt+X to get a prompt, this text at the top could be the reason why. I'm sure I have messed something up but honestly after 2 days of searching I am still no better off than I was before. Also, I cannot get my sd card to work properly. I've tried every way on earth to format the sd card to attempt to get 3 partitions. When I do this, I either cannot install update.zip to the fat32 part, due to the recovery screen not seeing anything on the card ("update.zip not found") or I end up boot-looping after the HERO screen. I'd like someone to help me start this over again. I've used all the different roms out there, I just want to get my SD card properly formatted so my HERO rom will use the swapfile and ext2/3 the right way. I'm not sure what I'm doing wrong, I've followed the "step by step" guides in this forum and to my knowledge I've done everything right a few times over. I used paragon to attempt to set up the sd card, and I was using the correct radio/spl for each rom I attempted to use. It also might help if I mentioned after re-installing the Cyanogen's recovery img, I saw no change in the (home+power) screen. If you need more details from me PLEASE don't hesitate to ask me, I just want to get my phone set up the right way so I can install all my apps and not have to stay in the habit of flashing my phone 5+/- times per day which is cool but getting old fast! So please help >.<
You need to reformat your SD card. That message means nothing. I had that before.
I have reformat the card over ten times now. I've tried using the paragon method, did it exactly as the guide said, I got boot loop and had to reformat the card back to fat 32 so i could even boot to hero. I still cannot use alt+x to access anything from the recovery screen either.
Do you still have root?
do you have access to ADB?
Yes I still have root, and I am currently running Soulife Roger's 2.8 if that makes a difference. I'm not sure what ADB means is that something I run in terminal?
check your private email
Recovery Trouble
darkphoenix2012 said:
I have reformat the card over ten times now. I've tried using the paragon method, did it exactly as the guide said, I got boot loop and had to reformat the card back to fat 32 so i could even boot to hero. I still cannot use alt+x to access anything from the recovery screen either.
Click to expand...
Click to collapse
try these steps from my root walkthrough:
3. Download the recover_testkeys.img
http://files.lucidrem.us/_fd.php?file=jf/ROOT/recovery_testkeys.img
4. Copy recovery_testkeys.img to SD FAT32
14. Type cat /sdcard/recovery_testkeys.img > /data/local/recovery.img[enter]
15. Type cat /sdcard/recovery_testkeys.img > /system/recovery.img[enter]
16. Type flash_image recovery /system/recovery.img[enter]
once you do this .. try to reboot .. let me know if you're good to go
LucidREM said:
try these steps from my root walkthrough:
3. Download the recover_testkeys.img
http://files.lucidrem.us/_fd.php?file=jf/ROOT/recovery_testkeys.img
4. Copy recovery_testkeys.img to SD FAT32
14. Type cat /sdcard/recovery_testkeys.img > /data/local/recovery.img[enter]
15. Type cat /sdcard/recovery_testkeys.img > /system/recovery.img[enter]
16. Type flash_image recovery /system/recovery.img[enter]
once you do this .. try to reboot .. let me know if you're good to go
Click to expand...
Click to collapse
I tried the "cat /sdcard/recovery_testkeys.img > /system/recovery.img" and I got this message " cannot create /system/recovery.img : read only file system "
You must type "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system" no quotes. Before the cat commands.
Tried using that command first and using those 3 commands again. Nothing happened other than when I load into recovery menu, I see Android recovery menu, test keys, then I get the same E:can't open /cache/recovery/command error as I was before. I'm still having SD card issues too. I can't seem to get this to work right, no matter how many times i read a "how to do xxxx"
darkphoenix2012 said:
I'm enjoying the new roms that are coming out, each one is better than the last, and I've tried just about every one of them. That being said I am still having a few problems with the g1. When I boot using (home+power) I see this at the top of the screen "E:can't open /cache/recovery/command" I've tried updating to cyanogens newest recovery console and it didn't change anything that I could tell, I can't even alt+X to get a prompt, this text at the top could be the reason why. I'm sure I have messed something up but honestly after 2 days of searching I am still no better off than I was before. Also, I cannot get my sd card to work properly. I've tried every way on earth to format the sd card to attempt to get 3 partitions. When I do this, I either cannot install update.zip to the fat32 part, due to the recovery screen not seeing anything on the card ("update.zip not found") or I end up boot-looping after the HERO screen. I'd like someone to help me start this over again. I've used all the different roms out there, I just want to get my SD card properly formatted so my HERO rom will use the swapfile and ext2/3 the right way. I'm not sure what I'm doing wrong, I've followed the "step by step" guides in this forum and to my knowledge I've done everything right a few times over. I used paragon to attempt to set up the sd card, and I was using the correct radio/spl for each rom I attempted to use. It also might help if I mentioned after re-installing the Cyanogen's recovery img, I saw no change in the (home+power) screen. If you need more details from me PLEASE don't hesitate to ask me, I just want to get my phone set up the right way so I can install all my apps and not have to stay in the habit of flashing my phone 5+/- times per day which is cool but getting old fast! So please help >.<
Click to expand...
Click to collapse
The "E:can't open..." is referring to the Nandroid backup- I had the same problem too and everyone thought I was crazy. This may be preventing you from updating to the cyanogen recovery.
When I rooted my phone I went directly to JF1.5 which does not have nandroid in it. To solve it, I flashed the previous JF (1.43?) and that went away.
Give that a try and then flash the cyanogen recovery. Good luck.
I had the the same problem mate! here is what I did to fix it....
1....format card to fat 32 (make sure you dont have any other partitions on your card!)
2....go here and download the "update.zip" version http://forum.xda-developers.com/showthread.php?t=523558
3....rename and flash the file in the normal way!
4....enjoy!
p.s. make sure you sdcard is freshly formatted and as only a single fat32 partition.
attempted that last suggestion twice before I posted here that it unfortunately didn't solve the issue I still get the same E:can't open /cache/recovery/command error i've been getting and cannot install cyanogen's recovery image. Is there anything else I could try? Surely there is a reason for all this trouble I've been having with the SD card partitioning working with the ROM, and being unable to use cyanogen's recov.
darkphoenix2012 said:
Tried using that command first and using those 3 commands again. Nothing happened other than when I load into recovery menu, I see Android recovery menu, test keys, then I get the same E:can't open /cache/recovery/command error as I was before. I'm still having SD card issues too. I can't seem to get this to work right, no matter how many times i read a "how to do xxxx"
Click to expand...
Click to collapse
What happens when you type this?
alritewhadeva said:
You must type "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system" no quotes. Before the cat commands.
Click to expand...
Click to collapse
Does it go back to the command prompt or error?
I'm pretty sure that the error message I've been getting is the only reason I'm having these issues. IF I could use cyanogen's recovery, I could follow the exact guidelines here http://forum.xda-developers.com/showthread.php?t=533731
Since I cannot do the " How to install custom ROM (With full wipe)" part of the guide, I think that is where my issues with SD partitions working properly within the ROM.
Again thank you for the help, I don't have much black hair left, the gray is running wild
temporizer said:
What happens when you type this?
Does it go back to the command prompt or error?
Click to expand...
Click to collapse
^ It went back to the command prompt without an error, and this time after typing all three lines of code, and rebooting the phone to check the recovery menu, the error was still there as if I had done nothing.
how were you able to update to cyanogen's recovery if you can't get into recovery in the first place? or did i read that wrong?
When I flash the Cyanogen's recovery, its as if it did nothing, I'm assuming from what I read it would add more functions to the screen or it would be obvious that it did something. I thought that if that had flashed correctly I would be able to use alt+X to open a prompt. I could be completely misunderstanding what it is supposed to do, but I don't know I thought I was more sure of what I read
I thought my error message at the top of the screen (after home+power) was what was preventing me from installing the recovery.
Ok I tried flashing an older version of the JF1.42 and my recovery error has been solved. Thank you for all your help!! Would I need to flash to something else If I wanted to run the latest and greatest hero rom? Either way what would you suggest I do next?
I had to reset my phone today, since for some odd reason, I switched it off and back on, and it wouldnt get back the flashing android screen (havent even made any changes to it recently, God knows why it decided to do this).
Anyway, I figured, format the phone, reflash JF 1.5, and then move apply apps2sd (I already have my apps on my SD card, just have to link them back to the phone so it can see them), and the small customisations I can do later, I would get my phone back to functioning level.
I am using these instruction from SDK on my computer:
1. Check if your phone is recognised.
adb devices
2. Mount the phone into ADB.
adb remount
3. Bring up the shell.
adb shell
4. Check if /system/sd is visible.
df
5. Skip this step if you already have your apps on SD.
cp -a /data/app /system/sd
6. Skip this step if you already have your app-private on SD.
cp -a /data/app-private /system/sd
7. Remove the current apps folder on device.
rm -r /data/app
8. Remove the current app-private folder on device.
rm -r /data/app-private
9. Link the app folder on sd to the one on device.
ln -s /system/sd/app /data/app
10. Link the app-private folder on sd to the one on device.
ln -s /system/sd/app-private /data/app-private
11. Finally Reboot.
reboot
Well, I can flash the phone fine, but when I am trying to follow the instructions for relinking the apps from SD to the phone (stage 4), it doesnt show /system/sd, instead it shows /sdcard.
Does this mean I should change the following steps to say 'sdcard' instead of '/system/sd'? I have tried this with no luck, shows me the android screen indefinitely.
I have an ext2 partition on the phone on which I have my apps, I have done this whole process before many times, but not for a while so I am missing something important.
And I am skipping steps 5 and 6, since I have already got all my apps on my SD card.
Any help would be must appreciated, this is wasting quite a bit of my time.
PS: the only thing I have changed since I last did this, was I flashed the phone with a google ion build, while it had JF 1.5 on it. What I did notice after that was the phone ran a lot slower. That is the only change I can think of which separates this process working perfectly previously, and not at all now.
Um reformat your entire card to fat32. And then use cyanogen's recovery 1.31. to split your sd into 2 partitions. Msg me on gtalk or by email and I'll help you out
Many thanks for the reply.
Hmm I would have thought a reformat of the SD card would be last resort, is there no way to sort this out without going down that route?
Don't think there's another way, You could try switching ROMS see if that fixes it...
Might not need to reformat it all just yet.. Been awhile since I used JF, but I don't think it automatically mounts /system/sd
I think you might need the init.rc from this post -- http://forum.xda-developers.com/showthread.php?t=512743
Personally - and I try not to be preach about it, but I think CM users can't help that -- I'd suggest trying CyanogenMod since you're reflashing anyway. It isn't quite as stock as JF, but it is rock solid and fast, and it should pickup your existing A2SD partition automatically.
Agreed with Saiboogu. Try out Cyanogen's ROM you will NOT regret it
Ok, I am up for that.
BTW, when I format my phone (Alt+W I believe), and start it up again, its firmware is still upgraded.
If I reflash with a ROM, will that cause any problems or slowing, will it be overwriting anything? I guess I dont quite understand what the formatting of the phone is doing, and what it is leaving behind, and then what reflashing with a ROM is doing on top of that.
Also,m when you say Cyanogen's rom will do apps2sd automatically..how? Will it recognise the apps currently on the ext2 partition of my SD card? It wont delete them will it?
It will not delete them. It uses bind mounts to automatically do the apps to sd . Just wipe and flash
Ok, giving it a try now.
Hmm something I should have asked beforehand, my partition is ext2, do I need to change that to ext3 before I flash the cyanogen ROM?
Like alritewhadeva said - it just recognizes your existing apps.
A wipe clears out all the custom data.. Your settings, application data in the /data partition, your google account data that is synced to the phone. It doesn't touch the actual OS, which is why your ROM is still installed after a wipe.
With that said.. Cyanogen builds can be "broken" if you wipe after a flash. So always either just flash, or wipe *then* flash.
PERFECT! its worked like a charm! no hassle at all!
Great! You won't regret it.
one problem I have noticed, my camera keeps force closing (wont even start up without force closing straight away).
Any solution to this? Have tried going into the camera app in applications manager and clearing defaults, but no defaults were set.
That one sounds familiar, but I can't find an actual reference to it right now. Probably want to search the Cyanogen thread for mentions: http://forum.xda-developers.com/showthread.php?t=518851
Also keep an eye out for updates - Cyanogen is prolific, and will probably get one released sometime this evening. It may fix the issue.
That one sounds familiar, but I can't find an actual reference to it right now. Probably want to search the Cyanogen thread for mentions: http://forum.xda-developers.com/showthread.php?t=518851
Also keep an eye out for updates - Cyanogen is prolific, and will probably get one released sometime this evening. It may fix the issue.
Edit: Ah, here it is - http://forum.xda-developers.com/showthread.php?t=536687
He says he had to wipe his SD card, repartition and everything. Not sure if that is your issue or not.
Ah I posted a fix for that just take the camera.apk from an older cyanogen build (3.6.5) and push it over.
so put the camera.apk on sdcard
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
cp Camera.apk /system/app
reboot
I am afraid due to my pathetic ignorance of how android works, I cant decipher what you said.
How do I get the camera apk? And once I acquire it, and put it on my SD card (I am assuming not in any folder, just on the main directory of the card), I use the terminal emulator to type in those commands?
well thats rather funny, just switched my phone on and off and the camera is working now.
raukodur said:
well thats rather funny, just switched my phone on and off and the camera is working now.
Click to expand...
Click to collapse
well then awesome
Great that you got it working. For future reference (because these things do happen occasionally), alritewhadeva was suggesting that you download an older version of CM (link on his build thread), unzip it and find the camera.apk file. Then place that file on your sd card, and follow his directions in Terminal Emulator on the phone.
so i just got a new TOPRAM 16gb sd card and yes i know cheap cheap. but whatever...anyways it works on my g1 and the g1 can read the files on it and i can mount it so my comp can see it but when i run the command
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
it just says something like invalid something and fails to mount. im not sure what the problem is considering the memory card works on my phone as well as computer and can be mounted threw android ui instead of code so wtf?
plus its giving me trouble with certain adb commands
That command not working has nothing to do with your new sdcard.
Are you rooted? If so your gonna need to give people more info (like the error message). If not then that's your problem.
im pretty sure it does because ive used it manytimes before when i needed to considering ive been playing with different roms for awhile now and yes, i am rooted and all that. usually that command always works for me, whether it be thru terminal, recovery, or adb. and that only changed once i put this new card in. its no big deal, cuz it works and everything. but I just dont understand why i cant mount it for rw
I have partitioned sd card and I have the hello im apk on the sd and I want it on my phone because it wont let me change my buddy pic it says please make sure your sd card is in the phone so Im going to try to put it back on internal storage to see if it works. So how do I move it? I parted with apps2sd but the app wont work with cyan 4.0.1 so how Do I move it?
Apps2sd is really an all or nothing proposition. You can't have one app on internal memory and the rest on the SD card.
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
OTOH, if an app is complaining about the sd card it's probably talking about the fat32 partition that it wants to store images on. Is your fat32 close to being full or something?
on a side note im on cyan 4.0.1 I was at 3.6.8.1 when I used the apps2d app and now when I try to open it it says Oops! Looks like you need to go through the tutorial to set up apps to sd. Please go to blah blah blah why is it doing this
what do I have to do to get this app running gain I already haves apps going to sd.
The top part of Cyanogen's stable thread says not to use any other method of apps to sd because his has a script built in.
So. Stop fiddling with whatever apps2sd app you have.
go to terminal and type:
Code:
su
ls /dev/block/mm*
Tell me what you see. (And please take a moment to make your posts a little more readable, I'm having a hard time deciphering what you're asking/saying. )
what Am I suppost to do? I dont want to do it without knowing
open the application 'terminal emulator' -- this is like the dos 'command prompt' in windows or a term window in Linux
type 'su' and press enter -- this Switches User to root, or the administrator of the machine (your phone)
type 'ls /dev/block/mm*' -- 'ls' is 'list' directories. /dev is where all the devices are, block is hard-drive like devices (your internal memory and the sd card) and mm* is every block device that starts with 'mm....' which should be mmcblk0 (the sdcard), mmcblk0p1 (the fat32 partition) and mmcblk0p2 (the ext partition)
If the last exists, the cyanogen automatic apps2sd will have already moved all your applications there. If only one exists, it means you either formatted the whole SD card to ext2 for apps2sd (and left nothing fat32) or formatted none of it and your apps are already on your phone.
if your 'ls /dev/block/mm*' says that you have a mmcblk0p2, than run "ls /system/sd/app/*" and you should see a bunch of files ending in .apk. If so, then you have to undo apps2sd to get the Hello IM app back to internal memory.
Report back on the outputs of the above and further instructions will be provided.
Ok Iv done all that so how do I undo them and if so how will I get them back?
Tell me what all that said back when you typed it in. THEN I can tell you what to do.
I see all my apk files now what? I want to move that 1 app onto the phone memory and every other apk on the sd. Im ready for the next step.
I see a bunch of files ending in .apk now what?
Hmm. I just looked up 'Hello IM!' and see that it's a paid app.
So, we can move just paid apps to the internal memory and leave the free ones on the sd card.
if yes run the following in terminal emulator:
su
rm /data/app-private
mkdir /data/app-private
cp /system/sd/app-private/* /data/app-private
Copying the apps may not work and you may have to uninstall/reinstall, but when you install them they'll be on the internal memory.
Oh, but cyanogenmod will put them back on the sd card when you reboot, so if having the app on the internal memory does fix the problem, you'll have to edit the a2sd script.
The problem isn't that your apps are on the sdcard. The app itself doesn't know. Your partions may be out of whack or the app itself may just need to be reinstalled.
When your apps are on the sdcard they are on a different partition then what every app uses your sdcard for. Not sure if I wrote that where you can comprehend it or not...
wat do u mean out of wack
PsychoI3oy said:
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
Click to expand...
Click to collapse
I've done some searching, and haven't found any way to do this that has worked for me. Could you please pass some of this info along?
Thanks.
HowTo - un-apps2sd (on CyanogenMod)
Ok, this is based on the assumption that you are running a Cyanogen rom. I'm sure it could be adopted for use on another one, but Cyanogen 4.0.x is what I'm running. You'll probably have to re-install any paid apps (app-private) but normal apps should run fine after this.
Instructions for use with adb:
Code:
adb remount
adb push a2sd.txt /system/bin/a2sd
adb shell
# rm /data/app
# mkdir /data/app
# cp /system/sd/app/* /data/app/
# rm /data/app-private
# mkdir /data/app-private
# cp -r /system/sd/app-private/* /data/app-private
# reboot
for terminal emulator, assuming the new a2sd.txt is on your sdcard:
Code:
mount -o rw,remount /system
mount -o rw,remount /data
cp /sdcard/a2sd.txt /system/bin/a2sd
and then continue the adb instructions from after 'adb shell'
after reboot you can confirm that it worked by running:
ls -l /system
from terminal emulator (no need to remount/su) and you should see 'app' and 'app-private' as directories (and not app -> /system/sd/app).
If you're running some other a2sd method, you'll have to edit/remove the script that's doing the linking, then delete the symlinks and copy back (should be similar to above).
The modified a2sd.txt attached just takes away the apps-to-sd part. Dalvik-cache is still run from /system/sd/ as are whatever other magical juicy bits he's got in there.
If you upgrade to another Cyanogen rom, the new version of a2sd will get pushed and everything will be moved back. The only way to get rid of it permanently would be to delete the ext2/3/4 partition on your sd card.
If you decide you want apps2sd again and don't want to upgrade, just put the a2sd.orig.txt back as /system/bin/a2sd and reboot, it'll automagically move everything back to the /system/sd/app on your ext partition.
I just did the un-apps2sd then put the original back and everything's fine (and was fine with un-apps2sd).
That should cover most things....
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
daveerickson said:
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
Click to expand...
Click to collapse
Trailing slashes are optional in most shells, including this one.
Glad it worked for you.
these doesn't seem to be working for 4.2.1, no a2sd file exists in /system/bin, maybe he moved it somewhere else, i'm trying to find it but i'm not being lucky.
any help?
No, he broke up the bits that were in a2sd and spread them across several files in /system/etc/init.d/
http://wiki.cyanogenmod.com/index.php/Removing_Apps2SD has the instructions now.
This used to only happen from time to time, now it happens about 90% of the time.
Using RA-Recovery 1.6.2, I do a nandroid +ext backup, it will get half way through, and drop the error "Error, run nandroid-mobile.sh from console".
I can do this no problem, it's just very inconvenient. I'd like to know why the command doesn't work properly. I have PLENTY of space on my sd card, because running it from console works perfectly.
It's just a pain because there are no back lights on the keyboard, so unless I'm out in the daylight, it's hard to see the keyboard and use console.
Any ideas?
tehseano said:
This used to only happen from time to time, now it happens about 90% of the time.
Using RA-Recovery 1.6.2, I do a nandroid +ext backup, it will get half way through, and drop the error "Error, run nandroid-mobile.sh from console".
I can do this no problem, it's just very inconvenient. I'd like to know why the command doesn't work properly. I have PLENTY of space on my sd card, because running it from console works perfectly.
It's just a pain because there are no back lights on the keyboard, so unless I'm out in the daylight, it's hard to see the keyboard and use console.
Any ideas?
Click to expand...
Click to collapse
Just a theory on my part, but I think that it has something to do with the fact that there isn't a /system/sd directory anymore for CM5 builds, thus no ext partition to backup according to nandroid. A workaround is simple. Just create a /system/sd directory.
adb remount
adb shell mkdir /system/sd
then your nandroid + ext backup should work as long as you have a sufficient battery charge.
Thanks for the reply mate, I had figured that too, but then when it worked correctly via console, I dismissed it. I guess since I'm not the only one to think it, I'll give it a shot, see what happens.