Develop Bugs

Does rooting only removes the ability for OTA updates?

Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4

Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app

You just need to have the stock recovery to receive OTAs.

Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4

Takes 10 seconds to reflash the stock recovery.

UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.

Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.

Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?

It was common on other platforms I've used, but I don't know about here.

Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.

phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.

TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2

nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.

Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)

phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?

Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.

If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?

[GUIDE] INSTALLING TWRP on LGG2 (VZW, AT&T, TMobile, KT, d802, others) [UPDATED]

NOTE! This guide is extremely old and likely isnt up to date. I cannot maintain it any more. If anyone is willing to take it over and fix any issues, let me know!
TOOK THE OTA AND GOT STUCK IN RECOVERY LOOP? DERP, DONT TAKE OTAS, DUH. ANYWAYS, IF YOU CANT GET INTO DOWNLOAD MODE AFTER OTA, DO THIS
GUIDE:
Thanks to Bliss who worked the exploit into Loki, Dees_Troy built TWRP for us, djkinetic, Huskehn, and myself tested.
So good news folks! TWRP is now working on LG G2 thanks to an updated loki patch from bliss. Note that Loki patch is not necessarily an unlocked bootloader, but for the end user there is basically no difference. We can flash kernels (when they exist) roms (when they exist) recoveries etc etc. A full bootloader unlock could come someday, but this is all you will need until then.
First off, if you have issues with ADB not connecting, try THESE DRIVERS
The install is super simple, and you have two or 3 options.
Download the img for your device:
AT&T IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Verizon IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
TMobile IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Korean Telecom IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
d802 IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
For other models, click HERE and scroll down to find the files beginning with d2, and see if any of the folders sound like your model.
NOTE FOR THESE DOWNLOADS! READ ME! UPDATE! Ok, so if you look in the download page for your device and you are getting a zip file, this is a flashable zip, but it cannot be treated the same as an IMG file in this guide. You need to flash an older one that is a .img file, and then use that to flash the newer zip.
YOU MUST ALREADY BE ROOTED! follow This guide to do so if you arent. BE AWARE THAT THIS ROOTING METHOD ONLY WORKS BEFORE TAKING THE OTA. IF YOU ARE UPDATED AND UNABLE TO ROOT, FOR NOW THE ONLY WAY IS TO FLASH BACK TO STOCK AND ROOT BEFORE THE OTA, THEN TAKE THE OTA, THEN INSTALL TWRP
NOTE THAT ALL GUIDES BELOW ARE REFERENCING THE VZW img file. Be sure to replace it with whatever version you downloaded!
ABSOLUTELY DO NOT FLASH ANYTHING NOT MADE FOR YOU PHONE SPECIFICALLY!
OPTION 1 RECOMMENDED The way I tested it in #lg-g2 Possibly safer as loki runs some safety checks first. Download loki from github here Click download zip on the right. and go into the bin folder of the zip. push loki flash and the img like so:
Code:
adb push loki_flash /data/local/tmp/loki_flash
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
exit
adb reboot recovery
-------------------------------------------------------------------------------------
OPTION 2 via dd. Push just the recovery img like this:
Code:
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
dd if=/data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
--------------------------------------------
OPTION 3 easy, untested (as of time of writing) install it from goomanager on the phone! This aparantly does work bu you have to manually browse to the file or something... anyone who's tried care to clarify?
I tried and cant figure out where you find the recovery. I recommend Option 1 or 2
----------------------------------------------
Troubleshooting:
If you get "Failed to open aboot for reading." when following method 1, Be sure you have the # prompt, not $. If you rooted properly you should alutomatically have # in shell, but if not just type su to get it. then run the flashing command.
If you had confusion based on the pushing steps because the two img names listed in the command were different, my bad. the filenames changed while I was writing from test version to final, I missed replacing the first name in the commands. Look at the post again as it is fixed now.
If adb reboot doesnt work, make sure that "exit" command fully exited you out of the adb shell prompt. you should be at standard command prompt for that. type exit again if you arent, or heck just open a new command prompt
-------------------------------------------------------------------------
Be happy with what you have, so soon. Be sure to thank all the devs and donate to them![/SIZE][/U]

Got stuck trying to send the recovery to my ATT G2, replacing verizon files, renamed all the files including recovery file to RECOVERY and got it running. TWRP up and running. WOOOHOOO, let the roms begin lol

What? You mean no one cares whether or not I get this device only what @scrosler gets?
I kid, I kid.
Nice work on getting TWRP on the device. Now it is time for something truly awesome to happen, now that this first step has been taken.
Thread Cleaned

can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?

Walter21026 said:
can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?
Click to expand...
Click to collapse
I'd like to know this as well, please

This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?

If this works as the loki for the S4 did, then we will have access to flash everything. Kernel, modem, and ROM. There are no boundaries.
Sent from my LG-D800 using Tapatalk 4

JustusIV said:
This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?
Click to expand...
Click to collapse
Currently this is a work around. Bootloader is still locked up tight

Goo says no recovery found for this device.
Sent from my LG-D800 using XDA Premium 4 mobile app

Basically the bootloader no longer matters except for the purity of beating them at their own game. I am sure there are other benefits, but crackflashers will have our fix
Sent from my LG-D800 using Tapatalk 4

i tried thru goomanager i went in to the install open script and it says no recoveries are available

HUGH Thanks to everyone that made this possible! :victory: You guys are the reason I stick with android and never worry about buying the latest devices.
Patience paid off. :highfive:
Now Bring on the ROMS!!!!!:laugh:

Doesn't work for me. I get a "cannot stat 'g2vzw.img': No such file or directory"

Do I need to root before this
Nvm I'm dumb
Sent from my VS980 4G using XDA Premium 4 mobile app

Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....

Han Solo 1 said:
Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....
Click to expand...
Click to collapse
i was about to try, then saw this when reading through it. i don't get it.

So in theory an OTA will patch this just like the S4 so be careful with updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.

jayochs said:
i was about to try, then saw this when reading through it. i don't get it.
Click to expand...
Click to collapse
Hopefully the OP will chime in here soon.

JustusIV said:
So in theory an OTA will patch this just like the S4 so be careful updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.
Click to expand...
Click to collapse
Stop by the store or CS they will push it up for you no problem. They did for me just ask nicely
Sent from my LG-D800 using XDA Premium 4 mobile app

Han Solo 1 said:
Hopefully the OP will chime in here soon.
Click to expand...
Click to collapse
i'm also frekaing out because this is the first i heard about this chinese root method possibly having spyware..that's the method i used, and despite the fact i deleted their superuser app immediately, i'm wondering if i should go back to stock and do all that bs just to root again with the new method..

Ota 5.28.605.2 ota

Just got it on my htc one... for use on stock rom/stock recovery....
https://www.androidfilehost.com/?fid=23622183712466856
RUU coming too
http://forum.xda-developers.com/showthread.php?t=2867643

Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?

rickyjohn said:
Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?
Click to expand...
Click to collapse
If you are s-on, you can't flash anything custom or stock. You will need to root and s-off first. Or you could take the ota if all you want is the update. If you want to get some customization on there...you should do some reading through the threads. Things are a bit different since a few years ago and this phone doesn't have an external sd card...
Sent from my Lunar Ecliptic One.

rickyjohn said:
Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?
Click to expand...
Click to collapse
First link is 100% stock and will work on stock recovery. Just place it on the phone storage or SD and boot to stock recovery. Choose the appropriate "apply update from" and then point to that file.
brymaster5000 said:
If you are s-on, you can't flash anything custom or stock. You will need to root and s-off first. Or you could take the ota if all you want is the update. If you want to get some customization on there...you should do some reading through the threads. Things are a bit different since a few years ago and this phone doesn't have an external sd card...
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse

every time i try to get into the recovery menu i just get a picture of the phone with a red triangle and exclamation point.

Any idea if towelroot works with this update? I noticed that the update notes on the vzw website says "Device root vulnerability issue has been resolved"
Sent from my HTC6500LVW using Tapatalk

rickyjohn said:
every time i try to get into the recovery menu i just get a picture of the phone with a red triangle and exclamation point.
Click to expand...
Click to collapse
That is your stock recovery. Stock recovery is not meant to go into like custom ones. It's used for ota's, factory resets, and that's about it.
Sent from my Lunar Ecliptic One.

got "invalid operation" when trying to update with the zip file, it is on device storage, any ideas? does the zip need to be renamed?

rickyjohn said:
got "invalid operation" when trying to update with the zip file, it is on device storage, any ideas? does the zip need to be renamed?
Click to expand...
Click to collapse
When flashing an OTA everything has to be bone stock. If you have stock tethering enabled, Xposed Framework installed, or files missing from /system/apps, it will fail.

That's a bummer. I'm totally stock. Just changed fonts, that's it. Guess it just won't go. thanks

I restored stock recovery and stock hotspot and the OTA still won't install properly -- I'm not sure what I'm missing. Is there any way to flash the OTA when rooted without wiping my phone?

Ovy13 said:
I restored stock recovery and stock hotspot and the OTA still won't install properly -- I'm not sure what I'm missing. Is there any way to flash the OTA when rooted without wiping my phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485319
Flash in trwp the full odex ROM. I don't know if updating via ota while rooted will work. I know unlock and s-off doesn't matter from personal experience.
Sent from my One using XDA Free mobile app

Uzephi said:
http://forum.xda-developers.com/showthread.php?t=2485319
Flash in trwp the full odex ROM. I don't know if updating via ota while rooted will work. I know unlock and s-off doesn't matter from personal experience.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
In the past, simply restoring stock recovery, updating normally, and then flashing a custom recovery was enough. Doesn't seem to work this time, or there's simply some customization I've forgotten about.

If I'm not mistaken, just the presence of the su binary can be enough to abort an official ota. If you have the official OTA zip and attempt flashing through the stock recovery and it fails, the error message should give some indication of the problem. The script runs a check on the contents of /system and if anything is off it will fail.

pastorbennett said:
If I'm not mistaken, just the presence of the su binary can be enough to abort an official ota. If you have the official OTA zip and attempt flashing through the stock recovery and it fails, the error message should give some indication of the problem. The script runs a check on the contents of /system and if anything is off it will fail.
Click to expand...
Click to collapse
Su is fine. It simply won't work afterwords. Any other system changes will cause it to fail though.

dottat said:
Su is fine. It simply won't work afterwords. Any other system changes will cause it to fail though.
Click to expand...
Click to collapse
So I have TWRP, root, s-off, and XPosed installed. Verizon sent me the OTA update, but I need to return everything to stock before I do anything with the update? I'm a little dense here...

PiperCub49 said:
So I have TWRP, root, s-off, and XPosed installed. Verizon sent me the OTA update, but I need to return everything to stock before I do anything with the update? I'm a little dense here...
Click to expand...
Click to collapse
Disable xposed. Flash stock recovery and take the ota. Then flash custom recovery via Fastboot and flash su.zip in Twrp.
Assuming of course you made no other /system mods other than root and xposed.

Re-flash stock recovery. GET RID OF TWRP

Hello, everybuddy, i recently installed twrp via flashify on my g3. Now that i see android L is being released, i would like to get the OTA for that so i have to get back to stock recovery. Can i just flash it via flashify? and if i can what do i flash? and will it be the same as it was before so i can get OTA? im also rooted, will i get eh OTA if i have root? i know it will kill it but i dont care about that, i just want to make sure ill get the OTA

Your best bet will probably be to follow this guide here:
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
This will take you back to stock. Getting rid of TWRP is not enough to get OTA to successfully install. You also need to unroot and restore any apps that you may have frozen or removed such as CarrierIQ. Additionally remove xposed if running. Again, instead of going through that trouble, it would be easier to get restore to stock since it's a quick flash.
Note: I would not necessarily be in a hurry to take the OTA. It's possible that it may not be easy to obtain root. Thus I would suggest waiting till one of the devs has had the opportunity to review and confirm that root can still be obtained.

cbb77 said:
Your best bet will probably be to follow this guide here:
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
This will take you back to stock. Getting rid of TWRP is not enough to get OTA to successfully install. You also need to unroot and restore any apps that you may have frozen or removed such as CarrierIQ. Additionally remove xposed if running. Again, instead of going through that trouble, it would be easier to get restore to stock since it's a quick flash.
Note: I would not necessarily be in a hurry to take the OTA. It's possible that it may not be easy to obtain root. Thus I would suggest waiting till one of the devs has had the opportunity to review and confirm that root can still be obtained.
Click to expand...
Click to collapse
i havent removed any apps. just used twrp to check out the pac rom, which was awsome. so i cant just flash the stock recovery?

chronichemp said:
i havent removed any apps. just used twrp to check out the pac rom, which was awsome. so i cant just flash the stock recovery?
Click to expand...
Click to collapse
You still running pac rom? If so OTA will not work. However if you already flashed back to stock and are just rooted, then yes you can unroot and flash back the stock recovery. I believe the stock recovery can be found somewhere here. If I find a link I will post.

cbb77 said:
You still running pac rom? If so OTA will not work. However if you already flashed back to stock and are just rooted, then yes you can unroot and flash back the stock recovery. I believe the stock recovery can be found somewhere here. If I find a link I will post.
Click to expand...
Click to collapse
thanks thatd be great! yes i nandroided back to my original state. just wanted to see how pure android looked, and it was gorgeous! but i want to save the experience for android L.

chronichemp said:
i havent removed any apps. just used twrp to check out the pac rom, which was awsome. so i cant just flash the stock recovery?
Click to expand...
Click to collapse
Yes, you can restore the stock recocovery.img using Flashify.
See link for stock d851 "c" & "m" partitions:
http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions

AndroidUzer said:
Yes, you can restore the stock recocovery.img using Flashify.
See link for stock d851 "c" & "m" partitions:
http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions
Click to expand...
Click to collapse
Thanks alot man! The 10m partition i should use because thats the newest one right? Flashed and everythings back the way it was.
Sent from my LG-D851 using XDA Premium 4 mobile app

Do you guys know where i could find the stock recovory image for the d852g ? If anyone can post a link it would be much appreciated..

AndroidUzer said:
Yes, you can restore the stock recocovery.img using Flashify.
See link for stock d851 "c" & "m" partitions:
http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions
Click to expand...
Click to collapse
Hi, I am looking for flashing stock recovery on my LG G3 Sprint LS990. I believe the same method will work. I am currently running on stock ZVB ROM rooted and TWRP installed as recovery. In the download folder for LS990-ZVB http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVB, there is no recovery image file, but in ZVA folder there is. I am just wondering if I can flash ZVA folder's recovery image using Flashify to my ZVB ROM LS990 and if that will work.
My LS990 is rooted and currently have TWRP. i get secure boot error when the phone reboots after accepting Android updates installation that come automatically. I believe installing stock recovery will resolve this issue and allow to install Android updates I do not want to going back to stock completely, that will unroot my phone and again I have do all these staffs.
Anyone can help to advise, will be appreciated. Thanks.

How Autorec works

Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.

Simone98RC said:
Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.
Click to expand...
Click to collapse
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have

RapHaeL_4_4_4_ said:
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have
Click to expand...
Click to collapse
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?

Simone98RC said:
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?
Click to expand...
Click to collapse
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.

If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone

ypsmav said:
If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone
Click to expand...
Click to collapse
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
RapHaeL_4_4_4_ said:
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.
Click to expand...
Click to collapse
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?

Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone

ypsmav said:
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone
Click to expand...
Click to collapse
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
RapHaeL_4_4_4_ said:
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Click to expand...
Click to collapse
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.

Simone98RC said:
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.
Click to expand...
Click to collapse
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.

NatusVincere said:
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.
Click to expand...
Click to collapse
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid who won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).

Simone98RC said:
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid which won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).
Click to expand...
Click to collapse
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one

bender_007 said:
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one
Click to expand...
Click to collapse
Thanks much for the specification: since I want to flash a firmware newer than 20H, I need latest Autorec to work with that [emoji106]
https://www.androidfilehost.com/?fid=24052804347817962
After all you are the official Autorec developer

^ yap, flash safely, after that flash fulmics
That's how I was using it
Plus thx to all people involved in here for answering and helping out
Poslano sa mog LG-H815 koristeći Tapatalk