Related
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!
Hi guys Zeph here.
I've just rooted my Redmi Note 4 without any problems. I've tried to install several custom ROMs like HAVOC, Pixel, etc using TWRP but it showed some error I don't know. My backup ROM did not install so I've tried to install Global Stable ROMS from Internet but those were shown as corrupt. I've also tried using fastboot, ADB sideloader but same problems are happening. So basically my phone is just a hollow without any OS. Any solutions please because that is my only phone.
Here are some screenshots..
Can you boot up normally?
If not what happens, when you try?
gabtit7 said:
Can you boot up normally?
If not what happens, when you try?
Click to expand...
Click to collapse
Sorry when the backup ROM didn't get installed I had completely wiped all data for sake of installing Global custom ROMs. But it still didn't get installed. So my phone is like DOS without any OS.
Oh. Well thats a problem.
First of all:
Go to https://c.mi.com/oc/miuidownload/detail?device=1700309
dowload the rom (its a zip) and transfer it to your phone
go to twrp
flash it with twrp
reboot to system
Now if (while booting up) it says "The system has been destroyed":
Just keep booting in twrp, back to system, back to fastboot and repeat for some time and multiple times a day. For some reason thats how you call the autorepair to wake up, it will remove the ROM you just installed and probably install a backup one on its own
If this doesnt work too:
I will suppose you have a pc with fastboot & adb drivers available
Since the phone is alr in deep s***, lets try something quite risky
1)
go to twrp > wipe > format data
2)
connect your phone to pc while in fastboot
and execute these commands
fastboot erase system
fastboot erase cust
fastboot erase boot
fastboot erase vendor
CAREFUL: NOW YOUR PHONE IS BRICKED, BUT FIXABLE (probably)
3)
repeat the steps on the top of this message
All this should fix the problem, if not i am sorry but the phone will be unrepairable without any professional technician
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me
after patching boot.img with Magisk and flashing over the patched boot.img, the phone (Doogee S88 Plus) will just infinitely reboot after the message `Your device has been unlocked and can't be trusted`
luckily, patching the original boot.img back fixes it (albeit flashing it back is kindof tricky, have to reboot multiple times while holding down the volume-down button before i can re-flash)
so it's not bricked, but i haven't been able to root it either, any suggestions?
fwiw, i'm using this firmware: https://drive.google.com/drive/folders/13bxhk-eEsJ81FmJWZaEEsOkZBMsYJE3x
update: finally managed to root it, the final piece of the puzzle was that S88 Plus wanted the magisk-patched boot.img signed with the publicly-available-private-key from https://forum.hovatek.com/thread-35862.html
screenshot:
https://imgur.com/EbjK0qX
the magisk-patched + signed boot.img if anyone is interested:
where boot.img ?
and you chose which twrp ?
avalondrey said:
where boot.img ?
Click to expand...
Click to collapse
avalondrey said:
and you chose which twrp ?
Click to expand...
Click to collapse
i did not use twrp at all, i only used magisk, and the boot.img is the file i uploaded above with the name "magisk_patched-23000_TY62U.img" , just rename it to "boot.img"
does your phone has a vbmeta.img?
It control if the image is signed, if you don't flash an empy vbmeta.img the system will bootloop.
It was a problem when rooting the Ulefone Armor 8-11
root is ok , flash tool, install boot and reboot
Harlock1978 said:
does your phone has a vbmeta.img?
It control if the image is signed, if you don't flash an empy vbmeta.img the system will bootloop.
It was a problem when rooting the Ulefone Armor 8-11
Click to expand...
Click to collapse
interesting, yes the phone has a vbmeta.img, and no i did not patch the vbmeta.img, and i did experience the reboot-loop, but signing the patched boot.img fixed the reboot loop without touching the vbmeta.img
This did it..dont flash vbmeta...the Boot ist the only Thing you Need...flashing vbmeta will end in bootloop...maybe a signed vbmeta...but why trying when Boot is enough...
after hours of trying I finally got it working.
Because I tried so much stuff I'm not exactly sure what was the key.
The signed boot.img flashed with sp flash tool alone did not work - i did not have the device unlocked with fastboot at that moment.
Then I tried a lot of different stuff.
I _think_ what was needed is these two things:
- signed boot.img from @hans henrik
- unlocking bootloader with fastboot (fastboot flashing unlock && fastboot flashing unlock_critical)
How did you unlocked it? And are you running gsi rom?
I have the s88 pro and i like to install custom rom
the doogee s88 plus should support galileo GPS standard Pu on mine it does not show any gaileo satelites. could anybody check?
Hi please help me i have doogee S88 plus and i use this guild https://unofficialtwrp.com/twrp-3-4-0-root-doogee-s88-plus/
now me phone keeps restarting, show "orange state", logo launches, I tried different combinations of buttons but nothing helped
what can i do or is there any way i can get it back to normal?
only now found this thread, currently the phone has a bootloop after these three commands
fastboot erase userdata
fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
OK, i use sp flash tool but when i turn on me phone i see a bars on screen
i tried with all the stock roms i found, everywhere the same, the phone seems to work but instead of images there are stripes
this rom worked
OneDrive
onedrive.live.com
I finally managed to root my phone after days of endless boot loops (fixed by flashing stock using SP flash tool). Turns out I didn't need to flash an empty vbmeta or install TWRP at all. I was able to root it by following this guide https://www.hovatek.com/forum/thread-35862.html. For some reason your patched magisk image didn't work on my S88 Plus, so I made my own using the stock boot image from the official Doogee website (which appears to be the same one used in your patched version?) and Magisk 25.2 apk. For the Hovatek guide, I used python2 since python and python3 did not work. I currently have a red "Not Verify" watermark and an NVRAM WARNING: Err = 0x10 wifi network error, but should be able to resolve those with root access from guides I read earlier.
I would also like to install a GSI (lineageos preferably) but have had no success since nothing seems to officially support the S88 Plus even though it is project treble compatible, and I have ran into boot loops so far.
I have attached my working magisk_patched.img but would recommend building it from scratch using the linked guide to avoid any issues.
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.