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.

How to Root Honor 8 FRD-L09 (NOUGAT 7.0 EMUI 5.0 With Bluetooth, NFC, system apps)

I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
I have only tested this with the device: (Honor 8 FRD-L09)
If anyone got this working on other devices please leave a comment so I can add it to this list for other people to see.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this with OldDroids TWRP or with surdu_petrus TWRP: Link(36.2MB) and Link(24,2MB)
1- Flash OldDroids or surdu_petrus TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid, surdu_petrus and phhusson

thierrybla said:
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this only with OldDroids TWRP: Link(36.2MB)
1- Flash OldDroids TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid and phhusson
Click to expand...
Click to collapse
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM

omartins said:
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
Click to expand...
Click to collapse
I have only tested it on the FRD-L09
I can't say for sure if it works on the others, I'm sorry.
If you got this working on a different device please let me know.

Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?

david320te said:
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
Click to expand...
Click to collapse
Yes SuperSU doesn't work as far as I know you need Phh Superuser.
But if you already have nougat 7.0 B380 you can just begin at the boot.img installing step and it should work for you too.
Good luck!

Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The difference is that the TWRP that I linked can flash .img 's
wich you need to flash the boot.img
Try to get back in TWRP and start at step 1 just do the whole guide then your phone should boot again

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Q: Why does booting take so long?
A: Because of the decryption process which need to finish
its work before twrp tries to access /data partition.
Click to expand...
Click to collapse
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
You are right it is for P9 but it worked for me regardless though :fingers-crossed:

david320te said:
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
Click to expand...
Click to collapse
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot bootloader),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.

N01tra said:
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot fastboot),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
Click to expand...
Click to collapse
I had the same as you describe here but I fixed it by flashing the 2 files I posted up here (a and b)

After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/

david320te said:
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
Click to expand...
Click to collapse
I'm glad to hear it works! :highfive:
TWRP backups never worked for me I always just flash it clean and then have titanium backup do the rest
Have a nice day

Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.

fourcc said:
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
Click to expand...
Click to collapse
Hey,
Your question is not stupid I can see why you are confused but everytime I tried to root or preroot something it didn't work for me I also run 380 and once I tried the prerooted 378 made by atariii it worked so there is no reason te be skeptical because I was in the same situation as you and this worked for me just give it a try you won't be disappointed

Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!

fourcc said:
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
Click to expand...
Click to collapse
Tell me how it went !
Goodluck!

Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!

fourcc said:
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
Click to expand...
Click to collapse
that's fine too I'm glad it worked good for you!
Have a nice day!

[Guide]How to update from B380 or B381 to B389, B394, B399, B401, B402 and root

This guide is for update within versions if you are rooted, if not, simply download and install de ota or with FF.
If you update to B394 from any version, downloading the last complete packet in update system, it locks the bootloader !!! be advised
If you update to B399 or B401, B402 from B394, downloading the last complete packet in update system, DO NOT LOCK the bootloader !!! good news
My first problem was when I was in B380 and rooted , the b389 ota arrived...then I unroot, put stock recovery and unistalled busybox, but ota failed at 8%
The solution to this :
1 - flash stock recovery from version you have
2 - download the last complete packet in update system , for me 2.41 Gb, not the ota
3 - (optional but useful for future) connect to pc and copy the 3 files downloaded the update in HWOUC to pc
4 - make the normal update in update system
7 - copy supersu 2.82.zip original file or Magisk to SD
8 - Flash last twrp recovery twrp-3.1.1-1-frd , enter in twrp recovery and:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
10 - Make a backup of boot (for future) if you want
11- flash supersu 2.82 original or Magisk
12 - reboot and it's done!!!!!!!!
Update to B394
if you have done all the process and you want now to update to b394, you can uninstall first supersu within options menu saying yes to all questions when uninstalling and without errors or bad uninstallation; then, delete binaries of busybox, flash stock recovery and try to install ota...for me the ota not installed and done with errors.
Then I installed b394 full and locked my bootloader, forcing me to format all because i unlocked the bootloader (remember to activate oem bootloader unlock on and usb depuration on).
After installing the same twrp recovery, I tested the magisk v14 and works perfect, but with an inconvenient, you have to disable the option of magisk manager "magisk hide" to work with fingerprint ,At version 15.3 I didn't see this error.
B394 to B399
Tried the uninstaller of magisk flashed with twrp to unroot and then put the stock recovery and failed, then I flashed stock boot and failed ....finally it worked downloading the last complete packet in update system.Then the habitual, flash twrp recovery, magisk v15.3 from twrp and magisk manager v5.5 in android...and worked perfect
B399 to B401
This time I only unistalled binaries from busybox and flashed stock recovery; then launched Full update (2.41 Gb) without problems.Then flashed twrp, magisk 15.3 from twrp as usual and nothing more...magisk manager detected all ok and I have a rooted device again.
B401 to B402
Simplified the process, now only flash the stock recovery 401 and make the full update packet (2.41Gb). Then flash twrp, enter in twrp, flash magisk 16.0, reboot and that's all. Install busybox script, adaway hosts and done.
Notes:
1 - If the system downloaded automatically the small ota update. you must to try to update with an obvious error, then you can download the full update packet.
1 - the installation of magisk is simple, in twrp flash the magisk.zip , reboot and install magisk manager to control all. This is another app to root and don't need supersu. The advantages to make this is magisk hide, it permits to work with apps that can't work if your phone is rooted.

Wow awsome guide. Thanks alot bro .+1

gopinaidu77 said:
Wow awsome guide. Thanks alot bro .+1
Click to expand...
Click to collapse
happy to help!

9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option

warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
in the options of the twrp, last tab , there's a thick that says this

deadko said:
in the options of the twrp, last tab , there's a thick that says this
Click to expand...
Click to collapse
Bro , y u should mount vendor?

warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
gopinaidu77 said:
Bro , y u should mount vendor?
Click to expand...
Click to collapse
to root correctly with supersu original version

deadko said:
to root correctly with supersu original version
Click to expand...
Click to collapse
But i dont think modifying vendor part is good .

gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
I didn't say nothing to modify nothing, I said thick this option on, and in my case, I did nothing because is marked by default.

deadko said:
I did nothing to modify nothing, I said thick this option on, and in my case, I do nothing because is marked by default.
Click to expand...
Click to collapse
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part

gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
gopinaidu77 said:
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
Click to expand...
Click to collapse
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works

deadko said:
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
Click to expand...
Click to collapse
Ok , thanks though

On point 4 - download complete package - but where? On update app there offer only ota update package not full.

Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
at the tab up to the right in update system

Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
Click on 3 dots on the top right corner . U will see the option.

deadko said:
4 - download the last complete packet in update system , for me 2.41 Gb, not the ota
Click to expand...
Click to collapse
My option is greyed out, what should i do?

Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
fabh2o said:
My option is greyed out, what should i do?
Click to expand...
Click to collapse
the ota is avaliable for you?

deadko said:
the ota is avaliable for you?
Click to expand...
Click to collapse
Yes i'm downloading it right now
Edit: i'm downloading the 2,41 gb update, thanks for the support.

I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.

Snowjack said:
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Click to expand...
Click to collapse
very large process, but you make a hard reset, and my process is to preserve data and use original supersu not the modified , thanks for info

[Solved] Can´t update from version 5.1.2 to version 5.1.4 OnePlus5

So i tried to install the update for my OnePlus5 but TWRP gives ERROR 7 i also tried to wipe my data (including system),
i also tried to install the update with the stock recovery (without root) and the update just fails
oxygen updater won´t work aswell
thanks in advance
i´ve trieded newer versions of oxygen os too
sry for my bad english i am german

Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.

Alexandre-P said:
Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.
Click to expand...
Click to collapse
i used the OTA before but i will try the OTA you suggested
thanks in advanced:good:
Edit: can i theoretically use a newer version than 5.1.4?

Fredwuz said:
Edit: can i theoretically use a newer version than 5.1.4?
Click to expand...
Click to collapse
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.

Alexandre-P said:
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.
Click to expand...
Click to collapse
so i flashed version 5.1.3 and it did work but when i tried to flash to version 5.1.4 TWRP was stuck in "Patching system image unconditionally..." did i do something wrong?
After i flashed to 5.1.3 the devices worked normal as always

Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.

Alexandre-P said:
Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.
Click to expand...
Click to collapse
now the updater says my system is up-to-date but i only have 5.1.3 installed

Fredwuz said:
now the updater says my system is up-to-date but i only have 5.1.3 installed
Click to expand...
Click to collapse
Reboot, wait some time.

What is sometime are about 5 hours enough?
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
What is sometime are about 5 hours enough?
Click to expand...
Click to collapse
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.

strongst said:
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.
Click to expand...
Click to collapse
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Edit: I have to use version 5.1.4 or?
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Click to expand...
Click to collapse
Yes you can, that's what I suggested already

My experience with the 5.1.4 update - ERROR 7 & Treble error fix
Hi, I have 3 OnePlus 5's in my household and I have gotten them all to update to 5.1.4, then 5.1.5, then 5.1.6+ with this method.
(5.1.4 and then 5.1.5 is needed before flashing 5.1.6 or greater).
In my experience, no matter what caches I cleared or what recoveries I had used, 5.1.4 was not flashable on all three devices with the bootloader unlocked. If you have the patience and time, this method should 99.99% work for you if done correctly (leaving a 0.01% chance of failure just in case it does fail lol but that shouldn't happen.)
1.) Firstly, back up your device. I suggest doing this by making a full titanium backup, and copying all the files on the internal storage to a folder on your computer.
This may take a while to copy. In my experience, the fastest way to copy all the data off to the computer is to boot the device into TWRP recovery, plug a good USB C cable in to the device and to the PC's USB port, unlock the device in TWRP (put in the password/pattern to decrypt and mount the data partition [Ignorable if you dont set a password on the device]), and use the adb pull command to pull the files off the device. I found that ADB pull works much faster than an mtp file transfer in windows explorer.
Steps for ADB pull:
Ensure adb is installed on the computer with adb drivers. For Windows, open command prompt or powershell as admin. Type in adb devices and hit enter. If your OnePlus device comes up, then all is good. Use the command (without the square brackets):
[ adb pull /sdcard "XXX/." ]
Replace XXX with a directory on your computer (for example, you can do [ adb pull /sdcard "C:\Users\YOURUSERNAME\Desktop\OnePlus/." ]
If anyone notices any issues with this command please let me know so I can update the post. I am writing this off memory, so there may be minor mistakes.
2.) After your device backs up and you're happy with the backup (i.e. everything you need backed-up is saved off of the phone onto the computer), It's time to relock the bootloader and restore the firmware on the phone.
I haven't tried a simple fastboot OEM relock command, so I cannot say whether that is sufficient enough.
What I did was follow this thread:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Download the Driver and the Oxygen version.
Once downloaded, extract the driver Driver_OnePlus5.zip file to its own folder. Extract the firmware to its own folder (cheeseburger_23_O.13_170803).
3.) Using the firmware restoring tool to relock the bootloader and restore the device to factory firmware condition.
Now:
Turn off your OnePlus 5 device.
Hold volume up key.
Plug USB cable in to the PC and the Type-C side to the device. Make sure only volume up is held whilst you do this.
Open device manager and check for missing drivers/driver issues. If the driver isn't detected, use device manager to browse for the extracted Driver_OnePlus5 folder you made earlier.
The LED light on the OnePlus 5 should be yellow if I can remember correctly.
Open msm download tool as an adminstrator (right click, run as administrator)
Click the start button on the top left of the msm download tool. (If nothing happens, make sure drivers are installed properly and that the device is in download mode [Repeat the above steps])
If successful, one of the "Device Type" should show your device connected {com device} and the download process and time row will update. Wait for the download progress to finish. The device will reboot on its own when completed. The status should turn green and say done/finished (If I remember correctly).
When your device reboots, do a quick setup. Don't bother putting your google account in or restoring anything if you plan on unlocking the bootloader later for TWRP or other reasons.
Unlocking the bootloader will wipe the phone. For now, just focus on the updates.
Connect the device to Wi-Fi. I found one of the devices I used this method on wouldn't connect to Wi-Fi (modem issue or something). Luckily, I had the 5.1.4 update already downloaded on the computer so I copied the update to the root folder on the device and used the local upgrade option in the OTA update options (in the phone system update settings). Updating the firmware fixed my Wi-Fi issue.
Basically, just do the OTA updates as you would normally. Start with 5.1.4, then you can do the 5.1.5. Do not jump to 5.1.7 because OnePlus only just added treble support in 5.14/5.15 releases so it is important do do those in order first. If you can, do 5.1.4, 5.1.5, 5.1.6 and then 5.1.7 in order. Just follow the updates that the OTA screen allows you to take.
Notes for the Pie update:
I haven't had issues installing Pie with the bootloader unlocked, so if you wish to stay on oreo for now and update later with an unlocked bootloader, that should be fine.
If your bootloader is locked, and you're on at least OOS 5.1.5, you should be able to flash the Pie OTA with the stock recovery without issues.
If you encounter issues installing Pie, and your bootloader is unlocked follow this:​
Unlocked bootloader - Pie Update - Removing compatibility.zip from firmware archive:​
Method 1: Pre-Removed compatibility.zip modified firmwares:
For STABLE:​Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Download " OxygenOS 9.0.0 Full Zip (modified, without compatibility.zip) ".
For BETA:​Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Download " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
Copy the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) " to the device.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
Wipe dalvik-cache and cache.
Enjoy Pie.
Method 2: Manual Method to remove compatibility.zip for unlocked bootloaders:
Download the FULL firmware OTA (from device settings, or from the OnePlus website).
Copy the firmware to the computer (If downloaded on the device, it will be in the ".ota" folder. Else, it is available on the OnePlus firmware downloads page.
Open the firmware archive with 7-Zip.
Delete Compatibility.zip from the archive.
Copy the now-modified firmware back to the device.
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash your manually-modified OTA/firmware archive in TWRP.
Wipe dalvik-cache and cache.
Enjoy Pie.
DO NOT use winrar or any other non-recommended programs to remove compatibility.zip. I found that winrar causes treble errors or error 7.
4.) Re-unlocking the bootloader & Restoring your data.
Once you've installed 5.1.5 or greater, you can now safely go into developer settings and enable oem unlocking, and then reboot to the bootloader to unlock the bootloader (which will wipe/erase the phone data but keep the version to whatever you updated it to). You may then proceed to install TWRP, magisk if you plan on restoring with titaniumbackup, and restore all your sd card contents (or the sd card contents that you need) back from the computer backup the the device (I usually use ADB Push whilst booted in TWRP recovery because it copies quicker than MTP).
Updates should work from now on ( I was able to install android PIE Beta with the bootloader unlocked [See the Pie notes above]. Only had issues with the 5.14 / 5.15 updates with the bootloader unlocked ).
Hope this helps. If anyone has any more information, or questions about this method, do share. Like I said earlier, if done correctly, this method should definitely work for you guys.

Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Glad you got it working! Happy new year to you as well

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