I have a Nexus S(I9023) and used the full Rom to update from 2.3.3 KB3 GRI54 to the 2.3.4 KD1 GRJ22 version, except I can't get my clockworkmod recovery to stick, I unlocked the bootloader and flashed the recovery with clockworkmod 3.0.2.5, and installed the superuser file, except each time I boot into the OS, and then boot back into recovery, the clockworkmod is gone, and I'm stuck with the stock recovery again.
What I did was the following procedure:
Odin flashed back to stock 2.3.3 - KB3 - GRI54
installed the full update 2.3.4 with the recovery
unlocked bootloader
flashed clockworkmod recovery 3.0.2.5
installed superuser
reboot
checked if superuser app was installed successfully - yes
reboot to recovery
And to my surprise the clockworkmod recovery was gone, and I was stuck with the stock recovery again.......
How do you make the CW stick and not have it reverted to the stock recovery?
There is a script that resets it. Been like that for a while. Look in the root threads on how to make it permanent
Sent from my Nexus S
Matridom said:
There is a script that resets it. Been like that for a while. Look in the root threads on how to make it permanent
Sent from my Nexus S
Click to expand...
Click to collapse
Tried looking in the Root threads, but can't find the solution, the funny thing is that I never had this before, only started after updating to 2.3.4.
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
pullermann said:
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
Click to expand...
Click to collapse
Yep. Also if you use this method you will still have to flash CWM one more time after you do what this poster says (the script runs when the phone boots) .
Sent from my Nexus S using XDA App
I had same problem..it worked for me..now should I back up that Tom so I don't gotta do it again??
Sent from my Nexus S using XDA App
pullermann said:
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
Click to expand...
Click to collapse
Thanks for the solution, I did what you described, and things are working now
You just saved me a lot of frustration........
RISHI-O said:
Thanks for the solution, I did what you described, and things are working now
You just saved me a lot of frustration........
Click to expand...
Click to collapse
Guides for rooting had the solution for this problem.Dont frustrate just search )
Sent from my Desire HD using Tapatalk
Related
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
Just use Odin to flash back to stock
Sent from my SPH-D700 using XDA Premium App
deflin39 said:
I used Epic All in One Root and Recovery v2.04 a while back to root my Epic. Uninstalled a few of the apps. Got the froyo push today but it wouldn't take, figure it had to do with removing apps and rooting. I recovered the apps and removed root. Downloaded the update.zip and booted into recovery mode to install. I'm now getting an assertion error because the install cannot find /system/bin/playlogo
I've read some threads and noticed some of the root procedures created a playlogo-orig. I don't have that file. I do have playlogos1 though, though I'm guessing that isn't the same file?
Sort of stuck on what to do next. Can't seem to locate a playlogo to download to sdcard. Any help would be appreciated.
Click to expand...
Click to collapse
You are correct playlogos1 is not the same file as playlogo.The one click root should backup playlogo since it still gets run by the script that replaces playlogo it just runs playlogo-orig from the script that is named playlogo that one click installs.
Thanks for the info. I'll give Odin a shot.
Hi i just update to 2.3.4 and try to root it and work fine with me
Download this file and move it to your NS
http://www.mediafire.com/?0a4abln7x3gjgrv
after your flash the recovery then ..
On your phone, use the volume key to highlight "recovery". Press power to boot into recovery.
in the recovery screen, select mounts and storage
mount /system
mount /data
go back, and choose install zip from sd card
choose "choose zip from sd card"
pick the su package zip file you copied over earlier
choose Yes
when done, reboot.
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
it is for the i9023??
So after I flash 2.3.4 update, all I have to do is reboot and flash SuperUser again, and then Nexus S is re-rooted again?? Thanks!
amjad_2020 said:
Hi i just update to 2.3.4 and try to root it and work fine with me
Click to expand...
Click to collapse
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
I have a custom kernel. How do I Install 2.3.4
Sent from my Nexus S using XDA App
italia0101 said:
I have a custom kernel. How do I Install 2.3.4
Click to expand...
Click to collapse
You have to go back to stock GRI40, i.e. with a Nandroid restore?! But this will be the correct thread for you: http://forum.xda-developers.com/showthread.php?t=1055591&page=12
kevin_ngckk said:
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
hehe how on earth can someone provide real feedback on battery life 2 seconds after installation?
Thanks for sharing, I'll wait for Team Douche to implement this on CM7.
Trouble
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
smlmn said:
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
Click to expand...
Click to collapse
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
jungbum said:
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
Click to expand...
Click to collapse
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
Yes, same here SuperUser ist still available, but without any function
on nexus s 9023 ??
what about it ?
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
jamallj said:
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
Click to expand...
Click to collapse
No sorry. It's not possible to install busybox without root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
That means you're not rooted.. you have to root again.
bolabola118 said:
That means you're not rooted.. you have to root again.
Click to expand...
Click to collapse
I've tried to reroot again and totally get result
But I also done that:
!Once you are in recovery mode, select the relevent mounts and storage by Mount / System and Mount / data.
(I can not post links)
Thx
Handymeister said:
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
Click to expand...
Click to collapse
Same situation/problem
For those stock rooted but bootloader locked 2.3.3 users that previously rooting using CWM recovery to update and superuser root method.
You can root the same way...but save the trouble of fastboot recovery step via PC which novice users could be stuck on getting fastboot usb driver to work properly.
0) Just installed ROM Manager (From Market) into your phone
1) Store both 2.3.4 update.zip and SuperUser.zip into SDCard
2) Run ROM Manager
3) Activate CWM Recovery
=> Make sure recovery is installed succesfully..check ROM Manager screen which tell whether the installation is successfully done.
4) Reboot recovery from ROM Manager App
5) Follow thread #1 on the rest
6) After applying update.zip..do not reboot...do a system mount from CWM Recovery then apply SuperUser.zip ..after completing all steps..do a reboot..
Voila your 2.3.4 is installed and rooted..
Thanks, but this way comes to late for me and some other users. We've flashed the update without rooting.
And now we need another way for root ...
All,
I have updated to 2.3.4, lost root as expected and tried to reroot 2.3.4.
I had no luck, once i ran ./Gingerbreak the script would sit and not do anything after displaying the initial text.
Has anyone successfully done this?
I thought about updating with the prerooted 2.3.4, but the devs started to add all sorts of stuff in there, and right now that is not what I am after.
Thanks!
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
- I didn't unlock the boot loader on the phone and now really don't want to go through the hassle of having the phone reset when I do... too much on it.
- Can't do a nandroid backup (to unlock) because I don't have root.
Catch 22 circle. Am keeping my eyes open, hopefully someone comes up with an alternate method. Once I get root again I will unlock the boot loader after making a backup so this doesn't happen again.
51Cards said:
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
Click to expand...
Click to collapse
Custom bootloader? Just unlock the one you have and flash a new recovery. It takes a whopping 3 minutes to flash recovery, then SU, and reboot. If you want to keep everything stock so you can OTA, the stock ROM will overwrite the recovery when you boot and you'll end up with rooted stock ROM with OEM recovery. If you want to then flash a custom rom, you can do so through ROM manager.
Want to unroot? Download the FRG33 passimg.zip and boot into bootloader.
This stuff is stupid easy on the N1.
ATnTdude said:
Custom bootloader? Just unlock the one you have and flash a new recovery.
Click to expand...
Click to collapse
Ok so feeling like a newb here.
First I meant 'custom recovery', not 'custom boot loader'... mixup in terms on my part.
But to put in a custom recovery I need to unlock the phone. Once I unlock the boot loader doesn't the phone reset to factory state? I had seen that mentioned several times and in the unlock video I was watching. After the phone was unlocked it went back to "Welcome to Android" etc on the next startup. Have far too much in the phone I don't wish to loose and I can't Nandroid it without root.
Thanks for the info.
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
I am attempting to keep my phone as stock as possible and only root to block ads and sometimes push some new app that google wont release to the n1.
I really don't want to mess with custom anything on my daily driver (used for business also). I have my g1 for that
SO....has anyone used gingerbreak successfully on 2.3.4?
Disregard. I misread the post.
MitchRapp said:
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
Click to expand...
Click to collapse
Yeah, the ROM manager option would have worked well before I did the OTA for 2.3.4 and lost root. I will keep it in mind for the future, thanks!
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Exactly what I did. Works smoothly and you're all set in minutes. As long as you had root in the first place, on 2.3.3.
Sent from my Nexus One using XDA Premium App
DownloaderZ said:
All,
I have updated to 2.3.4, lost root as expected
Click to expand...
Click to collapse
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
GnatGoSplat said:
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Click to expand...
Click to collapse
I'm looking to download all the files for this so I'm set from the start. I found FRG33 here but I haven't found the GRI40 update yet (although I haven't really looked yet either, that's not my question). I'm wondering, the site I listed has FRG83 as well as 33, does it matter which to use? 33 mentions a possible error.
What's the deal?
Thanks,
I think you should be able to use FRG83 instead. All you really need is something that can be named passimg.zip installed by the bootloader itself.
I got the GRI40 update from here:
http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip
GRI22 update:
http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Oh yeah, I forgot about that. Flashing PASSIMG.zip wipes out everything because it's a full flash.
brettbellaire said:
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Click to expand...
Click to collapse
There is no way to downgrade Android without wiping everything, as a downgrade is only possible with leaked shipped ROMS (i.e., ROMs that re-write the entire NAND flash memory on the device...
droidexplorer said:
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I do that as well now. However I have some steps I figured out that work for me. It's more direct (only 2 flashes, plus su), but you have to pay attention. If you didn't already have a CWM backup though, it will wipe everything:
1) Flash to FRG33 using PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip (rename to PASSIMG.ZIP), takes you to 2.2
2) Root using Super-One-Click
3) Install ROM Manager and flash CWM
4) Flash b90257ed8cd3.signed-passion-GRJ22-from-FRG33-121341.b90257ed.zip, takes you directly to 2.3.4
5) DON'T LET PHONE REBOOT into Android, go to recovery then Flash su-2.3.6.1-ef-signed.zip
6) Remove/rename /system/etc/install-recovery.sh via ADB
7) If you have a recent backup, use CWM to 'advanced restore' the data portion.
8 ) Profit! (or root)
Step 5 may require explanation:
Android will reboot at least once during the flash, this is ok, as it loads right back into recovery. However after the second reboot, it will boot normally. You must INTERRUPT this boot process (hold power button, battery pull, etc). At this point CWM is still on there (don't know why, I thought flash was going to wipe it).
The reason you have to interrupt the boot process (for anyone who doesn't know) is because of the install-recovery.sh script. Stock android will automatically flash the stock recovery on bootup.
So boot into CWM, then flash su. After bootup up again, CWM will be gone, but we have root! So remove (I renamed) that file (/system/etc/install-recovery.sh), then reflash CWM using ROM Manager.
EDIT: After posting this, I had a thought: it should be possible to remove install-recovery.sh via CWM using ADB. That would remove the step of reflashing CWM a second time. I updated the step-by-step, but left the explanation as-is.
When I originally wrote these steps a few months ago, gingerbreak wasn't released. So I don't rely on it.
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
GnatGoSplat said:
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
Click to expand...
Click to collapse
In theory. It does seem to work for other devices (gTablet). I haven't had much luck with modifying the updater-script inside the zip file however. Whenever I change one, I get errors when I flash the zip. That's why I haven't tried that method.
I wanted to make my own flashable zips to tweak ROMs on my own, but never could get it to work, so I abandoned my work.
In addition though, you could just try to replace the recovery.img in the zip file with CWM. That might work too, as long as signature verification is off. I don't remember if I tried that.
EDIT: Forgot one key thing: Doing this won't prevent the OS from reflashing the stock back anyway on bootup (using install-recovery.sh). You MUST remove that file regardless, if you're on a stock ROM. If you want to remove that from the zip you can, but again requires updater-script changes. However if you want to OTA, then I'd recommend just renaming it, since some OTA's update that file. That way you can rename it back for the update.
On the GRI40 to GRJ22 update, I didn't have to do anything too complicated like modifying scripts. I simply yanked the Recovery folder out of the update and that seemed to do the trick with no error messages and CWM still intact.
I can flash it, it works as it should until I reboot the phone. Once I reboot, the stock recovery comes back. Ive seen threads about deleting a couple files, but not sure if I should be doing that. any ideas on what I may be doing wrong?
blackhemi4x4 said:
I can flash it, it works as it should until I reboot the phone. Once I reboot, the stock recovery comes back. Ive seen threads about deleting a couple files, but not sure if I should be doing that. any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
Stock restores the install-recovery.sh file in /system/etc. This prevents recover mods from "sticking." After you root, load up your favorite root file explorer and delete/rename that file in /system/etc/ . Then, reflash recovery and you're golden.
belyle said:
Stock restores the install-recovery.sh file in /system/etc. This prevents recover mods from "sticking." After you root, load up your favorite root file explorer and delete/rename that file in /system/etc/ . Then, reflash recovery and you're golden.
Click to expand...
Click to collapse
Thanks
Just tried that, but my root explorer is not allowing write access.
Flashed superuser again, same thing....
I starting from scratch again, 4.0.4 is getting installed as I type.
Ill try rooting again and getting my root explorer to delete that file and try again
for some reason my cwm recovery is sticking and its causing my play store to stay on 3.4.7
Any ideas on why the recovery is sticking I didn't even touch the install-recovery.sh
Infact all I did was get the stock image from google flash that
then flash cwm to gain root and install superuser
after that my stock recovery just won't come back, any ideas?
Flash the newest version of su.zip
albundy2010 said:
Flash the newest version of su.zip
Click to expand...
Click to collapse
I got the latest version 3.0.7 it still won't work, I've tried so many different methods including manually flashing the stock recovery but that doesn't help with updating the play store either
---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------
blackhemi4x4 said:
Thanks
Just tried that, but my root explorer is not allowing write access.
Flashed superuser again, same thing....
I starting from scratch again, 4.0.4 is getting installed as I type.
Ill try rooting again and getting my root explorer to delete that file and try again
Click to expand...
Click to collapse
to allow write access you just have to press "remount as R/W" in Root Explorer
There are different versions of 3.0.7. You should have efghi version.
Also as the other poster said you have to use root explorer the correct way if you're not doing so.
Thanks, its the little things that get me. I had the wrong 3.0.7. Got the efghi and all problems solved. time for a nandroid and mod this thing.
Is there a working circle bat mod for stock 404
Same issue
I had the same issue when I upgraded to 4.0.4.
I used the ADB shell to remount \system as R/W and was then able to rename my install-recovery.sh. After that I installed CWM and it sticks properly.
just download ROM manager from the market and install the newest CWM from the manager, it will stick. That's how I got it to stick
PhoenixIce22 said:
I had the same issue when I upgraded to 4.0.4.
I used the ADB shell to remount \system as R/W and was then able to rename my install-recovery.sh. After that I installed CWM and it sticks properly.
Click to expand...
Click to collapse
I had the same issue, rename the install-recovery.sh and manage to get CWM to stick.
Here's a fix recovery.zip just flash in cwm and it will stick.http://db.tt/B1vOd9K4 I didn't make it, just sharing it.
In order to root Lollipop, you have to flash a custom recovery such as TWRP. The issue is how to revert back to stock recovery for OTA updates.
Fortunately, it's relatively simple and doesn't require downloading a recovery image from some shady third-party hosted website -- the stock recovery installation is still there on your phone!
Tools required:
A root-enabled file manager, such as Root Browser or Ghost Commander
Depending on the abilities of your file manager, a terminal program, such as Terminal Emulator
(Optional) Flashify, to backup your stock recovery for the future
1. Using your favorite file manager, rename /system/recovery-from-boot.bak to /system/recovery-from-boot.p
note: depending on the file manager, you might need to remount system as read/writeable first
2. execute (with root privileges) the shell script /system/bin/install-recovery_original.sh
if you use Root Browser as your file manager, you can execute this script as root directly. Otherwise go to the terminal app and type:
cd /system/bin
su
./install-recovery_original.sh
This will install the stock recovery.
3. Reboot into recovery to make sure it worked
4. (Optional) Backup the stock recovery using flashify. Now you'll be able to revert to stock recovery in the future without going through all these steps!
Seriously said:
In order to root Lollipop, you have to flash a custom recovery such as TWRP. The issue is how to revert back to stock recovery for OTA updates.
Fortunately, it's relatively simple and doesn't require downloading a recovery image from some shady third-party hosted website -- the stock recovery installation is still there on your phone!
Tools required:
A root-enabled file manager, such as Root Browser or Ghost Commander
Depending on the abilities of your file manager, a terminal program, such as Terminal Emulator
(Optional) Flashify, to backup your stock recovery for the future
1. Using your favorite file manager, rename /system/recovery-from-boot.bak to /system/recovery-from-boot.p
note: depending on the file manager, you might need to remount system as read/writeable first
2. execute (with root privileges) the shell script /system/bin/install-recovery_original.sh
if you use Root Browser as your file manager, you can execute this script as root directly. Otherwise go to the terminal app and type:
cd /system/bin
su
./install-recovery_original.sh
This will install the stock recovery.
3. Reboot into recovery to make sure it worked
4. (Optional) Backup the stock recovery using flashify. Now you'll be able to revert to stock recovery in the future without going through all these steps!
Click to expand...
Click to collapse
I currently have KitKat installed (4.4.4), rooted, unlocked bootloader & TWRP installed on my XT1063 and unable to receive OTA updates. I've checked your proposed method. There's no "install-recovery-original.sh" file in system/bin rather there's a shortcut of the file "install-recovery.sh" this shortcut points to "/system/etc/install-recovery.sh". My question is that if i execute this file "install-recovery.sh" will it restore stock recovery? I've the backup file placed at the location mentioned by you and i've already renamed it to "recovery-from-boot.p".
uetian2k3f said:
I currently have KitKat installed (4.4.4), rooted, unlocked bootloader & TWRP installed on my XT1063 and unable to receive OTA updates. I've checked your proposed method. There's no "install-recovery-original.sh" file in system/bin rather there's a shortcut of the file "install-recovery.sh" this shortcut points to "/system/etc/install-recovery.sh". My question is that if i execute this file "install-recovery.sh" will it restore stock recovery? I've the backup file placed at the location mentioned by you and i've already renamed it to "recovery-from-boot.p".
Click to expand...
Click to collapse
yup. the filename is different on lollipop.
Seriously said:
yup. the filename is different on lollipop.
Click to expand...
Click to collapse
Thanks! I'll give it a try.
This looks great. So now we can go flashing custom recoveries and then be able to revert to stock anytime, without relying on "shady third-party hosted websites". Good find :good:
Not working
I got an error ..see in attached images..i got both files
super hat funktioniert.
not working
it tells me finished executing script file
exit value:127
stdout:
null
stderr:
/system/bin/install-recovery_original.sh[17]:/system/etc/install-recovery-2.sh: not found
can somebody help me
Thank you
nvm i figured out how to do it
i downloaded the stock firmware on my pc and took the recovery.img and put it in my internal storage, flashed it using flashify and backed it up
Please, I need the original recovery in format "img" to flash with fastboot, can anyone upload? Thanks in advance!
mufasa2001 said:
nvm i figured out how to do it
i downloaded the stock firmware on my pc and took the recovery.img and put it in my internal storage, flashed it using flashify and backed it up
Click to expand...
Click to collapse
And now you can have OTA updates?
svendsvin said:
And now you can have OTA updates?
Click to expand...
Click to collapse
Only if you are unrooted and on stock firmware without any changes too.
Sent with somewhat