Hi
i cant update my nexus 5 to android 4.4.4... from 4.4.3 i tried updating it automaticly with system update from the phone settings but after few seconds of instalation it says error with a dead android on screen. i tried to update it manualy from computer with nexus root toolkit it works but it says unfortunately android setting has stopped on screen and i can absolutly do nothing cause the message always pop up on screen. i returned to 4.4.3 with the same method. did some research on the xda forums and they say return to stock then update from phone, but when i returned to stock it also says unfortunatly android settings has stopped this time on 4.4.3. now i'm on 4.4.3 factory image taken from google flashed with nexus root toolkit the phone is rooted, bootloader unlocked and with a custom recovery. the phone shows me a notification to update 4.4.4 every time i open it. is there any other method to go 4.4.4 or a way to fix this android setting error ?
thanks
iBoum69 said:
Hi
i cant update my nexus 5 to android 4.4.4... from 4.4.3 i tried updating it automaticly with system update from the phone settings but after few seconds of instalation it says error with a dead android on screen. i tried to update it manualy from computer with nexus root toolkit it works but it says unfortunately android setting has stopped on screen and i can absolutly do nothing cause the message always pop up on screen. i returned to 4.4.3 with the same method. did some research on the xda forums and they say return to stock then update from phone, but when i returned to stock it also says unfortunatly android settings has stopped this time on 4.4.3. now i'm on 4.4.3 factory image taken from google flashed with nexus root toolkit the phone is rooted, bootloader unlocked and with a custom recovery. the phone shows me a notification to update 4.4.4 every time i open it. is there any other method to go 4.4.4 or a way to fix this android setting error ?
thanks
Click to expand...
Click to collapse
read this thread carefully http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
This is why you should learn adb and not use toolkits!!
Also :
shoeseat said:
read this thread carefully http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
This!!!
shoeseat said:
read this thread carefully http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
thanks i'll give it a try !
shoeseat said:
read this thread carefully http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
tried option 1 and it gave me this:
verifying current system...
"/system/priv-app/Settings.apk" has unexpected contents.
E:error in /tmp/update.zip
(status 7)
Instalation aborted
iBoum69 said:
tried option 1 and it gave me this:
verifying current system...
"/system/priv-app/Settings.apk" has unexpected contents.
E:error in /tmp/update.zip
(status 7)
Instalation aborted
Click to expand...
Click to collapse
thats because you or an app modified the system.apk
Zepius said:
thats because you or an app modified the system.apk
Click to expand...
Click to collapse
and how do i fix that ?
iBoum69 said:
and how do i fix that ?
Click to expand...
Click to collapse
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk
iBoum69 said:
and how do i fix that ?
Click to expand...
Click to collapse
Download and flash vomer's stock rooted 4.4.4 rom via a custom recovery. That's all you need to do.
Related
Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Start here, then still questions in that thread
http://forum.xda-developers.com/showthread.php?p=69234
Sent from my Nexus 5 using XDA Free mobile app
Hello,
Thanks for your reply. I can't access your link though.
D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Something is goofed up with xda. It's the ota help in the general forum. Look for it there. Should have everything you need
Sent from my Nexus 5 using XDA Free mobile app
D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
D5R said:
Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Click to expand...
Click to collapse
First thing, turn off mobile data. Your phone may try re-download it over and over again and use up your mobile data plan.
To install the ota via the ota update on the stock rom you will need to return to stock recovery and maybe stock kernel (not sure about this one).
NOTE: Before trying the below steps as I haven't tested them myself, please backup your ROM first. Better safe than sorry.
You can try installing the OTA updates manually from TWRP. You can find the links in the post - http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327.
If you are running 4.4.2 KRT16M you will need to download three updates.
1. KTU84M from KOT49H (4.4.2 update to 4.4.3)
2.KTU84P from KTU84M (4.4.3 update to 4.4.4)
Download them together and also put on a flashable zip of TWRP in the same location as it looks like it will reinstall the stock recovery.
You can even put on one of Franco kernel just in case too.
In TWRP select install zip and install number 1 first, then install 2. and finally install TWRP again. You should be updated to 4.4.4.
You can then install Franco kernel again just in case.
I hope this makes it easier.
EDIT: follow the link in the previous post as it has different scenarios and the steps needed.
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
JayZeus said:
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
Click to expand...
Click to collapse
If you made some modification to the 4.4.2 rom you'll have to restore the stock before upgrading to 4.4.4.
Bootloader can be unlocked, Recovery can be custom but any mod/root to the room will cause the error.
To restore to stock follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219
Thanks a lot, it worked!
By the way is the part where you erase you data mandatory ? In case I have to do this again.
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ! Thank you.
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) [emoji481]
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This way I'll keep my installed applications?
Thanks.
4.4.2 > 4.4.4. just rolled out in UK (o2 moto g).
right after i get my phone rooted and started setting it up...
Thanks for this thread.. what's the minimum we have to restore, basically the system partition so it's unrooted?
If we have stock 4.4.2 (rooted) can we flash JUST these 3 files?
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
and skip the rest? I want to save redo-ing as much as possible..
I got the 4.4.4 OTA today (210.12.40.en.GB) and I have unlocked bootloader + Philz recovery - Philz worked fine for the 4.4.2 OTA update, but when I downloaded the 4.4.4 OTA and rebooted Philz would abort with "a status 7" mismatch error and then the phone would boot to Android, then 20 seconds later shutdown and reboot to Philz again, continuously. After some playing, I did the following:
1. Flashed stock recovery (taken from Mototool AIO's 4.4.2 stock.img) from fastboot - re-downloaded the 4.4.4 OTA but that failed with "Error!"
2. Flashed stock kernel (I was running faux123) - same issue, 4.4.4 OTA failed still.
3. Flashed latest Philz recovery again (philz_touch_6.50.6-falcon.zip) then
4. Flashed stock 4.4.2 GB kernel (to match my OTA version) - kernel from here http://forum.xda-developers.com/showthread.php?t=2649763 - success... OTA downloaded and this time installed.
SO, conclusion is you don't need stock recovery to flash OTA, BUT you do need the correct kernel for your update and having a custom kernel causes the mismatch error.
Hope this helps someone!
So the UPDATE-SuperSU-v1.91.zip in MotoG-Tools.zip still works to root 4.4.4 right?
i found it here
http://www.swedroid.se/forum/showthread.php?t=106595
and this is what i used for 4.4.2
Most of the old guides around no longer worked in 4.4.2, i dunno if they closed any other holes in 4.4.4?
edit: version typo sorry
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
JayZeus said:
I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error.
Click to expand...
Click to collapse
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
agoodhi said:
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
Click to expand...
Click to collapse
I figured it out... I simply did a delete cache from CWM recovery and now no more boot loop.
fatechand said:
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
Click to expand...
Click to collapse
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Smiff2 said:
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Click to expand...
Click to collapse
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
fatechand said:
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
Click to expand...
Click to collapse
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
---------- Post added at 06:32 AM ---------- Previous post was at 06:14 AM ----------
agoodhi said:
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
Click to expand...
Click to collapse
CWM message:
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
assert failed: getprop("ro.product.device) == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma"
E: Error in /cache/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
(Status 7)
Installation aborted.
Rebooting...
fatechand said he had CWM 6047 installed and OTA update was ok. he just had to re-root? perhaps difference between 6046 and 6047 CWM, or some difference in way you rooted?
I have same recovery, rooted, 4.4.2, so should work... ?
I'm using nexus 5 running stock android 4.4.4 build no. KTU84Q. Got notification for android lollipop upgrade and i started downloading on wifi. After completion of download it shows verifying and then shows verification failed and after sometime starts downloading again. I have not installed custom ROM anytime in my phone.i have stable net connection and I have repeated the download for 4 times now but it's still showing verification failed.pls help
milan100kar1 said:
I'm using nexus 5 running stock android 4.4.4 build no. KTU84Q. Got notification for android lollipop upgrade and i started downloading on wifi. After completion of download it shows verifying and then shows verification failed and after sometime starts downloading again. I have not installed custom ROM anytime in my phone.i have stable net connection and I have repeated the download for 4 times now but it's still showing verification failed.pls help
Click to expand...
Click to collapse
Same here..... I tried with adb sideload and it shows that unexpected contents in platform.XML which is in Systems/etc/permission/platform.XML I and used SD fix tool and it changed my platform.XML file and I don't have backup.
Please if you found any way to update it than do lemme know. Thanks in advance.
milan100kar1 said:
I'm using nexus 5 running stock android 4.4.4 build no. KTU84Q. Got notification for android lollipop upgrade and i started downloading on wifi. After completion of download it shows verifying and then shows verification failed and after sometime starts downloading again. I have not installed custom ROM anytime in my phone.i have stable net connection and I have repeated the download for 4 times now but it's still showing verification failed.pls help
Click to expand...
Click to collapse
Did you make any modifications to the system? Xposed? Everything must go back to stock in order for OTA to be applied.
jasonftfw said:
Did you make any modifications to the system? Xposed? Everything must go back to stock in order for OTA to be applied.
Click to expand...
Click to collapse
Yes everything is stock . i never tweaked my system anyway. I dunno can any app cause this thing. I dont wanna sideload..
milan100kar1 said:
Yes everything is stock . i never tweaked my system anyway. I dunno can any app cause this thing. I dont wanna sideload..
Click to expand...
Click to collapse
If you are 100% stock there should be no issue. Are you running custom recovery? Do you have Xposed?
jasonftfw said:
If you are 100% stock there should be no issue. Are you running custom recovery? Do you have Xposed?
Click to expand...
Click to collapse
Not running on custom recovery .. Not Xposed ever. I never tweaked my nexus anyway. I'm trying agin to update!! May be I have to do a factory reset !!
milan100kar1 said:
Not running on custom recovery .. Not Xposed ever. I never tweaked my nexus anyway. I'm trying agin to update!! May be I have to do a factory reset !!
Click to expand...
Click to collapse
Try to sideload first, I had some issues with ota failing on device but then sideload worked.
jasonftfw said:
Try to sideload first, I had some issues with ota failing on device but then sideload worked.
Click to expand...
Click to collapse
Ok , I'll try that first. May be it has do with network connection. I'm using my othe cellphone's data and using its tethring to update ??
I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.
HopperPlaysMC said:
I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.
Click to expand...
Click to collapse
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?
dustcollector69 said:
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?
Click to expand...
Click to collapse
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"
HopperPlaysMC said:
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"
Click to expand...
Click to collapse
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader
dustcollector69 said:
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader
Click to expand...
Click to collapse
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.
I'm also going to try sideloading 5.0 again after clearing dalvik/cache again.
HopperPlaysMC said:
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.
Click to expand...
Click to collapse
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Will give it a try, but if not I will tell you what I see after trying to sideload to 5.
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Got GPE 4.4.4 running, I shall now try 5.0.1
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.
HopperPlaysMC said:
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.
Click to expand...
Click to collapse
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?
probably its corrupted, try download the ota from settings menu and tell us
esd316 said:
probably its corrupted, try download the ota from settings menu and tell us
Click to expand...
Click to collapse
OTA isn't showing up, but it may be corrupted
dustcollector69 said:
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?
Click to expand...
Click to collapse
Here's the link: goo.gl/zDJG9q (That'll directly download it)
HopperPlaysMC said:
Here's the link: goo.gl/zDJG9q (That'll directly download it)
Click to expand...
Click to collapse
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
dustcollector69 said:
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I have clockwork recovery, I will attempt to flash one of those later.
All of the ROMs for my phone on http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 are Brazilian.
Yep flash a stock rom for xt1032 (try a optimized) and that should work
esd316 said:
Yep flash a stock rom for xt1032 (try a optimized) and that should work
Click to expand...
Click to collapse
Can you link me one? Or do i just do a Brazilian one?
Tried installing the Brazilian one and... my phone is messed up again and I have no idea how I fixed it. Help again?
Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
Code:
...
....
Source: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS254 : user/release-keys
Target: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys
Verifying current system...
Package expects build fingerprint of oneplus/bacon/A0001/6.0.1/MHC19Q/ZNHKAS254 : user/release-keys or oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys;
this device has oneplus/bacon/A0001: 5.1.1/LMY48B/YOG4PAS1NO: user/release-keys
Updater process ended with ERROR: 7
Error installing zip file '@/cache/recovery/block.map
...
...
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!
Sopis said:
Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!
Click to expand...
Click to collapse
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.
Durso81 said:
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.
Click to expand...
Click to collapse
hi, thanks for your reply..I did that but it did not work
Sopis said:
hi, thanks for your reply..I did that but it did not work
Click to expand...
Click to collapse
What do you mean did not work? What happen when you flashed all the stock files via fastboot?
are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..
Sopis said:
are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..
Click to expand...
Click to collapse
Are you running stock recovery or twrp? Cause your title says twrp.
hey, I got it finally..thanks for the effort...thread can be deleted