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
Related
https://community.gethuawei.com/#
"This week Huawei is rolling out a new build B320 to Mate2 testers. The update was already to provided to small group of our "UUF" testers, and we were told that it would be delivered by OTA to devices that had previously installed the first public build B309. Yesterday I told testers that the OTA update would arrive by today, but that does not appear to have happened yet. If you are still on B309 and you would like to download B320, please send me a private message with your gmail and I will share it with you."
Sent from my MT2L03 using XDA Free mobile app
Just received the B20 OTA update on my HAM. I am not a beta tester. Haven't even tested it out yet. Still upgrading as we speak.
Error installing B320 with TWRP-L
gettting:
assert failed: apply_patch_check("/system/bin/appp_process32"...)
and
E:unknown command [update_log]
E:Error executing updater binary in zip '/data/media/0/HwOUC/update_sign.zip'
E: Error installing zip file '/data/media/0/HwOUC/update_sign.zip'
Any way around this?
When I tried to download and install it, it verified the download and when it rebooted it rebooted into TWRP but when I told it to reboot the system from the menu It was still B309 and not B320.trying to download it again now. If this doesn't work I may just have to get the update files and install it that way.
robertbarber said:
When I tried to download and install it, it verified the download and when it rebooted it rebooted into TWRP but when I told it to reboot the system from the menu It was still B309 and not B320.trying to download it again now. If this doesn't work I may just have to get the update files and install it that way.
Click to expand...
Click to collapse
Flash stock recovery...
Fixed
I reinstalled B309 from SD and was able to download and install B320.
B320 Install failed
Moody66 said:
Flash stock recovery...
Click to expand...
Click to collapse
tried that and it got to about 27% and said install failed so I will probably just flash the files when I can get them.
robertbarber said:
tried that and it got to about 27% and said install failed so I will probably just flash the files when I can get them.
Click to expand...
Click to collapse
Rerun B309 then update. Harris said that worked for him.
B320 update success
Moody66 said:
Rerun B309 then update. Harris said that worked for him.
Click to expand...
Click to collapse
Was able to get it installed, had to use the cleanup option in SuperSU to remove root then it worked. In the process of resetting up my root apps now. Does anybody know if this update fixes the Stagefright exploit that was recently discovered it wasn't in the update log .
I have two questions:
1. I checked for OTA updates, but I got "No Updates". Can we download the update manually.
2. I have TWRP installed. Does anyone have stock recovery for Lollipop because I didn't backup mine.
medwatt said:
I have two questions:
1. I checked for OTA updates, but I got "No Updates". Can we download the update manually.
2. I have TWRP installed. Does anyone have stock recovery for Lollipop because I didn't backup mine.
Click to expand...
Click to collapse
I have TWRP installed and the OTA update installed fine. I didn't need to flash stock recovery
TheIgster said:
I have TWRP installed and the OTA update installed fine. I didn't need to flash stock recovery
Click to expand...
Click to collapse
Surprisingly, I checked for OTA update just now and bam! I'm downloading it. I basically haven't uninstalled any system app. However, I have root access. Did you have to uninstall root ?
I had to for it to finish install. Also had to flash stock recovery. Used the cleanup option in SuperSU and then did the install.
What does 320 fix? Still not sure if I want to update from JB yet because I want my Xposed modules!
medwatt said:
Surprisingly, I checked for OTA update just now and bam! I'm downloading it. I basically haven't uninstalled any system app. However, I have root access. Did you have to uninstall root ?
Click to expand...
Click to collapse
Never had root. Just TWRP recovery so I could get my Wind version HAM to a OEM version.
TheIgster said:
Never had root. Just TWRP recovery so I could get my Wind version HAM to a OEM version.
Click to expand...
Click to collapse
Yes, but by updating to Lollipop you effectively had the stock recovery; not TWRP. Did you install TWRP after you upgraded to Lollipop ?
medwatt said:
Yes, but by updating to Lollipop you effectively had the stock recovery; not TWRP. Did you install TWRP after you upgraded to Lollipop ?
Click to expand...
Click to collapse
Oh, damn, forgot about that. Good point. No, I did not, so I would have stock recovery. Never thought about the update after the fact to LP. My bad.
So, the question now is, how can I get Lollipop stock recovery back ? I didn't back it up when I installed TWRP because I presumed I'll just download it when I need it and flash it over TWRP as I did with JB. Anyone ?
Could you downgrade to JB and then upgrade to LP again? Wouldn't that ensure you get stock recovery back?
I'm not going to even try that. Can you imagine how long that'll take ?
After taking root I'll still be able to update my phone using OTA? If so, the update will remove the root?
As updates OTA behave in relation to Xposed? Is everything going to work?
Sorry for the English, I used Google translator.
kubixmaster3009 said:
After taking root I'll still be able to update my phone using OTA? If so, the update will remove the root?
As updates OTA behave in relation to Xposed? Is everything going to work?
Sorry for the English, I used Google translator.
Click to expand...
Click to collapse
Unfortunately you can't update via OTA if your device is rooted.
To install OTA,
recover the ROM backup ( that you ''hopefully" made before rooting using TWRP ) from TWRP and then, install the OTA.
Edit: Or , (if you are patient enough to download the full ROM) you can dirty flash the full ROM and then install OTA.
When you do this, custom recovery (eg., twrp) will be replaced by stock oneplus recovery . Hence, you should again flash the custom recovery img through adb.
What if we extract the update file and only take the files that will not effect the recovery (the really updated files), make them into a flashable zip and overwrite the current system files?
Just dirty flash the full ROM, then the OTA zip(s) and after that root it again, flash Xposed or whatever you want.
There's no need to restore any backup or reflash recoveries etc.
Firefly1337 said:
Just dirty flash the full ROM, then the OTA zip(s) and after that root it again, flash Xposed or whatever you want.
There's no need to restore any backup or reflash recoveries etc.
Click to expand...
Click to collapse
You are right about dirty flashing the full ROM zip.
But, the recovery will be replaced by stock oneplus recovery when you install OTA update as of my experience.
sankarshan said:
You are right about dirty flashing the full ROM zip.
But, the recovery will be replaced by stock oneplus recovery when you install OTA update as of my experience.
Click to expand...
Click to collapse
Why should it be?
I can confirm from personal experience that this won't happen.
//Edit: Do you actually mean 'install' OTAs with the official updater in android itself? If so, then I don't know.
But by flashing the OTA zip (in recovery) it won't replace your recovery.
Firefly1337 said:
//Edit: Do you actually mean 'install' OTAs with the official updater in android itself? If so, then I don't know.
But by flashing the OTA zip (in recovery) it won't replace your recovery.
Click to expand...
Click to collapse
1.Yeah, I meant updating via "official updater".
2. That's one of the reasons why they(manually flashable OTA zips) are made. aren't they?
@sankarshan Yes you're right. I thought you meant flashing them as zip because I specifically spoke of flashing the OTA zips
winesh said:
What if we extract the update file and only take the files that will not effect the recovery (the really updated files), make them into a flashable zip and overwrite the current system files?
Click to expand...
Click to collapse
That's a great idea @winesh I also wonder if it is possible.
winesh said:
That's a great idea @winesh I also wonder if it is possible.
Click to expand...
Click to collapse
Are you talking to yourself? LOL
I just received the OTA update from 7.1.1 DP2 to MNF26F.
Here is the OTA url to download:
https://android.googleapis.com/pack.../2c6f100d0f9ef8ccee10d661b7454adb7161aa0e.zip
You can sideload it into your device and you will be on the official 7.1.1 release.
Just got it too. Only 27 megabytes.
Just download it... Where the downloaded OTA file located in our file system?
deani77 said:
Just download it... Where the downloaded OTA file located in our file system?
Click to expand...
Click to collapse
/data/data/com.google.android.gms/app_download/
If rooted on dp2 I can just download and install through TWRP, no?
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
thedead69 said:
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
Click to expand...
Click to collapse
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
RaceFaceXC said:
If rooted on dp2 I can just download and install through TWRP, no?
Click to expand...
Click to collapse
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
RaceFaceXC said:
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
Click to expand...
Click to collapse
Rooted with SuperSU on DP2. Using flashfire
I got this OTA this afternoon. Stock DP2 on Verizon.
rchtk said:
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
Click to expand...
Click to collapse
Thank.
I think I knew this at some point. Wasn't sure so that's why I asked.
thedead69 said:
Rooted with SuperSU on DP2. Using flashfire
Click to expand...
Click to collapse
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
onesolo said:
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
Click to expand...
Click to collapse
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Link ota for NEXUS 5X PLEASE
Link ota for NEXUS 5X PLEASE
hanibioud said:
Link ota for NEXUS 5X PLEASE
Click to expand...
Click to collapse
Wrong forum. This is for the Nexus 6P.
RaceFaceXC said:
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Click to expand...
Click to collapse
I didn't even try, cause I can enter on twrp fine. As I said, I have twrp and root. My sys is obviously modified. I'm not even trying to sideloaded over bootloader cause it wont work. The same thing on TWRP. I think that sideloading on TWRP only works with full OTAs and not with this one, that is an incremental OTA file, unless I'm completely wrong (I wish).
Anyone's got a changelog for those 26 MB of 'system stability and performance' ?
onesolo said:
Can you or someone help me?? Someone??
Click to expand...
Click to collapse
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
v12xke said:
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
Click to expand...
Click to collapse
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
onesolo said:
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
Click to expand...
Click to collapse
I didn't think flashing a ota over a rooted os, let alone a highly modified os/kernel/etc was a good idea with any utility.
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!
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
I read that Huawei rolled out an update which broke Magisk, does anyone know if the latest update is safe?
How can I tell if an update is safe to use?
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
mtvento said:
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
Click to expand...
Click to collapse
as opposed to version 8.0.0.379?
I currently have magisk and TWRP with no problem, is this problem you describe is new to the latest version?
Do you have a different custom ROM?
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
mtvento said:
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
Click to expand...
Click to collapse
So on EMUI9 there's no option of Root+Custom recovery?
So the options are either root or custom recovery?
Did I understand correctly?
Thank you
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
mtvento said:
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
Click to expand...
Click to collapse
That sucks big time.
What do you mean by "have to boot to recovery each time"? every time I restart the phone or turn it off and back on I must go through recovery?
I think I'll avoid EMUI9 and stick with EMUI8.
For some reason there are not much custom ROMs or honor 9
That is the last time I buy a non root friendly phone like Huawei/Xiaomi
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
buchman said:
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
Click to expand...
Click to collapse
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Clonimus said:
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Click to expand...
Click to collapse
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
buchman said:
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
Click to expand...
Click to collapse
When I do that it gives me 2 options, one is download a zip file (and then I need to install using TWRP, right?)
The other option is patch a boot image, and it lets me look for one. Is this option to patch a downloaded boot image and then I need to flash it? what do I do with this option?