Develop Bugs

Help! Is there a Verizon KDZ for the new VS98612a?

For some reason my phone will not let me take the newest update for the Verizon G4. Does anybody know of another way besides OTA or Verizon Update Assistant that I could update my phone? Can't find the KDZ to try and flash. Any help would be appreciated. Thank You

Mine won't see it either. They may have pulled the update?

Are you rooted?

geoff5093 said:
Are you rooted?
Click to expand...
Click to collapse
No not rooted

I would also love to hear of a way to update to Verizon's 12a without OTA. I unrooted my 11a version in order to get 12a to fix touchscreen issues. It seems the 12a OTA is not around, at least verizon doesn't want to give it to me.
Oddly enough after using kdz for 11a my software showed status as "Official". But a few hours later it switched to Modified, even though I'm not rooted. Not sure why.

I don't see it either
photos.by.fako said:
For some reason my phone will not let me take the newest update for the Verizon G4. Does anybody know of another way besides OTA or Verizon Update Assistant that I could update my phone? Can't find the KDZ to try and flash. Any help would be appreciated. Thank You
Click to expand...
Click to collapse
Same here, my phone is unrooted, and it is on Verizon Network.
I have tried OTA update, it keep saying i already have the latest update (which is 11A)
I have also tried Verizon Update Assistant Installer (working in windows 7, but not in Windows 10), same thing, when I tried to update, it keep saying I already have the latest update (which is 11A)
do any one know Verizon push OTA by the list? (e.g. some people will get first, and some people will get last) or every one should get OTA at once?
Also, is possible Verizon pull the 12A update due to notification issue?
thanks

It's highly likely that Verizon pulled this update. Nobody has reported receiving it since about 10/10. I'm sure we'll see a new one drop soon that fixes whatever was wrong with 12A.

oldblue910 said:
It's highly likely that Verizon pulled this update. Nobody has reported receiving it since about 10/10. I'm sure we'll see a new one drop soon that fixes whatever was wrong with 12A.
Click to expand...
Click to collapse
Thanks for the info.
Hoping Verizon does not take too much time, We will get Marshmallow soon, then 12A is no longer needed.

Installing the Official 6.0.1 update via Samsung Kies or Odin or different method.

Hey everyone.
I'm running on completely Stock 5.1.1 OK1 on my Note 4 and just recieved the official MM OTA update last night. Due to my phone having a lot of junk and being laggy I decided to flash the official firmware from any external method to have a clean install of the os. I heard about Samsung Kies which makes a back up of your phone and installs the latest os, I installed and backed up my phone last night but it didn't seem to give me an update on the os, it said "This is the latest version" (5.1.1 COK1).
My main concern about this is. I've bought this phone from Pakistan (used phone but in brand new condition) and I'm currently living in Malaysia and I have no idea who was the previous owner of this phone. In Kies it shows the phone number different than what I have (maybe its the Sprint phone number?).
What if my carrier is locked by having a clean install? Or any sort of other related issue occurs.
Please take some time to enlighten the facts from your knowledge, will highly appreciate it.
Regards.

waiting for official release bro. If rom is released on sammobile, see the icon kies highlighted on the right.

zincbros said:
waiting for official release bro. If rom is released on sammobile, see the icon kies highlighted on the right.
Click to expand...
Click to collapse
Yeah but you totally missed my question here.
Its not that I don't want to do some research myself, I'm a student and I'm busy most of the time. So if anyone can take out their precious time to answer my question I'd really appreciate the help.

If you're concerned about your phone or sim getting lock..you can just use galaxy tools apk v3.1.5 & then upgrade the apk to v3.1.8 & it will unlocked it for you... but i doubt it will lock you down... maybe you can just try to back your rom completely & restore if any issues encounter

it's dependent on the way that they unlocked the phone, someone in vietnam has been locked after updated the phone, but my phone was not.

zincbros said:
it's dependent on the way that they unlocked the phone, someone in vietnam has been locked after updated the phone, but my phone was not.
Click to expand...
Click to collapse
And I have no idea how my phone was unlocked, I just bought it like this. I can see the Sprint phone number on Samsung Kies maybe I should write an email to Sprint asking them to unlock it using that Sprint phone number?

Help regarding unrooting, restoring and accepting 7.1.1 OTA.

Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')

sheri.khan said:
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
Click to expand...
Click to collapse
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551

Jimi Mack said:
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Click to expand...
Click to collapse
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?

sheri.khan said:
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
Click to expand...
Click to collapse
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...

Jimi Mack said:
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Click to expand...
Click to collapse
Thanks brother.
I don't seem to get why the RETGB firmware isn't released.
I literally can't find anyone except i guess two or just 3 people who have the same software channel.
Thanks again!

On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?

jzamalot said:
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
Click to expand...
Click to collapse
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D

sheri.khan said:
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
Click to expand...
Click to collapse
Thanks, just wondering because the blackberry priv bootloader was also never unlocked or ever rooted

No OTA update after converting Unlocked to TMB

I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.

live_in_the_sky06 said:
I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.
Click to expand...
Click to collapse
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.

Yeah I did that. I'll back up my data and flash the old update, factory reset, and then see if it'll pull the latest update. Thanks. I've read where a couple of people are having issues with ota updating

I brought my Sprint Note 9 to TM. I didn't flash anything, but couldn't get OTA updates. I know I could have flashed TM, but I was lazy. I called my TM experts. They called Samsung. Samsung looked up to see where the nearest Samsung tech was. It was at a Best Buy. She was in the Geek Squad area. She evidently flashed the TM firmware. After that I was able to get the TM OTAs. There was no charge for this. I happily upgraded to the 10+ 5G when TM got it. I love it! It also came with Android 10 on it.

scottusa2008 said:
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.
Click to expand...
Click to collapse
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.

live_in_the_sky06 said:
... In the T-Mobile app my device shows as "Unknown device".....
Click to expand...
Click to collapse
This is normal since you brought your own device and didn't purchase it from T-Mobile.
live_in_the_sky06 said:
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.
Click to expand...
Click to collapse
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1

scottusa2008 said:
This is normal since you brought your own device and didn't purchase it from T-Mobile.
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1
Click to expand...
Click to collapse
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.

live_in_the_sky06 said:
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.
Click to expand...
Click to collapse
Yes

scottusa2008 said:
Yes
Click to expand...
Click to collapse
Thanks for your help

Question Custom OTA sideload with November radio?

My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?

The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/

Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?

If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.

I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.

chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)

Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.

chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.

TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.

chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.​

roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.​
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.

I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.

NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.

chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!