Database Users

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)
This thread is for the second Android N Preview.
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview 2 image released by Google on 4/13/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 2. If your internal storage is unencrypted before flashing it remains unencrypted.
For some people this didn't work. It seems to be the case when you have been encrypted by your previous Android N installation, in which case TWRP seems to have difficulty reading the file, and that seemingly Preview 2 doesn't play nice with TWRP. It works best when you are unencrypted and your recovery is 3.0.2-0. Thanks to @gammaxgoblin, @blitzerking1, @Michael in ATL, @HueyT, and @PhillyFlyer for debugging and hints.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.71 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Despite the fact that SuperSU 2.71 is supposedly re-written for Android N, there are still some apps that seem to have a problem obtaining root. The commonest complaint on this thread so far has been about Adaway. If you want to block Ads just manually do what Adaway does. Download a hosts file from any ad block list server such as http://winhelp2002.mvps.org/hosts.htm, copy the files on your sdcard, boot the phone into recovery, and using the TWRP file manager replace the file /system/etc/hosts with this file and set its permissions to 644 (rw-r--r--).

wouldnt flash first go. redl now
no flash again

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Same happened to me. It would not flash, same error

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
Same error for me as well. I can extract the zip and view the file it is talking about. I also tried on TWRP 3.0.1-0 and TWRP 3.0.2-0
Everything is working perfect for me with the new zip. I have a unencrypted phone and used 3.0.2 TWRP.

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
i tried 3.0.1 and 3.0.2 and i can also see the file

Method 2 works great

Method two works I used it myself

Shall I flash preview 2 directly from marshmallow?

Seems like TWRP is having a lot of troubles with each version of N Preview's encryption. I have same problem with both N6 and N6P, as do others in that forum too....:/

i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.

marius987 said:
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
Click to expand...
Click to collapse
Sorry for the stupid question. What do you mean for TB?

cerico76 said:
Sorry for the stupid question. What do you mean for TB?
Click to expand...
Click to collapse
I'm going to assume it stands for Titanium Backup.

Waiting for fixed method #1

outkastz said:
I'm going to assume it stands for Titanium Backup.
Click to expand...
Click to collapse
Ah,yes! Thanx!

Can someone please provide a link to the desktop website for the flashable zip?

Just to help with the installation of method 2, holding shift and right clicking a blank space in your unzipped folder, you can click open command window here. That will save you having to CD all the way to it.
Sent from my Nexus 6 using XDA-Developers mobile app

I did method 1. It upgraded fine. All my data remained. It killed root (expected this) and my TWRP. I was unencrypted before attempting.
I went and downloaded the latest TWRP and flashed via fastboot. Then downloaded latest SuperSU from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and flashed it via my newly installed TWRP. Root confirmed and all is well.
Good to go Thanks!

I've got an "Invalid boot image" issue :
Any tought ?

outpox said:
I've got an "Invalid boot image" issue :
Any tought ?
Click to expand...
Click to collapse
You may have to flash a previous stable release of marshmallow or lollipop from Google first and then try this because something seems to be corrupted in your system.

MotoG4+ XT1644 6.01 to 7.0 Saga (for others to avoid)

OK Please note (4-25-17) this message is a work in progress, as I slowly restore my system.
This is a listing and hopefully helpful listing of what I did (right and wrong)
in upgrading my Systemless-rooted (suuser) phone from 6.01 to 7.00 (nougat)
# 1. it did not work, and I went back to 6.01 successfully using the twrp recovery
I have previously used Bender's guid (here) to get the system-less root on 6.01.
essentailly, here's the best plan. Use the Minimal ADB and Fastboot package (MADB &F) (here)
(Explanation: the MADB&FB package will allow you do do LOTS of stuff related to updating your phone, with very little grief.)
it also includes the ability to automatically "push" a package over your usb connection if the ZIP file doesnt load right. **THIS will come in handy later!
Once MADB&F is installed, make note of your directory, and then make sure you start your dos window (for pc users) as an administrator!
BTW, if I HADN'T made the "TWRP backup" of my system, I'd be Sh*t out of luck right now...", because I screwed up the 7.0 upgrade.
the technical problem was that I had no data, no modem, no way of getting data/voice in/out.
SIMPLY using the TWRP restore fixed me!!!
(so far, we have MADB&FB, downloaded and bender's (chainfire) rootless guide.
Next you want to download the current firmware image for your phone. This will be a lifesaver, I promise!
3) Download a TWRP image (this will MAGICALLY load on your pc when you tell it you need help! Look HERE
(Athene is the Motorola Codename for the motoG4+)
3) copy the athene TWRP image into your madb&FB directory to make it easy to load
4) next, (you still haven't touched your phone yet, you realize: (skipping some basics here, you can search here on XDA to find more info)
a) plug your phone into your pc
b) make sure you are a developer
c) make sure your phone shows you are connected to your pc for file transfers, NOT for charging
5) in your MADB&FB directory, (aka a dos/(admin) window) type the following:
all commands at this point will take place in whatever directory you installed Minimal ADB & Fast boot (MADB&FB)
Connect your phone to your PC and open MADB&FB, check the connection with:
adb devices
return should include your "serial-no" and "device".
6) next, on pc, tell the system to reboot your phone to the bootloader!
Reboot into bootloader with:
adb reboot-bootloader
and check again with:
fastboot devices
7) Next you are going to download TWRP to your phone (not permanently, just for a bit!)
fastboot. flash recovery twrp-3.0.2-0-athene.img
Now you have TWRP (Team Windows RECOVERY PROJECT) loaded.
SO.. THIS is where you create a backup of your current stuff using the backup options.
NEXT:
take the suUser2.78 (stateless rooting), and once your backup is done, install it from TWRP
Then (I was) back to 6.01 rooted.
NEXT: 7.0 and then rooting... (will update tomorrow)
did a successful upgrade to 7.0,
then unsuccessfully tried to sideload supersu2.78, which bricked loader
then downgraded again to 6.01 (and rooted again, ok)
will continue tomorrow.
need working phone for now..
cheers to all, and to all, a happy spelunking!

You can't root factory Nougat as is, it is well encrypted.
You need to replace first the kernel with the ElementalX one, or you will end up with bootloops.
Only after that you can do SuperSU, but only with the latest beta.

A few pointers from your story:
1)As you've found out the hard way, you won't be able to update to Nougat if you have root and/or TWRP, because the update requires a stock system - stock recovery, system and no modifications (bootloader status doesn't matter). In other words, you'll need to unroot and restore your stock recovery - might be easier to reflash the stock system, probably the quickest way to flash a stock ROM (and update to Nougat) is to use the fastboot ROM. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this will remove root and TWRP, as well as potentially wipe your data, so back up accordingly. This should flash the NPJ25.93-14 build on your device, which appears to be the latest global build.
1a)Also, if you flash Nougat this way, your bootloader and GPT partitions will be updated, so if you wish to downgrade to Marshmallow at any point, when flashing do not flash these partitions from the Marshmallow ROM. Fastboot should stop you, but a brick may occur if these get flashed.
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
2) As SoNic67 has already mentioned, the stock kernel security will cause your device to bootloop should you choose to try to root following the Marshmallow method. If you wish to use SuperSU, follow this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You may wish to use a more up to date TWRP than the official 3.0.2 (I recommend shrep's TWRP 3.0.3 n4 here:https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337) Whatever you do, ensure you flash first the ElementalX kernel before you flash the SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), or apply the systemless fix with earlier SuperSU versions as directed in the aforementioned rooting with SuperSU guide. Else you'll be having bootloops or your device will not boot whatsoever. Here's my steps in successfully rooting Nougat: https://forum.xda-developers.com/showpost.php?p=71817346&postcount=225. Good luck either way.

echo92 said:
A few pointers from your story:
[...]
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
[...]
Click to expand...
Click to collapse
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shreps' unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk

bmeek said:
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shrep's unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Nice one, hopefully that'll help more XT 1644 users I'm still not sure if TWRP can backup/flash the baseband by itself, but I don't have a XT 1644 to test. I imagine your backup will need a clean flash (wipe data/cache/Dalvik) to work?
The OTA process does update the partition table, but as far as I know, that should not prevent you from flashing back to Marshmallow/Nougat as you wish, so long as you did not try to downgrade the GPT/bootloader.
There was an effort to create TWRP flashables of the stock ROMs a little while ago (you can see the thread here: https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147) which if I understood it created flashable radios and ROMs from the firmware files we have. We can't touch the GPT/bootloader since, as I recall, you need a signed stock firmware to do so (and besides, downgrading GPT might be asking for a brick). I recall some users mention they were able to run Nougat TWRP flashes on the MM bootloader/GPT without issue.
There were issues with simply flashing the Nougat 93-14 radio baseband files for some US users, losing LTE in the process and appears the only resolution was to flash the stock ROM - I don't know what the cause was (perhaps no/incorrect CDMA support in the radio files?). Your TWRP flash is from a US based phone so may have better luck in that department, and will likely behave on your device since that OTA has updated all the firmware on your device that TWRP isn't able to touch. I still am not sure if we can use this TWRP backup to update on a MM device without issue, but only one way to find out...

GAPP error 70 HELP

I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.

Yurodd said:
I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.
Click to expand...
Click to collapse
You're probably going to have to flash your phone back to stock to re-gain all of your apps.

Zachisimo said:
You're probably going to have to flash your phone back to stock to re-gain all of your apps.
Click to expand...
Click to collapse
So flash the rom again? is that going to wipe my phone?

Dark Nightmare said:
This is a basic write up to convert your bootloader unlocked T-Moilbe OnePlus 6T to the International Version firmware via fastboot flashable firmware files.
Contents:
-Disclaimer
- Full Device Backup - Precautionary - Optional, but Recommended.
-Firmware Versions and Flashing Instructions
-Rom Sources
-MSMDownloadTool
-FAQ's
-Additional/Optional Tools
-Credits
Disclaimer:
Like any other form of modding, there are risk involved, we have a near flawless option to recovery by use of the MSMDownload linked at the end of this post, but like with any form of modification, you are solely responsible for what is done to your device and you accept all risk involved, should something go wrong, for the most part, recovery is fairly simply, no matter how bad we screw up, thanks to OP.
Instructions to a full device backup:
1. Download the zip below and extract it to it's own folder
2. run cmd.exe while in fastboot mode and run the following commands:
3. Once twrp boots, run the backup.bat script included, it will backup all partitions on your device, including your efs.
4. zip all of the image files and store it somewhere safe.
Backup: https://androidfilehost.com/?fid=11410963190603855581
For Users Looking to Flash to Firmware versions 9.0.4-9.0.5
FLASHING STEPS
Requirements:
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Flashing Process
1.. Whichever full rom zip you choose, extract its contents. (In my case I used the 9.0.5 full zip)
2. In each zip file you'll find images.zip as well as others_flashall.zip, extract both of them into the same folder/directory as the rest of the original zip file.
(Optional, download the modded flash-all-partitions-fastboot.bat file at the end of the thread, it includes the reboot command to auto reboot when done flashing)
Attached Below is also a flash-all-partitions-fastboot.sh script for Mac OS users (Note this script will not wipe your device, so if you need to wipe, run the ./fastboot -w command in fastboot manually)
All bat files, images and adb files should all be in the exact same folder, no subfolder(s)
3. Now boot into fastboot using either the vol+/vol- and power key combo or via adb using the following adb command .
4. Once in fastboot run the bat file called flash-all-partitions-fastboot.bat
9
5. When asked, I would advise typing 'Y' for yes to format the device. (wipe only if you're converting for the first time)
The sparse header error is completely normal.
6. Upon completion, the script should pause and say press enter to continue, it will not reboot your device...
WAIT UNTIL NOTHING ELSE IS HAPPENING AND ITS NO LONGER FLASHING ANY FILES
At this point, hit power and reboot.
All done!
Firmware Version 9.0.6
Requirements
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Steps to Flash
Note: Modded fastboot flashing script attached at the end with the reboot command included, also attached is a script for MAC users, mac script will not wipe your device, wipe manually if you need to using
ROM Sources
Mauronofrio's Thread
T-Mobile 9.0 FULL Fastboot ROM
Saythis' International Firmware 9.0.6
Recovery - MSMDownloadTool
If for some WEIRD reason you brick, have a HW mismatch, etc, or you just can't boot go to this thread -> MSMDownloadTool - T-Mobile 9.0
OPTIONAL Steps
Root is available via two Options below:
- OnePlus Rooter
- Manual Root Using a Patched Boot Image
Automated Process
Luckily There are devs looking to make things simpler:
More an automated tool to carry out this process, go to the thread below:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-oxygen-os-9-0-6-fastboot-windows-t3870170
WARNINGS!
-Advisable you disable automatic updates in developer options upon boot if it is enabled.
-Do not attempt to update using the OTA files, so far we've had one softbrick due to it and said user was unable to boot into fastboot to attempt any kind of recovery.
-ALSO DO NOT FLASH WITHOUT THE FILES IN THE FOLDER, IF YOU DO YOU WILL END UP WITH A SOFTBRICK
-If you get either dump mode or fastboot bootloop check your downloaded rom file to make sure its complete, unzip again and flash again
FAQ
Q. Will this enable dual sim functionality?
A. Dual sim functionality works, volte, Wifi calling and vvm.
Q. Can I take OTA's like a regular device?
A. No, sadly.
Q. What about when a new update comes out?
A. Once a fastboot flashable ROM is made, you can update using the steps above, using the new ROM files.
Q. What if I brick or have a HW/SW mismatch?
A. Use the MSMDownloadTool to recover.
Q. Do all the features work?
A. For the most part, there are minor bugs, but they aren't consistent, so can't really say.
Q. Is this a full conversion?
A. Somewhat.
Q. Do I have to wipe everytime I update?
A. No, wiping may only be necessary for conversions, no wipe needed to update.
Q. Do I have to root everytime I update?
A. Yup, sadly.
Q. Do I have to convert to a specific version?
A. Nope, you can convert to any version.
if any edits are suggested, I'll include them.
Credits:
@mackentosh for testing and unfortunately bricking using the OTA File
@Velrix for being the second successful tester, among others.
All the other users who've been testing/contributing to testing
I'll add names when I get to comb through the threads.
@Dameon87 for the correct ROM source link of the unpacked ROM with batch files.
@Krunk_Kracker for the disable auto updates image
Thanks to @Addiso for the Stock T-Mobile Backup images
@mauronofrio for the scripts and for hosting the Rom zip @hartleyshc for testing and confirming full dual sim functionality.
@Saythis - for the 9.0.6 FULL ROM Zip
Click to expand...
Click to collapse
I would follow this guide. Than choose Y when asked to wipe data. If you want to choose N let me know how it goes. But the easiest way is going to be to start from fresh using this guide by @Darknightmare.

Update to OxygenOS 9.0.0

Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
Code:
Updating partition details...
...done
Full SELinux support is present.
Data successfully decrypted
Updating parition details...
...done
MTP Enabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
[COLOR="Red"]E:String resource 'zip_compatible_err' not found.
Using default value.
Zup Treble compatibility error!
Invalid zip file format!
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip[/COLOR]
Updating partition details...
...done
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks

Mouchoir said:
Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks
Click to expand...
Click to collapse
Hello, I can't recommend any guide on outside of xda cause they're not consistent...
Just follow this guide in the first post https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 would help you.
You can't flash twrp 3.3.1 cause you need newer firmware, pie firmware.
Please answer all the questions:
What is you current twrp recovery (file name)?
What is your current Rom(file name)?
What is your magisk version?
Is your storage encryped or decrypted?

Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo and use a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using an Oreo TWRP if you're on Oreo Firmware/ROM or Pie TWRP if you're on Pie Firmware/ROM) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash xXx No Verity 4.0.zip from here
Reboot
Note: First boot may take some time, so please be patient and wait for it to boot.
Click to expand...
Click to collapse
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks

Mouchoir said:
Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks
Click to expand...
Click to collapse
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).

strongst said:
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).
Click to expand...
Click to collapse
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho

Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP

Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
Clean flash wipes system and data, so no os, data and settings.

PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?

Mouchoir said:
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?
Click to expand...
Click to collapse
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8

strongst said:
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8
Click to expand...
Click to collapse
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Code:
Data successfully decrypted
Updating parition details...
...done
Successfully decrypted with a default password.
Updating parition details...
...done
Full SELinus support is present.
MTP ENabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
Patching system image unconditionally...
E1001 Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR:7
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip[/COLOR]
Updating partition details...
...done

Mouchoir said:
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Click to expand...
Click to collapse
Error 7 is corrupt file, you'll find about it here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003/page591

Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7

Mouchoir said:
Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7
Click to expand...
Click to collapse
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions

strongst said:
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions
Click to expand...
Click to collapse
As stated here, I used 7zip
PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.

Yes because to use fastboot you have to be in fastboot mode...

PierreVicquery02 said:
Yes because to use fastboot you have to be in fastboot mode...
Click to expand...
Click to collapse
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?

Mouchoir said:
As stated here, I used 7zip
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.
Click to expand...
Click to collapse
Mouchoir said:
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?
Click to expand...
Click to collapse
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device

PierreVicquery02 said:
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device
Click to expand...
Click to collapse
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out

Mouchoir said:
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out
Click to expand...
Click to collapse
That's such a strange bug. If you are in fastboot, it's impossible for your PC to recognize it in ADB mode. Try with another computer or use unbrick tool to clean your phone (it installs Oxy 9.0.8)

Well I managed to see the fastboot thanks to the EOM cable but I think I bricked my phone

One Plus 5 won't upgrade to new Android.

Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman

@lucider14 Just curious why you used the MSMDownloadTool from OxygenOS 4.5.8 and not the one for OxygenOS 9.0.11? You most likely won't see OTAs for Android 7 as it is now 4 Android Versions behind as of this week. Android 9.0.11 was the last official fully released OTA, OxygenOS 10.0.0 Hotfix is last official OTA OnePlus has released into the wild.

My phone waa bricked so had to use it. Please let me know if there is any workaround for this to update.

@lucider14 The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool

card13;83478941 [user=11104643 said:
@lucider14[/user] The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
Click to expand...
Click to collapse
@lucider14 OOS 4.5.8 is pre-treble. You can't jump directly to Android 9 or 10. One of the OOS updates before Android 9 set up treble on our phones. I don remember exactly which one. You're best to use Opt 2 above, it will be easier.
Cheers!?

lucider14 said:
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
Click to expand...
Click to collapse
First,flash it 9.0.11 build and then OxygenOS 10.0.0 Hotfix..

And with https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater

I've had a similar problem and I thought I broke my phone, got pretty scared can't buy a new phone but need a newer android for my apps to work.
I came from freedom OS on android 7 so I never had the project treble on my phone and tried to flash new factory images, as a result, no newer TWRP recovery worked and I was unable to boot into anything other than the bootloader. I had the same error with Error 7, from what I can understand this is from a screwed up or non-existing "vendor" partition which says stuff like "this is a OnePlus 5" for newer factory images to install (factory image told me I didn't have a OP5), this never existed in android 7 or OOS 4.X.X. ScRuFFy7 is correct, the vender partition was created in OOS 5.1.4 (or OTA 037) and only when android is booting up, this took like 10 mins on mine. Once this vendor partition is correctly created you can flash newer TWRP recovery (I flashed 3.4.0) and newer factory images, like OOS 9.0.11 then to version 10. The built-in updater and stock recovery can update to the newer versions with the flashable zip files. For whatever reason OnePlus don't size the partitions in their zips so they make small changes from one version to the next so skipping specfic versions throws up errors in the future.
Screw it, I should document what I did in case I mess up my phone in the future and maybe be helpful to someone else in need, especially in this messed up and depressing time of the plague. But anyway this is what I did to get my phone back, I should point out I have no idea what I'm doing. Meaning I'm a N00b.
NOTE: this process Wipes all the data from the phone, so I hope you have backups right now.
Will need ADB, you can install This on windows, it's super easy and works thanks to mauronofrio. You can get the all in one tool too from here it's pretty handy and can format and decrypt from the bootloader, from mauronofrio? I think? This guy is pretty good. I got all old firmware from Here thanks to Some_Random_Username for the life line since OnePlus won't provide the old Zips anymore.
1) Boot to TWRP recovery if you have it installed (VOL DOWN + POWER). If not Boot to Bootloader (VOL UP + POWER) and flash TWRP Recovery. You can use TWRP 3.1.1 This one works on OOS 4.X firmware without giving me a Black Screen.
1a) To Flash the Recovery you can use the all in one tool to flash it or open up command prompt and use the Fastboot Flash [insert recovery file name here .img] command to flash it, you can find the FastBoot Flashing Method in the middle of this page for instructions.
2) Format Data. The Format Data button in TWRP recovery not the swipe to factory reset, because we're going back to scratch.
3) Flash OTA_006 (OOS 4.5.2) original firmware from the link above (says ota_006 in the middle of the loong file name)
4) Boot into android and use System Update in settings and stock recovery it just flashed to flash OTA_020 (OOS 4.5.15) by clicking on the cogwheel in the corner and choosing Local Update. [probably skippable I just wanted to make sure it works]
5) Boot into android again and install OTA_27 (OOS 5.0) with System Update again.
6) If it doesn't boot, go to Bootloader and flash TWRP. Once in the recovery and you go to install and if you find all the folders have random numbers and letters for names then the storage in encrypted.
7) Format to get rid of encryption (random name folders) then reboot to Recovery and Flash OTA_27 again and let it start fresh on OOS 5.0 to make sure it's still booting and working.
8) Once booted Flash OTA_037 (OOS 5.1.4) wait for vendor partition to be created (took 10 mins on my OP5), reboot to TWRP and format if folders are encrypted and reflash OTA_037 if needed.
Once booted into android this is the point where you should have the Vendor Partition already created by the factory image, you can go back into TWRP (flash TWRP if needed) and under Mount be able to see, mount/unmount a Vendor partition without errors. This should solve the Error 7 problem with factory images. A newer version of TWRP Recovery should work now, I installed 3.4.0 from mauronofrio Here. 3.4.0 works with android 10.0 so I was glad.
9) Boot android again and flash OTA_038 (OOS 5.1.5) just to make sure with stock recovery. [Probably skippable but I was a Paranoid Android at this point, just to make sure it still works]
10) Boot to android again and install OTA_042 (OOS 9.0.0) with System Update to keep making sure it works. [Again, I was Paranoid. Probably Skippable]
11) Boot to android again and install OTA_054 (OOS9.0.11) as last Android 9 update to have things set up ok.
12) Boot into Android again and install the latest android 10 from OnePlus (OTA_068) with System Update and the Stock Recovery, this is Android 10.0.0 and OOS 10.0.0. Things should work fine at this point but I doubt the check for update will get new oneplus updates. As of Sep 25, 2020 it is up to date. Technically.
I should add something else I discovered after. I found a flashable zip file from one of the lineage OS posts of a oneplus5_vendor_5.1.5.zip Here. You might be able to just use that to create the Vendor partition then just Flash one of the OOS 5.X Firmwares and go from there, I've not tried it so I'm not 100% sure but it's a possibility?
Hope this is helpful to someone at some point in time. for troubleshooting at least. Honestly really glad I have a working phone right now.