Database Users

wifi stuck off after failed dirty flash

I'm on 6.0 Marshmallow XT1575 and my wifi toggles off on its own
Things I've tried to fix this:
-factory reset
-flash non-hlos.bin modem
-flash boot.img from here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
-restore nandroid backup from before the error
-a wipe then a flash of 6.0 stock from here:
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
-use the return to stock tool from a different post to return to 5.11 from here:
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
I'm on 6.0 Marshmallow with the may security update. I decided to do a dirty flash of 6.0 Marshmallow to get rid hidesu and return my phone to stock. I did the flash and booted my phone, but my lockscreen refused to unlock. Every time I did the right code it would lock again. I factory reset and was able to login, but wifi was stuck off, and sim card was not being recognized. From other posts here, I flashed modem and now my sim card access was restored, but wifi is still broken. I've since tried everything on the list above, but nothing brings back wifi. Any ideas?
Also, not sure if this is normal, but on my phone info I see the Wi-Fi MAC address as
02:00:00:00:00:00
which does not seem right to me
EDIT:
Honestly did not expect it to work, but I flashed a custom ROM, TruPureXMM 2.9, and now my wifi is back. I think I'll stick with it for a while.

The problem was with custom kernel you probably installed. I had the same problem with it.

WiFI doesnt work Show 02:00:00:00:00:00 mac address.

Hello to everybody, the wifi phone of my OP5 woked very well. One day I flashed one ROM, I dont remember what and broked the wifi, now show the typical broken mac address, I saw all the post even fixing nexus wifi phone but didnt work. I lnow that I need to upgrade to Oreo, now Im in Nougat, but the problem is when I flash the oreo stock rom the phone get a bootloop, I tryied everything so I need to forget upgrade. How can resolve this problem. I updated no stock ROM oreo like aiscp but the wifi not repair. I dont know what do. I tried with QPST QXSM but nothing I can repair my phone. Any help?. I tried too modificating all the files about wifi, wifi.bin (I dont remember the names) and didnt worked

If you are using TWRP make sure to update to latest codeworks version and in the wipe section select format data. This is necessary when moving from Nougat to Oreo on the OP5 if you are using a custom recovery. That will erase everything on your phone except TWRP. Plug your phone into a computer and it will show up like a USB drive. Copy and paste the Oreo ROM zip for stock OOS onto your phone. If you want to be rooted also copy the latest Magisk zip. Flash OOS zip within TWRP. If you boot into the system after that you will be 100% stock including recovery. If you want to be rooted and keep TWRP flash Magisk zip as well before booting into system. Given your circumstance I would highly recommend going 100% stock and making sure everything is working right again. You can always install TWRP and root again later.

i remember how i flashed blu spark kernel for custom rom, when i was at stock oos and get this broken wifi. try to look at that

jhs39 said:
If you are using TWRP make sure to update to latest codeworks version and in the wipe section select format data. This is necessary when moving from Nougat to Oreo on the OP5 if you are using a custom recovery. That will erase everything on your phone except TWRP. Plug your phone into a computer and it will show up like a USB drive. Copy and paste the Oreo ROM zip for stock OOS onto your phone. If you want to be rooted also copy the latest Magisk zip. Flash OOS zip within TWRP. If you boot into the system after that you will be 100% stock including recovery. If you want to be rooted and keep TWRP flash Magisk zip as well before booting into system. Given your circumstance I would highly recommend going 100% stock and making sure everything is working right again. You can always install TWRP and root again later.
Click to expand...
Click to collapse
I did it but didnt work

Help with soft brick

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Custom Kernel killed my FP Sensor, Camera, and WiFi modem. Help!

Device: ZB602KL 4gb
I was using the latest Liquid Remix 10.0.6 with the stock darkonah kernel for a wee after having just updated from LR 10.0.5 and Singh 2.7. When I noticed he released a stable update for his kernel to 2.8 I downloaded it and flashed it as normal. Upon booting into LR, the lockscreen no longer responded to my fingerprint. It wasn't even turning the screen on. After inputting my password, I noticed that my wifi wouldn't turn on. And later when I tried the stock gcam, it kept crashing. Cam2API Probe is completely blank.
Things I've done to try and fix this:
1. Rebooted multiple times.
2. Someone suggested wiping /system and /vendor only and dirty flashing the rom. Did that, dirty flashed LR, openGApps(wasn't sure I needed to, did it anyway), and Magisk 19.
3. Clean flashed stock 340, decrypt and magisk19.
4. Flashed fw_only-X00T-WW-16.2017.1902.037.zip. I had previously flashed fwpie050.zip(the one from opendesktop) when updating LR before all this happened.
5. Fully wiped phone including internal storage and flashed the latest HavocOS which I am on right now as I've given up and just need it to work as a phone for the meantime.
Camera seems to be working again on Havoc, though. Fingerprint is still missing from Security settings and WiFi will not turn on.
Any help would be appreciated. Thanks!

I also got bootloop by using magisk 19.0,use magisk 17.1 or 18.1.

How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM

Tianhe said:
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Click to expand...
Click to collapse
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.

defurious said:
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
Click to expand...
Click to collapse
Flash fastboot stock rom it will fix the issue.
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Hit thanks if it helped

Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged

farhanshaikh671 said:
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
Click to expand...
Click to collapse
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.

defurious said:
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
Click to expand...
Click to collapse
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,

akhil850 said:
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
Click to expand...
Click to collapse
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks

defurious said:
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/as...w-to/decrypt-zip-asus-stock-pie-roms-t3923265
Hit thanks if i helped.

Lineage OS 16 in Oneplus 5 - July 2019

Hi,
I bought a oneplus 5 phone because I was told it was going to be easy to install Lineage OS. I have try to install Lineage OS 16 on it for 2 days without success.
The first issue i had was installing twrp. Most of the twrp available did not worked with my phone. After flashing them with fastboot and reboot to recovery I would end up with a black screen and the the blue led turn on.
However I did find two TWPRs that work:
- twrp-3.2.1-1-cheeseburger.img
- twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
There might be other that would work, but this are the ones that I have tested.
After being able to boot to TWRP I try to flash the firmware 9.06 with success. Without reboot I flash lineage without success. I try to reboot and the system did not worked and I never reboot.
After a while I found a OxygenOS 4.5.10 that I hope is the stock rom. I has the following sha256sum: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
That did worked and give me a breath. At least I had a working phone now. However I try to update and it did not worked.
From there I have been strugling with this project to install Lineage OS in my new phone. I know there are guides out there, but most of them did not work or are outated. There ara also threads in this forums, but are to big to try to follow. So I start this one, hopefully you can help me.
It would be great if there is a step by step guide on how to run Lineage OS in this phone.
Best,
Panoramix Druida

panoramix.druida said:
Hi,
I bought a oneplus 5 phone because I was told it was going to be easy to install Lineage OS. I have try to install Lineage OS 16 on it for 2 days without success.
The first issue i had was installing twrp. Most of the twrp available did not worked with my phone. After flashing them with fastboot and reboot to recovery I would end up with a black screen and the the blue led turn on.
However I did find two TWPRs that work:
- twrp-3.2.1-1-cheeseburger.img
- twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
There might be other that would work, but this are the ones that I have tested.
After being able to boot to TWRP I try to flash the firmware 9.06 with success. Without reboot I flash lineage without success. I try to reboot and the system did not worked and I never reboot.
After a while I found a OxygenOS 4.5.10 that I hope is the stock rom. I has the following sha256sum: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
That did worked and give me a breath. At least I had a working phone now. However I try to update and it did not worked.
From there I have been strugling with this project to install Lineage OS in my new phone. I know there are guides out there, but most of them did not work or are outated. There ara also threads in this forums, but are to big to try to follow. So I start this one, hopefully you can help me.
It would be great if there is a step by step guide on how to run Lineage OS in this phone.
Best,
Panoramix Druida
Click to expand...
Click to collapse
Hello, seems that you did not follow the installation instructions within the official LineageOS thread https://forum.xda-developers.com/oneplus-5/development/rom-lineageos-16-0-pie-oneplus-5-t3843064
Your issues are clearly missed or skipped steps.
Please follow the instructions there and if you get stuck, report back with detailed information :good:

Thanks a lot for your quick response. It do have an issue with that guide and it is with point 1:crying::crying:
- Make sure your phone was running OxygenOS 5.1.4 at least once
Click to expand...
Click to collapse
I have OxygenOS 4.5.10 and it does not upgrade to OxygenOS 5.1.4. What happened, is that in my first attempts to get this thing working I brick the phone and loose the stock firmware. Then I found this rom that allow me to use the phone (OxygenOS 5.1.4)
OnePlus5Oxygen_23_OTA_015_all_1708252353_f05918.zip
sha256: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
It make the phone usable, but not upgradable. I doubt is the original, but I found the link on the Oneplus forums. (I can not post links because I am too new here)
After that I search for a ROM that comes with 5.1.4 and was really happy, and try to flash. It did not work, it is like it tries to boot, but never finish booting. I wait at least for 10 minutes. This the file and the sha256 hash:
OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip
sha256 2bb2e21a43572ac4bd2e5d1d30a3fb7562ddec280df3d452d61f58a4a8135f14
So I guess my first step would to find a way to get Oneplus 5.1.4 working. When I first try to upgrade the phone, I upgrade it from OxygenOS and it worked, however then I mess things and brick the phone. I found the rom that allow the phone to work (4.5.10), but for some reason the upgrades do not.
Thank you very much for your time.

panoramix.druida said:
Thanks a lot for your quick response. It do have an issue with that guide and it is with point 1:crying::crying:
I have OxygenOS 4.5.10 and it does not upgrade to OxygenOS 5.1.4. What happened, is that in my first attempts to get this thing working I brick the phone and loose the stock firmware. Then I found this rom that allow me to use the phone (OxygenOS 5.1.4)
OnePlus5Oxygen_23_OTA_015_all_1708252353_f05918.zip
sha256: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
It make the phone usable, but not upgradable. I doubt is the original, but I found the link on the Oneplus forums. (I can not post links because I am too new here)
After that I search for a ROM that comes with 5.1.4 and was really happy, and try to flash. It did not work, it is like it tries to boot, but never finish booting. I wait at least for 10 minutes. This the file and the sha256 hash:
OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip
sha256 2bb2e21a43572ac4bd2e5d1d30a3fb7562ddec280df3d452d61f58a4a8135f14
So I guess my first step would to find a way to get Oneplus 5.1.4 working. When I first try to upgrade the phone, I upgrade it from OxygenOS and it worked, however then I mess things and brick the phone. I found the rom that allow the phone to work (4.5.10), but for some reason the upgrades do not.
Thank you very much for your time.
Click to expand...
Click to collapse
You need to clean flash oxygenOS 5.1.4, then take ota update to 9.0.7 so you have the latest firmware.
Clean flash means that you need to wipe system, data, cache and format internal storage too.
So please backup everything off your device at first!
Everything you need you find here on xda, like the roms https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190

strongst said:
You need to clean flash oxygenOS 5.1.4, then take ota update to 9.0.7 so you have the latest firmware.
Clean flash means that you need to wipe system, data, cache and format internal storage too.
So please backup everything off your device at first!
Everything you need you find here on xda, like the roms https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks, I would try this when I have time later today.

strongst said:
You need to clean flash oxygenOS 5.1.4, then take ota update to 9.0.7 so you have the latest firmware.
Clean flash means that you need to wipe system, data, cache and format internal storage too.
So please backup everything off your device at first!
Everything you need you find here on xda, like the roms https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Finally I had time to work on this. The rom for 5.1.4 is: OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip, that I already tried and never boots . With twrp it seems that the Rom is installed, with the stock recovery the installation never ends. I am going to try with other ROMS. Hopefully one of them would allow updates.
I am going to start with the newest 5.1.7, and if that does not work would keep going down.
Thanks again.

panoramix.druida said:
Finally I had time to work on this. The rom for 5.1.4 is: OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip, that I already tried and never boots . With twrp it seems that the Rom is installed, with the stock recovery the installation never ends. I am going to try with other ROMS. Hopefully one of them would allow updates.
I am going to start with the newest 5.1.7, and if that does not work would keep going down.
Thanks again.
Click to expand...
Click to collapse
5.1.7 did not boot, however I have some progress. I installed 4.5.12, I was previously at 4.5.10, so my android setup security patch levels went from July 2017 to to September 2017. Small step forward.
I have have that hypothesis that it would work with 4.x.x versions and not with 5.x.x versions. Tomorrow I would try to flash the latest 4.x.x and the earliest 5.x.x to see when does this things stop working.

I did the tests and I can flash up to 4.5.15. I tried to flash 5.0 and that did not worked. It flashes correctly, but it never finish booting, I waited up to 10 minutes.
So there is something preventing the phone to use version 5.x.x Should I try upgrading the firmware? Other ideas?

panoramix.druida said:
I did the tests and I can flash up to 4.5.15. I tried to flash 5.0 and that did not worked. It flashes correctly, but it never finish booting, I waited up to 10 minutes.
So there is something preventing the phone to use version 5.x.x Should I try upgrading the firmware? Other ideas?
Click to expand...
Click to collapse
Please give detailed steps what you did including file versions. Otherwise I cannot help further.
Every oxygenOS version has firmware built in, no need to update it seperately.
Follow this:
1 flash this recovery with fastboot like the first time https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
2 boot the new twrp recovery
3 flash magisk 18.1 to make twrp stick
4 FORMAT internal storage(not wipe only) and wipe system and data partition
5 transfer oxygenOS 5.1.4 to the phone and flash it
6 boot oxygenOS 5.1.4 and take ota update to tg and latest OxygenOS(9.0.7 actually.
7 now you're on the latest OxygenOS and firmware version

Thank you very much, now I am with LineageOS