Related
My NEXUS 7 (2013) is running on Android 4.3 with the build version JWR66N
The Problem is that i get an OTA update notification for Android 4,3 System Update which is of appx (56 MB).
When i try to install it the Tab reboots and the update fails and it restarts again with the same build version ie. JWR66N.
Again after 2-3 days i get the same notification for that 4.3 System update and again it fails. PLEASE HELP !!!
How will i update to android 4.4 ???
I dont want to sideload or root.... Please suggest a normal fix !!!
Have you done any modifications to your n7 usually that borks any ota update
church said:
Have you done any modifications to your n7 usually that borks any ota update
Click to expand...
Click to collapse
No... I have not done any change.... After booting for the very first time i got an update which worked fine.... Then this OTA update message keeps coming but it never gets installed as it gives an error
red_ferrari007 said:
My NEXUS 7 (2013) is running on Android 4.3 with the build version JWR66N
The Problem is that i get an OTA update notification for Android 4,3 System Update which is of appx (56 MB).
When i try to install it the Tab reboots and the update fails and it restarts again with the same build version ie. JWR66N.
Again after 2-3 days i get the same notification for that 4.3 System update and again it fails. PLEASE HELP !!!
How will i update to android 4.4 ???
I dont want to sideload or root.... Please suggest a normal fix !!!
Click to expand...
Click to collapse
You likely have the problem that some system files got corrupted because of bad EMMC.
When the update fails and you have the fallen android, press/hold Power, then press/release VolUp, then release Power.
This will show you the error and can confirm or refute this diagnosis.
If you want to get past it in the more efficient manner, you'll probably need to unlock the bootloader, then flash one of the factory images.
I will see that when the OTA notification comes again..... But how can I solve the problem.... is anyone else facing it ?
Will I get an Android 4.4 update ?
Sent from my Nexus 7 using xda app-developers app
red_ferrari007 said:
I will see that when the OTA notification comes again..... But how can I solve the problem.... is anyone else facing it ?
Will I get an Android 4.4 update ?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
As I mentioned you'll probably need to flash a factory image to get around it, or you'll have to identify each file that is corrupted and replace it.
If you don't resolve the problem you won't get the 4.4 update automatically, but you can manually install the 4.4 factory image.
sfhub said:
As I mentioned you'll probably need to flash a factory image to get around it, or you'll have to identify each file that is corrupted and replace it.
If you don't resolve the problem you won't get the 4.4 update automatically, but you can manually install the 4.4 factory image.
Click to expand...
Click to collapse
see i found this link which apparently is talking about the same problem and a fix
http://forum.xda-developers.com/showthread.php?t=2380258
but i dont know anything about rooting and flashing.... Thats why i am afraid to do anything
red_ferrari007 said:
see i found this link which apparently is talking about the same problem and a fix
http://forum.xda-developers.com/showthread.php?t=2380258
but i dont know anything about rooting and flashing.... Thats why i am afraid to do anything
Click to expand...
Click to collapse
I and the op posted extensively in that thread. All the solutions there require unlocking your bootloader. If you are going to do that you might as well just flash the factory image.
Ya see that's what the problem is I don't know what's unlocking boot loader and flashing stock ram etc
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I and the op posted extensively in that thread. All the solutions there require unlocking your bootloader. If you are going to do that you might as well just flash the factory image.
Click to expand...
Click to collapse
So if i flash STOCK ROM of a next version would everything be fine ???
I found this video which shows the tutorial
Is it correct ?
http://www.youtube.com/watch?v=bsss9e71bKo&feature=youtube_gdata
red_ferrari007 said:
So if i flash STOCK ROM of a next version would everything be fine ???
I found this video which shows the tutorial
Is it correct ?
http://www.youtube.com/watch?v=bsss9e71bKo&feature=youtube_gdata
Click to expand...
Click to collapse
Person on the other thread mentioned they got a JWR66N->KRT16S OTA update.
Previously we had only seen JSS15R->KRT16S updates, which would mean you would need to get from JWR66N->JSS15R first. The JWR66N->JSS15R update would fail for you, but there is a chance a JWR66N->KRT16S update would work because more files are shipped whole and not as patches.
Regarding the youtube video, it should get your where you need to be. I would skip the relocking of your device though to keep future flexibility in case something like this happens again.
If you want to be on KRT16S(4.4), then just flash the KRT16S factory image. If you want to be on the latest 4.3 then flash JSS15R.
Keep in mind unlocking the bootloader will erase your use data (including your virtual sdcard) so backup anything important and move it off the tablet to your PC or the cloud.
GOT 4.4 UPDATE...Facing Problems
Today Morning I Finally Got Android 4.4 Update OTA. I installed it..... Installation went smooth...
The Tablet Workded fine for 5-6 Hours.... Now I am getting all types of touch screen issues...
1)Non Responsive
2)Ghost Touch
3)Lagging
Please Help
sfhub said:
Person on the other thread mentioned they got a JWR66N->KRT16S OTA update.
Previously we had only seen JSS15R->KRT16S updates, which would mean you would need to get from JWR66N->JSS15R first. The JWR66N->JSS15R update would fail for you, but there is a chance a JWR66N->KRT16S update would work because more files are shipped whole and not as patches.
Regarding the youtube video, it should get your where you need to be. I would skip the relocking of your device though to keep future flexibility in case something like this happens again.
If you want to be on KRT16S(4.4), then just flash the KRT16S factory image. If you want to be on the latest 4.3 then flash JSS15R.
Keep in mind unlocking the bootloader will erase your use data (including your virtual sdcard) so backup anything important and move it off the tablet to your PC or the cloud.
Click to expand...
Click to collapse
Hi, i was that guy on the other thread,i was wondering why i receive different size of ota of kit kat 253.1mb...others almost receiving 242.5 here on our forum of nexus 7.2 philippines wifi version,just wondring why different file size?
Sent from my Nexus 7 using xda premium
Touchsreen Dead
and2nckiko said:
Hi, i was that guy on the other thread,i was wondering why i receive different size of ota of kit kat 253.1mb...others almost receiving 242.5 here on our forum of nexus 7.2 philippines wifi version,just wondring why different file size?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
SOMETHING HAS GONE HORRIBLY WRONG MAN !!!!
My Entire Screen is dead !!! I mean the TAB is Working but My screen is Not Responding !!!! I am Screwed !!!!!
How Can I chat with u contact u ?
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk
Hello All!
I'm sorry if this has been asked before but I'm trying to install nougat on my phone and having some great difficulty.
So far my phone is flashed and I was running TWRP 3.0.2 however every time i try to flash a lineage 14.1 based rom it would never work. (tried straight lineage 14.1, nutOS, DOT) none of them worked (wiped the phone clean, then received error 7, removed the assert lines that let in install but just perpetually boot looped) . My many a google searches makes me believe that that particular version of TWRP does not work with nougat. but that's the only version I am able to get working. any newer version of TWRP gets stuck in a perpetual boot loop.
So with that said, if my suspicious are correct and i need a newer version is there anything I'm missing to install a newer version of TWRP? if 3.0.2 is a good enough version to install nougat based rom's what am I missing on that end?
Any help at all would be greatly appreciated! and Thanks in advance!
Ninja edit: I'm runnnig the Z00A (Z551ML) and i've been using using roms/images meant for Z00A
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Slent said:
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Click to expand...
Click to collapse
Yup that was it. My google-fu is off as i found my answer from a reddit post (5 seconds after asking this question in reddit...) My issue was that i was still on lolipop, the last OTA update and had no idea asus put out a manual update. worst part is, after unlocking the bootloader installing twrp, THEN installing that oem update, that might have cause my phone to crash mid update so it ended up bricking the phone...
I was able to Frankenstein it back together with old parts that I thought were no good, right now I'm on that last manual update and I gotta fight through a few issues preventing the boot loader from being unlocked.
Anyway you were correct, using the last OTA update updates the bootloader so I was stuck cause of that.
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
awarman said:
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
Click to expand...
Click to collapse
are you rooted?
Yes but I have removed root and tried, same thing. Cleared dalvik cache, same thing.
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
hallo dare said:
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Click to expand...
Click to collapse
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
awarman said:
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
Click to expand...
Click to collapse
You won't get incremental if rooted, only full updates.
hallo dare said:
You won't get incremental if rooted, only full updates.
Click to expand...
Click to collapse
So in theory, if I unroot then run OnePlus updater I should be able to get the update. Then reboot after. Correct?
Maybe I did something wrong, but I tried unrooting for the last OTA and still received the same error. I had to wait until the full version was on the OnePlus site, I think OnePlus updater grabs the zip from there too. It also took a month longer for the full zip to hit the OnePlus site.
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
I have global unlocked varient and when I first received it I just flashed BA/EU on both slots(local upgrade twice) and I've been able to get all full zip updates(via system updates and/or O2 updater app) staying rooted the whole time. I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Initially I was getting that error. Then I ran the uninstall in Magisk and chose to RESTORE IMAGES. I then just hit retry on the OTA from the phone settings (NOT Oxygen Updater) and the update installed. Initially this did not for 11.2.3.3 as it would still give the error after unrooting by uninstalling Magisk, then it worked for 11.2.4.4 and 11.2.5.5. So YMMV. You can look here for my update process as I was having an issue post-OTA:
No cell service after update to 11.2.4.4AA while keeping root
I'll try to keep this short. Global OP9 Pro on 11.2.2.2AA, bootloader unlocked, rooted w/Magisk. Been trying to find the best way to update. Decided on trying this: 1. Un-rooting by going in to Magisk and doing UNINSTALL->RESTORE IMAGES 2...
forum.xda-developers.com
jammin6996 said:
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
Click to expand...
Click to collapse
This worked, btw. Never had to do this with my OP8P. Hopefully this isn't a regular occurrence.
Shooter7889 said:
I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Click to expand...
Click to collapse
Not knowing that the AA variant would have dog**** updates from the start, and already having restored my old phone's data and not wanting to go through setup and restore again.
Edit: The goal is also to eventually get on crDroid anyway so it's whatever. I'm not resetting until there's an official crDroid build out.
Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.
Which phone version do you have?
luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.
skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing
I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!
TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,
I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.