Issues with the slots - OnePlus 6 Questions & Answers

I've only recently bought the OnePlus 6; maybe a month or so ago. So, I had the Havoc ROM installed earlier and when i tried to update it with the new version, i got the crashdump mode. I'm not sure what i did wrong, but whatever.
I downloaded the flashboot Pie OTA and installed it, and was able to boot it. I then went back into fastboot and booted up the blu_spark twrp and did a data wipe and installed Havoc and twrp again. and it installed successfully and when i tried to restart recovery, i keep getting a blank screen with the white led light. I googled that and it looks like a kernel issue or whatever. But I'm having trouble figuring out how to fix it. I can't seem to load my Slot A at all. Whenever i switch to slot A, i get the blank screen with the white led, but i restart into fastboot and switch my slot to B, it loads up the Pie OTA.
Is there something I can do to fix this? Or my slot A is just broken from day 1 and i never realized it?

you need pie fw on both slots before flashing a custom pie rom!
flash pie+twrp
reboot twrp and flash pie+twrp
reboot twrp and flash havoc+twrp
reboot twrp and flash others(i.e. gapps+magisk)
reboot system and you should be up and running
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123

snigor said:
you need pie fw on both slots before flashing a custom pie rom!
flash pie+twrp
reboot twrp and flash pie+twrp
reboot twrp and flash havoc+twrp
reboot twrp and flash others(i.e. gapps+magisk)
reboot system and you should be up and running
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Click to expand...
Click to collapse
the flashboot OTAs flash pie on both slots. I went through the batch commands and its flashing boot_a and boot_b, system_a and system_b. I'm talking about the fastboot OTAs found here https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

alienwolf426 said:
the flashboot OTAs flash pie on both slots. I went through the batch commands and its flashing boot_a and boot_b, system_a and system_b. I'm talking about the fastboot OTAs found here https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
oh, right.. my bad! did you test both slots with only pie?

So, an update in case someone else has this issue with a busted slot and they want to fix it.
I had to download the unbrick tool from here https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I ran that, and installed the OxygenOS Pie OB4 (but i guess it can work with whatever pie build) on both slot A and B.
And that fixed it.
I guess, what may have broken the slots for me was that i installed official TWRP and blu_spark TWRP, which probably fked up the boot image.

Not the slot that got ****ed up,it was you that didn't read and follow the guide. It's important to follow the steps when flashing custom ROMs. So,from TWRP you shouöd have flashed pie firmware 2 times. (Yes it says it's flashed to a and b,that is not the case still...that's why the guide tells you to do what it tells you to do) also the TWRP thing is incorrect,but whatever floats your boat.

Related

[TREBLE][Oreo][How-To] Install any Generic System Image (GSI) on the Razer Phone

Hello everyone,
I've been tinkering around with Generic System Images since the Oreo Developer Preview 1 came out for the Razer Phone. I'm glad to say I got it to work, with lots of help from @MishaalRahman, @P4Block and indirect help of @phhusson and @TheCrazyLex.
What's working as of right now:
- GPS
- Rear Camera (only one of the lenses, needs further testing/pulling the Razer camera app apk)
- Front camera
- Microphones
- Sensors, each and every of them
- Speakers, sound playback, videoplayback (needs further testing)
- Fingerprint scanner
- WiFi, Bluetooth, NFC
- 120Hz screen features
- Color adjustments from the Oreo DP1 by Razer
- 4G LTE
- In-Call audio
What needs further testing:
- 4G/LTE FIXED check out post #77!
- Once the above is confirmed to work => VoLTE on any carrier, and also testing on certain carriers like 3 UK (since they sold a version with different software).
What's broken:
- Audio in phone calls (works properly in VoIP/3rd party apps) FIXED check out post #48!​
What ROMs can be booted with this (as of 30-03-2018):
AOSP 8.1
Lineage OS 15.1
Resurrection Remix
More to come...
Setting up your device:
You'll need:
Code:
To [URL="https://forum.xda-developers.com/razer-phone/how-to/guide-to-unlocking-bootloader-t3706462"]fully unlock your bootloader[/URL] and [URL="https://forum.xda-developers.com/showpost.php?p=74607352&postcount=8"]unlock flashing capabilities[/URL] on your device.
[URL="https://eu.dl.twrp.me/cheryl/twrp-3.2.1-0-cheryl.img.html"]TWRP image[/URL] + [URL="https://eu.dl.twrp.me/cheryl/twrp-installer-3.2.1-0-cheryl.zip.html"]TWRP injector[/URL]
[URL="http://tiny.cc/latestmagisk"]Magisk flashable zip[/URL]
A GSI of your preference from the ones listed [URL="https://forum.xda-developers.com/project-treble/trebleenabled-device-development"]here[/URL]. PS: Use the Gapps+SU one if you choose AOSP ;)
0. Make sure you're running the Android O DP1 from Razer, or any future update to it.
THIS WON'T WORK ON NOUGAT
1. Properly install TWRP on your device: (I'll be using @Dees_Troy's guide with a few modifications to make very sure everything will work as intended)
- fastboot flash the twrp image as explained by him, in your currently active boot partition. PS: After flashing the Android O DP1, it will always be A.
Dees_Troy said:
Once you have adb working, run this command: adb shell getprop ro.boot.slot_suffix
It should say: [ro.boot.slot_suffix]: [_a] Or: [ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this: fastboot --set-active=_b Or on slot B type this: fastboot --set-active=_a
You should see something like this: Setting current slot to 'a'... OKAY [ 0.042s] finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this: fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Click to expand...
Click to collapse
2. Once you're in TWRP, DO NOT SLIDE to allow modifications, but tap on Mount as Read Only. Plug in your USB cable, and adb push the boot image from the Android O DP1 factory image to your sdcard, as well as the TWRP injector and the Magisk zip. That can be done with the following commands:
Code:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
Code:
adb push path/to/the/factoryimage/boot.img /sdcard
Code:
adb push Magisk-16.0.zip /sdcard
3. Go into Reboot, then make sure you're on partition A. Else, tap on the button to set A as the active partition.
Now go back, tap Install, then tap on 'Install Image' then choose the boot.img you just pushed, and flash it as boot image.
Now go back, into Reboot, and move to partition B and repeat the step above.
Once you're sure both partitions only contain the unmodified boot images, set the partition A as active, go into Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it.
Once it finishes, do the same with the Magisk zip file.
4. Go into Reboot, press on Bootloader.
5. Connect the usb cable, and flash the GSI system image onto your system_a partition through fastboot from your pc. This can be done with the command:
Code:
fastboot flash system_a system-arm64-ab.img
5.b If you wish, you can install a different GSI onto your system_b partition, and that can be done with the following commands:
Code:
fastboot set_active b
Code:
fastboot flash system_b system-arm64-ab-gapps-su.img
5.c If you wish to go back to the system_a partition, you can execute:
Code:
fastboot set_active a
6. Reboot and enjoy.​Prebuilt boot image:
If doing the steps from 1-4 seems messy or you don't get it to work properly, I've published the image I made following them with the latest Magisk and TWRP versions available as of April 20th 2018.
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
Code:
fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
SHA-2: 2f0c7348ac906f2f81fa39df7b24b69392783bd2379d5da357777be444c67d97​
Old version (from ODP1 - may experience the bootloader issues):
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180330_cheryl_odp1.img
Code:
fastboot flash boot_b boot_linuxct_20180330_cheryl_odp1.img
SHA-2: 8f763162415167b2e919a450654f9a46f69b81f6853013bcabf362dfeb2a115e
Many thanks to everyone that helped me today to get this to work properly!
Want some screenshots?
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
PupPupG said:
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
Click to expand...
Click to collapse
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
This is awesome!!!
I'd love to have a fully working resurrection remix build working on my cheryl!!!!! =D <3
KEEP UP THIS AWESOME WORK!!!!!!!!!
linuxct said:
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
Click to expand...
Click to collapse
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
PupPupG said:
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
Click to expand...
Click to collapse
Flash the Oreo DP1 image and start over.
linuxct said:
Flash the Oreo DP1 image and start over.
Click to expand...
Click to collapse
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Flashing the Oreo DP1 image actually flashes an empty, non-encrypted userdata image. That's why I requested to start over.
That can also be another solution, bit messier than starting over but it's good.
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
M1cky said:
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
Click to expand...
Click to collapse
I do. Try installing the latest beta of Magisk and then, if that didn't solve it, try setting a new Build fingerprint with a tool like MagiskHide Props Config (PS. Just to be sure, set the Google Pixel 2 XL one since that's the only 8.1.0 build fingerprint provided by that tool).
ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Happy to see people making use of Treble on Razer Phone this quickly.
Good job! @linuxct
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
RUNNERX said:
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
Click to expand...
Click to collapse
Yes, it happens sometimes. Let me explain this briefly:
1. This bootloader seems to forget what the active partition was when it was told to reboot the device instead of turning itself off, and I don't know why yet. It happens 1/5 times I press on "Reboot", more or less.
2. You need to re-set the active partition to the one you were using, in my case A, so with a cable and my pc I run
Code:
fastboot set_active a && fastboot reboot
Tired of typing, I made myself a script named razer in my /usr/bin
Code:
#!/bin/zsh
fastboot set_active a && fastboot reboot
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
el4nimal said:
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Click to expand...
Click to collapse
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
linuxct said:
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
Click to expand...
Click to collapse
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Resurrection Remix Intensifies
el4nimal said:
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Click to expand...
Click to collapse
Unless you have overwritten it, boot to download mode and use fastboot to switch to the other slot which will allow you to boot into TWRP and install Magisk. If you have overwritten TWRP, flash it on the other slot (for example if you have LOS installed in A, flash TWRP into B).
linuxct said:
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
Click to expand...
Click to collapse
It has happened after a power off also, would putting the same rom in a&b slot stop it? system_other is not bootable so the phone enters download mode? I don't understand the working of the a/b system.
And THANK YOU so much for working on this, so nice to be back on custom roms!

Can't fastboot boot TWRP

So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Ph0enix_216 said:
So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Click to expand...
Click to collapse
With MSM tool your oneplus 6 is locked again...Maybe you should look if bootloader is locked!
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
whizeguy said:
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
Click to expand...
Click to collapse
My bootloader is unlocked. Still can't get into TWRP.
Ph0enix_216 said:
My bootloader is unlocked. Still can't get into TWRP.
Click to expand...
Click to collapse
Did you enable debug?
Sounds like you may have the active slot set to an unbootable OS. Check the active slot with fastboot getvar all, then use this to change to the other slot.
fastboot --set_active=[a or b depending on which is inactive]
Was this the end of this? I'm in the same boat. I was recovering from a google account remove device wipe and so I went to restore my TWRP back-up and it succeeds so I reboot. Device is bricked into fastboot mode only. So I msm restore and boot system, enable debugging, unlock bootloader, still can't get into TWRP or versions that worked before, just that taunting blue light.. I found this and changed my active slot but the issue is the same and I'm kind of at a dead end, any help would be appreciated. I can boot into 5.1.5 OOS and stock recovery fine.
Nevermind I had to incrementally update the ROM
angelsenvy said:
Nevermind I had to incrementally update the ROM
Click to expand...
Click to collapse
You can download both twrp zip & img from here: https://drive.google.com/drive/folders/1bnGBrkL5XE3yt7DmIRSDD2v4J6MzFOsH?usp=sharing
fastboot flash boot twrp-3.4.0-1-enchilada-Q-mauronofrio.img instead of fastboot boot .
That will work

flashed TWRP over boot slot B

I ended up flashing TWRP over my boot slot (B) and now I just boot into TWRP. I have already installed TWRP on boot slot (a). I can't remember which version of oxygenOS I have installed and couldn't find a way to confirm. How can I fix this? Also want to update to latest version of oxygenOS and android. No data on phone yet. phone still connects to computer, adb sideloader and fastboot commands still work work. Thanks
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
redpoint73 said:
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
Click to expand...
Click to collapse
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
doctor_whooves said:
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
Click to expand...
Click to collapse
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
plasticarmyman said:
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
Click to expand...
Click to collapse
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
tech_head said:
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
Click to expand...
Click to collapse
in this case the best thing to do is just unbrick using MSM
plasticarmyman said:
in this case the best thing to do is just unbrick using MSM
Click to expand...
Click to collapse
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
doctor_whooves said:
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
Click to expand...
Click to collapse
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
hey guys. Not able to flash oos through twrp.
getting "error flashing zip".
tech_head said:
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
Click to expand...
Click to collapse
Doesn't TWRP back up everything including boot partitions?
Is there nothing that will take the entire internal storage and just make a 'bare metal' image of it for restoring.. the whole entire thing, byte for byte? If not, why doesn't this exist? It just seems so logical to me and would be so incredibly useful. Phone borked? No problem. Just re-image it form the archive you made. To me, that is what TWRP is all about, at least conceptually if not technically.

Oneplus 6 and magisk (stuck in fastboot )

hi guys,
my op6 is running stock oos with magisk as root. My phone worked fine for several months. Today I tried switching magisk from the stable version to canary by first upgrading the manager app and then hitting the direct install option. This failed several times and I got an error saying:
! Unable to unpack boot image
I thought this could be fixed by a reboot, but well... it wasn't. Now the phone only boots into the bootloader. I booted into twrp and tried to uninstall magisk via the uninstall.zip. This fails with error
-Unpacking boot image
! Unsupported/Unknown image format
- Unmounting partitions
cd /tmp/repackorig/ && /sbin/magiskboot unpack -h '/tmp/repackorig/boot.img' process ended with ERROR: 1
Error unpacking image
I don't really know what this means. I'm guessing my boot.img is corrupted?
Is there any way I can solve this problem without a factory reset? Can I just flash the stock boot.img via fastboot?
Do you have any idea what went wrong here, so that I can avoid the error next time?
Yesterday I broke op5 during the magisk update. The repair was simple, flash stock boot.img as boot partition.
I flashed it from TWRP.
Try dirty flashing your ROM without flashing magisk.
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
Click to expand...
Click to collapse
Maybe it's worth trying change the slot and see if it will start? Of course from the fastboot level.
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Click to expand...
Click to collapse
I managed to fix it as well by flashing the stock boot.img for my software version to both slot_a and slot_b using fastboot. I left the active slot setting alone otherwise.
Afterwards I booted into twrp through fastboot and installed blu spark twrp and magisk 21.4 from there as a user suggested on the Magisk github: https://github.com/topjohnwu/Magisk/issues/3924
Note that github link also has a solution to flawlessly upgrade to latest Magisk without data loss but I haven't had the time to look at it.

Can't Boot to twrp recovery (just displying twrp logo)

Hi guys,
just received from my sister a oneplus 6 and i tried to flash a new custom rom after updating the system. I was following the guide posted on these forum but, when i tried to boot from fastboot to twrp it just display endless the twrp logo. I tried to boot with an older twrp or blu spark but nothing, they all make QUALCOMM crashdump, just the latest never go past the twrp logo. Tried to search for someone with a similar problem but i couldnt find anything about my same problem. Thanks in advance.
Enossob said:
Hi guys,
just received from my sister a oneplus 6 and i tried to flash a new custom rom after updating the system. I was following the guide posted on these forum but, when i tried to boot from fastboot to twrp it just display endless the twrp logo. I tried to boot with an older twrp or blu spark but nothing, they all make QUALCOMM crashdump, just the latest never go past the twrp logo. Tried to search for someone with a similar problem but i couldnt find anything about my same problem. Thanks in advance.
Click to expand...
Click to collapse
Which android version are you? 9 10 11?
1. Unlock Bootloader (if is already unlocked, skip this step)
2. download platform tools and unpack
3. copy twrp img and installer zip to platform tools folder location
4. open cmd
5. reboot phone to bootloader
6. write in cmd fastboot erase userdata
7. then write fastboot boot twrp-file-image-name.img
8. twrp is booted, go to advanced and choos option Flash current twrp
9. if is done, then reboot to recovery
10. go to wipe option, choose format data and type yes
11. now you can flash rom using rom flashing instructions
12. remember, after done rom flashing, FLASH twrp installer
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Enossob said:
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Click to expand...
Click to collapse
Glad it worked out for you
Noob9496 said:
1. Unlock Bootloader (if is already unlocked, skip this step)
2. download platform tools and unpack
3. copy twrp img and installer zip to platform tools folder location
4. open cmd
5. reboot phone to bootloader
6. write in cmd fastboot erase userdata
7. then write fastboot boot twrp-file-image-name.img
8. twrp is booted, go to advanced and choos option Flash current twrp
9. if is done, then reboot to recovery
10. go to wipe option, choose format data and type yes
11. now you can flash rom using rom flashing instructions
12. remember, after done rom flashing, FLASH twrp installer
Click to expand...
Click to collapse
Enossob said:
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Click to expand...
Click to collapse
I have the same problem after flashing OO 11.1.2.2. I made a mistake flashing the wrong patched image to get rooted again but doing this I lost the access to twrp and now there is no recovery anymore. If I try to boot into any older version of twrp I receive a crashdump, if I try to boot to twrp 3.6.0 it gets stuck to logo. If I use the command "fastboot erase userdata" do I lose something?
tenderloin83 said:
I have the same problem after flashing OO 11.1.2.2. I made a mistake flashing the wrong patched image to get rooted again but doing this I lost the access to twrp and now there is no recovery anymore. If I try to boot into any older version of twrp I receive a crashdump, if I try to boot to twrp 3.6.0 it gets stuck to logo. If I use the command "fastboot erase userdata" do I lose something?
Click to expand...
Click to collapse
Yeah, everything
Enossob said:
Yeah, everything
Click to expand...
Click to collapse
Is there another way to restore twrp?
I don't use twrp anymore. Attached is Magisk patched boot for OP6 11.1.2.2 I patched from the latest payload.
fastboot flash boot_a magisk_patched-23000_OP6_11.1.2.2.img
fastboot flash boot_b magisk_patched-23000_OP6_11.1.2.2.img
tenderloin83 said:
Is there another way to restore twrp?
Click to expand...
Click to collapse
Install the twrp installer directly from magisk
What I did was trying to install Lineage OS 18.1 (the latest nightly from Jan 11 2022) with Lineage OS Recovery. Following the official wiki I always got stuck in the lineage os boot animation. Never got past that. Tried to fastboot boot twrp.img but TWRP stuck on logo. I think I never tried to boot twrp with the userdata erased. I think I will try it.
Anyone trying to install the twrp, check out SHRP recovery for OP6/t. Boot the img and flash the zip from that thread. tested works with both OP6 and OP6t in OOS 11.1.2.2.

Categories

Resources