http://forum.xda-developers.com/showthread.php?p=63255820
Sent from my VS986 using Tapatalk
Has anyone had luck doing this yet? When I get home from work I'm going to try it. I'll put together a walk-through guide with screenshots if I do.
chubbrock said:
http://forum.xda-developers.com/showthread.php?p=63255820
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
The user "jesssiii" reposted the download link since it was encrypted and others in the thread were having problems downloading.
Here's his new post with the corrected link: http://forum.xda-developers.com/showpost.php?p=63262160&postcount=231
I think you have to be on official 12A to push the rooted 12a over, but not 100% sure. Also, if you're still on 10b, I'd hold off on any Ota because bootloader unlock is rumoured to be available soon!
Sent from my VS986 using Tapatalk
chubbrock said:
I think you have to be on official 12A to push the rooted 12a over, but not 100% sure. Also, if you're still on 10b, I'd hold off on any Ota because bootloader unlock is rumoured to be available soon!
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
if you are on 11a then you are on v1
they are saying if you are on v0 you are the only one who would be getting the bootloader unlock right now.
11a has been out long enough for them to kow if v1 would work.
cmsjr123 said:
11a has been out long enough for them to kow if v1 would work.
Click to expand...
Click to collapse
I agree with that. I think they should be able to pull it off for us on 11a. I'm patient and I knew it would happen soon like the g3 bump. Just wait and watch....? just give it time they will unlock this phone
Sent from my VS986 using Tapatalk
chubbrock said:
I think you have to be on official 12A to push the rooted 12a over, but not 100% sure. Also, if you're still on 10b, I'd hold off on any Ota because bootloader unlock is rumoured to be available soon!
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
krazy_smokezalot said:
I agree with that. I think they should be able to pull it off for us on 11a. I'm patient and I knew it would happen soon like the g3 bump. Just wait and watch.... just give it time they will unlock this phone
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Thing is if they knew 11a would work i bet they would have said it.
12a is out already...
11a has been out for what 2 months now? they would know
If anyone has successfully used the rooted 12a image and had the phone boot correctly with no issues, please post. The rest of us need to know if it's worth the risk.
I was on rooted 11a, had to restore to stock 11a to take the OTA and went to 12a. I used the root injection method (pulled stock sys img, injected root and reflashed image) and everything is working very well. I have all the fixes of 12a plus root. However a factory reset does not lose root. Since I can't KDZ back to 11a without bricking my phone (hurry up 12a KDZ) I held the pwr+vol- buttons to get to LGs recovery screen and chose factory data reset. It resets everything to default like it came out of the box (starts at the setup wizard) but I still have root with SU app installed. For those who are hesitant, the instructions in the thread of root injection are really easy. I just downloaded Ubuntu ISO, burnt it to DVD and booted from DVD. Or just download a prerooted 12a image from one of the threads. Remember that if you want to go back to unrooted stock, save a copy of your own stock system image before you flash a rooted one since the only other way to get back to factory unrooted stock will be whenever a 12a KDZ is release.
This will not work. I've said this in the other threads. You cannot copy over a mismatched system image that differs from the bootloader. The actual OTA will update the bootloader to V2 and this will work.
If you are on 11A (like we all are) then this will result in a nice little Error message that the system image is corrupt and will just turn off until you flash a matching system image that matches the bootloader.
So THIS WILL NOT WORK. I've tried. Many times. Trust me.
Also the 12A update has been pulled because it will stop app updates while on wifi (no notifications while on WiFi). It is a huge bug and thus the update has been pulled. Even if we could flash this, you don't want to flash this.
Update: Only people who took the OTA can flash this rooted 12A system image. Everyone else has to wait for a fix.
player911 said:
This will not work. I've said this in the other threads. You cannot copy over a mismatched system image that differs from the bootloader. The actual OTA will update the bootloader to V2 and this will work.
If you are on 11A (like we all are) then this will result in a nice little Error message that the system image is corrupt and will just turn off until you flash a matching system image that matches the bootloader.
So THIS WILL NOT WORK. I've tried. Many times. Trust me.
Also the 12A update has been pulled because it will stop app updates while on wifi (no notifications while on WiFi). It is a huge bug and thus the update has been pulled. Even if we could flash this, you don't want to flash this.
Update: Only people who took the OTA can flash this rooted 12A system image. Everyone else has to wait for a fix.
Click to expand...
Click to collapse
Am I the only one who HASN'T experienced this wifi push notification bug? Things are running really well for me. I was shipped a replacement phone about 10 days ago though, but it did still come with 11a on it.
Edit: Actually let me take that back, snaps are only coming in over 4g. Weird. I guess I'll wait for an official fix as well. Until then the other issues were fixed anyway.
IPV6 appears to be causing the notification bug
I read on Android Authority that it's an IPV6 bug. Disable IPV6 (or wait for a new build) and notifications should work.
http://forums.androidcentral.com/lg-g4/592446-new-verizon-g4-update-4.html
xgerryx said:
I was shipped a replacement phone about 10 days ago though, but it did still come with 11a on it.
Click to expand...
Click to collapse
Damn, I bricked mine using 11A KDZ after updating to 12A. Was hoping my replacement tomorrow would be back on 10.
jesssiii said:
Damn, I bricked mine using 11A KDZ after updating to 12A. Was hoping my replacement tomorrow would be back on 10.
Click to expand...
Click to collapse
It COULD but at this point, unless they just shipped you one from the Verizon store, it'll probably have 11a. Considering the weird recall thing that Sprint had that I saw in another thread, I wouldnt be surprised if it came with 12a.
player911 said:
This will not work. I've said this in the other threads. You cannot copy over a mismatched system image that differs from the bootloader. The actual OTA will update the bootloader to V2 and this will work.
If you are on 11A (like we all are) then this will result in a nice little Error message that the system image is corrupt and will just turn off until you flash a matching system image that matches the bootloader.
So THIS WILL NOT WORK. I've tried. Many times. Trust me.
Also the 12A update has been pulled because it will stop app updates while on wifi (no notifications while on WiFi). It is a huge bug and thus the update has been pulled. Even if we could flash this, you don't want to flash this.
Update: Only people who took the OTA can flash this rooted 12A system image. Everyone else has to wait for a fix.
Click to expand...
Click to collapse
The system image doesn't care about the boot loader. The system image isn't working because the boot image (the kernel) doesn't match. The system image may work if you also flash the boot image, but the older boot loader may not like the signature on the newer boot image.
And if you're only flashing the boot image and the system image, you could still kdz everything back to 11a or 10b (whichever you were on before), so if we can get a rooted 12A user to rip the system and boot, we may be able to get 12a without OTA
danaff37 said:
The system image doesn't care about the boot loader. The system image isn't working because the boot image (the kernel) doesn't match. The system image may work if you also flash the boot image, but the older boot loader may not like the signature on the newer boot image.
And if you're only flashing the boot image and the system image, you could still kdz everything back to 11a or 10b (whichever you were on before), so if we can get a rooted 12A user to rip the system and boot, we may be able to get 12a without OTA
Click to expand...
Click to collapse
You cannot KDZ back to an older version. Once you are on 12A, you are stuck with it. Apparently there is a trip timer that is stored in NAND. 12A is v2... so you can no longer run v0 (10A) or v1 (11A).
I am not saying it is impossible. We can get low level partition backups (like how we pull and push the system image for root). I just have not heard of anyone allowing backups or fixes yet.
I think once the Devs are able to bootloader unlock v0 devices, they will be able to pull bits and pieces from other sections of the devices and work from the other side of the wall.
That's not what I'm saying... I'm saying if we get boot partition and system partition from 12a, we may be able to run them on 10/11b boot loader. Without having to ota
danaff37 said:
That's not what I'm saying... I'm saying if we get boot partition and system partition from 12a, we may be able to run them on 10/11b boot loader. Without having to ota
Click to expand...
Click to collapse
I get what you're saying but I do not think that is possible, at least not at this time. If it was, we would all be on 10A right now.
Maybe once they release the bootloader unlock, they can pull additional information. The way I understand it is that all of the parts must match the same software revision number and that there is a NAND partition that keeps track of the version numbers. So once the NAND says "v2", everything else must match or else it throws a system error on boot.
Now if they can find a way to edit that NAND section and edit that to v0, then we can push over the v0 partitions and effectively flash back.
All we can do right now is stop accepting OTAs because the further we go, the less likely we will be able to recover.
A little off topic but I can't seem to find the original 12a update anywhere. I'm on stock 11a and I am trying to find the stock 12a update file so I can update and see what I can do about IPV6. Can someone please help me find the 12a stock update ota file?
Related
Hi all,
I need someone to do me favor. When I took the 12a ota, I rooted it with the root injection method. However, I didn't make a backup of my stock unrooted system image. The way it sits now I am permanently rooted. I can't KDZ back to 11a for obvious reasons and when I reset to factory defaults, even through the LG recovery screen, it still keeps root. Since it's possible that big red pulled the 12a ota due to notification issues and such, I will not be able to take any more ota's until a KDZ is released.
So after expanding on that, all I'm asking is for someone with a Verizon variant of the G4 that is on 12a but is NOT rooted to please pull a copy of their stock UNROOTED system image (preferably right after a factory reset) and put it up somewhere for me to grab. That way if another ota comes back, I have a way to get back to stock without having to wait for a KDZ to be released. If someone is willing to do this for me, please post the MD5 so I don't flash a bad download.
Thanks so much in advance.
Anyone?
Try to unroot from super SU and uninstall Xposed with the zip if exists , might be helpful...
Unfortunately I am on 10B ?
Sent from my VS986 using Tapatalk
I know this is unrelated to your question, but is there anyway you could either copy your build prop info to a text or share your build prop file? Trying to see if the touch screen info on their would solve the issues on older versions of the software! Thanks in advance!
Sent from my VS986 using Tapatalk
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.)
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
EDIT: Just got the OTA for the N preview, so I guess it's just a roll out thing then. Just want to leave this here for anyone else who's new to nexus devices and was wondering the same.
AnrgKrshn said:
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
Click to expand...
Click to collapse
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
brholt6 said:
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
Click to expand...
Click to collapse
Just saw this after I posted my edit lol. Thanks for the confirmation
Will the ota work with systemless root?
94SupraTT said:
Will the ota work with systemless root?
Click to expand...
Click to collapse
You need to flash stock boot and recovery images to receive it or alternatively use chainfires flashfire app.
Hello,
I own the 32gb h791 nexus 5x and the phone is bootlooping after android 7.0 update.
so basicly the phone showing google logo and then reboot back..
My bootloader is unlocked, so I tried to flash marshmellow without any success.
I can not access the recovery.
I saw a thread about flashing tot but i read in the thread that It is re lock the bootloader.
I dont have efs backup..
Any help?
Thanks,
Nimrod
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
But that's a hardware bootlop no software
How many files had been flashed when you've tried to flash it? If any, have you done any modifications like root etc ?
If no, just lock bootloader and send RMA
If you can send to Google, you don't have to lock bootloader.
If your warranty expired, try to talk to Google may they will give you a replacement anyway, if not Google, you can try to LG because of 15mo warranty from production date
TypNguy said:
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
Click to expand...
Click to collapse
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
His problem is a hardware issue not software. Might get lucky and volte it back to life but I highly doubtful . LG notorious for certain models that infinite bootloop issue g4 was the worse.
Yes, the root toolkit worked for me. I still don't know how to flash correctly, so if you have the right driver's associated with your phone/laptop it should be a breeze. The best part is that there's a log, so you know what the toolkit is doing. For example, it may unroot your phone before it flashes the new stock image for you.
---------- Post added at 02:40 AM ---------- Previous post was at 02:36 AM ----------
Just found wugfresh's answer to your question I think.
Link
Address: http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?
There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
savi0 said:
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
Click to expand...
Click to collapse
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
5.1 said:
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
Click to expand...
Click to collapse
To clarify your meaning... The May Verizon OTA does or does not break root?
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
savi0 said:
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.
Click to expand...
Click to collapse
Hello,
If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...
savi0 said:
Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
5.1 said:
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
Click to expand...
Click to collapse
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Hey,
As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.
Cheers...
5.1 said:
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
Click to expand...
Click to collapse
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
sliding_billy said:
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...
Normally, we won't have to wait too long to get back TWRP/Root.
Cheers...
sliding_billy said:
I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
Hello,
I don't understand what you mean when you say:
alluringreality said:
That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update
Click to expand...
Click to collapse
If you have issues, just sideload the latest OTA from Google here:
https://developers.google.com/android/ota
Instructions are available on this page.
Good luck...
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.
Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
PrettyPistol555 said:
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
Click to expand...
Click to collapse
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
shagbag913 said:
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
Click to expand...
Click to collapse
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
PrettyPistol555 said:
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
Click to expand...
Click to collapse
Yep.
I haven't been around much in some time but figured I'd mention I woke to a update message on my phone. Going to push it if as long as I can, that is assuming there is still development going on.
I'll try to see if I can find a location to DL the image to provide it to whoever might be able to tell me if it's okay to apply to my tired phone.
freduser said:
I haven't been around much in some time but figured I'd mention I woke to a update message on my phone. Going to push it if as long as I can, that is assuming there is still development going on.
I'll try to see if I can find a location to DL the image to provide it to whoever might be able to tell me if it's okay to apply to my tired phone.
Click to expand...
Click to collapse
Yes, very surprising news.
This is probably OTA and full KDZ will be released soon. You can capture KDZ with LG Bridge URL.
drewcu said:
FINALLY! Almost 1 year later.... https://www.verizon.com/support/lg-v30-update/
Obviously no TWRP version yet, but at least LG/Verizon hasn't abandoned us completely just yet.
System Update 15
Release date: 08/31/2020
Android™ Security Patch Level: August 2020
Software Version: VS99630d
What's changing:
The current software update provides most up to date Android security patches on your device.
Click to expand...
Click to collapse
In the mean time, how do I stop big brother Verizon from bugging me to update the firmware. My phone is rooted with Magisk so I can't take OTA.
In the mean time, how do I stop big brother Verizon from bugging me to update the firmware. My phone is rooted with Magisk so I can't take OTA.
Click to expand...
Click to collapse
Use Titanium Backup to Freeze:
System updates 2_18_06_0
System updates 1_15_10_0
And possibly:
Software Update 9
spacepirates said:
Use Titanium Backup to Freeze:
System updates 2_18_06_0
System updates 1_15_10_0
And possibly:
Software Update 9
Click to expand...
Click to collapse
Just freezing the 2 System Updates will do it.
I have to say I'm very impressed! Like it's been 3 years since the V30 launched, right? I had started at replacing this phone due to the lack of security updates, but now I can keep using it a while longer, awesome!
I am currently on the debloated vs99630c rom. Can the Verizon updated rom be downloaded onto the phone without losing root?
Do we know if anyone is trying to make this into a twrp installable rom, hope so?
ChazzMatt said:
Yes, very surprising news.
This is probably OTA and full KDZ will be released soon. You can capture KDZ with LG Bridge URL.
Click to expand...
Click to collapse
Never used LG Bridge and saw a procedure you were trying out several years back: https://forum.xda-developers.com/lg-v30/help/us998-kdz-file-request-t3726918/page2
Couple questions:
1) Does the procedure for downloading the KDZ "mess" with your existing recovery / system partitions? (I'd like to try and get the KDZ but not at the expense of needing to worry about restoring things back to the way they are now.)
2) You seemed to have trouble extracting the URL at first, then had success later on. What was the trick to getting it to work?
Thanks,
Drew
EDIT: LG Bridge doesn't connect to my V30 VS996 for some reason. Have tried within TWRP and the LG Pie ROM. Have tried File Transfer mode, Charging mode, System Update mode, etc. Within File Transfer mode, the software appears to try to connect, then fails and suggests I disconnect/reconnect the cable which I do to no avail. Oh well, I tried.
gimpy1 said:
I am currently on the debloated vs99630c rom. Can the Verizon updated rom be downloaded onto the phone without losing root?
Do we know if anyone is trying to make this into a twrp installable rom, hope so?
Click to expand...
Click to collapse
You need TWRP flashable zip. The full KDZ has not been publicly released yet. JohnFawkes or Seadersn would have to make it, when the KDZ is released
---------- Post added at 07:04 PM ---------- Previous post was at 06:35 PM ----------
drewcu said:
Never used LG Bridge and saw a procedure you were trying out several years back: https://forum.xda-developers.com/lg-v30/help/us998-kdz-file-request-t3726918/page2
Couple questions:
1) Does the procedure for downloading the KDZ "mess" with your existing recovery / system partitions? (I'd like to try and get the KDZ but not at the expense of needing to worry about restoring things back to the way they are now.)
2) You seemed to have trouble extracting the URL at first, then had success later on. What was the trick to getting it to work?
Thanks,
Drew
Click to expand...
Click to collapse
You can look in the Bridge's download log file and find the URL that was used to download the .kdz
The link can then be downloaded by anyone using web browser. Sometimes User-Agent change is required, I think to "spider". I used a chrome extension to temporarily change the user agent so the LG Bridge server didn't see I was using a regular web browser.
Any chance that someone with a VS996 and LG Bridge that works can PLEASE check to see if the vs99630d KDZ is available for download?
I would, but I've tried using LG Bridge with multiple PCs and cannot get it to connect to my VS996. It shows the Connecting... screen but just times out regardless of what I do.
Thanks!
Drew
I will try
edit: LG Bridge is not working for me either. However I just googled and there is a 30d kdz on https://lg-firmwares.com/lg-vs996-firmwares/
Descartesisafraud said:
I will try
edit: LG Bridge is not working for me either. However I just googled and there is a 30d kdz on https://lg-firmwares.com/lg-vs996-firmwares/
Click to expand...
Click to collapse
Thanks for confirming I'm not the only one with LG Bridge issues and for finding the 30d KDZ!
Direct link to 30d KDZ page: https://lg-firmwares.com/downloads-file/23387/VS99630d_02_0821_ARB00
Now the next question is -- is @JohnFawkes still on the scene and able to work the same magic he used for the 30c TWRP zip with the 30d version? My guess is this is the last time Verizon/LG pushes out an update for the almost 3 year old phone.
Thank you!!
There is a tool to convert .kdz to twrp .zip. But it says it only works for old kdz. I dont know how the new KDZ are converted.
https://forum.xda-developers.com/tm...-kdzz-create-flashable-zip-kdz-files-t3902423
I think though you can update with the kdz using patched LGUP via REFURBISH or PARTITION DL. You will lose twrp, but you can reinstall twrp afterwards. Then I think you have to install magisk again, as well as Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) and AnyKernel 3 RCTD Remover (root checker disabler). All that is explained in this link.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500/post79972584#post79972584
Also I think you lose data, so have to backup apps and stuff if needed.
I might do this in the next time. I dont know if there will be a flashable twrp zip.
Descartesisafraud said:
There is a tool to convert .kdz to twrp .zip. But it says it only works for old kdz. I dont know how the new KDZ are converted.
https://forum.xda-developers.com/tm...-kdzz-create-flashable-zip-kdz-files-t3902423
I think though you can update with the kdz using patched LGUP via REFURBISH or PARTITION DL. You will lose twrp, but you can reinstall twrp afterwards. Then I think you have to install magisk again, as well as Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) and AnyKernel 3 RCTD Remover (root checker disabler). All that is explained in this link.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500/post79972584#post79972584
Also I think you lose data, so have to backup apps and stuff if needed.
I might do this in the next time. I dont know if there will be a flashable twrp zip.
Click to expand...
Click to collapse
Was just looking into KDZZ and yeah I think John figured out a way with new KDZs (or else we wouldn't have one for 30c). I recall it taking a few tries with us beta testers so it's evidently not super simple. If John is still around, hopefully he can share a how-to on this new KDZ, or just create the TWRP zip for 30d himself...
Not sure about your 2nd idea because that method seems to require fastboot commands which the Verizon firmware doesn't allow. I could be wrong here, but I'd hold off doing any of this until someone confirms one way or the other...
drewcu said:
Thanks for confirming I'm not the only one with LG Bridge issues and for finding the 30d KDZ!
Direct link to 30d KDZ page: https://lg-firmwares.com/downloads-file/23387/VS99630d_02_0821_ARB00
Now the next question is -- is @JohnFawkes still on the scene and able to work the same magic he used for the 30c TWRP zip with the 30d version? My guess is this is the last time Verizon/LG pushes out an update for the almost 3 year old phone.
Thank you!!
Click to expand...
Click to collapse
Thanks. I'll update the VS996 Pie KDZ thread tonight when I get home.
@JohnFawkes.
Nah I won't be updating anything. If you guys aren't aware, I don't do android development anymore. Please refer to this post as to why
https://twitter.com/topjohnwu/status/1304871604833329153?s=20
Sorry. If I was still doing development I would make it but after everything with fontchanger and all the bull**** I put up with, I can't force myself to do anything dev related anymore
---------- Post added at 09:29 PM ---------- Previous post was at 09:09 PM ----------
I'm sure @seadersn would do it if he has time though
the developer is fed up with the constant harassment (even death threats) from other "devs"
Click to expand...
Click to collapse
jesus, why do people have to be so aweful?
drewcu said:
Not sure about your 2nd idea because that method seems to require fastboot commands which the Verizon firmware doesn't allow. I could be wrong here, but I'd hold off doing any of this until someone confirms one way or the other...
Click to expand...
Click to collapse
good point, if fastboot commands dont work on 30d
Honestly you can just flash the kdz and select everything except recovery to keep twrp
JohnFawkes said:
Honestly you can just flash the kdz and select everything except recovery to keep twrp
Click to expand...
Click to collapse
@ChazzMatt
Since you are the guru for all things V30, have you already made a guide for how to flash a KDZ in LGUP and keep TWRP?
My Download Mode has been borked since Oreo on the VS996, so do you think flashing the US998 20e TWRP zip will fix that issue AND should I expect any problems flashing an Oreo US998 rom after being on a Pie VS996 rom?
I am guessing if I somehow regain Download Mode with this 20e method, then I use LGUP's Partition DL mode and check everything but Recovery for the 30d KDZ?
Then what else would we want to do before booting into the ROM in terms of encryption and all that John normally includes in his TWRP zip?
If anyone successfully completes this task of keeping TWRP and Root with 30d, can you please report back?
Thanks!
Drew
drewcu said:
@ChazzMatt
Since you are the guru for all things V30, have you already made a guide for how to flash a KDZ in LGUP and keep TWRP?
Click to expand...
Click to collapse
We tried that in the early days -- before Westwood24, JohnFawkes, and Seadrsn. It was hit or miss, and turned to mostly miss. Theoretically, using Partition DL but omitting the recovery partitions, it should cleanly only update the those partitions and leave TWRP intact. But for whatever reasons, that would often not work. (I can't remember whether it just bootlooped or got hung on logo. Been a couple of years ago. It would be discussed early in the Oreo KDZ threads.)
After attempting that, many people then had to reformat their phones, flash the full KDZ (either Refurbish or Partition DL) and then reinstall TWRP again. Bootloader was still unlocked, of course, but they had to go through Section 6 of WTF Instructions to reinstall TWRP over the updated KDZ. If you have H930 variant or US998 firmware, that's NOT a deal breaker as those have fastboot flash commands. But for Verizon firmware, you can't do that.
This is why the TWRP-flashable zips (basically stock ROMs) were such a godsend. You kept your data and kept TWRP.