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.
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.
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
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice
if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab
I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?
It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.
prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop
Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.
JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack
I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]
JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack
simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...
Quick conundrum...
Rooted my 32bg Nexus7 a couple of days ago using the Nexus 7 toolkit.
I have an unlocked bootloader and CWM recovery installed . i did the all in option in the toolkit..
Just installed Titaanium backup, and it says i'm not rooted??
Root check says i am rooted !
Busybox says i'm not rooted
Superuser fails on updating binary (root acess)
So the 64K question..
Am i rooted or not?
if not ,how do i root properly?
Mart
Srsly? Please go back and root it manually. It will work.
Mart360 said:
Quick conundrum...
Rooted my 32bg Nexus7 a couple of days ago using the Nexus 7 toolkit.
I have an unlocked bootloader and CWM recovery installed . i did the all in option in the toolkit..
Just installed Titaanium backup, and it says i'm not rooted??
Root check says i am rooted !
Busybox says i'm not rooted
Superuser fails on updating binary (root acess)
So the 64K question..
Am i rooted or not?
if not ,how do i root properly?
Mart
Click to expand...
Click to collapse
flash this in your recovery http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
your problem is that you used the rootkit on a nexus device. theres no need for that.
simms22 said:
flash this in your recovery http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
your problem is that you used the rootkit on a nexus device. theres no need for that.
Click to expand...
Click to collapse
This is what i used
http://forum.xda-developers.com/showthread.php?t=1809195
So if thats not correct, what is?
i looked at the nexus rootkit, but it didnt specify my model so i gave it a miss
Mart
Mart360 said:
This is what i used
http://forum.xda-developers.com/showthread.php?t=1809195
So if thats not correct, what is?
i looked at the nexus rootkit, but it didnt specify my model so i gave it a miss
Mart
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash a custom recovery, flash either the su binaries or a custom rom in your new recovery, reboot. that is all.
all you need to do is have the drivers and fastboot installed http://forum.xda-developers.com/showthread.php?t=1741395
If you go to terminal emulator and type in su, does the $ change to a #?
Sent from my Nexus 7
If you have access to directories like /system and /dev, you're rooted. If not, you're not. Skipsoft's Nexus 7 Toolkit works well. Just redo the root steps, watch for error messages, and use Super SU (not SuperUser), and you'll be fine.
This happened to me too so I re rooted it manually. I just followed this link:
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
Wow this is getting confusing... ive got two or more guides open both with varying methods and files to install..
if i download the new SU files and reroot, then it wipes all files ? so how does having the SU work
As to reflashing a new binary, thats what i dont want, i just want a stock set up thas rooted.
Also re terminal? it that putty ? and go into the device that way?
Mart
all the binary will do is give you root/su, that is what you want. no more, no less. youll need the supersu app too, to grant su.
simms22 said:
all the binary will do is give you root/su, that is what you want. no more, no less. youll need the supersu app too, to grant su.
Click to expand...
Click to collapse
Which binary? im really confused lol
I have SU as an APK, do i run this before rooting or do i run this apk from CWM? and then reroot using the toolkit?
Mart
Mart360 said:
Which binary? im really confused lol
I have SU as an APK, do i run this before rooting or do i run this apk from CWM? and then reroot using the toolkit?
Mart
Click to expand...
Click to collapse
the binaries i posted in post #3 http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
flash it in your custom recovery and reboot. you do have cwm recovery installed as i understand, right? that su binary is the most recent. you dont want su(superuser) you want the supersu app.
simms22 said:
the binaries i posted in post #3 http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
flash it in your custom recovery and reboot. you do have cwm recovery installed as i understand, right? that su binary is the most recent. you dont want su(superuser) you want the supersu app.
Click to expand...
Click to collapse
Yes i have those , i went into CWM and went to apply update from zip on SD card
the options i had were folders
one called clockwork mod
then a file called update zip appears, thats all iget
Its just a leap of faith now i guess, im just being cautious incase i brick the puppy
Mart
Mart360 said:
Yes i have those , i went into CWM and went to apply update from zip on SD card
the options i had were folders
one called clockwork mod
then a file called update zip appears, thats all iget
Its just a leap of faith now i guess, im just being cautious incase i brick the puppy
Mart
Click to expand...
Click to collapse
look in /data/media/0(downloads folder if you downloaded directly to your seven)
also, do you have the latest version of cwm?
simms22 said:
look in /data/media/0(downloads folder if you downloaded directly to your seven)
also, do you have the latest version of cwm?
Click to expand...
Click to collapse
:good: Done many thanks... it was in a different folder, but all seems to have gone ok, just backing up with Titanium backup.
One more daft nooby question,,,, where does Titanium backup actually backup too?
I havnt given any patch to my PC?
Mart
Mart360 said:
:good: Done many thanks... it was in a different folder, but all seems to have gone ok, just backing up with Titanium backup.
One more daft nooby question,,,, where does Titanium backup actually backup too?
I havnt given any patch to my PC?
Mart
Click to expand...
Click to collapse
they dont go onto your pc. normally they would go into the titanium backup folder, but you have an option of storing them in the cloud(i use the google drive option, then just restore from there too).
simms22 said:
they dont go onto your pc. normally they would go into the titanium backup folder, but you have an option of storing them in the cloud(i use the google drive option, then just restore from there too).
Click to expand...
Click to collapse
Again Many thanks sometimes we can be a bit slow on the uptake lol
cheers for sticking with me and seeing it through
Mart
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