My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium
Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app
heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??
How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.
Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Tinfoil Hat Tom said:
Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Flash the complete 4.4 KRT16S factory image. Download from here and extract the zip to your adb/platform tools directory. Make sure your drivers are working properly. If you don't want your data wiped, edit flash-all.bat and remove -w. Connect your phone and boot into the bootloader (you can do this by opening cmd in adb directory and entering "adb reboot bootloader"). Now simply run the flash-all script and wait for it to complete. You are now on KitKat 4.4
Flash TWRP and anything else you want to flash. Download and flash the 4.4.2 update if you want.
Thanks a lot for the quick reply. I managed to get root and twrp back using wugfresh's kit. It seems to me that twrp is not good with OTAs(there is a page on their site re. this) which might be the reason for this mess.
So now instead of flashing the zip using adb, can i do it with twrp? I dont have much experience with adb since i have always used twrp. (I am not averse to using cmd but the 480 mb download for the sdk just to get adb and stuff puts me off).
Do I necessarily need to wipe my data to install the kitkat update?
Sent from my Nexus 4 using xda app-developers app
Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!
dragancla said:
Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!
Click to expand...
Click to collapse
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?
Razor is the 2013 model. You might want to mention that before people here download your link and ruin their grouper or tilapia....
Why wouldn't you just download the stock images straight from Google? You didn't need to downgrade anything and you don't use Odin with a nexus....
Sent from my Nexus 5
dragancla said:
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?
Click to expand...
Click to collapse
Possibly...
Any modifications you may have made to your Nexus 7 (other then rooting and a Custom Recovery installed) will almost certainly cause an OTA to fail... as an OTA first runs a checksum verification test on all system files to ensure they are the original system files.
If they've been modified by the user, they cannot be 'patched', ie. updated... so the OTA aborts with no changes made.
Anyway... you really should be posting your question(s) here...
http://forum.xda-developers.com/nexus-7-2013
...as the Razor recovery you posted clearly identifies your device as a second generation Nexus 7(2013), and as @Pirateghost points out, posting that recovery in this forum could potentially mess up other peoples devices, if they were to flash it.
Rgrds,
Ged.
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind
This is my first post here because I usually find answers on my own but this seems to be an unsolved issue everywhere so please excuse me if I do not follow a proper format.
My Nexus 4's USB is broken (not the wire, but the actual microUSB) so I can charge fine but cannot connect to the computer. It is unlocked and rooted and I do not mind losing my data (everything is backed up) but I cannot get the update without a PC.
A way to get the update very easily and without losing data was to flash the OTA zip using TWRP 2.7 but it gave me an error saying it cannot install zips from sdcard. So I flashed the latest CWM which can do it but it gave me an error saying "package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or googleoccam/mako:5.0/LRX21P/1570855:user/release-keys; this device has google/occam/mako:4.3/JWR66Y/779366:user/release-keys." but my phone has 4.4.4 KTU84P and I know that. I am wondering if it is because of the weird looking kernel I have due to my use of Wug's NRT in the past so I flashed stock recovery to factory reset but when I found out my phone was going to be locked again, I flashed CWM using Flashify again. I'm attaching the screenshot of my 'about' below.
Since I do not mind losing data by flashing a factory image, is there any way I can do it without connecting it to the PC? Because I really want this phone to return to stock? (I know with Flashify you cannot) but I'm apprehensive of locking the phone again because I'd really like to root and install custom recoveries etc.
Thanks in advance!
NishkarshChugh said:
This is my first post here because I usually find answers on my own but this seems to be an unsolved issue everywhere so please excuse me if I do not follow a proper format.
My Nexus 4's USB is broken (not the wire, but the actual microUSB) so I can charge fine but cannot connect to the computer. It is unlocked and rooted and I do not mind losing my data (everything is backed up) but I cannot get the update without a PC.
A way to get the update very easily and without losing data was to flash the OTA zip using TWRP 2.7 but it gave me an error saying it cannot install zips from sdcard. So I flashed the latest CWM which can do it but it gave me an error saying "package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or googleoccam/mako:5.0/LRX21P/1570855:user/release-keys; this device has google/occam/mako:4.3/JWR66Y/779366:user/release-keys." but my phone has 4.4.4 KTU84P and I know that. I am wondering if it is because of the weird looking kernel I have due to my use of Wug's NRT in the past so I flashed stock recovery to factory reset but when I found out my phone was going to be locked again, I flashed CWM using Flashify again. I'm attaching the screenshot of my 'about' below.
Since I do not mind losing data by flashing a factory image, is there any way I can do it without connecting it to the PC? Because I really want this phone to return to stock? (I know with Flashify you cannot) but I'm apprehensive of locking the phone again because I'd really like to root and install custom recoveries etc.
Thanks in advance!
Click to expand...
Click to collapse
For the ota to work you need the stock recovery and no system files modified or deterred. I would flash the stock recovery in flashify and try the ota again
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
For the ota to work you need the stock recovery and no system files modified or deterred. I would flash the stock recovery in flashify and try the ota again
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
This post may help you http://forum.xda-developers.com/nexus-4/development/rom-flashable-stock-rom-radio-kernel-t2527806
pm_dsp_ra said:
This post may help you http://forum.xda-developers.com/nexus-4/development/rom-flashable-stock-rom-radio-kernel-t2527806
Click to expand...
Click to collapse
Thank you! This is a working solution, got the sweet OTA on my phone!
Requesting the mods to close this thread. Thank you!
Same problem for me (but to go to 5.0.1 from 5.0)
I re-flashed stock kernel and radio, but still the same message.
Why this 4.3 message??
Edit : wait, I forgot to flash stock recovery