Database Users

How to stock update with rooted and TWRP?

Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?

Chattersking said:
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Click to expand...
Click to collapse
You need the official recovery for update to work

Chattersking said:
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Click to expand...
Click to collapse
You can update to 21s on the US version (727) from TWRP with a few modifications to the updater-script file (see the below post/thread):
https://forum.xda-developers.com/showpost.php?p=72815409&postcount=48
This will remove root but it keeps TWRP so you should be able to just reinstall root through TWRP.

Thank you. Will it keep my data and apps intact or will it erase them? I don't want to lose all my important data and setup.

Chattersking said:
Thank you. Will it keep my data and apps intact or will it erase them? I don't want to lose all my important data and setup.
Click to expand...
Click to collapse
I did a wipe before updating but it should work without wiping as the update zip file is the official OTA with only a modified updater-script. Do a backup from TWRP before you try it and if anything goes wrong you can revert to that backup.

Running into the same issue..did your script and that worked. Thanks for that.
Flash 19s using TWRP and needed a somewhat official way to get to 21s. Use the script of d/l the official 21s update and pushed the modified zip to sdcard to get flashed in TWRP. So hopefully this update, updated whatever it needs to update and maybe it will fix my other issue... why when I flash Lineage base ROMs they show my battery only at 50%

I followed the above instructions and replaced with the updated script however TWRP is giving me Error 7 and a quick google search is saying it is due to problem with updated script. How do you guys fix this?

ZE520kl OTA upgrade doesn't work

Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?

bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.

[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?

vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.

[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?

vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .

@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.

wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.

[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.

[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked

wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.

@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.

wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.

[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.

wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).

simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?

bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.

I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX

Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?

ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.

[GUIDE] How to get Magisk Root & Xposed on Oreo 8.0 (STOCK)

I'M NOT RESPONSIBLE IF YOUR DEVICE BRICKS, SD CARD DAMAGES OR NUCLEAR WAR STARTS.
Rooting method described below will work on Oreo-running devices ONLY (confirmed on build OPN27.76-12-22 and on OPNS27.76-12-22-9).
Please follow all steps very carefully and make sure you downloaded correct versions of all .zip files mentioned in my instruction!
ROOT (SafetyNet test will PASS!)
1. Download all files listed below:
- twrp-3.2.3-0-addison.img (CLICK)
- Magisk-v17.1.zip or newer if availabe (CLICK)
- f2fsfix-2018.9.2.zip (CLICK)
2. Flash TWRP using Fastboot:
Code:
fastboot flash recovery twrp-3.2.3-0-addison.img
3. Flash Magisk-v17.1.zip (or newer if available).
4. Go to TWRP/Settings and open Terminal.
5. Run both of following commands:
Code:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
6. Flash f2fsfix-2018.9.2.zip
7. Reboot (it is crucial in case of installing Xposed afterwards).
8. Optional but recommended: update your Magisk Manager to the latest version (CLICK).
9. Open Magisk -> Modules and update f2fs-loopback-bug-workaround module to the newest version (can be done only via Magisk Manager only if new version of f2fs-loopback-bug-workaround module is available).
10. Enjoy rooted Oreo.
UPDATE 03.10.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 17.1.zip AGAIN (yes.).
3. Flash f2fsfix-2018.9.2.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me).
UPDATE 03.10.2018
XPOSED (be careful: Xposed for Oreo is still in BETA distribution and flashing it will break your SafetyNet!)
1. Open Magisk Manager -> Downloads.
2. Download Xposed Installer (the one from the screen below):
https://image.ibb.co/byLUuK/Xposed_Framework.png
3. Let Magisk install it.
4. Reboot.
5. Open Xposed Installer (you will see orange exclamation mark, don't worry).
6. Reboot once again.
7. Voila.
Hit THANKS if I helped!
Credits:
- @topjohnwu
- @rovo89
- @Artim_96
- @VR25

@rafikowy ah, so basically the problem was with dm-verity and forced encryption? That makes sense. So it would basically also work if you'd not extract the boot.img from the OTA zip and mod it with Magisk manager with both enabled and flash that (might be easier than flashing normal Magisk and then make the changes), so you'd basically just flash the img and the module zip in TWRP.
Well, if no bigger bugs appear I might try the Oreo OTA and root tomorrow. Don't think it will be here on its own till then, even if it's already the official rollout (Indian and brasilian users seem to get it officially)

First magisk manager did not want to open, but a reboot solved. thanks

So, Lenovorola is still "undecided" in regards to patching F2FS.
I wonder why...

Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?

Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Only a Soak test is available, the link is in the thread in the ROM section. And yes, it doesn't seem to update your bootloader, it was already successfully testet to go back to 7.1.1

Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Look at
https://forum.xda-developers.com/mo...se-attempt-t3812530/post76991120#post76991120

not work - moto z play - oreo soak
Unfortunately it does not work. : (TWRP prompts for a PIN to decrypt data.) How to select cancel and install Magisk on installation f2fs-loopback-bug-workaround-2018.1.31.zip displays an error that does not detect magisk or is incompatible. How do I format the date everything is installed but the phone does not turn on... Any idea?

Sorry but, if verity is enabled, that means you are unable to modify /system files?

Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
You can go back, problem is you will lose IMEI by going back to Nougat.

huma_dawii said:
You can go back, problem is you will lose IMEI by going back to Nougat.
Click to expand...
Click to collapse
I gone back to 7.1.1 Nov patch and everything is OK with my IMEI. Just flash 7.1.1 Plus ROM with TWRP. One issue what I have - In can't mount OEM partition in TWRP.

Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them

Camarda said:
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Click to expand...
Click to collapse
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.

St.Noigel said:
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
Click to expand...
Click to collapse
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now

Camarda said:
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Click to expand...
Click to collapse
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))

Can i go back to 7.1.1 and relock bootloader ??
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance

LovinVEVO said:
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
Click to expand...
Click to collapse
Nope. It's impossible for now. You can`t go back to full stock, because you'll lose your IMEI with flashing full 7.1.1 FW with RSD or fastboot.

St.Noigel said:
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Click to expand...
Click to collapse
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.

Camarda said:
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Click to expand...
Click to collapse
If you have bootanimation - just wait few minutes

St.Noigel said:
If you have bootanimation - just wait few minutes
Click to expand...
Click to collapse
Just waited for 30 minutes. It wont boot

OTA updates for rooted L29 P10+ ... without losing data

I have a rooted (With magisk) L29 P10+...So I have tried direct OTA update from EMUI...downloads and on reboot goes to TWRP. I tried using Firmware Finder and same thing happens (with and without proxy). I then tried uninstalling Magisk (root) and trying again but that did not work.
What I would like is top go to the newest OTA update so I don't keep getting the NAG message of my need to update...but MOST IMPORTANTLY...I do not want to have to redo my phone, i.e. data and layouts with folders. Is it possible? I cannot seem to find a link for the p10+...I kind of see one for the Honor and TWRP install but I do not want to corrupt and have to start from scratch.
Any help would be much appreciated.
Thanks in advance.

I have same issue. Did you get this resolved?

Well. i guess you have to:
a) install original recovery (may get one from update file or from forum, i saw download links here) with fastboot flash recovery_ramdisk recovery_ramdis.img
b) install update
c) install twrp with fastboot
d) install magisk from twrp
actually, there's this thread, which worked for me also. https://forum.xda-developers.com/p10-plus/how-to/flash-stock-updates-twrp-installed-t3819734

[PLEASE HELP] HW P9 Lite (VNS-L21) Downgraded to MM, unable to get back to Nougat.

So, due to my Pixel's battery life being atrocious I wanted to try LineageOS 14.1 and use my P9 Lite as a daily driver.
I started by downgrading to Marshmallow from Nougat as DC-Unlocker wouldn't work on 7.0 and I needed the bootloader unlock code.
( I used the firmware and tutorial from 4mobiles dot net, looks to be a polish one. )
Once on 6.0 MM I was able to get the code and unlock the bootloader, however, LineageOS and it's TWRP does not seem to work on 6.0 so I needed to upgrade to Nougat again.
Unfortunately, when I try the official update it says there are no updates available and any time I try to use the firmware finder app either the download fails or upon attempting install the phone reports a 'compatibility issue' and won't accept any firmware.
I tried loads of different update.zip files via the recovery update as well as through ADB. Nothing seems to work.
Finally I was able to get TWRP 3.0.2.0 on it, but again, only the version from 4mobiles dot net works. Other versions of TWRP just remove recovery altogether. (I guess they don't work with 6.0)
At this point it's a bit easier to try roms, but still none of 'em seem to work.
-I tried sideloading and manually installing lineageos 14.1 from the sdcard, it fails with ERROR CODE 7
(currently I'm stuck on the 'YOUR PHONE CAN NOT BE TRUSTED/BOOTLOADER UNLOCKED' screen, no splash but I can get into recovery and fastboot)
-Tried flashing boot.img and system.img of various OEM firmwares as well as LineageOS's manually through ADB, same result, bootloops
It seems to me that some other file makes the phone believe that it's incompatible with any of my roms. Maybe the firmware i got for 6.0 is region locked, or perhaps it's the vendor.img that I don't know how to flash?
I know it's a grave mistake but I didn't take a note on what my original version number was. It was the latest 7.0 Nougat EMUI 5.0 update on a UK based unlocked VNS-L21. The 6.0 MM I flashed on it with a rollback update was C900B300.
I tried the proxy method, custom DNS, and manual download on various roms in the Firmware finder app. Even when the download doesn't fail, the system always says the firmware is incompatible when I try to install.
Right now I could put 6.0 MM back on it and make it usable, but I doubt it would be much better than the 7.0 that was on it originally.
Can anyone tell me how I could put the original Nougat firmware back on it? eRecovery doesn't detect any possible updates.
Any help would be appreciated and thanks in advance!

richplays said:
So, due to my Pixel's battery life being atrocious I wanted to try LineageOS 14.1 and use my P9 Lite as a daily driver.
I started by downgrading to Marshmallow from Nougat as DC-Unlocker wouldn't work on 7.0 and I needed the bootloader unlock code.
( I used the firmware and tutorial from 4mobiles dot net, looks to be a polish one. )
Once on 6.0 MM I was able to get the code and unlock the bootloader, however, LineageOS and it's TWRP does not seem to work on 6.0 so I needed to upgrade to Nougat again.
Unfortunately, when I try the official update it says there are no updates available and any time I try to use the firmware finder app either the download fails or upon attempting install the phone reports a 'compatibility issue' and won't accept any firmware.
I tried loads of different update.zip files via the recovery update as well as through ADB. Nothing seems to work.
Finally I was able to get TWRP 3.0.2.0 on it, but again, only the version from 4mobiles dot net works. Other versions of TWRP just remove recovery altogether. (I guess they don't work with 6.0)
At this point it's a bit easier to try roms, but still none of 'em seem to work.
-I tried sideloading and manually installing lineageos 14.1 from the sdcard, it fails with ERROR CODE 7
(currently I'm stuck on the 'YOUR PHONE CAN NOT BE TRUSTED/BOOTLOADER UNLOCKED' screen, no splash but I can get into recovery and fastboot)
-Tried flashing boot.img and system.img of various OEM firmwares as well as LineageOS's manually through ADB, same result, bootloops
It seems to me that some other file makes the phone believe that it's incompatible with any of my roms. Maybe the firmware i got for 6.0 is region locked, or perhaps it's the vendor.img that I don't know how to flash?
I know it's a grave mistake but I didn't take a note on what my original version number was. It was the latest 7.0 Nougat EMUI 5.0 update on a UK based unlocked VNS-L21. The 6.0 MM I flashed on it with a rollback update was C900B300.
I tried the proxy method, custom DNS, and manual download on various roms in the Firmware finder app. Even when the download doesn't fail, the system always says the firmware is incompatible when I try to install.
Right now I could put 6.0 MM back on it and make it usable, but I doubt it would be much better than the 7.0 that was on it originally.
Can anyone tell me how I could put the original Nougat firmware back on it? eRecovery doesn't detect any possible updates.
Any help would be appreciated and thanks in advance!
Click to expand...
Click to collapse
use full update.zip from firmware finder. to upgrade, you can't use latest package. you must use first nougat update.zip.

RyotaGamer said:
use full update.zip from firmware finder. to upgrade, you can't use latest package. you must use first nougat update.zip.
Click to expand...
Click to collapse
I've only used Full-OTAs, no bugfixes. None of them seem to work.
Yesterday I tried manually selecting a different model in Firmware Finder;
VNS-L21C185 instead of the default VNS-L21C432-
and downloaded VNS-L21C185B397 update. It verified fine but I couldn't install it due to my recovery being TWRP and not the stock one. What I think I'll try is flashing the recovery of the original Marshmallow firmware that's currently on the system and seeing if it will install this update. I kinda doubt it will tho.
Any other suggestions?

Is there any way I can install a nougat TWRP without my current working firmware being on nougat?
If not, is there any way I can install a nougat firmware with TWRP 3.0.2.0? In order to flash update.zip / update.app files I need to get the stock recovery back, but I can't seem to be able to do that.
Is there any way I can flash a standard OEM Rom onto it with TWRP?

richplays said:
Is there any way I can install a nougat TWRP without my current working firmware being on nougat?
If not, is there any way I can install a nougat firmware with TWRP 3.0.2.0? In order to flash update.zip / update.app files I need to get the stock recovery back, but I can't seem to be able to do that.
Is there any way I can flash a standard OEM Rom onto it with TWRP?
Click to expand...
Click to collapse
you can't install nougat TWRP in EMUI 4. you can install update.app with original recovery.
extract UPDATE.APP from update.zip
place UPDATE.APP to dload folder in sdcard.
press power button, vol+ and vol-