Database Users

No sim card detected on custom roms

I have a XT1572 (Indian variant dual sim) . The sim card works good on both 6.0 & 7.0 (official roms) however remains undetected on any custom rom . Any guidance would be of great help .

Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.

Tried but no success
jason2678 said:
Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.
Click to expand...
Click to collapse
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .

Anyone ?
Sir2taj said:
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .
Click to expand...
Click to collapse
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .

Sir2taj said:
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .
Click to expand...
Click to collapse
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'

antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .

Sir2taj said:
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .
Click to expand...
Click to collapse
@antariksh pls help

Sir2taj said:
@antariksh pls help
Click to expand...
Click to collapse
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?

antariksh said:
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?
Click to expand...
Click to collapse
Very very strange because I do recall that all these custom ROMs used to run fine without any such stupid issues back in October last year . its really disheartening. Yes I am using nougat firmwares for nougat modem compatible ROMs and mm firmware for rhe mm compatible one's . Its just that be it any custom ROM this thing won't work at all ! Is it anyhow related to recovering phone from brick state because I do remember that I had to flash the bootloader on a memory card in order to get the device up ?
Appreciate your efforts brother.

i have similar problem

antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?

Sir2taj said:
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?
Click to expand...
Click to collapse
Yep. It is normal. TWRP was probably based out on XT1575. But it doesn't matter.
Only modems differ between XT1575 and XT1572.

Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.

parker.stephens said:
Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.
Click to expand...
Click to collapse
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.

Sir2taj said:
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.
Click to expand...
Click to collapse
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."

parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Will give it a try

parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Iam gettign error 6 . Pls share the edited updater script for bootloader - A0.52

I've got exactly the same issue.... Sim not detected on Nougat, can't boot Marshmallow roms.
Someone found a fix to this?

Perhaps I'm not the only one having the issue of no sim

Sir2taj said:
Perhaps I'm not the only one having the issue of no sim
Click to expand...
Click to collapse
i have the same issue my friend and i dont know what to do.

[mini-GUIDE] BRICKED / DOWNGRADE / SAME / UPGRADE - also ALTERNATIVE to RSDlite

I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.

I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.

You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.

echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!

KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?

echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????

echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.

KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.

echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.

I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?

Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!

KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead

Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...

KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD

Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.

Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)

KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.

Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.

So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.

Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...

can not found file flash_all_lock.bat error

Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were _Flash_lock.bat, _Flash_.bat, _Flash_erase_userdata_lock.bat and _Flash_erase_userdata_lock.bat files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks

finxminx said:
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were “_Flash_lock.bat”, “_Flash_.bat”, “_Flash_erase_userdata_lock.bat” and “_Flash_erase_userdata_lock.bat” files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
Click to expand...
Click to collapse
what about deleting those underscores before each word, i think they shouldn't be there.

kuartito said:
what about deleting those underscores before each word, i think they shouldn't be there.
Click to expand...
Click to collapse
I tried but no success. Maybe I'm doing wrong to use mi flash tool. Maybe I should just try to use bat files through fastboot, I don't know. I haven't found any information on the forum or google if I can do it like that.

finxminx said:
I tried but no success. Maybe I'm doing wrong to use mi flash tool. Maybe I should just try to use bat files through fastboot, I don't know. I haven't found any information on the forum or google if I can do it like that.
Click to expand...
Click to collapse
i'm by no means an expert and my advice has no value at all, but i don't see why you wouldn't give flashing from fastboot a try.

1: Those firmware are not meant for miflash, flash using twrp
2: Don't use the script that locks if you wanna avoid trouble.

What directory did you select in miflash?

JakobSWE said:
1: Those firmware are not meant for miflash, flash using twrp
2: Don't use the script that locks if you wanna avoid trouble.
Click to expand...
Click to collapse
I downloaded 3 copies of 10.0.3.0 firmware from different places and each one claimed those firmwares were for fastboot, not twrp. I attached the folder's screenshot.

henk_j said:
What directory did you select in miflash?
Click to expand...
Click to collapse
I attached the screenshot of the directory.

finxminx said:
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were _Flash_lock.bat, _Flash_.bat, _Flash_erase_userdata_lock.bat and _Flash_erase_userdata_lock.bat files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
Click to expand...
Click to collapse
flash this official pie rom
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz

...

Stuck in Loading Screen after Update Magisk
I have the same problem here,, This morning i got nontification from Magisk to update to the new version,, and update done, Magisk start reboot,,, when reboot,, i always stuck on Loading Screen. I check from TWRP my Internal Storage cannot detect by Pc,, So i think i cannot doing Flashing by TWRP,, I'm wipe out all data to clear this mess,, so i start to do a flashing with MIFlash, i'm download the custom rom and start flashing.. and i got this message "cannot found file flash_all_lock.bat"
Sorry for my Bad english.. cus i'm still young

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

Want to upgrade my OP5 from Oxygen 4.5.10 , Android 7.1.1 to the newest..

Hello
As the titel says..
Its been a few years since ive done anything like this, so dont really know what i need to do now..
Ive flashes newest twrp-3.2.3-0-20180822 and tryed to install OnePlus5Oxygen_23_OTA_052_all_1910082005_adf7221fba833a0.zip but witout any luck
Log in twrp says:
Installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_052_all_1910082005_adf7221fba833a0.zip'
Checking for digest files
Skipping digest check: no digest file found
vendor partition is not existed, exit ota!!
Updater process ended with Error: 7
Error installing zip file
I have no idea if its even possible to do this if i need other updates first ect.
Kinda rookies now haha..
Iv'e searched forum for help dunno if ive searched wrong or not, but couldnt find any help.

You have to install version 5.1.4 based on Oreo 8.1.0 and boot up the phone to enable vendor partition. Then you will be able to flash the latest Pie OS. If you want a faster way, you can use the 9.0.9 EDL package, but you will lose all data

Well i had a friend that said i could just install 9.0.9 firmware, well now ive ended up witj a phone which i cant enter.. Can still open fastmode and twrp but i cant add files on phone.. Any ideas on how to fix this mess?

mummilana said:
Well i had a friend that said i could just install 9.0.9 firmware, well now ive ended up witj a phone which i cant enter.. Can still open fastmode and twrp but i cant add files on phone.. Any ideas on how to fix this mess?
Click to expand...
Click to collapse
Use this EDL guide https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706

PierreVicquery02 said:
Use this EDL guide https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
thanks i will try

PierreVicquery02 said:
You have to install version 5.1.4 based on Oreo 8.1.0 and boot up the phone to enable vendor partition. Then you will be able to flash the latest Pie OS. If you want a faster way, you can use the 9.0.9 EDL package, but you will lose all data
Click to expand...
Click to collapse
So they changed the partition layout with Oreo? I am asking because I currently have the exact same problem.
Currently stucking on 7.1.1 with the same errormessage. I will try to upgrade to Oreo first and then move over to Pie. Thanks.

GoodSoul said:
So they changed the partition layout with Oreo? I am asking because I currently have the exact same problem.
Currently stucking on 7.1.1 with the same errormessage. I will try to upgrade to Oreo first and then move over to Pie. Thanks.
Click to expand...
Click to collapse
Yes, with the version 5.1.5 Project Treble was adopted and it requires a new vendor partition. That partition was created with 5.1.4, so if you are on a version lower than 5.1.4 you will need to install that version, boot once (the repartitioning is made during Android boot, not during the install) and then you will be able to upgrade to latest Pie version.
If you want to upgrade in one step, you can use EDL tool, but you lose all your data. Anyway, I advice you to do so because a format is a good operation when upgrading the Android version

PierreVicquery02 said:
[...]That partition was created with 5.1.4, so if you are on a version lower than 5.1.4 you will need to install that version, boot once (the repartitioning is made during Android boot, not during the install) and then you will be able to upgrade to latest Pie version.[...]
Click to expand...
Click to collapse
I assume I can then also move directly to 9.0.xx, right? Sorry, I forgot that the OP5 got Android 10!

GoodSoul said:
I assume I can then also move directly to 9.0.xx, right? Sorry, I forgot that the OP5 got Android 10!
Click to expand...
Click to collapse
You can install the latest ROM ONLY if you are on a version that is 5.1.4 or newer. If you are on an older version, you have to first upgrade to 5.1.4 and then the newer version (Android 10 will be out in the next months)

Feedback: Works great. Moved to that version, rebooted once, upgraded directly to latest OOS (9.xx whatev) with success. Thanks for all your support & comments!

GoodSoul said:
Feedback: Works great. Moved to that version, rebooted once, upgraded directly to latest OOS (9.xx whatev) with success. Thanks for all your support & comments!
Click to expand...
Click to collapse
You're welcome!