Database Info

[ROM] Stock 2.1 Hero Update zip from RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe

Since some people were interested I've made a stock update zip from the RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe so you can flash via recovery.
This is just for those who want a completely stock rom to work off of or those that can't or don't want to run the RUU. If you want something already tweaked then use DamageControl. I'm not trying to start a custom rom I just did this for a couple people that wanted it.
It does not include the new hboot or radio.img included in the RUU and the system is stock except for adding busybox, patched su and sh.
To use su you need to install Superuser.apk.
Busybox is not installed by default you can do that through a terminal app or adb executing su and running "busybox --install /system/xbin".
You must be rooted and flash via Amon_ra recovery. Recommend nandroid backup and wipe/factory reset before flashing.
Here is a link to my post on how to make an update zip from the RUU.
Download link for the update/rom:
http://dl.dropbox.com/u/6022412/zen-hero_0.1b.zip
The link might be down since dropbox just suspended my public links due to excessive traffic.
Alternate download:
http://www.4shared.com/file/YqMmKAzL/zen-hero_01b.html
This is a link to my google code site where i put up some of the binaries/scripts that I use for rom making. These are linux binaries. If you download them put them in your path so you can execute them from anywhere. Also make sure you chmod them to executable. If you don't know how the google can tell you.
http://code.google.com/p/zen-droid/downloads/list
Due to recent events I just want to say that the devs here put a lot of work into getting you guys these leaked roms. They risk their credibility and their sources risk their jobs. So have some respect and remember it's just a phone.

Thank you,I'm sure a lot of people were wanting this.

What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!

Roman G said:
What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!
Click to expand...
Click to collapse
For people not running windows and for people that don't want to risk flashing hboot or the radio.img.

See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!

Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.

obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
crazy, his link says zendroid in it too
http://code.google.com/p/zen-droid/downloads/list

obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
Yea I thought that was kind of funny. Nice name for a rom though

yeah well, I thought it had a nicer ring to it than fengshuidroid.... was going for a rom which was also centered around a nice clean theme to the sense ui. I'm still making headway on the project.

Re: [ROM] Stock 2.1 Hero Update.zip
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app

theclawpr said:
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app
Click to expand...
Click to collapse
yes you need root and a recovery image

Roman G said:
See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!
Click to expand...
Click to collapse
Interesting! What is the new PRI that you have now?

raynda said:
Interesting! What is the new PRI that you have now?
Click to expand...
Click to collapse
2.10_003 I believe it's the one that damage had that no one could figure out where he got it other than the official release!

okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?

rgildoss said:
okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?
Click to expand...
Click to collapse
adb shell
cd /sdcard
flash_image recovery blah.blah.blah

smw6180 said:
adb shell
cd /sdcard
flash_image recovery blah.blah.blah
Click to expand...
Click to collapse
error
flash_image: not found

rgildoss said:
error
flash_image: not found
Click to expand...
Click to collapse
Thats because the flash images is not called blah.blah.blah

VinceOB said:
Thats because the flash images is not called blah.blah.blah
Click to expand...
Click to collapse
i know that ...lol
ever i try i can not load the damn recovery image ...
power + menu gives me a picture of the phone with ! .....
how can i load the recovery image ?
The phone is rooted but just wont take the revory image

Now this might be a stupid question, but do we need Root for this? I have a friend who's terrified of Rooting but really wants 2.1, so could he just Flash this through the Stock Recovery Image, or should I force him to Root?
Edit: NVM sorry I just read the 1st post on page 2. Told you it was a stupid question.

It seems like the flash_image command is missing.

ClockworkMod Recovery 3.0.0.5

This is the latest ClockworkMod Recovery!! Instructions to install below
Downloads At bottom of page.
I am not responsible if you brick or damage your phone... blah blah blah... NANDROID FIRST cuz u never know wut might happen XD.
Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
Download ClockworkMod Recovery 3.0.0.5
Copy the recovery.img to root of the SD card.
Boot the phone into recovery.
Open command prompt.
Change directory to the AndroidSDK directory & type the following commands:
adb shell
mount sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Method II
Flash recovery using: RomManager
Download ClockworkMod Recovery 3.0.0.5
On the SD card, go to: /clockworkmod/download/mirror.sea.tdrevolution.net/cm/recoveries.
Rename the old image there named recovery-clockwork-2.5.0.7-heroc.img to recovery-clockwork-2.5.0.7-xxx.img.
Move recovery-clockwork-3.0.0.5-heroc.img to that folder and rename it to recovery-clockwork-2.5.0.7-heroc.img.
Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
Method III
Method III
Flash recovery using: H-Boot/S-Off Only
Download HERCIMG.zip
md5: 6dcd265a51cc7090824d7f9f889b370b
Move HERCIMG.zip to root of the SD card.
Power off the phone.
Hold the Volume Down and Power buttons until the phone boots into the bootloader.
Wait for bootloader to scan and find HERCIMG.zip.
Press action to install.
The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
http://www.mediafire.com/?2gwhom1m06tbboy - ClockworkMod Recovery 3.0.0.5
http://www.mediafire.com/?u86sj1w22db8kbt - HERCIMG.zip
thanks to romrepo.info/wiki

It would be great if someone could leave some screenshots for me.. i dont have the emulator on this computer srry.

deke2010 said:
It would be great if someone could leave some screenshots for me.. i dont have the emulator on this computer srry.
Click to expand...
Click to collapse
Check in the dev section for my thread on how to install adb. You'll have it up and running in like 15 to 20 min tops
Root-Hack-Mod-Always™

laie1472 said:
Check in the dev section for my thread on how to install adb. You'll have it up and running in like 15 to 20 min tops
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Im using my dads computer and i cant install anything on it soo..

deke2010 said:
Im using my dads computer and i cant install anything on it soo..
Click to expand...
Click to collapse
You can do all of what the op posted on your phone. Just follow his instructions and you should be fine
Root-Hack-Mod-Always™

laie1472 said:
You can do all of what the op posted on your phone. Just follow his instructions and you should be fine
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
i already have it on my phone but i cant get screenshots without the emulator on the pc which i cant install cuz its my dads computer.

When I download the recovery from my phone it downloads as a txt file. Do I rename it to recovery.img and push it that way.
Sent from my DROIDX using XDA App
EDIT nevermind I did the S Off method worked perfectly.

METHOD1911 said:
When I download the recovery from my phone it downloads as a txt file. Do I rename it to recovery.img and push it that way.
Sent from my DROIDX using XDA App
EDIT nevermind I did the S Off method worked perfectly.
Click to expand...
Click to collapse
Glad you got it working. To answer the question about .txt on the phone, others have reported that using a different browser works for downloading the .img file correctly. I think they used Dolphin browser from the market.

I tried method 2 and method 3 above without success. Trying to go from 2.5.0.1 to 3.0.0.5. Attempts to boot into recovery and then reboots again and boots normally. Suggestions?

Try the ADB method?

stayclean said:
Try the ADB method?
Click to expand...
Click to collapse
I will try that now. Quotes necessary around the filename?

No, do not use quotes.

kynov said:
I tried method 2 and method 3 above without success. Trying to go from 2.5.0.1 to 3.0.0.5. Attempts to boot into recovery and then reboots again and boots normally. Suggestions?
Click to expand...
Click to collapse
don't flash the 3.0.0.5, you don't need it for GB. the reason I think people have been having so much trouble is that the recovery is overclocked, so some phones can't handle it. same thing goes for the GB rom, if it loops and hangs etc., just flash a capped 691 kernel after the rom and gapps, it *should* work.
OK NOW - TO ALL FUTURE POSTS - PLEASE DON'T, LOL.
AOSP MADE THIS RECOVERY AND IS CONSTANTLY UPDATING IT
3.0.0.5 CAN BE FOUND IN THE 2.3 GINGERBREAD THREAD
INSTALL METHODS CAN BE FOUND ON THE THREAD "READ ME" WIKI,
DIFFERENT VERSIONS CAN BE FOUND ON ROMREPO.INFO

il Duce said:
don't flash the 3.0.0.5, you don't need it for GB. the reason I think people have been having so much trouble is that the recovery is overclocked, so some phones can't handle it. same thing goes for the GB rom, if it loops and hangs etc., just flash a capped 691 kernel after the rom and gapps, it *should* work.
OK NOW - TO ALL FUTURE POSTS - PLEASE DON'T, LOL.
AOSP MADE THIS RECOVERY AND IS CONSTANTLY UPDATING IT
3.0.0.5 CAN BE FOUND IN THE 2.3 GINGERBREAD THREAD
INSTALL METHODS CAN BE FOUND ON THE THREAD "READ ME" WIKI,
DIFFERENT VERSIONS CAN BE FOUND ON ROMREPO.INFO
Click to expand...
Click to collapse
AOSP didn't make CWM.....

stayclean said:
Try the ADB method?
Click to expand...
Click to collapse
EDIT: Managed to get 2.5.0.1 back on there. Gonna leave it as-is.

What's the clock speed on this?

theimpaler747 said:
AOSP didn't make CWM.....
Click to expand...
Click to collapse
ok Koush did, I know, but the version we are using is tweaked by him.
would you correct me if I said he made his rom, because technincally google MADE it, but he did in fact tweak it,build it,compile it, for the hero.
@aiwetir - 768

Method III worked fine for me. Just follow instructions carefully, and don't forget to do "su" first (lets terminal use root privileges).
I'm curious why RomManager doesn't update the version number. I know I'm using 3.0.0.5 because of the new orange text, but RomManager still shows 2.5.0.1
Anyone?

theimpaler747 said:
AOSP didn't make CWM.....
Click to expand...
Click to collapse
Pretty sure he tweaked cwm3.0.0.5 to make it work for our phones ... I'm sure duce didn't mean he made it made it just wrong wordage lol come on Impaler. You know aosp be a tweaker to make our phones the **** lol
Sent from my HTC Hero CDMA using XDA App

il Duce said:
ok Koush did, I know, but the version we are using is tweaked by him.
@aiwetir - 768
Click to expand...
Click to collapse
Beat me to it haha ... Impaler just hating caus3 his epic isn't as awesome as our hero's hahaha jk
Sent from my HTC Hero CDMA using XDA App

Question about Rooting FP5

Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?

jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
*sigh* look around...
Sent from my SCH-I510 using xda premium

jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
Here you gotaken from my thread)
5. How to root a pure stock FP1 and make CWM stick after reboot - Turn off your phone, use ODIN to flash CWM (0302 blue latest version - http://imnuts.net/zU2jkn) with "reboot" option unchecked,
After completed, disconnect the usb cable, pull the battery, reinstall battery, hold down volume up+home+power to boot into cwm,
(if you failed to boot into cwm and your phone boot up you have to redo the process). Now flash Super user package zip (Superuser-3.0.7-efgh-signed.zip - and su-bin-3.0.3.2-efghi-signed.zip (both can be download from here (look for Gingerbread) : http://androidsu.com/superuser/
Reboot phone. Use Root explore (or Root browser lite or ES file explorer) go to /system/ect/install-recovery.sh script, tab on mount R/W button (upper top). Long press on the script and in the popup menu, select permission, unchecked all permission then save the file.
Shutdown phone, re-Odin cwm again, once done reboot, now cwm should stick. Once phone came up, to verify root on your phone, you can download "root checker basic" from the Market. If you have issue, download "superuser update fixer" app from the market and run it.(no reboot required). That's it.

Wow great help with links and everything thanks a lot
Sent from my SCH-I510 using xda premium

Just to add to this very helpfull Post, this are the problems I run into and how I fixed them so that if anyone comes up with the same issues, you have the solution:
1. Flashing CWM with odin was failing, I changed usb port, I rebooted the computer, and the problem was that I was doing it without the battery, as soon as I put the battery in the phone and tried odin, it was succesfull, so, what I think is that there is not enough power to the phone just using the usb cable and that is why it was failing to flash.
2. after I flashed superuser and su-bin files, rebooted the phone, but as soon as my phone was on, and connected to the internet, for some reason, the phone automatically downloaded and updated this two files, so I could not change the recovery sh script, my solution, disabled data, reflash cwm, and the root files, then I was able to change the permissions of the file.
I AM NOW ROOTED!!!! thanks buhohitr

ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?

jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Again, please look around...
Sent from my SCH-I510 using xda premium

jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.

buhohitr said:
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
Click to expand...
Click to collapse
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!

jorge3687 said:
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
Click to expand...
Click to collapse
Nice! glad you got it working.

I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
Click to expand...
Click to collapse
I see all the replies with answers now. Don't know why they weren't there before.

yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
I see all the replies with answers now. Don't know why they weren't there before.
Click to expand...
Click to collapse
well, since I could not get help from the experts, I just did it myself and wrote the process for other people to make it easier.

Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.

Sigh... http://forum.xda-developers.com/showthread.php?t=1832040
Sent from my SCH-I510 using xda premium

read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.[/QUOTE]

jorge3687 said:
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Click to expand...
Click to collapse
[/QUOTE]
I had already tried the above without success. CWM was overwritten each time. There was another file to delete as well somewhere in system/ect which was also supposed to prevent recovery overwriting,mbut that solution proved just as fruitless.
I got itt working through trial and error, though. As it turns out, recovery actually UNmounts system after you flash a single file, so you must REmount after each if you are flashing multiple files. I do not see this "feature" explained anywhere. Maybe this is something fundamental about Linux which has escaped me over the years of android phone ownership.
Thank you for trying to help me even though.

It unmounts for safety reasons, and it's done by the package itself, not the recovery by default. You don't want power to be pulled from a filesystem in unix when it's mounted. The real issue isn't the unmount, but the mount itself seems wonky on this phone, so depending on how the CWM package is written, there's a good chance it won't be successful when it tries to mount the filesystems. It's better to mount them yourself if you're working with a package that wasn't specifically written with this phone in mind, and you even need to mount on some that are.

[Q] official KitKat ota error

I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??

kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.

scott_doyland said:
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
Click to expand...
Click to collapse
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.

kieranc88 said:
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
Click to expand...
Click to collapse
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').

scott_doyland said:
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
Click to expand...
Click to collapse
Yeah,send it,I'll try copying it,unrooting and then trying the update

kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
And will it matter what version of the stick recovery I'm using( if there are different versions)

kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx

tee_pot said:
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
Click to expand...
Click to collapse
OK,well at the moment I'm trying out cm11 unofficial builds,I'll see how they go, I'll try the full unroot option when I restore my cwm backup and reflash stock recovery and see if that works ,as I only tried the temporary unroot option in supersu(which is probably leaving some root files behind so it can reinstall su ) if that don't work I'll flash back to stock and try again.

kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I will send file tomorrow when I'm at my PC.

kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I have attached the file /system/etc/install-recovery.sh file to this post (had to gzip it as couldnt upload when it was just called .sh)
Im not sure what the original persmissions of the file should be on your phone, but if you make it read/write/executable by everyone then should be OK I guess.
As I mentioned it'd be good if you unrooted and did a backup and extracted the file to see the contents (before copying over the file). That would first tell you for sure if the file does revert back to original or if it stays as a 'superSU' file when you unroot.
If its reverted back to original then my theory is wrong anyway so no need to copy over the file.
Re the stock recovery type/version being different from what is expected - I dont know if that makes a difference to the OTA working or not. Its an interesting question though so I may do some googling and find out.

I also have a UK retail stock recovery.img (taken with CWM) (my phone is 16GB from phones4u). So if you want that you can have it. Should rule out the recovery type as a problem.
FYI the install-recovery.sh original file actually flashes a new stock recovery when an OTA is performed. At least if you look in the comments of the file I attached above thats what it says.

H91810i rooted with recowvery!

The latest update, it seems, can be rooted using the recowvery method. Dirtycow was patched by Google in a Dec. 5 security patch, but it seems LG didn't include that in their latest security update, which was created Dec 1! In any case, my phone is rooted with TWRP, and working just fine. So, for now we can still root with the update! I'd also like to point out, that this means we now have an official KDZ released version of rootable stock to roll-back to with LGUP!

Glad I forced ya to do it huh

How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error

ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.

Norcal232001 said:
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.
Click to expand...
Click to collapse
Ive been using easyrecowvery but ive tried that also. Maybe I messed up somewhere during the command line process thingy. Ill give it another go. Thanks

curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...

dimm0k said:
curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...
Click to expand...
Click to collapse
I was on 10i last week after i got phone back from service. I flashed NotSoStock Rom which said i was on the 10d base. Then flashed Overdrive Rom which put me back to 10i. I didnt have any problems switching basebands within custom roms if that helps.

ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
I have same error even I tried to enter recovery using "adb reboot recovery"
---- edit ----
Done.
You must do it manually according to the instructions
https://github.com/jcadduono/android_external_dirtycow#running
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Note: make sure you rename your TWRP to twrp.img, and put SuperSU file into memory card (your TWRP cannot open internal storage).

how do you unroot and go to full stock

dudeawsome said:
how do you unroot and go to full stock
Click to expand...
Click to collapse
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.

mingkee said:
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.
Click to expand...
Click to collapse
Wil it remove twrp also and have you tested it

dudeawsome said:
Wil it remove twrp also and have you tested it
Click to expand...
Click to collapse
100% bone stock