Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu
My LOS Install Guide
- Don't use TWRP 3.4.x. Use 3.3.1-32 (The latest 3.3.1 version.) 3.4.x will give you issues.
Thank you lot. Lineage ist booting =)
Thawu said:
Thank you lot. Lineage ist booting =)
Click to expand...
Click to collapse
I also just noticed you are trying to use a very old version of OOS (which also means old firmware). Why are you using 9.0.13? Perhaps this could be your issue.
I need to update my guide, but 10.3.5, and the latest weekly 9-3 work fine. One warning, I never did get the 10.3.5 fastboot ROM to work on either of my 6Ts. The 10.3.4 Fastboot ROM works fine, then I had to update to 10.3.5 using TWRP.
I asked if anyone else had problems with the 10.3.5 fastboot ROM in the fastboot thread but didnt get any replies...
I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu
Thawu said:
I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu
Click to expand...
Click to collapse
Also if you like themed TWRP @acuicultor and @ morphine1e1 have a really nice creation for OP6/6t here: https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752
It's latest twrp but I've been using it for months without any issues and I flash much more than a regular user. Installed LOS twice and all good.
或许你应该先升级到安卓10 再去安装lineage os 17
Thawu said:
Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu
Click to expand...
Click to collapse
I install it on HTC u11.. but voice call speaker not working and Bluetooth voice speaker not working .
Related
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.
Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis
mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.
Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.
Hello,
I have a big problem. I don't know what to do.
I wanted to make a clean install of OxygenOS 4.5.8 and so i downloaded it, did it on SD card together with Magisk and no_verity_op5.zip (because i read that this decrypt the data).
So i cleand data and installed no_verity_op5.zip via TWRP, but when i wanted to reboot it takes way to long (i waited 30minutes but it stays on boot circle)
After that i booted into TWRP and decided to made a factory reset and to install OxygonOS 4.5.8 in a clean version. But it was not possible anymore!
When i want to install the .zip it says Patching system image unconditionally... and it loads. after the blue is full it says:
writing static_nvbk image...
patching firmware images...
script succeeded: result was [1.000000]
And when i want to boot into system it says no OS installed.
I tried also to flash this rom or even any other custom rom through ADB Sideload but it does not work. Same like above..
What can i do? I do not know what to do
I hope my phone is not bricked.
Thank you for any suggestion.
Go to oneplus 5 official download page, download stock recovery and latest stock firmware and follow instructions on the download page.... But first with TWRP take a backup of all your data because restoring stock firmware will ERASE everything... Don't panic it will works
First off, don't panic! you're not bricked as long as you can reach your bootloader and recovery.
This happened to me as well and luckily the fix is easy!
You probably tried to flash the OxygenOS build from the Oneplus downloads right?
Somehow these won't flash properly through TWRP and you must therefore also flash the Oxygen recovery image listed in the downloads.
Here are some steps that'll fix your problem.
1 - Backup all of your private data from internal storage because flashing OxygenOS will WIPE/ENCRYPT all data on your device.
2 - Go to the Oneplus download center and download both the latest OxygenOS and it's appropriate recovery:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8
3 - Boot into your bootloader and flash the stock recovery you just downloaded. (fastboot flash recovery <recovery>.img)
4 - Boot into the Oxygen recovery and flash OxygenOS.
This should get you up and running again.
Once you get tired of OxygenOS simply reboot back into your bootloader and flash TWRP and any rom of your liking.
In the future if you want to flash OxygenOS from TWRP you have to grab a build from XDA I guess. I'm not entirely sure why flashing from within TWRP won't work with stock OOS but I believe it expects to be flashed from withing the stock recovery.
I'm pretty confident this will solve your problems.
Please backup your data first though, don't want anything to get messed up in there!
Good luck!
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
manuelbvb said:
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
Click to expand...
Click to collapse
It is possible to have both OxygenOS and TWRP for sure!
Only a clean flash from a non-encrypted state in TWRP seems to break stuff. You can use a modified OOS build from the forums.
TWRP can indeed backup your OOS install so that shouldn't be a problem.
The only exception seems to be flashing a clean install of OxygenOS (from Oneplus Download center) through TWRP.
Other than that everything works as expected.
Ok thank you.
So i will follow you instructions and i hope it will work.
And i think so.
And after it i will install TWRP again (because i need the backup tool), i will install magisk. will this work?
So i can use everything as in a custom rom, but cannot make a clean install? So official Oneplus OTA will work with TWRP or not?
Thank you soooo much!
Also, Magisk/root works just fine on OxygenOS.
Once you flashed OOS from the stock recovery and have everything set up simply boot into your bootloader and flash TWRP.
From there you flash Magisk and everything should be fine.
OTA's from Oneplus also install fine through TWRP as long as you go into Magisk and uninstall 'root' first. When OxygenOS tells you there's an update simply remove Magisk as I said above and it'll update fine.
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
manuelbvb said:
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
Click to expand...
Click to collapse
First off! YAY!! glad it worked out!
Be sure to use the TWRP build from the twrp.me website. The one listed on these forums are 'unofficial'. Not saying those are bad, but the official one has a pretty impressive track-record.
After flashing Magisk you are root-enabled so yeah, congrats you are now root! In order to pass safetynet you must enable 'magisk hide' in the magisk manager (the app that should now be installed on your phone).
If you do not have an app called 'magisk manager' then you can download this app from the magisk forums. It should however install itself while flashing the Magisk zip. So assuming you have it installed find the 'magisk hide' service and enable it.
From my experience you sometimes need to reboot in order for it to pass safetynet check.
Glad it all worked out for you!
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
manuelbvb said:
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
Click to expand...
Click to collapse
That's great to hear!
Enjoy and take care!
no os
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
xda___ said:
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
Click to expand...
Click to collapse
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Zocker1304 said:
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Click to expand...
Click to collapse
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
xda___ said:
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
Click to expand...
Click to collapse
Well just flash a different twrp via fastboot flash recovery *path to file*
So I tried updating to Oxygen is 5.0 ran into an install issue, stuck in boot loop. Lucky I had done a Nandroid back up and restore everything. The other night I decided to update to 5.1.1 thinking why not get Android 8.1.0 on my AWESOME phone. Downloaded update, placed in internal storage, booted into TWRP to do a Nandroid back up (due to issues with past update). Back up failed needed to clean drive. So I decided, phone works in Android 7.1.1, why can't what's not broken. Rebooted phone and somehow the update activated. I freaked since last time it failed and not stuck in a loop. This time update was successful but still got stuck in a boot loop. I plugged my phone to my computer and noticed all my files were gone on their install storage, no files / foldersI recognized (e.g. DCIM, DATA, DOWNLOAD, etc). Emailed One Plus and chatted with them. TWRP was gone and was back on stock recovery. Since all was lost I was asked to "Erase All". I did, rebooted and I'm now on 8.1.1 but all my stuff was lost. So I've done since searching and found FlashFire do to a Nandroid backup but need root. So my question is...
Can I re-root my phone without using TWRP but stock recovery and use FlashFire for my back ups? I am not going to flash custom ROM but if I need to flash something, wouldn't stock ROM flash anything on my phone (Magisk)?
If so, can anyone provide me with assistance on re-rooting my phone without TWRP.
Thank you
As far as i know you can't flash anything with stock recovery so you can't root. After flashing the stock os is normal that twrp is been erased by the stock. Just re flash the twrp. I mean, maybe i didn't get the problem, why you can't reflash twrp? If you do that flash twrp codeworx Universal with fastboot in the bootloader, boot in twrp, wipe cache/dalvik, flash magisk 15.3, wipe cache/dalvik, reboot system, update magisk to 16 with the app. I do that way and it worked
Hi
To root your OnePlus 5, you must to follow carefuly the steps below and take your time.
1 - Make a full backup of your data
2 - Unlock the bootloader (Note that'll erase your phone)
3 - Install another recovery : TWRP. This one : https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download
4 - Flash the full rom Oxygen OS 5.1.1 : http://otafsg.h2os.com/patch/amazon...23_OTA_034_all_1804201219_3824995916a49ee.zip
5 - Install magisk : https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
6 - Clear cache / Dalvik
7 - You're all done, reboot the phone
8 - Once your phone has booted up, install magisk manager : https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
Check this tread, that'll help you as well : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
vanzant83 said:
As far as i know you can't flash anything with stock recovery so you can't root. After flashing the stock os is normal that twrp is been erased by the stock. Just re flash the twrp. I mean, maybe i didn't get the problem, why you can't reflash twrp? If you do that flash twrp codeworx Universal with fastboot in the bootloader, boot in twrp, wipe cache/dalvik, flash magisk 15.3, wipe cache/dalvik, reboot system, update magisk to 16 with the app. I do that way and it worked
Click to expand...
Click to collapse
Hello, thanks for the info and yes, I did try flashing Magisk with stock recovery, while waiting for a reply and can confirm installation failed. So if I reflash TWRP, flashing Magisk using TWRP will work. Therefore, do you have instructions (step-by-step) on how to install TWRP. I have downloaded the latest TWRP image from their website (twrp-3.1.1-1 cheeseburger) onto my desktop. Bootloader is already unlocked as I was previously rooted under Android 7.1.
Thank you.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
This is the official guide step by step, scroll down until you find "flashing twrp" if you had already unlocked the bootloader ( you already did that right??? xD). Anyway about the recovery and magisk version. The guys in the 5.1.1 thread advised to flash magisk 15.3 instead the 16 and only after the system reboot to make the upgrade to 16 with magisk app (dunno why). But when i tried to do that the last version of twrp (3.1.1-1) failed the flash. So i flashed the twrp 3.1.1-0-universal and 15.3 magisk. I can confirm this combination work, i can't tell for other combinations.
vanzant83 said:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
This is the official guide step by step, scroll down until you find "flashing twrp" if you had already unlocked the bootloader ( you already did that right??? xD). Anyway about the recovery and magisk version. The guys in the 5.1.1 thread advised to flash magisk 15.3 instead the 16 and only after the system reboot to make the upgrade to 16 with magisk app (dunno why). But when i tried to do that the last version of twrp (3.1.1-1) failed the flash. So i flashed the twrp 3.1.1-0-universal and 15.3 magisk. I can confirm this combination work, i can't tell for other combinations.
Click to expand...
Click to collapse
Hello, I finally got some time to re-root my phone and was reading the instructions you provided and clicked on the download but they are TWRP 3.2.1.x and Magisk 16. Do you have the links for the files you used
Grazie
jmoricone said:
Hello, I finally got some time to re-root my phone and was reading the instructions you provided and clicked on the download but they are TWRP 3.2.1.x and Magisk 16. Do you have the links for the files you used
Grazie
Click to expand...
Click to collapse
Sorry man i typed wrong, the one i meant was 3.2.1-0 Universal codeworkx, the fourth from up to down. About 15.3 magisk i dunno where you can find It, maybe try some google research, otherwise i can send It to you by email, is a little file
Try this link, get the ZIP file from the version you want: https://github.com/topjohnwu/Magisk/releases/
In case you need, this the official section: https://forum.xda-developers.com/apps/magisk
vanzant83 said:
Sorry man i typed wrong, the one i meant was 3.2.1-0 Universal codeworkx, the fourth from up to down. About 15.3 magisk i dunno where you can find It, maybe try some google research, otherwise i can send It to you by email, is a little file
Click to expand...
Click to collapse
Hey there, sorry for the late response..but thank you for the assist..phone is rerooted..all is good..thanks again
I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?
B1lal545 said:
I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?
Click to expand...
Click to collapse
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.
runninghamster said:
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.
Click to expand...
Click to collapse
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?
B1lal545 said:
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?
Click to expand...
Click to collapse
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.
runninghamster said:
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.
Click to expand...
Click to collapse
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.
B1lal545 said:
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.
Click to expand...
Click to collapse
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.
runninghamster said:
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.
Click to expand...
Click to collapse
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?
B1lal545 said:
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?
Click to expand...
Click to collapse
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.
runninghamster said:
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.
Click to expand...
Click to collapse
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.
B1lal545 said:
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.
Click to expand...
Click to collapse
That's correct. Go ahead with the flash, you're welcome for the help
runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
YAAAAAAAAAYYYY!!!
I just installed LOS 16 and everything seems to be working fine.
But the thing is I downloaded and flashed magisk through TWRP, and the installation went fine. When I booted into LOS even the magisk manager was installed.
But when I installed the root verification app from playstore, it said that the device was not rooted. Any advice? Other than that it feels so good to finally be on a custom ROM. Thanks for your help.
I wish you success and happiness from the bottom of my heart.
runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
Nevermind hahahahah. I checked another app. I'm rooted, forgot to grant Superuser permissions the first time.
Again thank you so much and I apologize if I was overbearing or annoying. You really helped me out and made this process much less painful than it could've been.
I was running on OOS 10.3 rooted with Magisk and flashed TWRP.
I tried to install Lineage OS 16 (the last version from the official website), but after sideloading it and the superSU file in TWRP I could only reboot in the Lineage recovery mode. I tried to flash a unofficial version of Lineage 17 but still not working, the Lineage recovery mode just became rainbow colored. Then I tried to do a factory reset and flash an OOS and since then I have no more access to the recovery mode and the only thing I have when I try to access it or when I turn on the phone is the unlocked boot loader message. I can only access the fastboot mode. Sometimes when I turn it on, I also have the Qualcomm Crashdump message, but nor every time.
I read about MSM, but I'm running on mac OS... Any ideas of solutions I can try with mac terminal?
Thanks for your help
lifeisblue said:
I was running on OOS 10.3 rooted with Magisk and flashed TWRP.
I tried to install Lineage OS 16 (the last version from the official website), but after sideloading it and the superSU file in TWRP I could only reboot in the Lineage recovery mode. I tried to flash a unofficial version of Lineage 17 but still not working, the Lineage recovery mode just became rainbow colored. Then I tried to do a factory reset and flash an OOS and since then I have no more access to the recovery mode and the only thing I have when I try to access it or when I turn on the phone is the unlocked boot loader message. I can only access the fastboot mode. Sometimes when I turn it on, I also have the Qualcomm Crashdump message, but nor every time.
I read about MSM, but I'm running on mac OS... Any ideas of solutions I can try with mac terminal?
Thanks for your help
Click to expand...
Click to collapse
Fastboot ROM. It's available in the Guides Section and the Instructions are pretty straightforward. You can Google "OP6T Fastboot ROM". Also, from the looks of it, you didn't flash LOS Correctly.
lifeisblue said:
I was running on OOS 10.3 rooted with Magisk and flashed TWRP.
I tried to install Lineage OS 16 (the last version from the official website), but after sideloading it and the superSU file in TWRP I could only reboot in the Lineage recovery mode.
Click to expand...
Click to collapse
If you had TWRP why sideload LOS? Here's how I flash LOS.
Thank you very much for your advices, I managed to flash OOS back and install successfully Lineage OS 17.1 ! :good:
lifeisblue said:
Thank you very much for your advices, I managed to flash OOS back and install successfully Lineage OS 17.1 ! :good:
Click to expand...
Click to collapse
what did you do different this time to get a working LOS? Did you use the fadtboot ROM?
Hp6t said:
what did you do different this time to get a working LOS? Did you use the fadtboot ROM?
Click to expand...
Click to collapse
I fastbooted the original ROM and installed TWRP back. Then I used TWRP to install LOS from a zip file. Basically I followed OhioYJ's instructions on his comment above.