Related
Hi everyone, im new to XDA. But that's kinda beside the point.
I have a Redmi Note 3 with Snapdragon 650 and 2gb ram 16gb storage. I wanted to install lineage os/R.remix because im kinda bored of miui and wanted nougat. I did the following steps to install.
1. Unlocked bootloader via no-permission or hack method.
2. Installed TWRP latest as of 10-6-2017 thru Fastboot.
3. Wiped cache,dalvik and data
4. Flashed R.Remix nightly 10-6-17 and then Gapps.
In this step, I had a problem. It was giving me error:7 (xiaomi.verify.modem) and so I modded the rom (updater-script) and worked. It had the animation loop soflashed NON-HLOS modem binary thru Fastboot and flashed the original signed ROM. But, the problem persists. It's stuck in the boot animation and looping infinitely. I left it for 30min-1hr and still loops. What do I do now? Please help me in this regard. Till then, MIUI again
bro you forgot to flash lazy flasher at first boot in rom after installing twrp.
dean [email protected]# said:
bro you forgot to flash lazy flasher at first boot in rom after installing twrp.
Click to expand...
Click to collapse
There's no need of lazyflasher on a custom Rom!
Do you want to know something else about what I did to solve the problem? Although I rolled back to miui bcos I needed my phone:good:
U need to update ur firmware. Download it from below link & follow the below steps.
https://www.androidfilehost.com/?fid=817550096634767927
Wipe system, Data, cache, Dalvik cache
Install above firmware
Install Custom Rom of ur choice
Enjoy
Let me know if it doesn't works
ExtGame said:
Hi everyone, im new to XDA. But that's kinda beside the point.
I have a Redmi Note 3 with Snapdragon 650 and 2gb ram 16gb storage. I wanted to install lineage os/R.remix because im kinda bored of miui and wanted nougat. I did the following steps to install.
1. Unlocked bootloader via no-permission or hack method.
2. Installed TWRP latest as of 10-6-2017 thru Fastboot.
3. Wiped cache,dalvik and data
4. Flashed R.Remix nightly 10-6-17 and then Gapps.
In this step, I had a problem. It was giving me error:7 (xiaomi.verify.modem) and so I modded the rom (updater-script) and worked. It had the animation loop soflashed NON-HLOS modem binary thru Fastboot and flashed the original signed ROM. But, the problem persists. It's stuck in the boot animation and looping infinitely. I left it for 30min-1hr and still loops. What do I do now? Please help me in this regard. Till then, MIUI again
Click to expand...
Click to collapse
Don't flash that miui firmware from post above, it will relock your bootloader because you are not officially unlocked.
Best way to go is to flash latest global dev fastboot rom, unlock officially. This way you will have no problems with flashing nougat custom roms.
So, should I install the latest global developer rom? I checked yesterday it was v7.6.7 while latest global stable was 8.2.4 which I have currently installed. I also checked via fastboot OEM device-info and, yeah, bootloader locked.:crying: So, I should install the dev. Rom and ask for permission and then unlock, like, the official way? I'm waiting for the reply. Make it clear and I'll try it. Thnx.
Edit : I also somehow got TWRP uninstalled:crying::crying: I don't know if this unexpected or was doomed to happen but yeah, again, just saying.
I just asked for permissions to unlock and..... Surprise!!! I got the permission in 5 minutes!!!
I feel kinda sad for the people who are waiting for more than 21 days...
Capt. John Yossarian said:
Don't flash that miui firmware from post above, it will relock your bootloader because you are not officially unlocked.
Best way to go is to flash latest global dev fastboot rom, unlock officially. This way you will have no problems with flashing nougat custom roms.
Click to expand...
Click to collapse
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to me
ExtGame said:
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to me
Click to expand...
Click to collapse
Good luck.
https://www.digitbin.com/unlock-bootloader-xiaomi/
https://www.howtogeek.com/240047/how-to-flash-twrp-recovery-on-your-android-phone/
https://forum.xda-developers.com/showthread.php?t=2317790
OMG OMG OMG IM TRIGGERED WHAT IS THIS??????!!!!!!!!!!!!!!
*calms down*
This MI Flash gets stuck at 99% even tho I got permissions (an SMS from MI) and shows current account not bound to device. What do I do? I also tried binding my account to phone by settings-->dev. options-->mi unlock which gave code 86012 and some Chinese characters which I honestly can't understand. I also tried installing global dev and doing the same thing but gives same 86012 and Chinese. Plzz help me in this regard. Would be greatly appreciated. Thanks.
Actually, nvm. I got lineage is installed and running on my phone by following a guide on how to install twrp without unlocking bootloader. Worked like a charm for me. I'm typing this now on lineage:silly: Anyways, thanks for the effort. Thread closed.
You could've just waited for 7 days and you would've unlocked your bootloader officially
how did it go buddy ?
ExtGame said:
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to medid you falsh the custom rom , does it work cause i get stuck on bootanimation too
Click to expand...
Click to collapse
I am using it thru locked bootloader mrthod
ExtGame said:
OMG OMG OMG IM TRIGGERED WHAT IS THIS??????!!!!!!!!!!!!!!
*calms down*
This MI Flash gets stuck at 99% even tho I got permissions (an SMS from MI) and shows current account not bound to device. What do I do? I also tried binding my account to phone by settings-->dev. options-->mi unlock which gave code 86012 and some Chinese characters which I honestly can't understand. I also tried installing global dev and doing the same thing but gives same 86012 and Chinese. Plzz help me in this regard. Would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Same here please help
You can follow the tutorial on how to install lineage os with locked bootloader on redmi note 3. Works like a charm, i am using lineage os 14.1 with locked b.loader!!:good:
recommend you to wait for 5-7 days and unlock it officially...
So that you would never face problems in future.
Hi!
I have a big problem to return to stock after trying the Elemental v. 1.1.
I have tried the full backup from here: https://forum.xda-developers.com/ma...other-development/oeminfo-collection-t3762385 but it says that it is rooted when I boot it.
I then tried: https://forum.xda-developers.com/ma...evelopment/stock-rom-rne-l21c185b142-t3764065 (I know it is the wrong localization, but I was desperate, sorry ) and this actually booted with no problem, no notice of being rooted BUT now I faced that the unit had been turned into a NEO-L21.
I thought that I could fix that with the first links change of OEM, but it would not work...what am I doing wrong?
And does anyone have a backup without root, or a way to fix it using the newly published Full-OTA that have started to come for our device?
Thanks in beforehand!
davurleon said:
Hi!
I have a big problem to return to stock after trying the Elemental v. 1.1.
I have tried the full backup from here: https://forum.xda-developers.com/ma...other-development/oeminfo-collection-t3762385 but it says that it is rooted when I boot it.
I then tried: https://forum.xda-developers.com/ma...evelopment/stock-rom-rne-l21c185b142-t3764065 (I know it is the wrong localization, but I was desperate, sorry ) and this actually booted with no problem, no notice of being rooted BUT now I faced that the unit had been turned into a NEO-L21.
I thought that I could fix that with the first links change of OEM, but it would not work...what am I doing wrong?
And does anyone have a backup without root, or a way to fix it using the newly published Full-OTA that have started to come for our device?
Thanks in beforehand!
Click to expand...
Click to collapse
to remove the NEO-L21 phone settings.
you should restore the boot backup only.
Backup BOOT RNE-L21C432B133 clean
** https://mega.nz/#F!s4s1WKIQ!kDwYTMP9YmGan1thThXRfA
and restart.
boot
Chisetdel31260 said:
to remove the NEO-L21 phone settings.
you should restore the boot backup only.
Backup BOOT RNE-L21C432B133 clean
** https://mega.nz/#F!s4s1WKIQ!kDwYTMP9YmGan1thThXRfA
and restart.
Click to expand...
Click to collapse
I don't know what goes wrong, but it does not boot with this boot partition. Could it be because the NEO-L21 backup I restored is Android 6.0?
davurleon said:
I don't know what goes wrong, but it does not boot with this boot partition. Could it be because the NEO-L21 backup I restored is Android 6.0?
Click to expand...
Click to collapse
It's not Android 6.0. The info in "About Phone" is just wrong. You are on android 7.0. I would recommend you to do what I have done for myself.
https://forum.xda-developers.com/ma...pilation-firmware-flasheables-huawei-t3761483
Follow the instruction in this topic which is:
(Remember to get the unlock code for bootloader before you flash anything !!)
1.Flash the OEM info from cust432 or whatever cust you want.
2.Unlock the bootloader and flash TWRP
3.Flash the firmware proper for your cust from the above topic and everything should work. I did this for my phone that was cust c738 before and it works like a charm now and I am on cust432. The only thing for me is that I can't do an OTA update to B133. I am on full stock without root, but I have unlocked BL. I tried to relock it to see if it changes anything but then my phone is stuck on bootloop.
So since I'm here can anyone tell me...Do I have to be on locked BL in order to perform an OTA update ?
If yes how do i relock it ? Because if i do "fastboot oem relock code" then my phone is stuck on bootloop....
We can't back to stock rom, since huawei not release online, we can go to customer service thay said.
Hey Guys,
what do you think is the best costum rom (stable) for the Mate 10 pro?
Is it possible to flash it with Pie 9.0.161?
Thanks for Help :victory:
Just wait for the ota update to pie.
that's definitely a worse rom. i'm on it right now.
wooley4766 said:
Just wait for the ota update to pie.
Click to expand...
Click to collapse
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Pie Update
HauAbDuLauch said:
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Click to expand...
Click to collapse
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
revjamescarver said:
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
Click to expand...
Click to collapse
but no custom
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
93starletgt said:
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
mirandam said:
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
Click to expand...
Click to collapse
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
93starletgt said:
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
Click to expand...
Click to collapse
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
mirandam said:
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
Click to expand...
Click to collapse
Thanks! Last question. If I would like to go back to stock using the All In One Tool, how can I flash stock recovery? And where can I find it? Many thanks for your help.
are there custom roms for the huawei mate 10 pro??
cause cant find it on xda.
mine is stock it works but the no status bar pull down on lockscreen is anoying ;( sometimes and that only the stock sms app show on the always screen on...
Hello, I'm about to buy this phone from tradingshenzen and i have question for you, does anybody successfully rooted this device? I'm planning to unlock bootloader there to install xiaomi.eu and root it, without root it's hard to use device personally for me. Is root possible for today? How long we have to wait to unlock bootloader? 72h or 8days? And when twrp will be available does flashing it delete user data? Thanks for replies
my unlock wait time is 7 days, flashed to EU developer weekly rom and rooted it with magisk patched boot image. did not manage to flash unofficial TWRP though always endup in with recovery_a partition not found. guess that have to wait till official TWRP is out.
dan079 said:
my unlock wait time is 7 days, flashed to EU developer weekly rom and rooted it with magisk patched boot image. did not manage to flash unofficial TWRP though always endup in with recovery_a partition not found. guess that have to wait till official TWRP is out.
Click to expand...
Click to collapse
Thank you for your reply, quite long unlock time, anybody know why Mi does it? (It's still better than no option to unlock bootloader - for me no option to buy that type of device)
Did you used this metod: https://topjohnwu.github.io/Magisk/install.html with patching boot.img?
dan079 said:
my unlock wait time is 7 days, flashed to EU developer weekly rom and rooted it with magisk patched boot image. did not manage to flash unofficial TWRP though always endup in with recovery_a partition not found. guess that have to wait till official TWRP is out.
Click to expand...
Click to collapse
Since the Mi Mix 4 is an A/B-Device, you will never ever find a recovery-partition.
I wanted to report, that if you update your rom, you will loose the Magsik SAR.
Xpatryk89 said:
Thank you for your reply, quite long unlock time, anybody know why Mi does it? (It's still better than no option to unlock bootloader - for me no option to buy that type of device)
Did you used this metod: https://topjohnwu.github.io/Magisk/install.html with patching boot.img?
Click to expand...
Click to collapse
Yes on the boot omg patch. Why Mi implement the wait period, beats me too
SanHelios said:
Since the Mi Mix 4 is an A/B-Device, you will never ever find a recovery-partition.
I wanted to report, that if you update your rom, you will loose the Magsik SAR.
Click to expand...
Click to collapse
Well aware that the device is an A/B, no recovery partition. There is report of user success fully flashing unofficial TWRP using some Chinese tool (yet to find that tool). Maybe that tool flashes the recovery to the inactive boot partition.
I use to use the Mi9 which is an A/B device which I am able to flash TWRP.
Xpatryk89 said:
Hello, I'm about to buy this phone from tradingshenzen and i have question for you, does anybody successfully rooted this device? I'm planning to unlock bootloader there to install xiaomi.eu and root it, without root it's hard to use device personally for me. Is root possible for today? How long we have to wait to unlock bootloader? 72h or 8days? And when twrp will be available does flashing it delete user data? Thanks for replies
Click to expand...
Click to collapse
Don't they offer to ship it with Xiaomi.eu installed on it already?
Yes, they do however you need to pay for it and wait another two weeks (roughly).
Regards'
I bought version with CN system and unlocked, rooted and installed Xiaomi.eu by myself, it's quite easy, i prefered to get phone and start using it earlier even with cn miui
Xpatryk89 said:
I bought version with CN system and unlocked, rooted and installed Xiaomi.eu by myself, it's quite easy, i prefered to get phone and start using it earlier even with cn miui
Click to expand...
Click to collapse
Please can you give me more details with you installed rom on xiaomi mi mix 4
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.