Verizon specific 7.1.2 build?

T

TheLastBoyScout

Senior Member
Oct 30, 2012
61
16
0
Apr 9, 2017 at 6:55 PM
canemaxx said:
Have you tried installing the OTA via TWRP?
Click to expand...
I have not, since I was attempting to keep TWRP and root if possible. I might make a backup and attempt the flash just to see what happens. I can always roll it back.

However, I am posting my error in the FlashFire thread and will see what info anyone can give me about it.
 
canemaxx

canemaxx

Senior Member
Aug 23, 2012
538
59
0
Wilder,VT
Apr 9, 2017 at 6:58 PM
TheLastBoyScout said:
I have not, since I was attempting to keep TWRP and root if possible. I might make a backup and attempt the flash just to see what happens. I can always roll it back.

However, I am posting my error in the FlashFire thread and will see what info anyone can give me about it.
Click to expand...
Regaining TWRP and root is very quick and easy ....But you flash fired the OTA coming from 7.1.2 or 7.1.1? If you were in 7.1.2 the error could be just that.
 
T

TheLastBoyScout

Senior Member
Oct 30, 2012
61
16
0
Apr 9, 2017 at 7:15 PM
canemaxx said:
Regaining TWRP and root is very quick and easy ....But you flash fired the OTA coming from 7.1.2 or 7.1.1? If you were in 7.1.2 the error could be just that.
Click to expand...
I was on 7.1.1 and kept getting the error message.

Tried researching for a solution to no avail, and decided to try the Google 7.1.2 just to make sure it wasn't an issue with FlashFire. FlashFire loaded the Google 7.1.2 with no issues. Tried rolling back, and I still can't get the Verizon 7.1.2 to load with FlashFire.

Granted, getting TWRP and root is pretty simple, but the idea is to figure this out so there is a quick and painless way to update via FlashFire, without the need to connect to a PC to get TWRP and root back.
 
canemaxx

canemaxx

Senior Member
Aug 23, 2012
538
59
0
Wilder,VT
Apr 9, 2017 at 7:22 PM
TheLastBoyScout said:
I was on 7.1.1 and kept getting the error message.

Tried researching for a solution to no avail, and decided to try the Google 7.1.2 just to make sure it wasn't an issue with FlashFire. FlashFire loaded the Google 7.1.2 with no issues. Tried rolling back, and I still can't get the Verizon 7.1.2 to load with FlashFire.

Granted, getting TWRP and root is pretty simple, but the idea is to figure this out so there is a quick and painless way to update via FlashFire, without the need to connect to a PC to get TWRP and root back.
Click to expand...
I could be wrong but to the best of my knowledge there's no way to update without losing TWRP and root
 
C

csick

Senior Member
Apr 29, 2011
75
25
38
West Warwick
Apr 10, 2017 at 12:16 AM
hub1 said:
I sideloaded the "E" version before I found out about the VZ specific version. I have an XL purchased from Verizon and on VZ network. What I did was enrolled in the beta program to get back to 7.1.2 beta, then un-enrolled to get back to 7.1.1 and then got the VZ ota. My XL is completely stock VZ model. I'm not savy enough to pull the ota image....
Click to expand...
This worked for me to get me back to 7.1.1.
Word of warning that when you un-enroll your phone and downgrade it will wipe your data, so make sure you've got everything backed up, first.

Update:
Just got the OTA and now I'm on NHG47K
 
Last edited:
  • Like
Reactions: hub1
C

coldconfession13

Senior Member
Oct 10, 2010
1,410
187
0
Apr 10, 2017 at 3:32 AM
Hmm I get an error. Might have been cause I was on a modified kernel. I flashed the stock kernel and it updated just fine going through settings. Now to find a modified kernel so I can use android pay
 
Last edited:
canemaxx

canemaxx

Senior Member
Aug 23, 2012
538
59
0
Wilder,VT
Apr 10, 2017 at 3:35 PM
I am now on the K build with TWRP and root ....Phone is more responsive , better wifi connectivity and Bluetooth is flawless . I did however have to do a clean install of 7.1.1 in order to get the OTA ...No noticable differences such as VZW bloat..Although VZW app no longer asks for su permissions
 
Last edited:
0

0hfrankieboy

Member
Oct 10, 2016
33
16
0
Apr 10, 2017 at 5:09 PM
canemaxx said:
I am now on the K build with TWRP and root ....Phone is more responsive , better wifi connectivity and Bluetooth is flawless . I did however have to do a clean install of 7.1.1 in order to get the OTA ...No noticable differences such as VZW bloat..Although VZW app no longer asks for su permissions
Click to expand...
I also did a clean install of 7.1.1 and noted that I was booting into slot A. I then allowed the phone to download the OTA for K build and noticed that it upgraded to K on slot B. When I switched back to slot A it was still on 7.1.1 and is having force closes of the "Pixel Launcher", "android.process.acore", and "com.android.phone". Has anyone else noticed this? It doesn't seem normal any insight is appreciated.
 
canemaxx

canemaxx

Senior Member
Aug 23, 2012
538
59
0
Wilder,VT
Apr 10, 2017 at 5:15 PM
0hfrankieboy said:
I also did a clean install of 7.1.1 and noted that I was booting into slot A. I then allowed the phone to download the OTA for K build and noticed that it upgraded to K on slot B. When I switched back to slot A it was still on 7.1.1 and is having force closes of the "Pixel Launcher", "android.process.acore", and "com.android.phone". Has anyone else noticed this? It doesn't seem normal any insight is appreciated.
Click to expand...
Yes that's exactly what happened to me so I did the clean install of 7.1.1 let the phone update completely via the OTA to the k build then I installed TWRP and SuperSU and I've had no issues since. I did have to fully unroot again to get Snapchat installed and logged into and then rerooted all is well now

---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
0hfrankieboy said:
I also did a clean install of 7.1.1 and noted that I was booting into slot A. I then allowed the phone to download the OTA for K build and noticed that it upgraded to K on slot B. When I switched back to slot A it was still on 7.1.1 and is having force closes of the "Pixel Launcher", "android.process.acore", and "com.android.phone". Has anyone else noticed this? It doesn't seem normal any insight is appreciated.
Click to expand...
Sounds like you had some data carry over when you reverted ...I had the same FC and when I went to developer options it said it wasn't available for that user..I only had one user so not quite sure where all that was coming from but once I installed 7.1.1 again with the -w included I was fine
 
  • Like
Reactions: 0hfrankieboy
0

0hfrankieboy

Member
Oct 10, 2016
33
16
0
Apr 10, 2017 at 5:45 PM
canemaxx said:
Yes that's exactly what happened to me so I did the clean install of 7.1.1 let the phone update completely via the OTA to the k build then I installed TWRP and SuperSU and I've had no issues since. I did have to fully unroot again to get Snapchat installed and logged into and then rerooted all is well now

---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------


Sounds like you had some data carry over when you reverted ...I had the same FC and when I went to developer options it said it wasn't available for that user..I only had one user so not quite sure where all that was coming from but once I installed 7.1.1 again with the -w included I was fine
Click to expand...
Hmm.. I never removed the -w. Let me run you through the steps I took to see if there is anything I might have done wrong.
1. Reverted to 7.1.1 NOF27B with the flash-all.bat
2. Noted that I was on slot A
3. Took OTA update for K build
4. Rebooted into Bootloader and noticed that slot had switched to B, 7.1.2 got pushed into slot B although I had taken the update through slot A.
5. Switched back to Slot A and noticed that it was still on 7.1.1 and force closing constantly.
6. Took OTA again through slot A, but once again it did not stick and slot got switched to B.

Note that this only happens with the K build I did not have this issue when I flashed N2G47E originally.
 
canemaxx

canemaxx

Senior Member
Aug 23, 2012
538
59
0
Wilder,VT
Apr 10, 2017 at 5:48 PM
0hfrankieboy said:
Hmm.. I never removed the -w. Let me run you through the steps I took to see if there is anything I might have done wrong.
1. Reverted to 7.1.1 NOF27B with the flash-all.bat
2. Noted that I was on slot A
3. Took OTA update for K build
4. Rebooted into Bootloader and noticed that slot had switched to B, 7.1.2 got pushed into slot B although I had taken the update through slot A.
5. Switched back to Slot A and noticed that it was still on 7.1.1 and force closing constantly.
6. Took OTA again through slot A, but once again it did not stick and slot got switched to B.

Note that this only happens with the K build I did not have this issue when I flashed N2G47E originally.
Click to expand...
When you take the OTA it switches to the inactive slot which is b then you need to clean install build b then take the OTA.....That's what I did
 
  • Like
Reactions: 0hfrankieboy
0

0hfrankieboy

Member
Oct 10, 2016
33
16
0
Apr 10, 2017 at 5:52 PM
canemaxx said:
When you take the OTA it switches to the inactive slot which is b then you need to clean install build b then take the OTA.....That's what I did
Click to expand...
Thank you for the prompt replies, if I understand correctly I need to clean install build B again while in slot B and take the OTA again through slot B?
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone