Custom recovery random disappear

[hlxanthus]

Well, I used a nandroid of stock ZVD ROM to restore from cm7 to update profile and prl. Somewhere in the process, when I rebooted my phone to nand back to my cm7 backup it loaded into stock recovery !! All I could do was stare at it. I have been running custom roms on this device since I got it like 6 months ago, so I am not clueless of what I should be doing. I booted back into the stock rom and of course superuser is gone too. Does anyone have a clue on how this happened? I would have thought it was impossible.

A little history, about a month ago I upgraded to the rooted zvh stock rom. Then soon after switched to gROM. But I was having data sync issues with google voice. I got frustrated enough that I jumped ship back to zvd by way of the sprint provide update.zip that is posted on the boards. Of course re-rooted using gingersnap and manually reinstalled xionia recovery. Here may be where I went wrong. After booting back into android and then back to recovery to make a nand. From there I decided to flash thekravens CM7 (which I loved by the way, along with all other devs versions of it). Got my phone set back up to my standards loading apps and custom themes ect. But was still having sync issues with voice (which kraven is now saying is due to gVoice not a baseband issue, but oh well LOL). So that is where I am now, having restored back into stock VD rom and updating profile and prl.

While typing this, I went into the market and just for giggles, downloaded superuser and wireless tether for root users. Both installed and the tether app works, so I still have root, just recovery removed . . . So I will reinstall that here in a little bit, but would like to know what I did that reverted it.

Oh, and sorry this is a little long. But thought you should have all the facts I know about.

Edit: Just wanted to add, that I used zefies DebugFormatALL.zip both before initially flashing to cm7 (with no issues) and before restoring the nandroid backup of stock VD rom. Maybe that was the culprit

 

[blackops1125]

Edit: Just wanted to add, that I used zefies DebugFormatALL.zip both before initially flashing to cm7 (with no issues) and before restoring the nandroid backup of stock VD rom. Maybe that was the culprit

That is not the problem, I do that all the time when swithing between roms OR doing Nandroid restores!

 

[hlxanthus]

That is not the problem, I do that all the time when swithing between roms OR doing Nandroid restores!

Well, I had always before used the Debug-FormatSYSTEM.zip, but I switched to Debug-FormatALL.zip as I figured it couldnt hurt.

 

[sfhub]

The most likely reason is you did not (successfully) perform:

cd /system/etc
mv install-recovery.sh install-recovery.sh.bak

After running the ZVD update.zip

 

[hlxanthus]

The most likely reason is you did not (successfully) perform:


After running the ZVD update.zip

Even if I had successfully booted into xionia several times and created nandroid backups and performed restores?

 

[sfhub]

The recovery is replaced when booting into Android. If your nandroid backup had that file, it'll restore stock recovery when you boot into Android. It does so without fanfare, so you might not have noticed it happening unless you contantly booted into recovery after every applicable operation to check on it. After the stock recovery was put in place, you might have restored yet another nandroid backup which didn't have that file there, so it might not even be there right now.

However it might still be there, so just ls that directory and see if it is there. If it is, that would definitely explain the behavior. If not, it wouldn't tell you one way or another, because it could have been there at some point.

 

[hlxanthus]

Okay, I have reinstalled custom recovery following zefies instructions. I would like to make sure this doesnt happen agian. How exactly do I go about checking that all is right, as I didnt really understand what you were asking me to check. Any help is appreciated.

 

[sfhub]

In adb shell:

$ su
# cd /system/etc
# mv install-recovery.sh install-recovery.sh.bak
# ls -l install-*

If there is an error with the mv, that is fine, just means that file is not there or already renamed.

The "ls" confirms what files are there. Post the output of the "ls" if you want to be sure what you have is good.

 

[hlxanthus]

In adb shell:


If there is an error with the mv, that is fine, just means that file is not there or already renamed.

The "ls" confirms what files are there. Post the output of the "ls" if you want to be sure what you have is good.

Okay, just ran those in adb shell. As you said when I ran "mv install-recovery.sh install-recovery.sh.bak" it came back with an error of "mv: can't rename 'install-recovery.sh' : No such file or directory". I assume that is right. Then when I ran "ls -l install-*" it came back "ls: install-*: No such file or directory

Script

Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Christian>adb shell # su su # cd /system/ect cd /system/ect cd: can't cd to /system/ect # cd / system/etc cd / system/etc /system/etc # mv install-recovery.sh install-recovery.sh.bak mv install-recovery.sh install-recovery.sh.bak mv: can't rename 'install-recovery.sh': No such file or directory # mv install-recovery.sh install-recovery.sh.bak mv install-recovery.sh install-recovery.sh.bak mv: can't rename 'install-recovery.sh': No such file or directory # ls -l install-* ls -l install-* ls: install-*: No such file or directory #

 

[sfhub]

Looks fine. That means you don't have any script that will restore your recovery to stock.

If you restore nandroid backups or use the update.zip's from Sprint, you should check again.

 

[hlxanthus]

That is with running kravens cm7. Maybe i will load reborn if i need to update prl instead of returning to stock rom to avoid this issue. It was a pain in the butt having to reinstall !

Thanks so much for your input.

 

[sfhub]

None of the custom ROMs should have install-recovery.sh. That will only be ther for one of Sprint's ROMs.