I'm trying to flash this recovery, but it does not seem to stick.
I have CM9.1, and i have tried flashing the zip and manually flashing the .img.
Both times don't work.
Any ideas?
bringonblink said:
I'm trying to flash this recovery, but it does not seem to stick.
I have CM9.1, and i have tried flashing the zip and manually flashing the .img.
Both times don't work.
Any ideas?
Click to expand...
Click to collapse
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
polobunny said:
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
Click to expand...
Click to collapse
You can get this working by flashing the recovery from rommanager. Worked for me.
Sent from my Nexus S using xda app-developers app
polobunny said:
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
Click to expand...
Click to collapse
rather than deleting I suggest a renaming of the file to <filename>.<ext>.bak , as if he wants to return to stock , though I doubt that will ever happen
ReVo_007 said:
rather than deleting I suggest a renaming of the file to <filename>.<ext>.bak , as if he wants to return to stock , though I doubt that will ever happen
Click to expand...
Click to collapse
I'm on cm 9.1 and don't have that file
Sent from my Nexus S using Tapatalk 2
Related
Is it possible to make an update.zip file that replaces the build.prop file, or any way to replace the build.prop file without doing a full restore?
I did it using adb commands.
Well I tried using adb shell to swap the file, but when I ran su I got "[1] + Stopped (signal) su"
So I guess I'm going to be forced to do a nadroid restore of my system
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Sent from my GT-I9000 using Tapatalk
Boot loop
Clienterror said:
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Click to expand...
Click to collapse
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
You could just reflash your current ROM and it should replace it.
korockinout13 said:
You could just reflash your current ROM and it should replace it.
Click to expand...
Click to collapse
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
P
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
Actually there is a potential option... can you get into recovery? And does your recovery have a file manager? If so go into mounts and mount /system. Then use the file manager in recovery and you should be able to access build.prop. copy it to your SD and then you should be able to mount your SD to your computer through recovery.
Edit: when you mount /system make sure you mount the SD as well or you won't be able to copy to it while you're in the recovery file manager.
Sent from my SGH-I897 using xda app-developers app
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
remuscat said:
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
Click to expand...
Click to collapse
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
remuscat said:
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
Click to expand...
Click to collapse
BWolf56 said:
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
Click to expand...
Click to collapse
From what I'm reading he doesn't even have a captivate. He's using some Chinese tablet.
Sent from my SGH-I897 using xda app-developers app
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
mrnexus said:
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There is a .sh file that needs to be removed, totally forgot the location of it :/
/etc/install-recovery.sh needs to be deleted or renamed.
It's a "safety" feature in 3.3.1 and above to restore the stock recovery if it doesn't pass a check on boot each time.
This is pointed out in numerous threads...search a little for more details if you need them.
Ok thanks
Sent from my Nexus S using XDA App
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
mrnexus said:
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
distortedloop said:
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
Click to expand...
Click to collapse
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
EDIT: Nevermind, I used root explorer and was able to find "mount r/w" and rename it finally. Thanks.
godzigga said:
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
Click to expand...
Click to collapse
Because those won't allow you to modify system files. Get Root Explorer, like he said, and use that.
AllGamer said:
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
Click to expand...
Click to collapse
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
sarge363 said:
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
True, I used adb, spent like 2 hour trying to get the pc drivers to recognize the nexus. I used the PDAnet drivers eventually.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Are you on a custom ROM like CM or Bionix? They remove the script that rewrites stock recovery.
If you're on stock, what version of it are you on? 2.3.1 and higher have a file called /etc/install-recovery.sh on them, and if that's there it should be reflashing stock on every boot, whether you renamed the image you flashed to recovery or not...
I downloaded everything in the cwm final
I used file manager to overwrite the old files and when I boot into recovery I still get the old recovery and not cwm
There is also nowhere for me to instal from update.zip
I have done this on my evo and it was easy but I'm clearly missing something with my galaxy 4g would someone be so kind as to give step by step instructions?
BGVampire said:
I downloaded everything in the cwm final
I used file manager to overwrite the old files and when I boot into recovery I still get the old recovery and not cwm
There is also nowhere for me to instal from update.zip
I have done this on my evo and it was easy but I'm clearly missing something with my galaxy 4g would someone be so kind as to give step by step instructions?
Click to expand...
Click to collapse
reinstall packages
krylon360 said:
reinstall packages
Click to expand...
Click to collapse
No fair you beat me to it.....duh winning..
Sent from my SGH-T959V using XDA Premium App
krylon360 said:
reinstall packages
Click to expand...
Click to collapse
and yes you must reinstall packages every time you want to re-enter CWM so you must leave the update.zip on you SD card
wrecless said:
and yes you must reinstall packages every time you want to re-enter CWM so you must leave the update.zip on you SD card
Click to expand...
Click to collapse
Thank you for your post. Common knowledge I know but a great reminder!
Sent from my Galaxy s 4g
can't flash CWM recovery
everytime i boot into recovery, i selected reinstall packages, then i get error : signature verification failed!
am I missing something? I have EVO too, it wasn't that difficult to install CWM.
anybody can help me by pointing to things I might have missed?
sarfrazhc said:
everytime i boot into recovery, i selected reinstall packages, then i get error : signature verification failed!
am I missing something? I have EVO too, it wasn't that difficult to install CWM.
anybody can help me by pointing to things I might have missed?
Click to expand...
Click to collapse
recovery.bin probably isn't being overwritten correctly. At first I downloaded the file with Dolphin Browser and had the same problems. Try downloading the file with firefox and then try pushing it to /system/bin again.
probably recovery file is not being copied in system/bin folder. i can see it has only read permission for group and write permission. i tried rom manager permission fix, that didn't change permission of recovery. i tried changing from terminal using chmod +w & chmod 755. but that didn't help change the permission on recovery file.
sarfrazhc said:
probably recovery file is not being copied in system/bin folder. i can see it has only read permission for group and write permission. i tried rom manager permission fix, that didn't change permission of recovery. i tried changing from terminal using chmod +w & chmod 755. but that didn't help change the permission on recovery file.
Click to expand...
Click to collapse
Rom Manager isn't working for the Galaxy S 4G yet.
What application are you using to copy recovery to /system/bin?
typically i use ES explorer but i tried File Expert too.
one typo on my prev post: i don't have write permission on recovery, only got read permission.
sarfrazhc said:
typically i use ES explorer but i tried File Expert too.
one typo on my prev post: i don't have write permission on recovery, only got read permission.
Click to expand...
Click to collapse
ES won't work. File Expert should work. Just make sure you have R/W permissions. Don't do anything with Rom Manager. That won't help.
yea it should work as they say but it does not. I tried changing permission using File expert,it click OK and then i check file permission on recovery right away, the write permission is not checked. even chmod 755 failed to change the write permission!
sarfrazhc said:
yea it should work as they say but it does not. I tried changing permission using File expert,it click OK and then i check file permission on recovery right away, the write permission is not checked. even chmod 755 failed to change the write permission!
Click to expand...
Click to collapse
I don't think you have any problems with R/W. I just don't think the recovery file was overwritten. Look in /system/bin in File Expert. Do you see recovery and recovery.bin? Or just recovery?
/system/bin/recovery file exists and i have been trying to change its permission.
sarfrazhc said:
/system/bin/recovery file exists and i have been trying to change its permission.
Click to expand...
Click to collapse
You don't need to change the permission of recovery. Copy the recovery file and navigate to /system/bin in file expert. When you get there you want to hit menu then more then mount. It will give you two options. Pick mount as read write. Then paste the recovery file.
Read through this thread again. It should help.
http://forum.xda-developers.com/showthread.php?t=1099374
mounted with read/write and now i could boot into recovery.
Thanks a lot for taking time to answer my questions. First backup is in progress...
sarfrazhc said:
mounted with read/write and now i could boot into recovery.
Thanks a lot for taking time to answer my questions. First backup is in progress...
Click to expand...
Click to collapse
No problem man.
Anyone else have this issue with their phone?
No I have not had an issue so far
Charged up post!
I just wiped and flashed again, no luck... anyone got any ideas? i tried to find gapps... but didnt find any.
Varelse said:
I just wiped and flashed again, no luck... anyone got any ideas? i tried to find gapps... but didnt find any.
Click to expand...
Click to collapse
Use a file explorer (e.g. Root Explorer or ES). For some incomprehensible reason danalo considers Google Talk bloatware and doesn't keep it installed in his rom. It should be somewhere in the system/apps folder as a .bak file. Just rename it back to the .apk and you should be good to go.
Yep just goto /system/app with Root Explorer (or similar) and rename 'Talk.apk.bak' to 'Talk.apk'. Reboot and it should appear.
I've pulled it out of system and installed it as a user app so I don't have to reinstall every release.
Sent from my SCH-I510 using Tapatalk
d-loko said:
Yep just goto /system/app with Root Explorer (or similar) and rename 'Talk.apk.bak' to 'Talk.apk'. Reboot and it should appear.
Click to expand...
Click to collapse
root explorer will not allow me to rename it.
did you give ESFile Ex root permission in the settings menu?
ducati966 said:
root explorer will not allow me to rename it.
Click to expand...
Click to collapse
Make sure u click that "mount R/W" button in the folder you're in. If you can't you're not rooted.
Sent from my SCH-I510 using XDA App
I've flashed CWM Recovery three times, and I cannot for the life of me get it to stick. My phone constantly resorts to the stock recovery, so, I'm rooted and have SuperUser working fine, but no custom recovery. I'm on a Mac by the way.
Just delete or rename /etc/install-recovery.sh
suksit said:
Just delete or rename /etc/install-recovery.sh
Click to expand...
Click to collapse
Where do i find that?
luv2vexx said:
Where do i find that?
Click to expand...
Click to collapse
It's located in your phone. You can access it by running adb shell command. Or use Root Explorer.