Has Anyone Got it yet? some nexus 4 and nexus 7 users are getting it right now in the usa it seems
http://www.androidpolice.com/2013/02/11/breaking-android-4-2-2-update-rolling-out-to-gsm-galaxy-nexus-nexus-7-nexus-10/
come on developers drop it to ROMs !!
anyone receive it
please help to find the ota link
step
http://forum.xda-developers.com/showpost.php?p=21025378&postcount=27
Popped up on my daughter's stock, unrooted N7 about 5 minutes ago. I assume because I'm running a custom ROM with a custom recovery OTAs will be blocked on my N10 (that's how it was on my OG Droid and LTE GNexus).
I might have been excited about this a few months ago but now it's just meh.. I'll just wait for Rascarlo to update RasBean... My tablet is rock solid stable right now.. I'm in no rush to beta test another one of Googles messes.
Nexus 10 4.2.2 OTA URL
Hi all,
You can download 4.2.2 OTA from below link. Have a fun!! :fingers-crossed:
MD5:ed637878ccba20ba9d44e62685ac67e9
http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
saltxyz said:
Hi all,
You can download 4.2.2 OTA from below link. Have a fun!! :fingers-crossed:
MD5:ed637878ccba20ba9d44e62685ac67e9
http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
Click to expand...
Click to collapse
awesome thanks ! now how to update ?
nightfox11 said:
awesome thanks ! now how to update ?
Click to expand...
Click to collapse
adb sideload UPDATE-NAME.zip from Recovery with Android SDK
Not showing up for me in Canada yet.
Sent from my GT-I9300 using xda premium
espionage724 said:
adb sideload UPDATE-NAME.zip from Recovery with Android SDK
Click to expand...
Click to collapse
And with stock rom and stock recovery? Update from zip?
lKBZl said:
And with stock rom and stock recovery? Update from zip?
Click to expand...
Click to collapse
you should have adb in stock recovery aswell. just boot to stock recovery, make sure that you've configured the drivers and use the above command to install the update via adb
I've never tried that procedure though, but I guess it should work
I'm rooted but with stock recovery. Can I just use OTA root-keeper to temp-unroot, install update and then re-root?
antonusklesk said:
I'm rooted but with stock recovery. Can I just use OTA root-keeper to temp-unroot, install update and then re-root?
Click to expand...
Click to collapse
Yes, but don't temp unroot, backup the root and then use backup to root again.
Cheers, looking forward to getting home and having a play.....even if it is only minor fixes.
And thus starts a barrage of soft brick help threads because toolkits make simple tasks stupidly more complicated then they need to be.
onemandivision said:
you should have adb in stock recovery aswell. just boot to stock recovery, make sure that you've configured the drivers and use the above command to install the update via adb
I've never tried that procedure though, but I guess it should work
Click to expand...
Click to collapse
Can this get me into a soft brick and the comment over this one says?
lKBZl said:
Can this get me into a soft brick and the comment over this one says?
Click to expand...
Click to collapse
Yup.
So, is there a changelog?
lKBZl said:
Can this get me into a soft brick and the comment over this one says?
Click to expand...
Click to collapse
heres what i did:
1) download the latest stock factory image from google: https://developers.google.com/android/nexus/images#mantaray (JOP40C)
2) download the ota update JP40C->JOP40D http://android.clients.google.com/p...gned-mantaray-JOP40D-from-JOP40C.07ac4f5d.zip
3) download the ota update JOP40D->JDQ39 http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
4) download the latest team win recovery .img file: http://techerrata.com/browse/twrp2/manta
5) reboot into bootloader mode
6) unzip the stock firmware from step 1)
7) open command line window, cd to folder where image-mantaray-jop40c.zip is, type fastboot update image-mantaray-jop40c.zip (add option -w if you want to clear userdata aswell, this will wipe your sdcard)
8) wait for reboot and get back into bootloader
9) open command line window, cd to folder where the team win recovery image file is, type fastboot flash recovery openrecovery-twrp-2.4.1.0-manta.img (filename can be different depending on the version you downloaded)
10) reboot into bootloader, select reboot recovery, open command line window, cd to where ota updates are, type adb push *filename* /sdcard for each ota update (replace *filename* by actual filename)
11) select install in team win recovery, install update from step 2) first, then update from step 3)
reboot.
you might lose all your data including your files stored on your tablet. this is probably the must reliable way to update because everything is set back to stock and then updated. so no customization whatsoever should interfere
heres the result:
Ignore the post by onemandivision previous steps are easier
Related
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
once i enter recovery and use the adb sideload command i get the following error:
device not found
vivalamoza said:
once i enter recovery and use the adb sideload command i get the following error:
device not found
Click to expand...
Click to collapse
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
dbolivar said:
Can we follow this procedure if using the ported GPE ROM in a C6833? Is there anything GPE-specific in the update ZIP that could brick a non-GPE device?
Thanks!
Click to expand...
Click to collapse
PLEASE DO NOT TOUCH THE INCREMENTAL OTA ZIP ON NON-GPE DEVICE!
bootloader/modem and lots of other things are getting patched!
wait for the fill flash zip and then port that...
What happens if I click restart and install that notification won't go away
Sent from my C6806_GPe using XDA Premium 4 mobile app
Okay restoring from the full 4.4.2 OTA then sideloading of the 4.4.3 OTA worked.
Definitely not as using fastboot....
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
If not, how do I re-root?
Thanks,
Flipper
DooMLoRD said:
So guys thanks to the lovely people here on XDA we have the incremental OTA captured!
its NOT the full ROM but is rather a patch to allow you to update to latest 4.4.3
Since this is incremental patch you will need to be on stock/minimally modified Stock KOT49H 4.4.2 ROM, most importantly you will have to be on original kernel (boot.img)...
best would be to use this procedure:
[IMP][ZU_GPe][How-To] Restore to original Google Play Edition firmware!
to get back to stock 4.4.2 (but you may lose your app data)
If you want an in-place upgrade and if you are using any of my kernel (recovery kernels or DooMKernel) then you will have to revert to pure stock kernel..
unfortunately you wont be able to flash the original KOT49H kernel via fastboot (considering that you might have unlocked bootloader)...
i am attaching below the original KOT49H as a recovery flashable zip:
ZU_GPe-DooMLoRD-Stock_KOT49H_kernel
flash it using CWM recovery and the kernel on your GPE device will be replaced with original kernel
now reboot into bootloader
Code:
adb reboot bootloader
select recovery and enter it...
select ADB method and flash the incremental OTA using the command:
Code:
adb sideload <NAME-OF-OTA-FILE>
it will take a while but once its done reboot device and enjoy latest KitKat 4.4.3
regards,
DooMLoRD
Click to expand...
Click to collapse
flipperg said:
So... Once I flash the 4.4.3 Update (Thanks btw); do I reflash your Kernel?
Thanks,
Flipper
Click to expand...
Click to collapse
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Awesome!
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
DooMLoRD said:
The kernel provided in the first post is for 4.4.2
If you flashed the 4.4.3 update properly then you you are good to go!
Though if you want custom recoveries just check the advanced stock kernel posted in my other thread...
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 02:26 AM ---------- Previous post was at 02:18 AM ----------
In case this helps others - I always change my DPI via ROM Toolbox build.prop editor and also install Xposed Framework...
Undo both (400 DPI, and Uninstall Framework) before you run the update or it will fail.
Flipper
flipperg said:
:laugh:
That's what I needed - thank you, I did exactly that and then re-rooted from CWM via your Advanced Stock Kernel. I'm back.
Thank you,
Flipper
Click to expand...
Click to collapse
DooMLoRD said:
you have to enable recovery menu (press POWER + VOLUME DOWN for a second or so when u see the "dead android robot screen")...
then select flash via adb (1st option in the recovery)
Click to expand...
Click to collapse
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
A driver is probably not installed correctly. Re-install it and try again. If that doesn't work:
- Boot your phone
- Go to developer settings and enable USB debugging, and authorize ADB (it'll pop up and ask you on your phone)
- Open cmd on your computer and type "adb devices". Your device is a string of characters and numbers, like: "4JKF45234F" etc.
- If your device is found, try sideloading it now, by typing "adb sideload [file path]" and wait for it to flash it.
vivalamoza said:
Thanks
Did that and now I have a message on my phone saying:
Now send the package you want to apply to the device with "adb sideload <filename>...
The thing is when I send the file via adb I get the error: device not found
I check my device manager and I found a yellow exclamation mark next to the phone, does the phone need a different driver to use the sideload command?
Click to expand...
Click to collapse
I had this issue and drivers needed to be installed. Right click on device with exclamation, tab over to drivers, then select update drivers and "choose browse my computer", find the Sony fastboot and adb drivers from flashtool folder and install them. If you are on win8 or 8.1 you will need to disable signature verification. I assume somehow flashtool is able to use the drivers without them actually being installed?
@vivalamoza another option is to copy update to SD card and flash it from there using stock recovery.
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
Exactly that's a question I had, can't I just choose apply update from SD instead and browse the file location on my phone.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did it that way by copying update to SD , flashing the CWM flashable stock recovery, then following the return to stock guide. Except at the end I chose apply update from SD instead of adb sideload. If you have used xposed to edit framework I would use the uninstall option inside xposed installer app. Also if any system apps have been deleted it will error out and not install.
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
adfurgerson said:
@DooMLoRD do you have any idea what broke our cameras after update? Is it possible to return to 4.4.2 using your restore method with the full ota?
Click to expand...
Click to collapse
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
DooMLoRD said:
Full OTA of 4.4.2 won't work... Give me a few days I am out of town, will work on a fix soon!
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks!
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
vivalamoza said:
I flashed 4.4.3 using stock recovery and I'm unrooted. I'm having no camera problems, everything seems to be working fine. I'm using Google camera.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odd. My camera is completely broken.
Sent from my BN NookHD+ using Tapatalk
Hi
Yesterday I received the OTA update (LMY48I stagefright-fix) on my unlocked and rooted Nexus 9. When I tried to install it update the tablet rebooted and I ended up with a dead android on screen and the message: "Error". I was able to reboot but the update was not installed. I assume it is because it is rooted that I can't use OTA update.
How do I properly update to LMY48I without risking bricking my device? I have been searching around a bit but I can't seem to find a safe way to do it.
Has anyone experienced similar problems?
Any help is appreciated.
Thanks
Kenneth Andreasen said:
Hi
How do I properly update to LMY48I without risking bricking my device? I have been searching around a bit but I can't seem to find a safe way to do it.
Click to expand...
Click to collapse
OTA failed to install because you were rooted, as you suspected.
I assume that by "unlocked", you mean your bootloader is unlocked?
If so, follow the "Long Method" in the following tutorial (short method, flash_all doesn't work) > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Download your factory image from here > https://developers.google.com/android/nexus/images
cam30era said:
OTA failed to install because you were rooted, as you suspected.
I assume that by "unlocked", you mean your bootloader is unlocked?
If so, follow the "Long Method" in the following tutorial (short method, flash_all doesn't work) > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Download your factory image from here > https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
cobyman7035 said:
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
Click to expand...
Click to collapse
Yes. Only flash the following files:
bootloader.img
system.img
vendor.img
boot.img.
Note the following:
1) Make sure your Android SDK is reasonable up to date. Google updated fastboot in November 2014, to allow flashing these very large system.img files for Lollipop.
2) IF you are unencrypted, you will need to flash an unencrypted kernel.
3) IF you want to keep root and TWRP, do the following:
- after you fastboot flash the last .img file, stop using your PC/terminal.
- pick up your N9 and using the volume buttons, navigate to hboot and select it with power button.
- once in hboot, use buttons to navigate to and select Recovery
- TWRP will boot. Flash your SuperSU .zip and then reboot from recovery
cobyman7035 said:
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
Click to expand...
Click to collapse
Have the same situation as you wherein I am unlocked and am rooted. Follow this guide for the respective LMY48I build and you should be fine with no data loss. Just remember to reroot with CF-Auto root afterwards as you will loose root.
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26
Just wanted to say that I used the Nexus Toolkit (http://www.wugfresh.com/nrt/) to easily flash the stock lmy48i upgrade, then re-root & re-flash my custom recovery. All while preserving my data and apps.
The process was super simple, and the toolkit program even downloads and verifies the stock images for you.
A reddit user captured his link to the DP
Here is the link
https://android.googleapis.com/pack.../f9cb176ee75399a48e927d9f1bd6aeb6a643272c.zip
Credit: https://m.reddit.com/r/Nexus6P/comments/5edfam/captured_my_ota_url/?compact=true
Flash guide: *should* work
1. Boot twrp on DP1
2. flash SU of choice
3. reboot
4. install FlashFire from play store
5. Select "Flash firmware package"
6. Select the zip
7. Flash it!
**** A FEW DISCLAIMERS
**** TWRP seems to be based on 6.0.1 and the OTA can only be flashed on 7.1.1
**** In this case twrp will NOT flash this OTA file
**** FlashFire IS REQUIRED
**** I am not google. Yes I am sorry that force encrypt wiped your data or you got stuck in
**** a boot loop because you flashed it incorrectly BUT I am NOT google, I am NOT even
**** the person who captured the link for the ota ALL I DID WAS SHARE IT
**** If your data partition got wiped, you got stuck in a boot loop, or the guide didn't work
**** chances are you did something wrong
**** if you would like support but Google up in the DMs
**** I am happy to help just know I won't troubleshoot what you screwed up
Would we get a full OTA as well?
gqukyo said:
Would we get a full OTA as well?
Click to expand...
Click to collapse
If by full OTA you mean full ROM zip, here it is.
WelcomeToTheSkye said:
A reddit user captured his link to the DP
Here is the link
https://android.googleapis.com/pack.../f9cb176ee75399a48e927d9f1bd6aeb6a643272c.zip
Credit: https://m.reddit.com/r/Nexus6P/comments/5edfam/captured_my_ota_url/?compact=true
Click to expand...
Click to collapse
Sorry for being a noob but do I flash the zip file through TWRP or is there some other way? I am rooted with custom recovery on DP1.
Thanks
marmeak7 said:
Sorry for being a noob but do I flash the zip file through TWRP or is there some other way? I am rooted with custom recovery on DP1.
Thanks
Click to expand...
Click to collapse
If you're rooted, use flash fire from play. It restores twrp and root after updating. Haven't used any other method. No problems. Best app ever.
Just updated. Sound louder, November security patch and overall smoother scrolling.
No regrets getting the 6P. Amazing phone.?
It work fined at my Nexus 6p. All the rooted apps working fine. Thank you very much for your sharing. Appreciated it.
Just curius, has anyone of you guys unencrypted?
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Can't flash it in TWRP --> error
edit: I got E3001: the build fingerprint doesn't match. How can I fix this?
I succesfully flashed using Flashfire.
First thing I noticed is the many (repeating) superuser notifications I get for apps getting root during boot.
DRD70 said:
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Click to expand...
Click to collapse
the same for me... I only have twrp and have modified system... maybe is because of that... but I tought that would not be a problem... guess I'm going the twrp way
hmm, now I get it... this is not a full ota file.
Will I be able to flash it via TWRP like I did with the full OTA file from DP1 ??
^You need the full ota not this type of ota...
So this is the update from DP1 to DP2, correct? Is there any other way to install it besides with Flashfire? I've always installed from my PC, so is there any way to sideload it or install the zip through TWRP?
DRD70 said:
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Click to expand...
Click to collapse
You must be on dp1 and select flash firmware package not flash zip
ahmd gomaa said:
You must be on dp1 and select flash firmware package not flash zip
Click to expand...
Click to collapse
I was on dp1 and my first selection was firmware package and nothing happened. So i tried the other with the same outcome.
I finally revert it to stock and got ota update the dp2 since I'm a beta tester and root it again.
Rooted with TWRP on NPF10C
So I'm rooted and have TWRP installed, how can I update to DP2 ?
aakash dabrase said:
So I'm rooted and have TWRP installed, how can I update to DP2 ?
Click to expand...
Click to collapse
Install FlashFire from the play store and select firmware
swa100 said:
Can't flash it in TWRP --> error
edit: I got E3001: the build fingerprint doesn't match. How can I fix this?
Click to expand...
Click to collapse
Noted it in the op
Twrp is based on 6.0.1 afaik just use FlashFire
WelcomeToTheSkye said:
Install FlashFire from the play store and select firmware
Click to expand...
Click to collapse
Here's what I did:
1. Downloaded the OTA (137 MB) on pc.
2. Copied it to phone.
3. Selected Flash OTA in flashfire and selected the zip.
4. Flashfire failed to do it.
Should I use flash firmware option instead of flash OTA?
Also there are further options to select like recovery etc. What about them?
aakash dabrase said:
Here's what I did:
1. Downloaded the OTA (137 MB) on pc.
2. Copied it to phone.
3. Selected Flash OTA in flashfire and selected the zip.
4. Flashfire failed to do it.
Should I use flash firmware option instead of flash OTA?
Also there are further options to select like recovery etc. What about them?
Click to expand...
Click to collapse
Yep select firmware (it says that in op) select what you would like to keep
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
matt1515 said:
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
Click to expand...
Click to collapse
Please could you post the build.prop. I'm interested in the ro.build.date of the beta.
matt1515 said:
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
Click to expand...
Click to collapse
Is this a full or incremental OTA?!
I know that it's a big file, but still...
Sent from my Nexus 6P using Tapatalk
https://developer.android.com/preview/download-712.html
Still nothing...
Sent from my Nexus 6P using Tapatalk
xdatastic said:
Please could you post the build.prop. I'm interested in the ro.build.date of the beta.
Click to expand...
Click to collapse
Here you go
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Is this ota or full image?
I usually flash full images with flashfire
matt1515 said:
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Click to expand...
Click to collapse
I got the same error. I was hoping this build would get me out of the bootloop that N4F260 has me stuck in.
thegios said:
Is this ota or full image?
I usually flash full images with flashfire
Click to expand...
Click to collapse
OTA. There is a working TWRP flashable zip here.
Thanks but gonna wait for full image to be uploaded by Google on beta site
SubuHyd said:
I got the same error. I was hoping this build would get me out of the bootloop that N4F260 has me stuck in.
Click to expand...
Click to collapse
Try formatting cache and then factory reset in recovery and see if it boots (assume you have locked bootloader). If no boot try and sideload this again. Might work if not try full OTA zip when released good luck hope you get it figured out
matt1515 said:
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Click to expand...
Click to collapse
Those of you getting errors, did you happen to check the SHA-1 hash of the downloaded OTA file? It should match the file name (E7ADC4A02314908BFDC7A3EEA85214E67B4E8E39). I downloaded it just to check, not going to install myself due to no new features. Weird that Google is going with the SHA1 hash on this as recently Google has been using SHA256.
Also, are you using most recent version of Platform Tools, 25.0.3? https://developer.android.com/studio/releases/platform-tools.html
Flash this .zip ， need modify updater.script。fastboot lock couldn't flash it
When you sideload ,the script run
package_extract_file("recovery-two-step.img", "/dev/block/platform/soc.0/f9824900.sdhci/by-name/boot");
set_stage("/dev/block/platform/soc.0/f9824900.sdhci/by-name/misc", "2/3");
reboot_now("/dev/block/platform/soc.0/f9824900.sdhci/by-name/misc", "");
Click to expand...
Click to collapse
But after reboot . it isn't continue. I think because recovery couldn't find zip file.. but it is flashing recovery to boot .