Ok so I sideloaded 4.4 on to my tablet. I did it on stock no Rom and not rooted. I downloaded the .zip from android police.
http://www.androidpolice.com/2013/11/13/your-kitkat-is-ready-download-and-flash-android-4-4-ota-update-krt16o-for-2013-wi-fi-nexus-7/
Everything worked out great and looked well. But then I noticed, that may mic input wasn't working. Every time I try to use google search or mic input on the keyboard, The mic icon will just flash randomly as if it's picking up sound, but never pick up my voice. Now I wanted to know if there is a fix for this, or did I just **** up my sideload?
I've tried to use the Official Factory Image for both 4.3 and 4.4, but I keep getting the error:
E:footer is wrong
E:signature verification is wrong
Any help would be great, Thank You.
jpxzero said:
Ok so I sideloaded 4.4 on to my tablet. I did it on stock no Rom and not rooted. I downloaded the .zip from android police.
http://www.androidpolice.com/2013/11/13/your-kitkat-is-ready-download-and-flash-android-4-4-ota-update-krt16o-for-2013-wi-fi-nexus-7/
Everything worked out great and looked well. But then I noticed, that may mic input wasn't working. Every time I try to use google search or mic input on the keyboard, The mic icon will just flash randomly as if it's picking up sound, but never pick up my voice. Now I wanted to know if there is a fix for this, or did I just **** up my sideload?
I've tried to use the Official Factory Image for both 4.3 and 4.4, but I keep getting the error:
E:footer is wrong
E:signature verification is wrong
Any help would be great, Thank You.
Click to expand...
Click to collapse
Hey hey,
You shouldn't sideload the KRT16S factory image. You need to sideload the ota update (marked KRT16O->KRT16S OTA - flo/WiFi) at http://forum.xda-developers.com/showthread.php?t=2534698. That's assuming you are currently on KRT160 of course.
mbdw said:
Hey hey,
You shouldn't sideload the KRT16S factory image. You need to sideload the ota update (marked KRT16O->KRT16S OTA - flo/WiFi) at http://forum.xda-developers.com/showthread.php?t=2534698. That's assuming you are currently on KRT160 of course.
Click to expand...
Click to collapse
Thanks, I side loaded KRT16O. That's when my mic first stopped working. The OTA update to KRT16S came out 2 days later. So I updated to it OTA. So I am currently on KRT16S... Any ideas?
Thanks for the reply btw!
jpxzero said:
Thanks, I side loaded KRT16O. That's when my mic first stopped working. The OTA update to KRT16S came out 2 days later. So I updated to it OTA. So I am currently on KRT16S... Any ideas?
Thanks for the reply btw!
Click to expand...
Click to collapse
My first course of action would be a wipe in recovery of the data and cache. Have you already tried that route?
mbdw said:
My first course of action would be a wipe in recovery of the data and cache. Have you already tried that route?
Click to expand...
Click to collapse
Yeah so I've done a factory restore. I've wiped out my cache also. But nothingso far
jpxzero said:
Yeah so I've done a factory restore. I've wiped out my cache also. But nothingso far
Click to expand...
Click to collapse
Hmm, well next I'd make a nandroid then backup using titanium backup (just in case), and make sure you've got the 4.4 factory image (obviously not just the ota). Then I'd go to custom recovery, factory reset, wipe system, data, dalvik and cache, and then flash the stock image.
That's what I'd try at least... Maybe somebody else will have a better idea. You are on stock kernel, right?
mbdw said:
Hmm, well next I'd make a nandroid then backup using titanium backup (just in case), and make sure you've got the 4.4 factory image (obviously not just the ota). Then I'd go to custom recovery, factory reset, wipe system, data, dalvik and cache, and then flash the stock image.
That's what I'd try at least... Maybe somebody else will have a better idea. You are on stock kernel, right?
Click to expand...
Click to collapse
That is what I also did. Just downloaded the KRT16S factory image from Google developers site and flashed it.
Related
Important info in the story:
Device: Nexus 7 (Rooted)
OS: Cyanogenmod 10.2.0
Overall problem: Google play not working or getting apps on working Google play system.
So let me start from the beginning. I was trying to get an app to work but the app kept saying i need root permission, so i went on SuperSU and i accidentally clicked a button that supposedly gets rid of supersu (no warning whatsoever). so to fix this problem i reboot my device that doesn't work. So i went in twrp and installed supersu. so now another problem arose. When i open Google play it says no connection, even though i can get on chrome and other things. so at this point i'm just concerned. i go home and tried uninstalling Google play and reinstall it. doesn't work. Then i try clearing cache, doesn't work, then data, still doesn't work. after that i try to delete my gmail account to see if that works, does not. so then i try on backing up my device with twrp, then making a whole new restore to get a fresh copy of cyanogenmod. everything works but i have no apps and data. so backup this new cyanogenmod and tried to go back on my old not working save and it wont restore, it says it failed. so i wipe all data so now i don't have an OS and then i solved that and got back rooted and installed cyanogenmod. the i try to just restore data from my old cyanogenmod and it goes through but this time on boot it optimizes apps, done with that, now is stuck in a infinite bootloader. so i restore to my old cyanogenmod and this is where i am now.
The overall question is how to i either fix google play store, or how do i port my apps and data to the working cyanogenmod Google play store?
If you can't follow with my terrible typing skills tell me and ill try to clarify. I just thought starting from the beginning of the problem would help.
--resolved--
Lionex1 said:
Question: Why are you using cyanogenmod 3.2? Or was that a typo? Currently, you should be on either 10 or 11.
Click to expand...
Click to collapse
typo
HVC FOG3Y34 said:
typo
Click to expand...
Click to collapse
Thanks.
My suggestion:
-----BACKUP EVERYTHING-----
Flash the stock factory image and the stock kernel, and go from there. You can easily reinstall a new CM, and reroot if you lost it in the process. WugFresh's N7 toolkit is great for this.
Also - I had problems with TWRP on my nexus. CWM touch works much better, I find.
EDIT: The N7 toolkit will restore everything to factory defaults, and can do backups as well.
Lionex1 said:
Thanks.
My suggestion:
-----BACKUP EVERYTHING-----
Flash the stock factory image and the stock kernel, and go from there. You can easily reinstall a new CM, and reroot if you lost it in the process. WugFresh's N7 toolkit is great for this.
Also - I had problems with TWRP on my nexus. CWM touch works much better, I find.
Click to expand...
Click to collapse
how do i flash the sock factory image and the stock kernel?
HVC FOG3Y34 said:
how do i flash the sock factory image and the stock kernel?
Click to expand...
Click to collapse
http://www.wugfresh.com/nrt/
^that's the toolkit. Pretty self-explanatory GUI.
So doing this i won't lose any apps and data and ill have to reroot? cause all i care about is not losing apps and data and getting google play to work again with a root.
^that's the toolkit. Pretty self-explanatory GUI.
Click to expand...
Click to collapse
ok so when i'm selecting my android build what "CUSTOM ROM (Wi-Fi Tablet) - ?" do i use JB or KK?
HVC FOG3Y34 said:
ok so when i'm selecting my android build what "CUSTOM ROM (Wi-Fi Tablet) - ?" do i use JB or KK?
Click to expand...
Click to collapse
Android 4.4+ is kitkat, 4.1-4.3 is JB. Select what it's running currently.
Lionex1 said:
Android 4.4+ is kitkat, 4.1-4.3 is JB. Select what it's running currently.
Click to expand...
Click to collapse
I seem to be having trouble, can you take me step by step on what to click to do this?
HVC FOG3Y34 said:
I seem to be having trouble, can you take me step by step on what to click to do this?
Click to expand...
Click to collapse
Sure, what exactly are you having trouble with?
When you first start the app, it will ask for the version and device model. After that, it will ask for your recovery that you're currently running (maybe not in that order), select TWRP in your case. It will then download things, and the program will start up.
Lionex1 said:
Sure, what exactly are you having trouble with?
When you first start the app, it will ask for the version and device model. After that, it will ask for your recovery that you're currently running (maybe not in that order), select TWRP in your case. It will then download things, and the program will start up.
Click to expand...
Click to collapse
I got that part selecting the model type, i'm now in advanced utilities do i select flash zip?
HVC FOG3Y34 said:
I got that part selecting the model type, i'm now in advanced utilities do i select flash zip?
Click to expand...
Click to collapse
You don't have to go to advanced utilities. On the first screen, "backup", then "back to stock"
After that's done and everything works, you can root and flash custom recovery if you lost it.
Lionex1 said:
You don't have to go to advanced utilities. On the first screen, "backup", then "back to stock"
After that's done and everything works, you can root and flash custom recovery if you lost it.
Click to expand...
Click to collapse
Ok now what do i do in "Which factory image?" remember i have cyanogenmod 10.2.0 or do i just get default android then reroot and get cyanogen mod again.
HVC FOG3Y34 said:
Ok now what do i do in "Which factory image?" remember i have cyanogenmod 10.2.0 or do i just get default android then reroot and get cyanogen mod again.
Click to expand...
Click to collapse
Default, then reroot and cyanogen.
Confirm it's working on stock before flashing cyanogen.
Lionex1 said:
Default, then reroot and cyanogen.
Confirm it's working on stock before flashing cyanogen.
Click to expand...
Click to collapse
ok that part fixed it, i think i lost my root, but am i still unlocked? because isn't the unlocking part that loses your data.
HVC FOG3Y34 said:
ok that part fixed it, i think i lost my root, but am i still unlocked? because isn't the unlocking part that loses your data.
Click to expand...
Click to collapse
You backed everything up, right? I'm pretty sure it doesn't relock it if you reflash factory image (what you just did)
If it did, just unlock it.
Lionex1 said:
You backed everything up, right? I'm pretty sure it doesn't relock it if you reflash factory image (what you just did)
If it did, just unlock it.
Click to expand...
Click to collapse
Ok i have now got everything working except i now need to install cyanogenmod. but when i go to install it i click the thing that says "click here to install" it goes to twrp then stops. what can i do to fix this, im in twrp now.
HVC FOG3Y34 said:
Ok i have now got everything working except i now need to install cyanogenmod. but when i go to install it i click the thing that says "click here to install" it goes to twrp then stops. what can i do to fix this, im in twrp now.
Click to expand...
Click to collapse
Grab the flashable zip from somewhere, go into twrp, and select "install" then flash the zip.
where would the .zip be if installed it from Rom toolbox pro
Guys, i received push notification through system update to B125 and after downloading i tried to update but received error as attached.
i have tried using the dload + 3 buttons method without success so far.
Can anyone please advice how i can update ?
thanks a lot
harryhh said:
Guys, i received push notification through system update to B125 and after downloading i tried to update but received error as attached.
i have tried using the dload + 3 buttons method without success so far.
Can anyone please advice how i can update ?
thanks a lot
Click to expand...
Click to collapse
Try this:
1. Choose factory reset on the recovery.
2. Then retry update.
If that doesn't work:
1. Try to redownload the B125 ROM. It might be just that the file is corrupt.
If that still doesn't work:
1. Tell me; what ROM are you on right now? And did you just revert back from TWRP?
bokchoi2020 said:
Try this:
1. Choose factory reset on the recovery.
2. Then retry update.
If that doesn't work:
1. Try to redownload the B125 ROM. It might be just that the file is corrupt.
If that still doesn't work:
1. Tell me; what ROM are you on right now? And did you just revert back from TWRP?
Click to expand...
Click to collapse
Is that significant and why? I have the same issue and I have jut reverted from TWRP.
Thanks.
iwtfmcl said:
Is that significant and why? I have the same issue and I have jut reverted from TWRP.
Thanks.
Click to expand...
Click to collapse
I still need to know what ROM you installed previously. If you were on a Huawei stock rom, this situation is kinda weird.
If you were on a custom rom, you could try the following:
Warning: You will lose your data in this process. Make sure to backup anything that is valuable to you.
Go back to twrp.
Make sure you wipe the following:
System, Data, Custom storage, Dalvik Cache, cache
Then install stock recovery.
Then install B125.
bokchoi2020 said:
I still need to know what ROM you installed previously. If you were on a Huawei stock rom, this situation is kinda weird.
If you were on a custom rom, you could try the following:
Warning: You will lose your data in this process. Make sure to backup anything that is valuable to you.
Go back to twrp.
Make sure you wipe the following:
System, Data, Custom storage, Dalvik Cache, cache
Then install stock recovery.
Then install B125.
Click to expand...
Click to collapse
I am not OP but I had same issue. What happened in my case is weird. Originally I was on B118 International, then I went to B118CN to try and flash MIUI ROM. That didn't work and I force-flashed B118CN again. That's when I got push notification to update to B120. It was specifically saying that "P6-U06V100R001C17B118 will be updated to P6-U06V100R001C17B120.
After several failed attempts, update was no longer offered, and to my surprise my build number was showing P6-U06V100R001CNCN00B118. I am 100% sure that it was P6-U06V100R001C17B118 when I flashed it.
I have no idea what happened. I wanted to stay on chinese ROM and downloaded P6-U06V100R001C17B120, flashed and all is ok so far. Build number is showing P6-U06V100R001C17B120.
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
goodboy1 said:
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First make sure you have the latest twrp, then boot into it, flash the ota zip from inside twrp, the ota zip is located in /cache...be sure to wipe cache and dalvik before restarting.
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Me too!
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
goodboy1 said:
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
brandypuff said:
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
Click to expand...
Click to collapse
Both of you modified /system, you must dirty flash your stock system.img then flash the ota. Additionally, if you are using a custom kernel, you will probably have to flash the stock boot.img as well.
And both if you, don't forget to do a nandroid first!
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
brandypuff said:
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
Click to expand...
Click to collapse
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Updated!
Bought my Nexus recently and it was android 4.3 [Dad bought it in US and forgot to check the version)
I got the OTA update to 4.4.2 a few days back but it didnt install though it finished downloading. After trying all methods, i decided to do it with Nexus Root Toolkit. But to my surprise, NRT had the 4.4.3 stock img already! I flashed it and my Tablet is smooth. No problems noted till now. If you want me to check whether a particular app is working in 4.4.3 properly or not, let me know. I will test it and tell you
mdamaged said:
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Click to expand...
Click to collapse
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
brandypuff said:
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
Click to expand...
Click to collapse
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but any changes you made to /system will be gone, you will have to reapply those changes.
You did not ask, but I use MultiROM, and I will flash a new version to a secondary, then use titanium on app data, then boot into the new secondary, make whatever changes I need to, once I am fine with how it works, I then migrate my data to it, then use the swap ROM function in MultiROM. The whole OTA thing is a PITA when you modify too much of the system.
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but anychanges you made to /system will be gone, you will have to reapply those changes.
Click to expand...
Click to collapse
Thank you very much!
I will try this.
James
I fought with the Nexus 7 {2013} 4.4.3 update for a good day and a half. Tablet rooted with xposed modules , etc. Same messages you got.
Found that this method works very easily and preserves all data. Takes a few minutes to accomplish, then just one minute to reroot. Try this, it works:
http://nexus5.wonderhowto.com/how-t...ndroid-4-4-3-without-losing-any-data-0155334/
sucess
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
brandypuff said:
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
Click to expand...
Click to collapse
Just download the newest SuperSU and flash it from recovery. Then install busybox from playstore.
I had to uninstall xposed, re enable all apps. Recovery, install update in cache, wipe cache dalvik, reboot, reboot to recover flash su, boot, install supersu, reboot to TWRP and boot then reinstall xposed.
Yep if you're unlocked and rooted it can be done without a computer but it's way slower!
Sent from my Nexus 7 using Tapatalk
Thank you everyone. I used the nexus toolkit suggested a few posts back and everything works.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
mccartad said:
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
Click to expand...
Click to collapse
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
mdamaged said:
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
Click to expand...
Click to collapse
Holy shnikies it worked! Thanks so much!
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
Click to expand...
Click to collapse
can anyone please confirm that this is a flashable .zip of a full stock Kit Kat 4.4.3. or can anyone point me to one. - thanks :cyclops:
Hi, My system UI keeps failing on my HTC One M8, I have no status bar or home button, back button etc appear on my phone!
Version main: 4.16.401.10 and CID Num is: HTC__001
I have done a factory reset, cleared the delvic cache, data cache.
I get two error message when android boots up, HTC Dot View has stopped and another error message, System UI has stopped.
Can anyone help me? Thank you
You're in luck, shouldn't be to hard to fix. If you have the stock/working system ui apk you should be able to install it as an app. I had the same problem after using softkeyz. If you need the apk dm @ [email protected]
tylerleo said:
You're in luck, shouldn't be to hard to fix. If you have the stock/working system ui apk you should be able to install it as an app. I had the same problem after using softkeyz. If you need the apk dm @ [email protected]
Click to expand...
Click to collapse
Could you send me the apk file to my email address: [email protected]
Many thanks dude
Looks like you either deleted something or corrupted something in system. You can find the ota below if you don't still have it on your phone.
Flash that and you should be good. You need the correct stock recovery installed.
https://www.androidfilehost.com/?w=files&flid=24383
Stock Recovery
ashyx said:
Looks like you either deleted something or corrupted something in system. You can find the ota below if you don't still have it on your phone.
Flash that and you should be good. You need the correct stock recovery installed.
Click to expand...
Click to collapse
Hi, Would I have to put in a stock recovery first then install the OTA (link you provided me) Thanks.
Restart the phone, then once it boots before doing anything tap the app drawer and go to settings. Go straight to the apps, and navigate to all apps. click on the HTC Blinkfeed app, and clear the data. After that go to HTC Dotview and clear the data. Restart the phone again. This should fix your problem. I had this problem a few times after doing a restore of my nandroid.
suprtrukr425 said:
Restart the phone, then once it boots before doing anything tap the app drawer and go to settings. Go straight to the apps, and navigate to all apps. click on the HTC Blinkfeed app, and clear the data. After that go to HTC Dotview and clear the data. Restart the phone again. This should fix your problem. I had this problem a few times after doing a restore of my nandroid.
Click to expand...
Click to collapse
Hi, I have tried this however the clear data in dot view, blinkfeed are all greyed out. Can you suggest anything else please, this is so frustrating. Thank you
noorul89 said:
Hi, I have tried this however the clear data in dot view, blinkfeed are all greyed out. Can you suggest anything else please, this is so frustrating. Thank you
Click to expand...
Click to collapse
It will only be grayed out for a few seconds while it is calculating. Be patient and try again.
noorul89 said:
Hi, Would I have to put in a stock recovery first then install the OTA (link you provided me) Thanks.
Click to expand...
Click to collapse
As said you need the correct stock recovery. You can pull it from the firmware zip in the download or download it from the stock backups thread.
https://www.androidfilehost.com/?w=files&flid=24260
ashyx said:
As said you need the correct stock recovery. You can pull it from the firmware zip in the download or download it from the stock backups thread.
https://www.androidfilehost.com/?w=files&flid=24260
Click to expand...
Click to collapse
Hi, I have the stock recovery installed on my M8. I have the OTA downloaded, how do I install the OTA on a stock recovery?
Resolved!!
This issue was resolved by installing the stock recovery, going into data wipe and factory reset. Then restaring the phone. Phone boots up and is working as normal!! Woohoo i been spending most of the weekend trying to fix it and it turned out to be so simple. Thanks to everyone that helped me.
noorul89 said:
This issue was resolved by installing the stock recovery, going into data wipe and factory reset. Then restaring the phone. Phone boots up and is working as normal!! Woohoo i been spending most of the weekend trying to fix it and it turned out to be so simple. Thanks to everyone that helped me.
Click to expand...
Click to collapse
hey i am having the same problem. what recovery did you use? i only have the older 3......
alvahroee said:
hey i am having the same problem. what recovery did you use? i only have the older 3......
Click to expand...
Click to collapse
You will need to find your stock recovery.. Flash it from your custom recovery i.e twrp.
Boot into your stock recovery and go into wipe data/factory reset option.
That resolved the issue for me.
noorul89 said:
This issue was resolved by installing the stock recovery, going into data wipe and factory reset. Then restaring the phone. Phone boots up and is working as normal!! Woohoo i been spending most of the weekend trying to fix it and it turned out to be so simple. Thanks to everyone that helped me.
Click to expand...
Click to collapse
OMG Thank you so much. I was wiping all kinds of cache , restoring all kinds of backups and nothing was helping the matter. Thanks for making it clear that I have to flash back the stock recovery and data wipe and factory reset from there
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.