Database Info

[Q] installl-recovery.sh does not restore stock recovery

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!

[Q] Can't Update Transformer

Whenever I try to update, it will restart. Then an android with an orange progress bar will come up but in the middle, it will stop and the Android with the triangle with exclamation point inside would appear??
any solutions?
My version is in 3.2

What are you trying to update and how?

tweak89 said:
What are you trying to update and how?
Click to expand...
Click to collapse
I think I'm updating the tablet? I'm doing it OTA when I clicked check updates on the About Tablet area?

Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision

gee one said:
Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I'm running stock but I do have it rooted. Other than that, nothing else. I haven't even flashed recovery.

How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision

gee one said:
How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I used the root toolkit v7 that can be foundon the development section. I'm thinking that if I unroot the transformer, the update could work?
Or maybe if I just downloathe firmware from the asus website, will it work better? Though I don't know how to install it.

You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision

gee one said:
You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Owww. so 8659 is not the latest but the one on OTA? Will I lose root if flash that? and does root work on the newest update?

Yes, you will lose root and any custom recovery if you flash the stock image from the ASUS website. I think the tools in the dev section will still root as long as you have SBK v1 I.e., nvflash works on your tf. You rooted once, so it should be fine.

Having a lot of trouble

I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.

sounds like you're totally lost. I don't know what a recovery.img is, well I guess most android phones have a recovery partition and a boot partition and you would flash a recovery.img to those but the galaxy s series doesn't work anything like that.
lets start with you sharing some information. open settings>about phone and tell me the baseband and android version. because if I have to guess you are trying to use a froyo proceedure that was only needed before custom kernels existed and you're trying it on stock gingerbread firmware, either a Rogers phone or a phone that has been flashed with a gingerbread leak.
also do you mean miui??? auto correct is a *****. and if you flash miui then why an old build? wouldn't you want 2.3.7???

singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
huh .....
oh and this should be in the [email protected]

Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3

singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3

singhtjay said:
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
Click to expand...
Click to collapse
well first off its not a .img its a binary file with no extension a .img is something you get when you dump a partition or drive on a low level so all the Metadata and everything is copied exactly and it would be used for reproducing a drive as a backup or on another device, well it could be any extension really but .img is common.
other androids have a different partition layout and may have a recovery partition.
now what is going.g on is you are trying to do a proceedure for froyo on a gingerbread rom. Samsung changed the boot scripts making it impossible to use cwm without a custom kernel. the boot scripts are in the initramfs which Samsung uses in place of the boot partition which means cwm and init.d support can't be added without replacing the whole kernel.
good news is Samsung has a flash tool called Odin. and there is an open source substitute called heimdall and if you are rooted there is a phone based program called sgs kernel flasher that will flash the kernel. look into the Rogers infuse root thread. the root kernel will also give you cwm. you could also use the hellraiser kernel, entropy's dd kernel, or the infusion gb kernel.

[Q] ICS to Gingerbread

I tryed to do this one and failed had to send phone out for warranty. I got it back. I HATE I.C.S. Want it back to gingerbread. This time a little more better understanding but still a total NOOB. I dont wanna have to send the phone out again.
Here it is:
Nexsus S I9020A
Network Koodos
Unlocked
CWM v5.0.2.0
Android 4.0.4
Radio KJ1
Bootloader KL1
Build # 1MM769
I cant find a flash file for these specs. Also what is the most NOOB friendly way to flash. Anyone please. Im not rushing through it again. Wait pateintly for help. Thanks in advance.
Bruce

Download this file. It is Android v2.3.6 Gingerbread, build GRK39F. Specifically for the i9020a with the most recent Gingerbread version (2.3.7 wasn't released for any NS aside from the 4G i believe).
What you have to do is backup anything you need to. Apps, files, etc. Whatever is on the phone that you want to keep, back it up. Titanium Backup might help too. A good way to do this is to do a NANDROID in CWM (CWM --> backup and restore --> backup). Now backup your entire SDCard to your computer. Now we want to copy over that file you just downloaded to the SDCard.
In CWM, you want to wipe the main partitions to get a clean install. To do this, in CWM:
-Data/factory reset
-Format /system
-Format /boot
Now, immediately after this, click on Install Zip and locate the zip file you put on the SDCard. Let it do it's thing then reboot. Rebooting will take a little longer than usual the first time, but once it's up and running you're good to go

Thanks SO much. You couldn't of spoon fed me better. This site rocks.

All done worked great THANKS AGAIN. Woohoo mo more ICS

One last stupid question. So my phone is unlocked and cwm v5.0.2.0 is installed. To root it what do I do.

Good to hear you got it sorted
To root, just download the latest su binary. Easiest way is to use this official flashable zip (latest is 3.0.7 efghi, linked). Just copy it to your sdcard then flash it via CWM (install zip option).
By the way, i forgot to note that CWM will be replaced by stock recovery after a stock ROM flash. You'll have to use fastboot to flash CWM again, then you can flash superuser.zip. To stop stock recovery flashing each boot, using any file manager (e.g. ES File Explorer), rename /system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak. Next time you flash a recovery after doing this, it will stick.

I got es file explore. Im in it but cant find /system/etc/install-recovery.sh ??? Never Mind had to change a setting in es file explorer.

K I got superuser on there now. But a problem. When in ES file explorer i go to the file and add the .bak to it. But it tells me soory operation failed. Lol Sorry in ES just had to check to mout system. Im all Good Thanks for everythng. 2 Thumbs up

[Q] Lost root after installing 9ZGgDXDi.zip

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