Database Users

COS 13.1 ZNH2KAS1KN - New Update for OPO

Cyanogen recently pused out COS13.1 for our beloved OPO.
Here is the link to OTA :-
http://builds.cyngn.com/incremental/bacon/cm-bacon-64003595ee-to-ced5430fc0-signed.zip 378 MB
"Upgrade your device to Cyanogen OS 13.1. Based on Android™ 6.0.1, Marshmallow, this update provides critical security fixes, improved stability/performance, product upgrades, and new mods for Cortana, OneNote, Microsoft Hyperlapse, Skype, and Twitter."
Changelog :-
Complete changelog currently unknown.
1st June Android Security patch level
Some MOD Addons.
Skype integration in dialer.Removal of NextDialer. Looks like stock dialer.
Hyperlapse mod in camera.
Update Instruction :-
Stock Unrooted Devices
To flash OTA you need stock unrooted phone.
Flash via stock recovery.
Rooted devices
1st unroot the device or flash system image from previous update then flash the OTA from recovery.

Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.

gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
try flashing from stock recovery !

gauravsaini964 said:
try flashing from stock recovery !
Click to expand...
Click to collapse
Same for me lol

gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
flash the stock system with the correct recovery over, then flash update

stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0

dam76 said:
stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0
Click to expand...
Click to collapse
Try to install the previous update, and then with recovery stock reinstall the last update.

alijoregon said:
Try to install the previous update, and then with recovery stock reinstall the last update.
Click to expand...
Click to collapse
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg

dam76 said:
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg
Click to expand...
Click to collapse
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.

alijoregon said:
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.
Click to expand...
Click to collapse
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure?
does the full zip update wipe apps and data?
thanks in advance for the help

dam76 said:
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure
thanks in advance for the help
Click to expand...
Click to collapse
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.

alijoregon said:
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)

Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.

Seems to be fine. Minimal fixes but at least something...
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
leokook said:
Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)
USER ABOVE YOU POSTED HOW HE DID IT. FOLLOW HIS GUIDE AND THANK HIM

anyone have problem with titanium backup on latest ota s1kn ? i cannot freeze and restore app , any idea ? su version 2.65

Are there also any changes with the camera?

prototyp01 said:
Are there also any changes with the camera?
Click to expand...
Click to collapse
Hyperlapse got added !

Is overall camera quality better than before? Or is Hyperlaps the only change?

prototyp01 said:
Is overall camera quality better than before? Or is Hyperlaps the only change?
Click to expand...
Click to collapse
I am sure some one else will be able to answer this better
I haven't flashed this update yet neither I am camera enthusiast.

Updated on this one yesterday, and I regret it....my phone now charges very slow, it took 8 hours to fully charge, dont have this issue before, tried everybody else fixes, but did nothing...do anybody has the flashable ZIP on the previous version and can be flashed using stock recovery?
Thanks

[marmite] Android 7.1.1 TOS118C fastboot/recovery images

For those that didn't receive the update yet, I've requested the links to the Wileyfox nougat support team, so here you can download the incremental, recovery and fastboot images of the latest upgrade TOS118C.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
INCREMENTAL UPDATE (OFFICIAL) (DRIVE MIRROR LINK by me) (from TOS089A to TOS118C / from decf3a575d to aa4d5d86bc)
In the post below you can have some information on how to grab OTA links from the WileyFox BSP server. Have fun, and don't forget to debloat your system

How to grab the official OTA from BSP's server
In the OP, I left a link to the official incremental update right from the OTA server (which I'll talk about a bit later). If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
... Or you can just wait til someone mirrors it, like I already did
Lastly, as a side note, I'd also like to comment the following, regarding BSP:
Wileyfox's devices software is now in charge of this company, called BSP.ninja and that clearly defines themselves as a company to "launch an Android device without knowing where to start". It's said to be formed by former Cyanogen employees, or, at least Ricardo Cerqueira @aremcee (which btw, is also in charge of the Open Source code available in BitBucket for the Wileyfox devices), since he's the owner of the domain. In any case, what I want to say is that the code is being done quite possibly by the very same people that did the job at the now dead Cyanogen, so it shouldn't be a reason to worry. Also, it'd be awesome if the team released a working device tree so that the community could bring custom ROMs just like you (the team) used to do.

linuxct said:
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
Click to expand...
Click to collapse
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?

boa05 said:
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?
Click to expand...
Click to collapse
Correct. I'm preparing a new version of my debloater tool, and I'll briefly explain in it's thread how to move from TOS089A to TOS118C without losing anything in rooted and/or debloated devices. Stay tuned!

Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.

zerospaced said:
Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.
Click to expand...
Click to collapse
I also skin my phone through substratum (the default orange theme is disgusting), I use magisk and plenty of other tools both systemless or even require modifying the system partition (like Wileyfox debloater), and, using the instructions I wrote in this post here I've found no single problem upgrading my device from a debloated, rooted and themed TOS089A to TOS118C to then debloat, root and theme it again. It's true you will need to install your substratum themes again, but the rest should work perfect.

I've tried the recovery update on my Swift 2X but can't get it to boot. I have TWRP installed (3.1.0-0) and it's rooted via SuperSU. Do I have to unroot first?
Edit for more info: I did the OTA upgrade from the stock CyanogenOS ROM to 7.1.1 TOS089A. Then I installed TWRP and flashed SuperSU. The OTA to TOS118C predictably doesn't work. Flashing the recovery image via TWRP seems to go fine but I'm stuck at the white "Wileyfox powered by Android" screen. Tried wiping Cache/Dalvik but no dice.
Edit 2: flashing Magisk afterwards seems to make it work.

I try to install the ZIP via TWRP and after the process ends the phone reboots but it remains stuck at the "WileyFox" white screen.
EDIT: I tried the fastboot one and it worked. Sometimes is hard to understand our devices

I'm guessing it's some kind of dm-verity issue? Flashing in TWRP worked for me when I flashed Magisk 12.0 afterwards, which seems to take care of dm-verity. Linuxct suggested installing Magisk in his debloat thread and I thought "what's the harm". Now I'm a happy camper.

Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.

Will this Firmware work on my Swift 2 Plus?

Cappucinto said:
Will this Firmware work on my Swift 2 Plus?
Click to expand...
Click to collapse
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.

Afifus said:
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.
Click to expand...
Click to collapse
Thank You so much

Installed it via fastboot and now iam stuck in a bootloop :S
EDIT: Did a factory reset in recovery! Works now.

Swift 2 Plus on 13.1.5 Cyanogen. Which method is best to install Android 7.1.1 TOS118C manually. The phone is stock, not rooted. Thanks

gaborkov9 said:
Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.
Click to expand...
Click to collapse
If you use the
Code:
adb reboot "dm-verity enforcing"
can you remove the dm-verity menu on boot or do you need it left as after bootloader unlocked?

TOS373J?
Anyone have the images for the latest update?

TOS373J OTA
other link

Pooh042 said:
TOS373J OTA
other link
Click to expand...
Click to collapse
doesnt work gives me instal error 7 when i try to instal it

DarthBraindrain said:
doesnt work gives me instal error 7 when i try to instal it
Click to expand...
Click to collapse
what is your current firmware version?

Anyone who installed TWRP and rooted on Marshmallow able to update to Nougat?

If so, how? Thanks!

magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.

worked for me perfectly

pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.

Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.

pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.

Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.

Help with soft brick

Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.

What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you

Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?

Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).

mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.

mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.

+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?

mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.

+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.

mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?

mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.

+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,

mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin

+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.

August images are up, and they're 9.0?

Google just posted the August images a few minutes ago, but they are listed as 9.0 Android P builds. PPR1.180610.009
I haven't been keeping up with the developer previews. Is this a new build or a preview?

MrDrift42 said:
Google just posted the August images a few minutes ago, but they are listed as 9.0 Android P builds. PPR1.180610.009
I haven't been keeping up with the developer previews. Is this a new build or a preview?
Click to expand...
Click to collapse
9.0 Pie is officially released 9.0.0 (PPR1.180610.009, Aug 2018)

Wow, just wasn't expecting it today, rumors were for the end of the month.

So would you be able to follow the below thread to go from Rooted 8.1.0 stock by just downloading the new image (9.0) and newer versions of magisk?
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
edit: and then i found this:
1. Boot into the bootloader and plug your phone into a PC with fastboot installed.
2. Flash the P factory image using the flash-all script.
3. Let the phone reboot back into the system and complete setup process.
4. Download everything needed for TWRP
SAILFISH FILES Twrp Image, Twrp installer
MARLIN FILES Twrp Image, Twrp installer
6.MAGISK
7. Boot your phone into the bootloader
8.
Code:
fastboot boot <twrp-image>
9. When TWRP boots, swipe to allow modifications
10. Flash the twrp ZIP
11. Reboot back into Android, then reboot back into TWRP
12. Flash the magisk zip
13. Reboot. If it freezes on the logo, hold the power button until it reboots.

Just installed on my stock OG Pixel XL and man is it smooth and fast. I believe it gave more life to this phone. I enabled the home key gesture but disabled after a few minutes. I will have to get used to it later. I'm on vacation and I don't want to have to learn new gestures yet. Hopefully battery life improves which is what I am reading it should do.
Sent from my Pixel XL using Tapatalk

Is magisk working with this? And is Safetynet passing?

KevinThaKid said:
Is magisk working with this? And is Safetynet passing?
Click to expand...
Click to collapse
Yes - rooted
No - safetynet pass
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
I did an OTA sideload, flashed TWRP, rooted with Magisk. No problems
Is there any advantage to flashing the full stock image instead of the OTA since this is an upgrade to 9.0?

I the ota came up on my phone today. I am currently on a unlocked loader and rooted. This is the first time Ive gotten an update notification. Is there any harm in taking the update. I really no longer have a use for root, or twrp.

OKAstro said:
Yes - rooted
No - safetynet pass
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
I did an OTA sideload, flashed TWRP, rooted with Magisk. No problems
Is there any advantage to flashing the full stock image instead of the OTA since this is an upgrade to 9.0?
Click to expand...
Click to collapse
Flash the full image, at least you'll know there won't be any left over stuff from Oreo, + fresh start. Side loaded the ota previews and then just flashed the official image with a full wipe, no problems yet.
---------- Post added at 09:47 PM ---------- Previous post was at 09:00 PM ----------
specd_out said:
I the ota came up on my phone today. I am currently on a unlocked loader and rooted. This is the first time Ive gotten an update notification. Is there any harm in taking the update. I really no longer have a use for root, or twrp.
Click to expand...
Click to collapse
Don't try taking an ota if your rooted, just sideload the ota.zip or flash the whole image with a full wipe (backup internal storage)

lordodin912 said:
Flash the full image, at least you'll know there won't be any left over stuff from Oreo, + fresh start. Side loaded the ota previews and then just flashed the official image with a full wipe, no problems yet.
---------- Post added at 09:47 PM ---------- Previous post was at 09:00 PM ----------
Don't try taking an ota if your rooted, just sideload the ota.zip or flash the whole image with a full wipe (backup internal storage)
Click to expand...
Click to collapse
So apparently my phone took the update, I do not recall accepting the update. But regardless I am on 9 and running ok.

specd_out said:
So apparently my phone took the update, I do not recall accepting the update. But regardless I am on 9 and running ok.
Click to expand...
Click to collapse

KevinThaKid said:
Is magisk working with this? And is Safetynet passing?
Click to expand...
Click to collapse
- Installed Factory marlin-ppr1.180610.009-factory-90a4fa8b.zip
- booted twrp 3.2.2.0
- installed Magisk-v16.7.zip
- Rooted = YES, Safety Net = YES
- Substratum does not have 9 for Android Version yet, tried 8.1 and it failed and no effect.
- All else is fine

jk8260 said:
- Installed Factory marlin-ppr1.180610.009-factory-90a4fa8b.zip
- booted twrp 3.2.2.0
- installed Magisk-v16.7.zip
- Rooted = YES, Safety Net = YES
- Substratum does not have 9 for Android Version yet, tried 8.1 and it failed and no effect.
- All else is fine
Click to expand...
Click to collapse
I wasn't able to get twrp to decrypt, no matter what password I set. Was able to install by turning off lock screen passwords entirely.

I honestly wasn't expecting to like P that much but I figured I'd give it a go. Honestly I quite like it. And the gestures. Now just to wait for custom roms and see what people can do.

jkennebeck said:
So would you be able to follow the below thread to go from Rooted 8.1.0 stock by just downloading the new image (9.0) and newer versions of magisk?
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
edit: and then i found this:
1. Boot into the bootloader and plug your phone into a PC with fastboot installed.
2. Flash the P factory image using the flash-all script.
3. Let the phone reboot back into the system and complete setup process.
4. Download everything needed for TWRP
SAILFISH FILES Twrp Image, Twrp installer
MARLIN FILES Twrp Image, Twrp installer
6.MAGISK
7. Boot your phone into the bootloader
8.
Code:
fastboot boot <twrp-image>
9. When TWRP boots, swipe to allow modifications
10. Flash the twrp ZIP
11. Reboot back into Android, then reboot back into TWRP
12. Flash the magisk zip
13. Reboot. If it freezes on the logo, hold the power button until it reboots.
Click to expand...
Click to collapse
Good stuff.
I am working on new guide: [Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch

Can anyone confirm if latest magisk Xposed is working on 9.0?

I am unable to change USB Options (e.g. file transfer) when plugging in a USB cable.. All choices are greyed out.
Any suggestions

Installed factory images on Pixel and Pixel XL from Oreo. Removed -w from flash-all, removed pin from phones, and everything worked fine. 16.7 Magisk after TWRP 3.2.2-0 .img only. I haven't installed TWRP and probably won't until a new version comes out that decrypts. Put PINs back on, then then the first time I ran SaftyNet on the XL, it came back invalid response, but then passed the next time I ran it (and has multiple times after that). PIxel passed 1st time and multiple times after. I had two apps come up with warning that they were created for an older version, but the message doesn't come back after hitting OK and relaunching. Both apps are working fine. The only thing I have noticed in Google Pay has an almost blank main screen (shows recent transactions only) but looks normal on other screens. I will try using it at a store today or tomorrow, but I suspect it will work since SafetyNet is passing and the app opened without an error.

twrp is up to 3.2.3-0 https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html

Pain-N-Panic said:
Can anyone confirm if latest magisk Xposed is working on 9.0?
Click to expand...
Click to collapse
Xposed is not compatible with 9 yet