Develop Bugs

[FAQ]Installing Verizon 4.0.4 OTA, Rooting, Etc.

There are many questions, and they are all being answered. That said, they are spread across 34324123213132 threads. So lets create a thread where they are all asked in one place.
Q: Where do I get it?
A: The mods refused to sticky this most valuable thread for me, but you can find it here:
http://forum.xda-developers.com/showthread.php?t=1482650
Make sure you get the right one.
Q: Where is the changelog?
A: This is not official yet. Hence, no official changelog. There is an unofficial one here by kangxi:
http://forum.xda-developers.com/showthread.php?t=1481044
Q: Can I install the 4.0.4 OTA over 4.0.3?
A: Of course not. It only updates stock 4.0.2. That means you must return to stock 4.0.2 to flash it, or use some packaged rom from the developer forum that is at 4.0.4.
Q: I keep getting an error 7 when trying to flash. What am I doing wrong?
A: You are not stock 4.0.2 and a patch check or assert is failing. If the file it fails on is mentioned, you can replace that file with a stock version and cross your fingers. Or you can remove the patch check and installation from the installer-script in the ota zip. Of course, then you must use clockwork recovery or the likes to install. Also, make sure your recovery (if non-stock) is up to date.
Q: Do I need to be rooted to install this update?
A: Not entirely. You must be unlocked, but you can then temp boot an adb rooted kernel and place the update in /cache. When you reboot to stock recovery, you are unrooted and back to stock. That leads into how (there are a few ways).
Recommended:
Code:
Download the pre-rooted 4.0.2 kernel:
[url]http://www.box.com/s/xf6bz8f1j004bk0zc78a[/url]
Enable usb debugging
adb reboot bootloader
fastboot boot newboot.img
---once back up----
adb remount
adb push 659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip /cache
adb reboot recovery
install from cache
choose the ota zip.
flash
Alternative method from williamthegoat:
Code:
Enable usb debugging
Put ota update on your sdcard
Temporary boot clockwork recovery. I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
adb reboot bootloader
fastboot boot recoveryimagename.img (use the correct name)
---once in recovery---
Flash ota.
Note: this method contains no signature checking for the ota to verify its validity.
Q: Will this break root?
A: Yup.
Q: How do I root again after the update?
A: You need to install clockwork mod recovery.
I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
Also grab the pre-rooted 4.0.4 kernel from here:
[url]http://www.box.com/s/dh5b2vjg13qm2uodfysk[/url]
To install clockwork (permanent) and flash Superuser:
adb reboot bootloader
fastboot boot 404boot.img
--once back up---
adb remount
adb shell
mv system/etc/install-recovery.sh system/etc/install-recovery.bak
adb reboot bootloader
fastboot flash recovery recoveryimagename.img (use the correct name)
fastboot reboot
---once back up---
adb reboot recovery
flash su.zip
To install Superuser temporarily and flash Superuser:
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
adb reboot bootloader
fastboot boot recoveryimgname.img (use the correct name)
---once in recovery---
flash su.zip
Q: I am on xxx's aosp rom? How do I update?
A: Go back to 4.0.2 stock or use one of the prepackaged, precompiled roms in the dev section. At this time, 4.0.4 is not on the aosp repos.
Q: What about GSM users?
A: I am sure they will see it soon, if not by ota, then by aosp.
More will come as I see them needing to be answered.

confused
how can i get here from AOKP......? LULZ

adrynalyne, why didn't you predict my <insert user error here> ?
Sorry, I had to get in before the flood of "you broke my phonez!!" posts.

Thanks guys. Always nice to have input from the IRC crowd

Will this work on my Charge?

Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?

sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
What I posted, works 100%.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
adrynalyne hacked a new version that works on 4.0.4.

matt30 said:
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
It will still receive updates from the market as well.

matt30 said:
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
Cool, thanks.

Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?

Se7enLC said:
Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?
Click to expand...
Click to collapse
Nope. Its exactly what I meant. There is gui root, via Superuser, and there is adb root, via kernel.

I updated by unlocking, temp booting CWM, and updating through there. Either way works

williamthegoat said:
I updated by unlocking, temp booting CWM, and updating through there. Either way works
Click to expand...
Click to collapse
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.

adrynalyne said:
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.
Click to expand...
Click to collapse
Oh, seriously? Should I go back to 4.0.2 and do it the other way? Does it make a difference? I still want to be getting OTAs and what not.

I wouldn't worry about it. I am just the paranoid type.

I got it to work, but trying to flash the update using the factory recovery would just give me the error with the android belly open with the !. I just moved it to the sd card then and used the alternative method (without verification) and it worked great. Thanks for everything - I really wanted to check this out. We'll see how long I stay on it though.

Thanks for the su file adrynalyne! I flashed it through cwm and it worked like a charm.
Sent from my Galaxy Nexus using xda premium

Can someone please explain this line and what goes in the image name spot?
fastboot boot recoveryimagename.img (use the correct name)
I tried the recommended upgrade and got the same as the person a few posts above "flashed the update using the factory recovery would just give me the error with the android belly open with the !"

following the recommended install way, i too get the android with red exclamation when trying to adb reboot recovery; after pushing the update into /cache.
Any suggestions?

LS980 ZVE OTA Update Zip and ZVE TOT File Download

thanks to @NSTar1 for getting the file name...
and thank you to the anonymous donor that sent me the ZVE TOT file to share!!
ZVE TOT file here: LS980ZVE_03.zip
Use this to go directly to stock ZVE then root with Stump. ZVE is now the suggested firmware for every Sprint G2 owner who wants to run on stock. If you are on stock ZVD and just want to manually flash the OTA update instead... keep reading below.
ZVD -> ZVE update can be DOWNLOADED HERE.
Zip can be flashed thru stock recovery (don't try to take OTA with TWRP installed)... If taking OTA from ZVD -> ZVE and you are rooted and also want root in ZVE you must unroot completely before taking OTA and then reroot using Stump! If you do not unroot first, you risk root not working properly when you boot into ZVE.. and Stump will detect you as already rooted and will not attempt to run. To avoid this just be sure to fully unroot by opening SuperSu and going into the Settings/Options and selecting the uninstall root option. Then reboot. Then continue with the OTA.
Directions:
1. Remove USB cable from phone.
2. Power phone off.
3. Press and hold volume down + power until you boot into stock recovery.
4. Select "update with adb"
Rename edde6cf75ecbda8e54a279c5e41a564bed335b6b.ls980zvd_19-ls980zve_03_update.zip file into ls980zvd_19-ls980zve_03_update.zip
Code:
adb sideload LS980ZVD_19-LS980ZVE_03_update.zip
sure there are other ways to manually update... This is just one.
Be sure to unroot before taking OTA then root with Stump after.
Alternate Directions to skip using ADB:
1. Must be rooted... stick OTA zip file in the /cache directory
2. Unroot completely (install SuperSu then use SuperSu settings for full unroot)
3. Power off and boot into stock recovery (vol down + power)
4. Select the Update from cache option... then select the update zip you placed in /cache
OTA Security Rundown:
There was a "security patch" included with this update...
I've confirmed ZVE has blocked IORoot (DATROOT method) properly. ZVD blocked "reboot into recovery" but you could still manually flash DATROOT.zip.
TowelRoot has also been blocked. All new updates from any phone should be blocking futex at this point so this came at no surprise.
PurpleDrake root method for G3 and other LG's does not work on this model.
Stump root the only other LG root left and is confirmed to root ZVE - GET STUMP HERE
Stump root will not run if it detects su/daemonsu files.. even if root is broken. Be sure to unroot before taking ZVE or you will get stuck with broken root and Stump will not run... your only option will be to flash the ZVE TOT and start over fresh.. then root with Stump.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ZVC -> ZVD OTA can be DOWNLOADED HERE​
Click to expand...
Click to collapse
hi

You sir are pure greatness!!

autoprime said:
✓✓
Click to expand...
Click to collapse
The file seems to be gone, same for the screen capture

I had ZVD, root, and TWRP. Root was done via AutoRec, and I also had Dorimanx kernel to restore Knock On. After doing the official OTA process, phone boot loops into TWRP. I'll attempt to restore/etc.

hunterintustin said:
The file seems to be gone, same for the screen capture
Click to expand...
Click to collapse
Looks like the filename needs to be capitalized. This links works:
http://android.clients.google.com/p...4bed335b6b.LS980ZVD_19-LS980ZVE_03_update.zip
- 007

"update 3*
ok rather than waste any more time.. just gonna tot back to zvc (can confirm downgrading still works)
then will take ota's up to a 100% stock ZVE. i will then try to root with stump. "
How did you do it to begin with?
There's no way to flash this in TWRP yet correct? So the only way to take it is to tot back and then update right? I saw someone that was rooted and running custom rom/kernel tried to install the update and boot looped but that's to be expected.

If you try to update with custom recovery you will have to tot to get your device to boot.
Taking OTA with custom recovery will disable booting into Android. Unless someone modifies this and makes it flashable you will have to tot and take updates.

rootlinux said:
If you try to update with custom recovery you will have to tot to get your device to boot.
Taking OTA with custom recovery will disable booting into Android. Unless someone modifies this and makes it flashable you will have to tot and take updates.
Click to expand...
Click to collapse
I might .tot and take updates once someone confirms that stump root will work with ZVE.

barleysoda said:
"update 3*
ok rather than waste any more time.. just gonna tot back to zvc (can confirm downgrading still works)
then will take ota's up to a 100% stock ZVE. i will then try to root with stump. "
How did you do it to begin with?
There's no way to flash this in TWRP yet correct? So the only way to take it is to tot back and then update right? I saw someone that was rooted and running custom rom/kernel tried to install the update and boot looped but that's to be expected.
Click to expand...
Click to collapse
I forget how I rooted with ZVC/D to be honest.. but I had confirmed working root before the OTA. Took the OTA.. su and daemonsu remained on the phone yet I could not get a root shell. IORoot is blocked. TowelRoot is blocked. Purpledrake doesn't work. Stump root would try to run but then detect the phone was rooted (it saw su and daemonsu in /system/xbin).
So I just used TOT to get back to ZVC... took ZVC -> ZVD OTA... took ZVD -> ZVE OTA. Ran Stump. Stump worked.
I am not 100% sure if it was just a fluke with me or what... I would say it is risky to take the OTA while rooted and expect to keep root. It may work.. it may not. It WILL work if you UNROOT first.. take OTA.. then root with Stump.
AFAIK, there is no way to flash the OTA with TWRP... but I haven't tried. Though if you have TWRP installed then you would have the downgraded bootstack that works with Loki... so that would not work with the patches in the OTA zip file. They would have to be removed... so only System gets patched.

rootlinux said:
If you try to update with custom recovery you will have to tot to get your device to boot.
Taking OTA with custom recovery will disable booting into Android. Unless someone modifies this and makes it flashable you will have to tot and take updates.
Click to expand...
Click to collapse
If I tot back to ZVC and then run the ZVC to ZVD OTA and then the ZVD to ZVE OTA is there a way to get TWRP back once on ZVE or am I stuck with stock recovery?
EDIT* Has anyone that has tot and then updated to ZVE and then root with Stump tried Autorec to install TWRP?

barleysoda said:
If I tot back to ZVC and then run the ZVC to ZVD OTA and then the ZVD to ZVE OTA is there a way to get TWRP back once on ZVE or am I stuck with stock recovery?
Click to expand...
Click to collapse
barleysoda said:
If I tot back to ZVC and then run the ZVC to ZVD OTA and then the ZVD to ZVE OTA is there a way to get TWRP back once on ZVE or am I stuck with stock recovery?
Click to expand...
Click to collapse
you would need to downgrade your bootstack and patch your boot.img (run autorec) to get TWRP installed... tho that has yet to be confirmed.
if you plan on not flashing any aosp-type roms and just want a twrp to make backups and flash mods in.. I may have something for you later tonight or tomorrow

autoprime said:
you would need to downgrade your bootstack and patch your boot.img (run autorec) to get TWRP installed... tho that has yet to be confirmed.
if you plan on not flashing any aosp-type roms and just want a twrp to make backups and flash mods in.. I may have something for you later tonight or tomorrow
Click to expand...
Click to collapse
Thanks Prime, I don't run ASOP roms but I do run the stock ones and 2faced ZVD. I am waiting to see if autorec works with ZVE so that I can get TWRP back and mostly run backups, mods and stock based roms.

I am running ZVD stock rom, rooted, wifi tether mod and SIM unlock mod. Can I just run this update zip and keep everything all that? Also, does this update like Windows would update (keeping all programs and settings) or does this perform a full wipe?

ChrisFSU said:
I am running ZVD stock rom, rooted, wifi tether mod and SIM unlock mod. Can I just run this update zip and keep everything all that? Also, does this update like Windows would update (keeping all programs and settings) or does this perform a full wipe?
Click to expand...
Click to collapse
If you are rooted you need to unroot.
If you have a custom recovery it will probably crash your device.
If you have lots of mods or removed some important files it may crash your device.
Best thing to do is back up your device, move backup to PC.
TOT back to stock then take ota updates. No one has reported success with root on ZVE so I would hold off.
If you can gain root then run autorec and move backup back to device.
Restore data partition only as a system restore will effect the updated files and cause issues.
Just my thoughts on it.

Sounds easy enough.

rootlinux said:
If you are rooted you need to unroot.
If you have a custom recovery it will probably crash your device.
If you have lots of mods or removed some important files it may crash your device.
Best thing to do is back up your device, move backup to PC.
TOT back to stock then take ota updates. No one has reported success with root on ZVE so I would hold off.
If you can gain root then run autorec and move backup back to device.
Restore data partition only as a system restore will effect the updated files and cause issues.
Just my thoughts on it.
Click to expand...
Click to collapse
great advice from top to bottom.. except where you mention no one reporting ZVE root. In OP I mention I have confirmed root with Stump.
but as you said.. you should unroot first. must have stock recovery. all system mods(including tether) must be reversed or the system check will fail before the OTA even tries to patch in the update. SIM unlock should be fine.. unless u edited the build.prop.. if so you must put the build.prop back to how it was exactly.
or u can tot back to zvc.. then ota to zvd then zve then root.
the update works by checking your system partition to make sure it's untouched. the updates are patches... so the original file must be exact for the patch to work. this is why OTA fails if you change system files... it sees an md5 of one of the files is bad and aborts the update before the patching even starts.
after system is confirmed to be perfect and match all md5 sums.. system gets patched.. then recovery and boot get flash.. then the bootloader and modem gets updated. OTA.. data does NOT get wiped. but if you tot back to zvc it WILL get wiped.

How can i update this via sd card? I put it on the internal memory and it still won't show up when I select that option.

_Epic said:
How can i update this via sd card? I put it on the internal memory and it still won't show up when I select that option.
Click to expand...
Click to collapse
not sure if that works... you could put it into /cache and choose that method tho. root would be needed of course.

autoprime said:
not sure if that works... you could put it into /cache and choose that method tho. root would be needed of course.
Click to expand...
Click to collapse
Stock recovery gives me the option to install via sd card. It also gives me a install via cache. and then the adb method. I guess I will just wait to automatically receive the update. I can't seem to get ADB to ever work on my computer.

_Epic said:
Stock recovery gives me the option to install via sd card. It also gives me a install via cache. and then the adb method. I guess I will just wait to automatically receive the update. I can't seem to get ADB to ever work on my computer.
Click to expand...
Click to collapse
right.. but i think it wants external sdcard.. which we dont have. that.. or the file needs to be named something specific.. maybe just "update.zip" ?
you arent rooted? if you root you can use root explorer or es file explorer to put the update in /cache/ and then you can update without adb. or you can step your adb game up! comes in handy sometimes.

[Rogers/Fido] Lollipop Update Issues/Solutions

Rogers released the OTA update for Canadian M8 today, Feb 3. My M8 was rooted, and I previously modified some files. As a result, I encountered errors during the update. The following is what I did to resolve the problems and successfully updated to Lollipop. Please be aware that my data was completely wiped in the process, and so remember to backup important files.
First of all, when your OTA update process failed, you would see the green triangle in recovery turned to red. At that point, you should hold the vol+ button, and tap once on the power button. It will show an error log.
Error 1 - Unexpected content
The update checks for integrity of the current files, and would report error and stop when it detected any system files that had been modified. Please note that just because your M8 is rooted, you still may not get this error, as it depends on whether any files were modified after root. But if it the update ran into this problem, you would see the following error message:
Verifying current system...
"___(some file name)____" has unexpected content
Solution to Error 1 -
One could try to restore individual file back to stock, but I chose to flash the entire rom back to stock. For Rogers, there is no RUU file, and so I could only use a TWRP nandroid image. This is the procedure I followed:
1. Using this toolkit, unlock bootloader, and flash to install TWRP recovery. I used the custom recovery option, to install the latest TWRP (2.8.4.0; link can be found in my 2nd post below);
2. Restore to the 3rd TWRP image with HBoot 3.19 in this post,
3. Flash back stock recovery (*must be recovery from 4.4.4 or 5.0.1. If not, you will run into Error 2 below)
I use the recovery embeded in the 5.0.1 OTA update file downloaded. According to this post, it is down by:
downloading the OTA file; when it ask to install, select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img
Error 2 - Outdated recovery*
Prior to the loading the updated rom, the installation software checks the version of the existing boot loader. It is expecting the version from either Android 4.4.4 or 5.0.1. If one of these is not found, you will get the following error:
Package expects build fingerprint of htc/rogers/wwe/htc_m8:4.4.4/KTU84P/401507.4:user/release-keys or htc/rogers_wwe/htc_m8:5.0.1/LRx22C/4463267.2:user/release-keys; this device has htc/rogers_wwe/htc_m8:4.4.2/KOT49H/318414.17:user/release-keys.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The solution is to simply update the recovery from the OTA zip file as described above. Make sure your bootloader is unlocked first.
[Update] Alternative to doing the OTA update to Lollipop, here is the TWRP nandroid backup with Lollipop 5.0.1 for Rogers.
To gain root after Lollipop, go directly to the next post.
Finally, you could also change recovery back to stock recovery for 5.0.1 (attached in the nandroid backup above).

Rooting lollipop
After updating to Lollipop, you could re-root it using the same method as in kitkat. However, make sure you use the latest version of TWRP and SuperSU:
openrecovery-twrp-2.8.4.0-m8.img (link) and
UPDATE-SuperSU-v2.45.zip (link)
The M8 Toolkit available in the xda forum still works in helping me to flash the custom recovery.

Any requirements to flash the stock recovery?

MarwanSamirIbraheem said:
Any requirements to flash the stock recovery?
Click to expand...
Click to collapse
For an OTA? Yes. You need stock recovery.

xunholyx said:
For an OTA? Yes. You need stock recovery.
Click to expand...
Click to collapse
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.

Must be fully stock, right recovery installed. No modified system files, deleted or freezed apps.

MarwanSamirIbraheem said:
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.
Click to expand...
Click to collapse
Unlocked bootloader needed. S-on is fine.

Also rooted is ok.

ikeny said:
Unlocked bootloader needed. S-on is fine.
Click to expand...
Click to collapse
It's already Unlocked bootloader. BTW the software status: Modified .. not official
and there is something strange. I tried to install the Lollipop OTA with ADB and it didn't work but after this the information in the bootloader changed to: os: 4.16.401.10 15 but the software is 4.4.4 .. How?!

MarwanSamirIbraheem said:
I want to install OTA. But when it begins to install it boots into bootloader and nothing happen.
so I want to install stock recovery to flash this OTA. And my question is.. is there any requirements to do to install "the stock recovery" first?
I have TWRP, bootloader Unlocked, S-on and rooted.
Click to expand...
Click to collapse
Go to this thread for downloads and instructions on how to find the recovery you need, and how to flash it.

MarwanSamirIbraheem said:
I tried to install the Lollipop OTA with ADB and it didn't work...!
Click to expand...
Click to collapse
Did you try to just run the OTA under system update? Post the error message (Vol up + Pwr button).

ikeny said:
Did you try to just run the OTA under system update? Post the error message (Vol up + Pwr button).
Click to expand...
Click to collapse
I will try to download NanDroid backup. Thanks alot for responding!
---------- Post added at 12:40 AM ---------- Previous post was at 12:08 AM ----------
xunholyx said:
Go to this thread for downloads and instructions on how to find the recovery you need, and how to flash it.
Click to expand...
Click to collapse
I'm downloading a Stock Nandroid Backup for my phone now. should i unroot the phone first or what because i want it full stock after restoring this backup.
Or should i restore it and install a stock recovery too? is the backup comes with the stock recovery? i want to make sure all of this.
Can you tell me step by step what to do here?

MarwanSamirIbraheem said:
I'm downloading a Stock Nandroid Backup for my phone now. should i unroot the phone first or what because i want it full stock after restoring this backup.
Or should i restore it and install a stock recovery too? is the backup comes with the stock recovery? i want to make sure all of this.
Can you tell me step by step what to do here?
Click to expand...
Click to collapse
First, you do not need to unroot first. The Nandroid backup will wipe everything including traces of root.
Nandroid restore however won't replace your boot loader. Read my first post again. The step by step guide is already there, under Soultion of Error 1.

UniversalKID said:
Not if the nandroid backup is rooted.
Click to expand...
Click to collapse
This is probably correct. I haven't used the stock backups, so I can't say for sure. The backups are taken with a custom recovery, after all. That usually points to rooted.
But...
You install the custom recovery before you flash superuser, so the backups can be made before root is actually gained. There's a good chance they are. Like I said, I don't use them. S-Off and such.
And there is no way to tell if the backup is rooted for sure, from the downloads I have seen.
So make your own backup, and flash the stock nandroid. You can always go back to the way you were. You rooted already once, right? You can do it again.

UniversalKID said:
Not if the nandroid backup is rooted.
Click to expand...
Click to collapse
I can't speak for others. But the one linked in my first post is not rooted, and it works fine with OTA update to Lollipop.

ikeny said:
I can't speak for others. But the one linked in my first post is not rooted, and it works fine with OTA update to Lollipop.
Click to expand...
Click to collapse
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?

MarwanSamirIbraheem said:
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?
Click to expand...
Click to collapse
Try doing a factory reset at boot loader.

MarwanSamirIbraheem said:
After installing the OTA update of 5.0.1 version, Wi-Fi doesn't open.
it says turning on then after 2 minutes say Error, what is this?
Click to expand...
Click to collapse
Ana labess fe nafs 7warak
All I need is stock recovery instead of TWRP... Is it easy to do?
And Did the lollipop work fine?Wifi problem still there?

Adham L. Alfy said:
Ana labess fe nafs 7warak
All I need is stock recovery instead of TWRP... Is it easy to do?
And Did the lollipop work fine?Wifi problem still there?
Click to expand...
Click to collapse
If you knew how to install TWRP custom recovery, then it is easy to revert back to stock recovery. Same method, just flash the new img file.
No WiFi issue with my lollipop. I did do a factory reset though.

ikeny said:
If you knew how to install TWRP custom recovery, then it is easy to revert back to stock recovery. Same method, just flash the new img file.
No WiFi issue with my lollipop. I did do a factory reset though.
Click to expand...
Click to collapse
Is there a possibility to brick my phone if I install an incompatibly stock recovery with my phone version.... I mean how safe is the procedure? Regardless wiping my data (doesn't matter to me)

[Guide] Sprint LG G2 LS980 Official Lollipop Update(OTA)+Root+SIM Unlock+Recovery

Sprint G2 (LS980) users who want to update to ZVG (Lollipop) look here! I
I updated to the official firmware AND rooted AND SIM unlocked using the following steps:
WARNING backup EVERYTHING that is on your phone NOW. TOTing to ZVE WILL wipe EVERYTHING.
1. TOT back to ZVE using the instructions here: http://forum.xda-developers.com/showthread.php?t=2432476
Get the ZVE .tot file here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/LS980ZVE_03.zip
No need to unlock/root while on ZVE. If you are already on ZVE just unroot. If you installed TWRP i recommend you still TOT, as I don't know of ways to go back to stock recovery.
2. After booting up, connect to a wifi/mobile network and go to settings>About phone>Software Update>LG Software and download the OTA update. Install it and after ~20 mins it should reboot straight into Lollipop.
************************************
In case you can't install the update from the settings for some reason, follow these steps instead:
a. Download the ZVG update from here: http://forum.xda-developers.com/sprint-g2/general/zvg-ota-update-zip-t3094537
b. Install adb (if you haven't already) with this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
c. Follow this guide to side loading the update: http://forum.xda-developers.com/sprint-g2/development/ota-zvg-installation-instructions-t3094623
Instead of dropping into C:\Android, drop the update zip into C:\adb instead and proceed to side-load from there (don't forget to
cd C:\adb in the terminal).
**************************************
3. Device should be running ZVG now. Root it using http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
I used the GUI version. If it tells you to enter download mode do so and it will work from there. After it finishes phone should reboot and be rooted (SuperSU in drawer too).
4. SIM Unlock the device using this fantastic tool by summer.cat: http://forum.xda-developers.com/spr...click-tool-sim-unlock-network-manual-t3114446
Reboot and the phone should recognize your SIM now. If it doesn't go to the Mobile Networks settings menu and change the Network type to Global or GSM/WCDMA, if it isn't already on it.
5.(OPTIONAL) If you want to play around with custom ROMs, you can install TWRP recovery by installing this apk: https://www.androidfilehost.com/?fid=23991606952595532
And then installing through the app. After it's done you should be able to boot into TWRP by holding vol down and home button until Recovery screen shows up.
Hope I helped any of you!

camalger said:
Sprint G2 (LS980) users who want to update to ZVG (Lollipop) look here! I
I updated to the official firmware AND rooted AND SIM unlocked using the following steps:
WARNING backup EVERYTHING that is on your phone NOW. TOTing to ZVE WILL wipe EVERYTHING.
1. TOT back to ZVE using the instructions here: http://forum.xda-developers.com/showthread.php?t=2432476
Get the ZVE .tot file here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/LS980ZVE_03.zip
No need to unlock/root while on ZVE. If you are already on ZVE just unroot. If you installed TWRP i recommend you still TOT, as I don't know of ways to go back to stock recovery.
2. After booting up, connect to a wifi/mobile network and go to settings>About phone>Software Update>LG Software and download the OTA update. Install it and after ~20 mins it should reboot straight into Lollipop.
************************************
In case you can't install the update from the settings for some reason, follow these steps instead:
a. Download the ZVG update from here: http://forum.xda-developers.com/sprint-g2/general/zvg-ota-update-zip-t3094537
b. Install adb (if you haven't already) with this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
c. Follow this guide to side loading the update: http://forum.xda-developers.com/sprint-g2/development/ota-zvg-installation-instructions-t3094623
Instead of dropping into C:\Android, drop the update zip into C:\adb instead and proceed to side-load from there (don't forget to
cd C:\adb in the terminal).
**************************************
3. Device should be running ZVG now. Root it using http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
I used the GUI version. If it tells you to enter download mode do so and it will work from there. After it finishes phone should reboot and be rooted (SuperSU in drawer too).
4. SIM Unlock the device using this fantastic tool by summer.cat: http://forum.xda-developers.com/spr...click-tool-sim-unlock-network-manual-t3114446
Reboot and the phone should recognize your SIM now. If it doesn't go to the Mobile Networks settings menu and change the Network type to Global or GSM/WCDMA, if it isn't already on it.
5.(OPTIONAL) If you want to play around with custom ROMs, you can install TWRP recovery by installing this apk: https://www.androidfilehost.com/?fid=23991606952595532
And then installing through the app. After it's done you should be able to boot into TWRP by holding vol down and home button until Recovery screen shows up.
Hope I helped any of you!
Click to expand...
Click to collapse
hi
thanks for your elaborate tutorial..i wanted to know If I flash [ROM][6.0.1]Temasek's CM13 for Sprint G2[UNOFFICIAL] or Bliss rom 6.4 or Dirty Unicorns as per the roms instructions flashing hybrid bootstack and all the other rom and gapps files, will I lose my unlock?
brin

rhinasaur said:
hi
thanks for your elaborate tutorial..i wanted to know If I flash [ROM][6.0.1]Temasek's CM13 for Sprint G2[UNOFFICIAL] or Bliss rom 6.4 or Dirty Unicorns as per the roms instructions flashing hybrid bootstack and all the other rom and gapps files, will I lose my unlock?
brin
Click to expand...
Click to collapse
I think yes.

thanksssssssss, success, now it offers me to install a patch critical security (stagefright) 132,7Mb. should I install it or just keep ignoring it ? if i install do i lose sim unlockand root ?

You can't install it if you are rooted already.
If you weren't rooted, you can install it as it would bring you up to zvh level. LG one click root still works on that and so does autorec for installing twrp. You can use twrp to install the modded version of zvi that is already rooted.
Sent from my LG-LS980 using Tapatalk

Thank you

My experience
camalger said:
Sprint G2 (LS980) users who want to update to ZVG (Lollipop) look here! I
I updated to the official firmware AND rooted AND SIM unlocked using the following steps:
WARNING backup EVERYTHING that is on your phone NOW. TOTing to ZVE WILL wipe EVERYTHING.
1. TOT back to ZVE using the instructions here: http://forum.xda-developers.com/showthread.php?t=2432476
Get the ZVE .tot file here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/LS980ZVE_03.zip
No need to unlock/root while on ZVE. If you are already on ZVE just unroot. If you installed TWRP i recommend you still TOT, as I don't know of ways to go back to stock recovery.
2. After booting up, connect to a wifi/mobile network and go to settings>About phone>Software Update>LG Software and download the OTA update. Install it and after ~20 mins it should reboot straight into Lollipop.
************************************
In case you can't install the update from the settings for some reason, follow these steps instead:
a. Download the ZVG update from here: http://forum.xda-developers.com/sprint-g2/general/zvg-ota-update-zip-t3094537
b. Install adb (if you haven't already) with this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
c. Follow this guide to side loading the update: http://forum.xda-developers.com/sprint-g2/development/ota-zvg-installation-instructions-t3094623
Instead of dropping into C:\Android, drop the update zip into C:\adb instead and proceed to side-load from there (don't forget to
cd C:\adb in the terminal).
**************************************
3. Device should be running ZVG now. Root it using http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
I used the GUI version. If it tells you to enter download mode do so and it will work from there. After it finishes phone should reboot and be rooted (SuperSU in drawer too).
4. SIM Unlock the device using this fantastic tool by summer.cat: http://forum.xda-developers.com/spr...click-tool-sim-unlock-network-manual-t3114446
Reboot and the phone should recognize your SIM now. If it doesn't go to the Mobile Networks settings menu and change the Network type to Global or GSM/WCDMA, if it isn't already on it.
5.(OPTIONAL) If you want to play around with custom ROMs, you can install TWRP recovery by installing this apk: https://www.androidfilehost.com/?fid=23991606952595532
And then installing through the app. After it's done you should be able to boot into TWRP by holding vol down and home button until Recovery screen shows up.
Hope I helped any of you!
Click to expand...
Click to collapse
First, thank you because I know helping other with this requires time.
Ok, here is my experience with this tutorial:
I was able to downgrade to KK using the information in step 1, then the phone automatically updated to LP so did not needed step 2. Step 3 (root) did not work. I had to install kingroot app to root. If I unistall it, it unroots the phone so I cannot install supersu by chainfire (best app). Anyway it allowed me to do sim unlock (step 4) that worked fine after I got the computer to recognize my phone in adb. One important thing is that I was unable to set up my apn from the network menu, so I had to download an app from the playstore to do so, the app's name is "Change APN". Step 5, autorec, works fine to install twrp but I had to download it from other site because the link in the post does not work anymore.
Again thanks so much and I hope this post helps other that might want to use your tutorial. :good:

mitsh2032 said:
thanksssssssss, success, now it offers me to install a patch critical security (stagefright) 132,7Mb. should I install it or just keep ignoring it ? if i install do i lose sim unlockand root ?
Click to expand...
Click to collapse
Don't install the security update cause if you do you will not be able to root your phone, just keep ignoring it.

pichulo said:
First, thank you because I know helping other with this requires time.
Ok, here is my experience with this tutorial:
I was able to downgrade to KK using the information in step 1, then the phone automatically updated to LP so did not needed step 2. Step 3 (root) did not work. I had to install kingroot app to root. If I unistall it, it unroots the phone so I cannot install supersu by chainfire (best app). Anyway it allowed me to do sim unlock (step 4) that worked fine after I got the computer to recognize my phone in adb. One important thing is that I was unable to set up my apn from the network menu, so I had to download an app from the playstore to do so, the app's name is "Change APN". Step 5, autorec, works fine to install twrp but I had to download it from other site because the link in the post does not work anymore.
Again thanks so much and I hope this post helps other that might want to use your tutorial. :good:
Click to expand...
Click to collapse
You're welcome.

If you need to change your APN, dial ##3282# from your phone dialer. It brings up a menu that will let you modify it.
Sent from my Moto G (4) using Tapatalk

Update - OK, so I did find a working link for lollipop autorec for zvg ls980 along with some other answers in this thread:
https://forum.xda-developers.com/sprint-g2/help/autorec-ls980zvg-t3405988
Was able to get TWRP installed using that which resolved the security question below.
Remaining question:
Should I update twrp to the blastagator version?
Thanks again!
======
Can someone please point me to a working link for autorec for LS980 zvg(h). All of the links I find are dead.
2 more questions: should I be using the blastogator TWRP versions?
I am currently at the point where I get the security error when trying to boot to recovery. Will Autorec install twrp in this situation or does it need to be able to boot into recovery? Is there some other way to resolve this issue without going all the way back to zve?
Thanks much!!

This is the version of autorec I used
Sent from my LG-LS980 using Tapatalk
---------- Post added at 06:03 PM ---------- Previous post was at 05:57 PM ----------
tekweezle said:
This is the version of autorec I used
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4AgmvCEsbJCVExpYUoxMlRLc2s/view?usp=drivesdk
Sent from my LG-LS980 using Tapatalk
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
I had a problem seeing the lollipop button to start the root. I fixed it by going into supersu and checking on Mount namespaces
Sent from my LG-LS980 using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-LS980 using Tapatalk

tekweezle said:
This is the version of autorec I used
Sent from my LG-LS980 using Tapatalk
---------- Post added at 06:03 PM ---------- Previous post was at 05:57 PM ----------
https://drive.google.com/file/d/0B4AgmvCEsbJCVExpYUoxMlRLc2s/view?usp=drivesdk
Sent from my LG-LS980 using Tapatalk
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
I had a problem seeing the lollipop button to start the root. I fixed it by going into supersu and checking on Mount namespaces
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Thanks much! I do appreciate it.
I th9nk I saw you in the zvi thtead. Any first hand opinion on zvi esp battery life I am seeing some say is poor compared to zvg?
thanks again

It's about the same. If you want better battery performance, get rid of any apps like Facebook Messenger that constantly polls in the background. Also drop your screen brightness. There's little else that you can do.
You need to update to zvi or your phone will keep downloading the update.
Sent from my LG-LS980 using Tapatalk

Software says my phone is D802, when i check the main board of my phone its written ls980?
So please someone help me what is the drama.
---------- Post added at 08:16 AM ---------- Previous post was at 08:16 AM ----------
Software says my phone is D802, when i check the main board of my phone its written ls980?
So please someone help me what is the drama.

muradak5545 said:
Software says my phone is D802, when i check the main board of my phone its written ls980?
So please someone help me what is the drama.
---------- Post added at 08:16 AM ---------- Previous post was at 08:16 AM ----------
Software says my phone is D802, when i check the main board of my phone its written ls980?
So please someone help me what is the drama.
Click to expand...
Click to collapse
I have converted my LS980 to a D802 D801 also, it allows me to use any sim card and use it with T-Mobile. I can also flash the new latest LineageOS (9.0) made for the D802 D801. You just have to remember to never flash a Sprint ROM or upon boot will soft perma-brick and you will need to short pins and use the dreaded QUSB 900X partition flash upload.
So to answer your questions: (will only work if they are using the Modified boot stack to make it a D802)
- To turn back into an LS980, you need to flash the LS980 boot stack, the TWRP LS980 Version Recovery and then boot back into the LS980 recovery and flash an LS980 ROM.
- To go back to a D802 version, you would flash the modified D802 bootstack made for the LS980 and then flash the TWRP D802 recovery, boot back into the D802 recovery and flash any D802 T-Mobile ROM (you will have to open the updater script in the ROM and remove the first few lines that check the phone version)
--Edit: I only have the modified boot stacks for the D801 not the D802. The path back to LS980 should be the same.

OTA update after rooting

Hi. I have just rooted my Pixel 2 XL with Magisk after reading the guides here on XDA. This is my first Android phone and my first time rooting so I'm trying to figure out the update situation here. How would I go about installing version 8.1 when I get the OTA update for it? Would I have to wipe my device again and reinstall Magisk?
On a side note, does anyone know if MinMinGuard on systemless Xposed breaks SafetyNet?
Thanks in advance.

Unroot, apply OTA, re-root.

I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Can you install OTA with unlocked bootloader?

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Thanks. Would this remove all of my data?

darkfire404 said:
Thanks. Would this remove all of my data?
Click to expand...
Click to collapse
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk

dyingearth said:
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk
Click to expand...
Click to collapse
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nitin

turboencab said:
I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Did it work?

Cowbell_Guy said:
Did it work?
Click to expand...
Click to collapse
I don't know, I got impatient and sideloaded the OTA. I essentially followed the procedure listed by dyingearth in post #6 above.

Just went to do this but Magisk says Stock Backup Doesn't Exist... I didn't delete anything, anyone know why this would happen? And now the question is... How do I go about getting an update with forking my phone? I don't mind freshly doing it all over from scratch, but would like to get Magisk to backup the stock stuff so that when I follow the OTA instrustions on the Magisk link tips it would work.

OTA
I'm on rooted Pixel XL 2 already on 8.1, can I take the security patch, or do I need to unroot before taking the update?
nitin.chobhe said:
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
Nitin
Click to expand...
Click to collapse

Bump

Following.
My 2xl unrooted today. On it's own. Went to break around 3 and had magisk notification about installing 15.3zip which I was already on. Looked in manager and it showed not installed. Have been reading yesterday about updating while rooted. Checked system update and shows available update today. So I tried to install but failed. Looks like I'll have to wait till after work....at 7pm!!

After taking ota update with magisk installed did not reboot through Magisk so I lost root. Magisk is still on phone but not installed. How to reinstall? Do I need to reflash or can I just hit install on app? Will gladly provide more info aas needed. I have searched and did not find a exact answer to my problem. Build number pq3a.190801.002

You need to sideload ota manually for updates

prot- said:
You need to sideload ota manually for updates
Click to expand...
Click to collapse
I can't figure out how it took the ota in the first place with no errors. I found the guide on how to do the ota with it installed but after i got the ota. When I open the Magisk it says i can install Magisk and Magisk Manager from the app. Im worried it will mess something up.

The quickest and simplest way to update your phone monthly:
- download the stock taimen image for current month
- unzip and edit the 'flash-all.bat' file by removing/deleting the '-w' from the code. Removing the '-w' ensures that your data is NOT wiped
- boot into bootloader and run the 'flash-all' script from your adb folder
- after it completes the update, let the phone boot into Android
- restart and boot into TWRP. Note: decryption is broken for some people (like me), you will need to remove your PIN code before booting into TWRP
- flash Magisk 19.3 or whatever you prefer (and any additional apps you such as Vanced YouTube, etc.)
- Reboot into rooted phone
- Add your PIN code (or whatever security measure you want to use)
If you need a more detailed information, please check the main rooting thread.

OP follow this exactly, and you will have no problems. https://forum.xda-developers.com/showpost.php?p=80039116&postcount=778