Hello,
I am having a minor problem, I am a newbie to rooting and things a like.
I've been trying to setup cwm recovery and I go to stock recovery and I select reinstall packages,
it will work for a second and then it will say "Whole signature failure: Installation aborted"
And then it will automattically reboot. Any help will be appreciated!
ImShiney said:
Hello,
I am having a minor problem, I am a newbie to rooting and things a like.
I've been trying to setup cwm recovery and I go to stock recovery and I select reinstall packages,
it will work for a second and then it will say "Whole signature failure: Installation aborted"
And then it will automattically reboot. Any help will be appreciated!
Click to expand...
Click to collapse
Two things, you must:
1. Have modded recovery binary
and
2. Make sure you are using the correct CWM 3.0.2.8
EDIT:
http://www.mediafire.com/?mex4qna8rr3urck Modded Recovery
http://www.mediafire.com/?jvtpra5ashdmctn CWM
Make sure you change CWMx.x.x.x to update.zip and the modded recovery must be placed in /system/bin
Backup current recovery file and make sure you overwrite with this, using a file explorer that allows you to get to root access.
shadowscott said:
Two things, you must:
Backup current recovery file and make sure you overwrite with this, using a file explorer that allows you to get to root access.
Click to expand...
Click to collapse
One thing to remember about this is that you MUST mount the internal storage as read/write. Ghost Commander (free on Google Play) lets you do this. You have to enable root explorer in its menus, and then go to where your stock recovery is and mount the volume as read/write. Then, paste the modified recovery in the directory and overwrite the stock one. Now, you should be able to get into CWM.
First things first: did you successfully root your phone?
ged92781 said:
One thing to remember about this is that you MUST mount the internal storage as read/write. Ghost Commander (free on Google Play) lets you do this. You have to enable root explorer in its menus, and then go to where your stock recovery is and mount the volume as read/write. Then, paste the modified recovery in the directory and overwrite the stock one. Now, you should be able to get into CWM.
Click to expand...
Click to collapse
Sir, thank you so much! It works now and I can finally flash mods thank you.
Just make sure you wipe everything an go to advance menu an wipe all that
an make sure you nandroid right after helps out a lot
Sent from my SGH-T839 using xda app-developers app
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
OK, so after fighting with my Nexus S 4G for three hours trying to get it rooted (it took 15 - 30 minutes for my Hero and Evo Shift) I finally established root and wanted to install ClockworkMod. Of course I've come to learn that it's just not that simple, and I have to rename the default recovery, which require r/w permissions, and just more hoops to jump through.
Long story short, I rooted, set r/w access and renamed install-recovery.sh and used ROM Manager to install ClockworkMod. Reboot to recovery, and all seems well. Except that the next time I reboot, I'm back to the default recovery, my renamed install-recovery.sh.old is no where to be found and low and behold, install-recovery.sh is back.
Considering how easy this was with HTC devices... I'm starting to get a little pissed off.
Anyone have any idea why I can't maintain ClockworkMod?
Why don't you just use fastboot and flash the recovery image? It will be permanent if you do that... It takes about ten seconds.
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
If you're sure you did the renaming properly and after that the file got restored back, I'd suggest you trying to trick the system by making a backup of the original install-recovery.sh and then instead of renaming it, just delete everything in that file so you still have the file named install-recovery.sh which will do noting to the recovery partition
radadev said:
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
OK... tried this. No go.
Reboot still shows the default and not clockwork.
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
jungbum said:
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
Click to expand...
Click to collapse
This is the first thing I tried. No dice.
Sophos1 said:
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
Click to expand...
Click to collapse
I don't see an "install-recovery.bak"
Stupid question, is your bootloader still unlocked?
wild1z said:
Stupid question, is your bootloader still unlocked?
Click to expand...
Click to collapse
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Shadodragon said:
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Click to expand...
Click to collapse
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
wild1z said:
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
Click to expand...
Click to collapse
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Shadodragon said:
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Click to expand...
Click to collapse
I can only tell you what I would do. I would try to get it back to stock and lock it up to start over.
Maybe JasonMahoney, AOSP and Lilduce will come on over and share this fun with us.
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.
Lost root after installing 9ZGgDXDi.zip.
This of course installed JB 4.1.1 but then when I go to recovery after entering fast boot menu I see a supine green robot with a red triangle with an exclamation point spilling out of its guts. (truly a horrible sight)
It also installed recovery-from-boot.p in System folder.
I know the solution is to rename recovery-from-boot.p file to recovery-from-boot.p.bak or renaming to something else or deleting, however since I lost root I don't see how I can rename or delete this file.
When I use root explorer I cannot mount r/w so cannot rename the file
Using ES File Explorer I rename the file but get the message that rename failed.
Connecting the phone via usb and turning on usb storage I can only access files from sd card and so cannot get to system folder in the parent directory.
Please can someone help destroy or rename the .p file.
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
chronophase1 said:
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Click to expand...
Click to collapse
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Kitch16 said:
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
Click to expand...
Click to collapse
Tried that site, but the links to software are broken
edited to add:
oops, yes the links to software work, just didn't see the correct download for all the advertizements.
Thanks for your help but I have solved my problem by adb flash of cwr
koyanishi said:
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Click to expand...
Click to collapse
You get this from the fastboot screen?
chronophase1 said:
You get this from the fastboot screen?
Click to expand...
Click to collapse
I think its after fastboot screen - that is when I go to apply zip from sd card
However I have since solved the problem by using adb to install cwr again so I am now back to root
thanks to both of you for trying to help
I remember downloading this and saving it when I still had the SK4G. It works great, just replace the update.zip on the / of your sdcard to use. Click the THANKS button if you D/L'ed/Used/Referred To/So on...
Just because of the nature of this mod, I cannot and will not be held responsible for any mishaps to your devices and or any of its accessories (SDCards) that in this weird world of ours may just happen. This should not discourage you to use it, just saying.. You break it, You fix/replace it.
LINK: CLICK MEEEEEE
I'll still help you with your device (tech help mostly), if you need anything PM me. (probably only/fastest response)
dude your a life saver im on att and a flashaholic unfourtunatly while me and some pantech flex users are hard at work getting recovery after we successfully rooted our device about 5 days ago i havent been able to flash anything because the new cwm for the sk4g had been taken down everywhere and the koush one is so buggy and wont let me backup or flash i been looking everywhere for this
this doesnt work for me. Invalid signature. How do you install CWM when you have none after stock odin?
rpmccormick said:
this doesnt work for me. Invalid signature. How do you install CWM when you have none after stock odin?
Click to expand...
Click to collapse
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?
dudanko said:
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?
Click to expand...
Click to collapse
I may be wrong, but I think its due to not replacing the stock binary file with the modded binary file. I'm trying to find it online but krylon's site no longer hosts the file...
dudanko said:
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?
Click to expand...
Click to collapse
Make sure you guys are extracting the the zip and putting the extracted recovery into the system/bin, not the whole zip.
You can also use the search and find where I reposted sduvicks fakeflash utility. It will install CWM for you.
In V2 eXDialer have force closes
shadowscott said:
I may be wrong, but I think its due to not replacing the stock binary file with the modded binary file. I'm trying to find it online but krylon's site no longer hosts the file...
Click to expand...
Click to collapse
His page on Android Spin? I used to download it from there .. don't know if its stopped working now :/
I tried sduvick's script but it wasn't working for me so I had to push the files myself.
rpmccormick said:
this doesnt work for me. Invalid signature. How do you install CWM when you have none after stock odin?
Click to expand...
Click to collapse
dudanko said:
I have the same problem. My sidekick is just rooted. I wanted to instal your cwm, but it writes Invalid signature. How can I install it?
Click to expand...
Click to collapse
replace the update.zip on the /root of the SD. No Odin required. Rename to update.zip, and place it straight on your SD.
That did not work until after I rooted it using RageAgainstTheCage
Re-upped by me here:
http://www.mediafire.com/?hn5ikyt6xpn8d9x
After doing that, then it allows the update.zip to work without failing signature check.
EDIT: Then I also used SuperOneClick to shell-root.
-__-
Ok guys the actual problem here is that there is a file missing that you need to push through to your "/system/bin" folder in your SK's root directory.
The missing file is the custom "recovery" binary file that krylon360 created. After doing so, either by ADB pushing the file or copy pasting it with a root file manager, you may boot into recovery then run the 'reinstall packages' command in the stock recovery. This in turn loads the new recovery.....
ALWAYS CHECK YOUR MOUNTS IN CUSTOM RECOVERY. It will save you an accidental pain in the ass. Trust me.
Mounts should look as follows:
----------------------------------------------------------------------------------------------------
-unmount /cache
-mount /data
-mount /sdcard (this sometimes says it is mounted-- not important)
-unmount /system (MOST IMPORTANT. IF IT DOES NOT READ AS THIS SAYS- THEN FIX THAT AND MOUNT IT BEFORE ANY BACKUPS OR WIPES. YOU WILL GET STUCK IN THE SCRIPT)
----------------------------------------------------------------------------------------------------
I will see if I can host the file in my Dropbox. As for the help, it is available in many older posts already. But a hitting that thanks button couldn't hurt ;D
Zydrate_blue said:
Ok guys the actual problem here is that there is a file missing that you need to push through to your "/system/bin" folder in your SK's root directory.
The missing file is the custom "recovery" binary file that krylon360 created. After doing so, either by ADB pushing the file or copy pasting it with a root file manager, you may boot into recovery then run the 'reinstall packages' command in the stock recovery. This in turn loads the new recovery.....
ALWAYS CHECK YOUR MOUNTS IN CUSTOM RECOVERY. It will save you an accidental pain in the ass. Trust me.
Mounts should look as follows:
----------------------------------------------------------------------------------------------------
-unmount /cache
-mount /data
-mount /sdcard (this sometimes says it is mounted-- not important)
-unmount /system (MOST IMPORTANT. IF IT DOES NOT READ AS THIS SAYS- THEN FIX THAT AND MOUNT IT BEFORE ANY BACKUPS OR WIPES. YOU WILL GET STUCK IN THE SCRIPT)
----------------------------------------------------------------------------------------------------
I will see if I can host the file in my Dropbox. As for the help, it is available in many older posts already. But a hitting that thanks button couldn't hurt ;D
Click to expand...
Click to collapse
IIRC, I believe this is the file that everyone wants..
http://www.4shared.com/file/BqnNCX3K/recovery.html
Thank you
I would like to say thanks to you all helping out with this. My lack of signing in here has to do with me not even having an Android-powered device anymore. I sold my SideKick and MyTouch together for about $250. I still come back here and look around every now and then, but see that a lot of you guys have it under control. So, once again thank you.:good: