Related
So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.
Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,
So im trying to root my oneplus 5 and i started off by using Lineage OS but i wasnt too happy with it and i liked Oxygen OS much better so i decided to go back to it and while doing so like an idiot i wiped everything in twrp including the storage with all my ROM files and the phone was bricked and after a long struggle i used the unbrick tool which is called MSM tool which installed oxygen 4.5.8 using some some Qualcomm mode or something and it booted and worked fine but ever since i wasnt able to download the oxygen 5.1.1 update through the phones update section, it reaches 100% and says signature verification failed and goes back to 5%. So i tried downloading the latest Open Beta from the OP site and tried local upgrade which said installation failed so i try installing it locally through the Oxygen Recovery but again Installation failed so i try unlocking the bootloader again and installing it through twrp and it just keeps showing the boot animation forever( i know people say be patient but i waited for 20 mins+). So i decided to use the unbrick tool again and now im stuck on the OOS 4.5.8 unable to update the phone.
I tried to flash the latest oreo through twrp several times and just tried flashing it through so many ways where none worked , even adb sideloading it worked till 47% and said installation failed and everytime this happens i have nothing left to do but use the tool and unbrick it again and this takes so much time as i have to unbrick and then do the first setup and then go to fastboot and unlock the bootloader and do the setup again and transfer the files and then install twrp and flash.
Nothing has worked so far
And now even when i go back to the 4.5.8 stock after unbricking for some reason it just doesnt connect to any wifi , it just says Connecting and then saved and then disabled and repeat, only my mobile data works.
I tried to flash lineage again but got an error 7 with it or something and im back to the stock unbricked state without wifi and all i can do is unlock bootloader and install twrp.
If anybody has any suggestions and can help me please do so immediately. I require my phone urgently and need to fix this fast.
Thank You !
(btw im in India and do local service centres fix such issues?)
Make sure you use newest twrp. And also flash firmware for 5.1.1
Vika__ said:
Make sure you use newest twrp. And also flash firmware for 5.1.1
Click to expand...
Click to collapse
i am using the latest codeworkx twrp 3.2.1 and when should i flash firmware? can you just give the process i should do? stuck at 4.5.8 without wifi with twrp and unlocked bootloader
Wipe everything except internal storage, after that click format data and type "yes" to accept. Then download oos 5.1.0 firmware from here https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/firmware/ and lineageos 15 (or any rom you want now), gapps and move all 3 packages to your phone. Flash firmware first and then reboot to recovery. Then flash rom or gapps and reboot
You have to flash the latest TWRP from twrp.me, then download the latest OxygenOS build. Reboot into TWRP, wipe data, cache, system and flash the latest build, then just go to wipe > format data, type "yes" and reboot
Lol man your OP5 is not bricked, if you can boot on TWRP, you can install all that you want
I advise to Format Data/Storage, Wipe everything and install xXx 10.7 (OOS Custom with a great Aroma installer), choose decrypted, it's better if you want swtich rom in the future AOSP > OOS > AOSP
bro i have same probleme after install any rom custom or official , always stuck on boot logo , any solution ?
no solution??
Its a shame.
7 years unlocking bootloaders, installing CWM or TWRP or Philz recovery, flashing rom after rom, not even one device bricked, and today, i messed up, i hope its not bad.
So the short version of what i did is that i flashed twrp.img trough and older version of twrp and now it wont boot into twrp, it says that it failed to verify the recovery image or something like that, and my laptop wont recognize the cellphone, the cellphone boots into the latest Havoc rom but without Gapps and without root because i did not install it beforehand, when in bootloader mode it just says that it could not recognize the device.
The long version is that i had Resurrection Remix, obviously an unlock bootloader, magisk etc... everything was fine until today that i tried to install Havoc, the installation went well but i found out that ambient display was not working, someone told me that the previous version of Havoc did not had that problem so i tried to flash it but it bootlooped for like 1hr, so i read that the version of TWRP provided by the OP was the way to get it to work, i downloaded the .img file and flashed it trough TWRP and tried to install Havoc again but i was stuck in a bootloop, so i flashed the latest Havoc build so i could download the latest version of twrp, i did not flash Gapps or Magisk because i was going to re flash the rom and then flash Gapps and magisk, so i downloaded TWRP and flashed trough TWRP and thats when the sh$& hit the fan, now it wont boot into TRWP and my laptop wont recognize the device, neither on android nor in bootloader mode.
So, thank you guys in advance for your help, tomorrow im going to try on a computer at my work and see if its my computer and if not, well, ill have to se what you geniuses come up with. thank you so much again.
Info:
Rom build number: opm6.171017.030.h1 or 20180811 android 8.1.0
TWRP: i started with 3.2.2-0 then i downgraded to 3.2.1-0 and the one that messed up everything was 3.2.3-0
By the way, I have a full twrp backup of when my phone was stock, (but no way to use it) T_T
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.