Related
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.
so i installed cwrecovery, rooted my NS and renamed install-recovery.sh. then I installed a few root-only apps (ROM manager, ROM toolbox, titanium, file expert, etc) and tried oxygen2.2.2 and devnull1-1. now i want to restore the stock recovery image so I renamed install-recovery.sh back. but when i reboot into recovery, cwm5.0.1 is still there. isn't the install-recovery.sh supposed to restore the stock recovery image when i reboot the phone?
I rooted a friend's NS earlier today, this time just unlocking the bootloader, flashing cwm5.0.1, and installing su (did not rename install-recovery.sh). when that phone rebooted, it no longer had the cwm5.0.1 image.
whats up with my install-recovery.sh? why doesn't it restore my recovery?
My guess is the install-recovery.sh has to be called by some startup script, which *I think* does not exist in those custom ROMs.
In your friend's case, because his NS is still on stock ROM it makes sense that the install-recovery.sh was called properly.
suksit said:
My guess is the install-recovery.sh has to be called by some startup script, which *I think* does not exist in those custom ROMs.
In your friend's case, because his NS is still on stock ROM it makes sense that the install-recovery.sh was called properly.
Click to expand...
Click to collapse
sorry. forgot to say this: i have reverted to the stock rooted Gingerbread ROM (restored via cwm backup). so i'm no longer running devnull or oxygen.
Install recovery.sh is a stock binary. You don't rename anything to make this file. It is patched in with OTA updates.
So......put intall-recovery.sh in /etc and put recovery-from-boot in /system
http://db.tt/hLKJDY0
http://db.tt/M2fKfC3
^^^both files above^^^
snandlal said:
Install recovery.sh is a stock binary. You don't rename anything to make this file. It is patched in with OTA updates.
So......put intall-recovery.sh in /etc and put recovery-from-boot in /system
http://db.tt/hLKJDY0
http://db.tt/M2fKfC3
^^^both files above^^^
Click to expand...
Click to collapse
thanks. i'll check those files out. i didnt "make" the install-recovery.sh file from anything. I took the original file and renamed it to install-recovery.sh.old to prevent it from overwriting the cwm recovery image with the stock image.
now that I WANT it to overwrite the CWM image, i renamed it back to install-recovery.sh but its not working.
i didnt touch recovery-from-root.p, just install-recovery.sh
flyfingersfly said:
sorry. forgot to say this: i have reverted to the stock rooted Gingerbread ROM (restored via cwm backup). so i'm no longer running devnull or oxygen.
Click to expand...
Click to collapse
In that case I think you should check the file permissions -- it should be something like rwxr-x-r-x.
suksit said:
In that case I think you should check the file permissions -- it should be something like rwxr-x-r-x.
Click to expand...
Click to collapse
oh wow. can't believe i missed that. LOL.
That was it. Thanks!
I cant go to recovery through Rom Manager for some reason. It works manualy( power+volume) but when I click it from the app it freezes, and shows an exclamation point triangle
have you tried to reinstall the app?
Wich CWM do you have?
thy the above post; if that doesn't work, go into recovery manually and fix permissions
that must be why
I was following this video http://www.youtube.com/watch?v=PVyGw6vycFo
and it said I had to wipe my data which I did, and maybe CWM was removed?
Ill try to flash CWM and see what happens.
Worked! thanks
In wich way?
Have you reinstall Rom manager App or reflah CWM Recovery?
actually, theres been a trend going on here....
I went on recovery to check if its working after I flashed it and it worked, after turning it off and removing the usb out of my computer I tried again and it didnt work.
Any ideas why?
Edit: when I had ROM manager I already tried to Flash CWM there if you're wondering.
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Harbb said:
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Click to expand...
Click to collapse
where can I find /etc/install-recovery.sh and what do you mean by file explorer with root capability?
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Harbb said:
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Click to expand...
Click to collapse
fairly new to android so I have no clue what you are talking about sorry... can you give me some steps on how to do that. again I apologize, Im still new
Download this from the market, i'm sure you'll figure it out
quick unrelated question: I tried to apply the ROM and it didnt continue, it said it was aborted or something
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
HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!
Machlev said:
HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!
Click to expand...
Click to collapse
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
no MD5 file found while installing via TWRP. Should I wipe /system?
Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
I wiped system and pushed an md5 file. Still fails with no reason.
I use this ROM -
https://cyngn.com/products/oneplusone/
(On the bottom)
What error are you getting?.. You could try another download (that one may be corrupt) or CM11 ROM, you should still be able to keep your app data as long as you don't wipe that partition.. You only need to wipe system/dalvik/cache..
Sent from my OnePlus ONE
Are you mounting /system with TWRP before doing that?
Also, dont move the file, try cp which works better with crosslink devices
And try chmod 755 /system/build.prop with adb while in recovery and check the build.prop isnt edited in Windows so EOL is Windows-like, then use Notepad++ to change to UNIX-type
easy, you copy pasted so permissions are not the same as the original
reflash system or rom
Sent from my A0001 using XDA Free mobile app
Yep. Permissions should be rw-r-r (or 644). If you don't know what you're doing don't mess around with system files.
Transmitted via Bacon