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.

[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

[RECOVERY] Fixed CWM v3.0.2.8

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:

[Q] Need Stingray final stock

I have looked for hours for the final stock recovery for Stingray. I have found 4.1.1 and updates, but not what I need to flash my Xoom back to root. Can someone point me to a copy please?

TWRP won't work? Download goomanager and have it download and install it.

rastaguy said:
I have looked for hours for the final stock recovery for Stingray. I have found 4.1.1 and updates, but not what I need to flash my Xoom back to root. Can someone point me to a copy please?
Click to expand...
Click to collapse
Are you using the stock kernel and stock ROM right now? If you are, just download the JZO54M OTA file from Google. Open the ZIP file, and go under the "recovery" folder. Put recovery-from-boot.p in /system and put install-recovery.sh in /system/etc. Set the permissions on install-recovery.sh to 544 and set ownership to root:root. Reboot and it'll flash stock recovery for you on the next bootup. :good: