It's under applications settings and must be enabled by the app developer to work.BTW...were do you see the app2sd option on FRF50? i cant find that anywere
I used to see it with previous roms....
Thanks
BGW
It's under applications settings and must be enabled by the app developer to work.BTW...were do you see the app2sd option on FRF50? i cant find that anywere
I used to see it with previous roms....
Thanks
BGW
The application has to support it, and for now, very few do.Codin... i think you answered my problem... I flashed back the original 1.7.0 recovery and i got the same error. So definately the recovery img was installed correctly.
BTW...were do you see the app2sd option on FRF50? i cant find that anywere
I used to see it with previous roms....
Thanks
BGW
It's in the first page.Whenever I install the recovery images the work the first time immediately after, but then resort back to the stock recovery screen. I thought I read something about that but no cannot find the info. Any idea what is going on?
I have followed the pre-requirements as well. Thanks for any help.
Check if there's no /system/etc/install-recovery.sh script if you keep booting back in the stock recovery (exclamation mark with a little Android).
I've been using Amon RA recovery for several months (along with Cyanogen roms) with my Nexus One and everything was working fine. Lately, backups started failing. Giving me that Error: run nandroid in adb line. Sometimes it worked, mostly not though as of late. I've been trying out different ROMs and radios the last few weeks, does that effect how nandroid works?
So, I flashed the latest 1.7.0.1 via fastboot, hoping known issues may have been fixed. First backup I did with this version said it was successful... but after restoring, all my data was missing and it only restored the stripped ROM. That was a bummer (note to self, invest in SMS backup app)! (FYI, I do not use apps2sd or have a partitioned SD, so I do not use backup+ext.) So had to use an older backup to restore from that was good. Tried to backup again, and started getting same errors (run nandroid in adb).
I am not sure how to use adb, so is there another way to troubleshoot this? via terminal? If anyone can point me in the right direction to get nandroid backups working again, let me know.
Thanks!
It's in the first page.
which means delete or rename that file if you have it. Then flash recovery again.
I am somewhat of a n00b, so please excuse the ignorance of this question.
Can this be flashed without currently having root but currently having an unlocked bootloader? I was on Paul's Froyo, went back to 100% bone stock, and now realizing the error of my ways. Unless I have to, I don't want to have to root again - would rather just install the recovery and then use it to reinstall Paul's Froyo.
Thanks in advance!
fastboot devices
fastboot boot recovery recovery-RA-nexus-v1.7.0.1.img
hey i tried flashing by terminal app on cm5.0.7.1 when i try to boot in to recovery mode its stuck on the screen with the unlocked sign but im still able to boot into normal operating mode
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)