Maybe it's me not understanding what's new, I've "rooted" quite a few phones going back to the OG Droid - Motorola, Samsung, HTC. Never had any significant issue following directions and getting it done. Maybe things have changed over time. OG Pixel, 128GB, with sailfish-opr3.170623.008 (8.0.0). Auto-update disabled, USB debugging enabled, bootloader unlocked.
Setup: twrp-3.2.1-2-sailfish.img in platform-tools with adb and fastboot (latest versions). twrp-pixel-installer-sailfish-3.2.1-2.zip and Magisk-v16.0.zip at root of "Pixel/Internal Shared Storage". I also extracted a fresh boot.img from a factory image.
Just to make sure I'm starting fresh:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot --slot other flash boot boot.img
So far so good.
Code:
fastboot boot twrp-3.2.1-2-sailfish.img
TWRP comes up, I give it my PIN, it says decrypt OK, I tell it to install twrp-pixel-installer-sailfish-3.2.1-2.zip. Install seems fine, no errors reported. Back up a couple of levels, and "reboot recovery." It tries, eventually goes to a black screen for a few seconds, then does another reboot to system. No TWRP. Am I wrong in thinking I should be in TWRP at this point?
I can do the above, but flash Magisk-v16.0.zip instead, and I do end up with root, so that works. Just no way to get to TWRP except by fastbooting an external image.
I've also tried installing VerifiedBootSigner-v8.zip after installing twrp.zip, but that fails at the end with an "unable to verify..." or similar message. I'm not sure if that's supposed to be required or not currently, the TWRP install instructions don't mention it, but other guides do.
What am I doing wrong?
All I've ever done was boot to fastboot, adb boot <path-to-twrp>.img, and flash twrp. No need to use the boot signer anymore.
Sent from my Pixel using Tapatalk
Well, I can only guess that twrp-pixel-installer-sailfish-3.2.1-2.zip isn't compatible with the boot image in sailfish-opr3.170623.008.
I installed sailfish-opm1.171019.021-factory-68d3b69a.zip, then the twrp (and Majesk) install worked, just as expected.
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 everyone,
I have tried to get root priviledges following a guide from Droidwin.com to flash Magisk throught TWRP. At the very last step, after flashing Magisk 19.3 throught TWRP when I tried to reboot my phone, it gets stuck on the "unlocked bootloader warning message", which is supposed to disappear after a few seconds and move on to the boot animation.
It seems like I can go to the stock recovery, which shows fastboot and wipe actions. At this point, I can acces the fastboot screen, but the device is not listed using the ADB command "adb devices", nothing is find.
I'm wondering, what can I try to restore the phone ? I thank you in advance for any suggestions.
Here are some additionnal informations:
---Device---
Oneplus nord running OxygenOS 10.5.5, european version.
---What I've done to get in this situation---
Unlock bootloader using ADB
Launch an TWRP image file using ADB
"Try" to root using Magisk 19.3 zip throught TWRP
Power off from recovery (using TWRP touch interface), but the guide tells to click reboot at this step ...
Get stuck on the warning message, not having any boot animation.
Try to boot in Fastboot.
Turn the Nord Off and start it with plus minus and Power.
Boot TWRP with "Fastboot boot "TWRP File name.img" and flash magisk 20.4
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Search forum....
Msm tool oneplus nord wipes phone but fixes any issues
thibdur said:
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Click to expand...
Click to collapse
Plug your phone to your PC while in TWRP, then you can use adb to push files to your phone, for example with adb push magisk.zip /sdcard. Then, flash Magisk in TWRP.
How about flashing stock boot to see if your OPN boots to system again and then simply load Magisk zip to your internal storage and then flash via TWRP?
Thank you a lot for your suggestions !
Here is the solution in my case :
Because fastboot was working, I was able to flash stock oxygen rom, and get every working, but it needs to erase all your data.
You can find a guide on the XDA topic "[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord". The rom list have the lastest roms version (09/2020), and the process is super automated.
Have a good week-end XDA !
Hello,
I'm having a problem with Onplus 7 Pro bootlooping. It wont go past the "The boot loader is unlocked and software integrity cannot be guaranteed." screen.
It stays in that screen for about couple of minutes and then boots itself into fastboot mode. Im guessing it has something to do with Magisk, because when i uninstall it from TWRP it boots just fine. The funny thing is that i've been using Magisk for ~2 years now with this phone and haven't had any issues until now. The bootloop started after i just normally restarted the phone. And im running android 10 on the phone.
It boot into recovery fine. Also it boots into TWRP from fastboot.
Help would be appreciated, because i really dont want to reset my phone.
I will provide logs etc. if needed (im kinda new so dont know what helps).
Thanks in advance!
Kloopset said:
Hello,
I'm having a problem with Onplus 7 Pro bootlooping. It wont go past the "The boot loader is unlocked and software integrity cannot be guaranteed." screen.
It stays in that screen for about couple of minutes and then boots itself into fastboot mode. Im guessing it has something to do with Magisk, because when i uninstall it from TWRP it boots just fine. The funny thing is that i've been using Magisk for ~2 years now with this phone and haven't had any issues until now. The bootloop started after i just normally restarted the phone. And im running android 10 on the phone.
It boot into recovery fine. Also it boots into TWRP from fastboot.
Help would be appreciated, because i really dont want to reset my phone.
I will provide logs etc. if needed (im kinda new so dont know what helps).
Thanks in advance!
Click to expand...
Click to collapse
Sounds like maybe a bad or corrupted magisk module. This is what I do to remove all modules due to bootloop:
You'll need your stock boot.img and a magisk_patched.img.
1. Boot into fastboot: "fastboot flash boot boot.img", reboot
2. Start process of entering safemode: on my phone you long press power button for power menu. Long press "power off" for safemode option. Once choosing safemode, boot back to fastboot before your phone boots all the way up.
3. In fastboot flash your magisk_patched.img "fastboot flash boot magisk_patched.img", reboot. You should now boot rooted and in safemode. In cmd window, run this script:
"adb wait-for-device shell magisk --remove-modules"
Your phone should reboot rooted with all modules removed.
I don't have your phone but this works for me on mine
Tulsadiver said:
Sounds like maybe a bad or corrupted magisk module. This is what I do to remove all modules due to bootloop:
You'll need your stock boot.img and a magisk_patched.img.
1. Boot into fastboot: "fastboot flash boot boot.img", reboot
2. Start process of entering safemode: on my phone you long press power button for power menu. Long press "power off" for safemode option. Once choosing safemode, boot back to fastboot before your phone boots all the way up.
3. In fastboot flash your magisk_patched.img "fastboot flash boot magisk_patched.img", reboot. You should now boot rooted and in safemode. In cmd window, run this script:
"adb wait-for-device shell magisk --remove-modules"
Your phone should reboot rooted with all modules removed.
I don't have your phone but this works for me on mine
Click to expand...
Click to collapse
Thanks for the help, but i tried that already, it didnt solve my problem. It seems i'm going to need to do a reset
What modules are you using?
Try using Magisk canary
Did your phone get a android 11 update? If u look in twrp file manager are the file encrypted,this is what happened when 11 updates. If it's not that, and u think it's a module u can also use twrp explore and remove them ,or the terminal.
on the OnePlus 7 Pro with the Android 11 Open Beta 5.
A few hours back I decided to reinstall TWRP on my phone as I hadn't yet permanently done so. I believe I may have installed the wrong version (guacamole), as the moment I reinstalled Magisk and rebooted, my phone bootlooped. I ended up with a Qualcomm error with exit code 0 the times I got it to stop. It took a few tries but I was able to get it into fastboot and flash the original boot image, but to little avail. For some reason, if I reflash the boot image, wipe the device cache, and get REALLY lucky (like 3 out of 30 reboots now), my phone will turn on in safe mode. But as I quickly realized, rebooting throws the phone back into a bootloop. I'm able to access apps through safe mode, though very limited.
I'm currently making a backup of my phone, but is there anything I can do now to avoid the reset process?
You have a few options now, which I would try in following order:
Diable the Modules:
If you manage to boot your phone enable USB-Debugging and use following command in ADB:
Code:
magisk --remove-modules
This will remove all modules, which could be causing the bootloop.
Reflash Magisk:
Boot Nebrassy TWRP from bootloader
Code:
fastboot boot twrp.img
twrp.img should be the name of the recovery downloaded
Mount storage
Download latest Magisk apk
Rename the .apk to .zip
Transfer to phone
Flash latest Magisk. This might fix something.
Uninstall Magisk:
Boot Nebrassy TWRP from bootloader
Download latest Magisk apk
Rename the .apk to uninstall.zip
Transfer to phone
Flash the uninstall.zip This should remove Magisk
Reflash TWRP (this will also remove Magisk)
Boot Nebrassy TWRP from bootloader
Code:
fastboot boot twrp.img
twrp.img should be the name of the recovery downloaded
go to Advanced > Flash Current TWRP
Reflash latest Magisk if you want to keep it (not reccomended in your case)
Hope you get it fixed.