Database Develop

[Q] Q. Is it possible to unwittingly lose Custom Recovery? Please Help.

Firstly, my nexus one is Locked + Rooted with Stock FRF91.
OK, So I rooted with 1-click, installed a custom recovery (first Clockwork then Amon RA 1.8.0.0).
Did a full backup
Tried out a couple of Roms
Reverted to Stock from backup. All good!
Now 1 week later, I really want to try MiUI Rom so I power on phone with VOL-, select Recovery - all I see is the yellow exclamation in a white triangle with a green Android below. Isn't that normal / stock recovery???
Could the FRG83 OTA that I have not installed (it is still bugging me to do so ) have restored the stock recovery?
Did I clear something / do something wrong when performing the Stock backup or restore?
TIA for any advice.

The OTA update did install, and in the process replaced install-recovery.sh and recovery-from-boot.p, which meant that the stock recovery was automatically reinstalled by the OS on reboot.

Hi rusty, thanks for the reply. I have not installed the update, it is still asking to be installed. I even checked the build number in about phone - frf91.
Are you saying that with out my explicit permission the ota has modified my phone and restored the stock recovery - that certainly would explain it.

I misread your post, sorry about that.
However, restoring your backup is probably the cause, due to the same reasons above.

To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.

khaytsus said:
To simplify, you can lose your recovery in this fashion:
Start with stock ROM
Root
Install custom recovery without removing the .sh and .p files mentioned
Boot up phone
Now, if you install custom recovery using several automated methods, OR manually remove the files previously mentioned in thread, no problem. But if those files remain the stock ROM will automatically run them and restore the recovery image. Happens to a lot of people.
So likely that's what happened; restoring and using your stock ROM had those scripts in the image.
Click to expand...
Click to collapse
Thankyou both for your help. It makes a bit more sense now.
So in order to get back to a custom recovery, will I need to reinstall it or will removing these .sh and .p files do the trick?
Ps, what is the exact location of these and how would I delete them (i assume they are system/ protected)
Thanks, Steve.

You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
or remove them altogether
Code:
rm /system/recovery-from-boot.p
rm /system/etc/install-recovery.sh
My advice would be to rename, just incase you feel like stock recovery again at some point.

Rusty! said:
You'll have to remove/rename the files and flash it again.
They are: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
You could rename them:
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
Click to expand...
Click to collapse
Perfect. Understood.
I'll try to remember to update this thread with how I get on once i'm done but even if I dont, I think the info contained is pretty clear.
Thanks Rusty & khaytsus.

Also I'm pretty sure that if you use ROM Manager to flash custom recovery, it automatically zaps the files that would otherwise revert you to stock recovery.
Sent from my Nexus One using XDA App

I did use rom manager and I have since done clockworkmod through rom manager but when I go into recovery I get the stock one. that's why I did the manual process installing ra after clockwork the first time round.
Anyone else has that where rom manager seems to install the custom recovery but then when you go there its stock?

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!

I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR

I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).

Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.

I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem

k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img

So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone

chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks

If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol

Where in root explorer do i need to rename

Where in root explorer do i rename it

plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.

chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...

Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes

chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.

Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways

I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

[Q] Confused w/ busybox

This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.

boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back

did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.

then you should flash firmware and root again

Superuser
maybe update superuser binary?

solved
chmod 777 path name n got busybox 1.12

You lost root access because there is no busybox. Reflash the ROM. Easy way out.

nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.

Cannot root... CWR: repeatedly attempted supersu and superuser

Hello,
I've unlocked the bootloader on my One, then proceeded to install supersu via zip through clockworkmod recovery.
I rebooted, attempted to gain root access, and was unable to.
I then rebooted into clockworkmod recovery and attempted to install superuser from this thread, rebooted and was unable to gain root. I then installed supersu from the same thread, and was unable to gain root.
Lastly, I attempted to wipe the cache partition and dalvik cache in effort, and still I am not able to gain root.
I'm unsure exactly what to do from here on out, as the process is truly very simple, but just not working.
Should I flash an official recovery and start over?
Thanks,
Matt

Have you opened the su app and updated the binaries?

I used twrp recovery a few days ago when I rooted. try to flash latest version of twrp through adb and wipe, clear cache,and retry.
If you still have trouble, check out wwjoshdew on youtube. I followed his instructions and rooted/unlocked with no hiccups.

BD619 said:
Have you opened the su app and updated the binaries?
Click to expand...
Click to collapse
Thanks for replying quickly.
The state I'm in now is:
- The SuperSu apk is gone.
- Superuser is installed.
- Root Checker, Helium, ES File Explorer's "root explorer" report no root
- Shark reports root (aka starts).
- superuser info reports `su` 3.2.18
- Used ES File Explorer to verify presence of `/system/bin/su`
Any idea on what could be wrong?
Thanks again,
Matt

How about another try on TWRP 2.6.3.0 recovery?

Sure, I will try this, Originally I tried TWRP, but couldn't access my internal storage (don't know why). Attempted sideload and failed, so I install clockwork and was able to install superuser.zip from /sdcard/.
Thanks!

Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)

branded said:
Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)
Click to expand...
Click to collapse
Get the latest version of SuperSU from here
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
I would suggest using it as it is updated more often then superuser as far as I know

Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt

Glad you got it enjoy

So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!

dtracycar said:
So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!
Click to expand...
Click to collapse
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...

Devilish_Angel said:
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...
Click to expand...
Click to collapse
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?

dtracycar said:
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?
Click to expand...
Click to collapse
... Does it show rest of the files ...

Devilish_Angel said:
... Does it show rest of the files ...
Click to expand...
Click to collapse
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.

dtracycar said:
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.
Click to expand...
Click to collapse
... you might want to install TWRP 2.6.3.0.
Get it from here http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
this is the .img file so you ought to flash it from fastboot ...

branded said:
Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt
Click to expand...
Click to collapse
4.3 was your problem. You needed to use a different SuperSU and this is the case with anyone else who wants to root 4.3 or 4.4. I believe I used SuperSU v1.65. Glad you got it working!

mHamers since
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse

dtracycar said:
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse
... might be a bad SU file. download from here and flash from recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip ...
Click to expand...
Click to collapse

Devilish_Angel said:
dtracycar said:
... might be a bad SU file. download from here and flash from recovery
Well, I finally got it to work! Thank you for all your help! Now if I could only get wifi hotspot or foxfi to work. Thats the whole reason I rooted in the first place!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Build.prop, stuck in boot screen

Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.

Neblue said:
Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.
Click to expand...
Click to collapse
I don't know about the chmod command, but the TWRP "Fix Permissions" does not work with our current (old) version of TWRP. It just messes up the phone.
1) since you have TWRP, did you make a back-up? If so, restore that. Problem solved.
(If no back-up, why not? That's one of the reasons we use TWRP, so we can restore a good backup when we screw something up.)
2) If you have TWRP, that means your bootloader is unlocked. GOOD.
Boot back into recovery, reflash your ROM. Problem solved.
Reboot, make sure everything is OK, then make a TWRP back-up!
EDIT: OOPS. I see you are using stock 5.0.2, not custom ROM. OK, I hope you made a backup. See #1.
There may be other solutions but all the ones I find seem to involve pushing new files to your phone and you say you can't do that...
______
Also in our version of TWRP, if you wipe cache do NOT attempt it from the "install" prompt (There's an option there to wipe cache. Ignore it.) Only wipe Cache from the "Wipe" section/Advanced Wipe/checkmark Cache and Dalvik Cache. (Even though we use ART, habits die hard.)

OK, I restored a backup following your thread, but before, searching for a solution, I formated the cache/data partition from f2fs to ext4 (so dumb), there's a way to undo it? There's no f2fs wipe option in twrp, I think I'll need to wait to a new version of twrp? Or flashing with rsd lite will do it?
Everything is working fine.
Thanks for your answer.
Sent from my XT1225 using XDA Free mobile app

Neblue said:
OK, I restored a backup following your thread,
Everything is working fine.
Thanks for your answer.
Click to expand...
Click to collapse
Glad your phone is back up and running! Aren't you glad you made a back-up?
Not sure about the F2Fs stuff. I haven't messed with it.
Yes, I agree we need a newer version of TWRP. I would gladly donate money toward to the developer!