Hello i installed on my Rooted and Bootloader Unlocked Oneplus 6t the pixlify module
Then i clicked restart and now i can only see the Dark Google Boot animation
I Already Tried :
Turning off (restart) while pressing power and volume up to go intop Recovery (TWRP)
Its just not working i cant get into twrp
What happens Exactly after i pressed : power and volume up
Phone restarts
I see the Bootloader Warning
And then again the Boot Animation
Volume up + Power combination boots into bootloader not recovery, recovery combination is Volume down + Power.
Anyway you can't even boot to bootloader? Or it restarts after booting to bootloader?
XDHx86 said:
Volume up + Power combination boots into bootloader not recovery, recovery combination is Volume down + Power.
Anyway you can't even boot to bootloader? Or it restarts after booting to bootloader?
Click to expand...
Click to collapse
So i am in the BootAnimation and If i press volume down and power its just restarts normaly and same with volume up and power
Tinx_LD said:
So i am in the BootAnimation and If i press volume down and power its just restarts normaly and same with volume up and power
Click to expand...
Click to collapse
You need to delete this module, you shouldn't install any magisk module without reading what they do or how they work.
It's perfectly stated in the repo that pixelfy isn't for OOS (Oxygen OS).
You need to boot into TWRP recovery, If your device is detected on your PC try adb reboot recovery
Or if it's detected in fastboot/bootloader then use fastboot boot twrp.img (Replace twrp.img with your image location and name)
If it's not detected try fastboot continue (You may have to spam this command for a couple of times)
Note: To run these commands you may want to install your device specific driver and adb tools. You can get the driver from here.
If you successfully booted into TWRP then flash pixelify zip again to completely uninstall it.
Related
Hey all, I recently flashed the xXx_NoLimits_3.5_magisk_rom
magisk module and the blu_spark_r136-custom_treble_op5-op5t_d8ba1bb.zip and my Wi-Fi function broke.
I did a backup on TWRP previously but then found out I can't boot into either recovery (not even stock recovery) or fastboot mode. I then uninstalled the xxx magisk module but still can't boot into recovery/fastboot mode. Thus, I suspect the problem is with the custom kernel. Problem is, even if I want to flash a new kernel, I can't use fastboot to install twrp boot.img
I did a factory reset but the phone just did a regular reboot with no data loss at all. Is there something I can do to get fastboot working again?
xdalu91 said:
Hey all, I recently flashed the xXx_NoLimits_3.5_magisk_rom
magisk module and the blu_spark_r136-custom_treble_op5-op5t_d8ba1bb.zip and my Wi-Fi function broke.
I did a backup on TWRP previously but then found out I can't boot into either recovery (not even stock recovery) or fastboot mode. I then uninstalled the xxx magisk module but still can't boot into recovery/fastboot mode. Thus, I suspect the problem is with the custom kernel. Problem is, even if I want to flash a new kernel, I can't use fastboot to install twrp boot.img
I did a factory reset but the phone just did a regular reboot with no data loss at all. Is there something I can do to get fastboot working again?
Click to expand...
Click to collapse
If you power down the device and power up with pressed power h volume up button what happens? Did you see the menu to select either fastboot or recovery to boot in?
Which stock oos rom do you have?
strongst said:
If you power down the device and power up with pressed power h volume up button what happens? Did you see the menu to select either fastboot or recovery to boot in?
Which stock oos rom do you have?
Click to expand...
Click to collapse
Hi, adb recovery boot, quick reboot pro app, and OP5 advanced reboot buttons didn't work, but booting into recovery manually (holding vol down + power buttons) worked, so you are right about the method. Thanks for your reply.
If you are running OOS, you flashed the wrong kernel version. Note the difference below:
blu_spark_r136-oos-treble_op5-op5t_4aea761.zip
blu_spark_r136-custom_treble_op5-op5t_d8ba1bb.zip
I succesfully can flash TWRP to recovery_ramdisk via fastboot. PHONE and FRP are unlocked. My phone is bricked and when i boot to OS i get "ERROR MODE Attention! ..." And i cant go to twrp by holding volume up + power key. But i can go to some kind of recovery mode by pressing all buttons (volume up, volume down and power key). Can somebody help me?
Thanks.
My phone is HUAWEI WAS-LX1C482
I just deleted System particion with fastboot. but i dont know how to install android now...
Hello everybody !
My A2017G displays the unlocked bootloader warning message, and then says that "Your device is corrupt [...] will poweroff in 30 seconds".
When the second message is displayed, if:
I hold power button, LOS15.1 starts properly and work well.
I hold power button + volume up, Recovery TWRP Nfound is launched.
So my question is: Is it the normal way to start the phone? Or something wrong during flash ?
What I have done:
I tried to flash my A2017G from LOS14.1 to LOS15.1, with some difficulties
I booted in (functional) TWRP, flash zip file of Oreo modem and universal bootloader, success
Always in TWRP, I flash TWRP NFound image. Try to reboot in the new recovery ... Problem occurs
Finally I found a way to go into recovery mode (read above) and format data, system ... and flash LOS15.1
I have access to fastboot, recovery and EDL mode.
TTR6214 said:
Hello everybody !
My A2017G displays the unlocked bootloader warning message, and then says that "Your device is corrupt [...] will poweroff in 30 seconds".
When the second message is displayed, if:
I hold power button, LOS15.1 starts properly and work well.
I hold power button + volume up, Recovery TWRP Nfound is launched.
So my question is: Is it the normal way to start the phone? Or something wrong during flash ?
What I have done:
I tried to flash my A2017G from LOS14.1 to LOS15.1, with some difficulties
I booted in (functional) TWRP, flash zip file of Oreo modem and universal bootloader, success
Always in TWRP, I flash TWRP NFound image. Try to reboot in the new recovery ... Problem occurs
Finally I found a way to go into recovery mode (read above) and format data, system ... and flash LOS15.1
I have access to fastboot, recovery and EDL mode.
Click to expand...
Click to collapse
this is normal due unlocked bootloader and custom bootstack.
Its mentioned everywhere....
Predatorhaze said:
this is normal due unlocked bootloader and custom bootstack.
Its mentioned everywhere....
Click to expand...
Click to collapse
I already know about warning message due to unlocked bootloader. After 5 seconds phone boots normally.
But in my case, after the warning, phone doesn't boot and displays "Your device is corrupted ..."
I can boot only if I press power button during the second warning.
If I try
Code:
fastboot boot recovery.img
, phone will never boot into recovery.
TTR6214 said:
I already know about warning message due to unlocked bootloader. After 5 seconds phone boots normally.
But in my case, after the warning, phone doesn't boot and displays "Your device is corrupted ..."
I can boot only if I press power button during the second warning.
If I try , phone will never boot into recovery.
Click to expand...
Click to collapse
Also the second screen is normal,its because modified bootstack.Just press power button and your good to go.Modified b20 splash bootstack does not have this
Predatorhaze said:
Also the second screen is normal,its because modified bootstack.Just press power button and your good to go.Modified b20 splash bootstack does not have this
Click to expand...
Click to collapse
Ok thanks for your answer and explanation
So I just rooted and got everything to work just fine (.33). Thought i'd smash in Viper4Android aswell.
The phone is now stuck on the logo with the red and two white dots.
I can get it to reboot with Vol+ and power, but the power-button does not let me go into recovery mode at all. It's like its disconnected.
Is there anything you can do to get into recovery/fastboot from here?
Also tried every single vol+powercombination with 0 results..
Thanks in advance.
What viper4android version did you install? And what Android version are you on?
If using Magisk 21> you should be able to hold down power button to boot into safe mode.
Hold power button and volume down and up at the same time, this should boot you into bootloader.
If you're on Android 10:
Boot into TWRP and remove module folder from data/adb/modules
Android 11 (or 10)
[Recovery][Stock OOS]Oxygen OS Stock recovery with ADB enabled
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled...
forum.xda-developers.com
Lossyx said:
What viper4android version did you install? And what Android version are you on?
If using Magisk 21> you should be able to hold down power button to boot into safe mode.
Hold power button and volume down and up at the same time, this should boot you into bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
I seem to have solved it (for now..).
I could not get any key to answer to my commands when i rebooted the phone (hence why i couldnt get into recovery etc.), it only went back to the loop after displaying the usual message about the bootloader being unlocked.
Holding down both volume-buttons and using the msm-tool i managed to get it back to OEM (with everything locked. Again. Lmao) so now i just gotta watch out when I install Viper again (if i do..).
Running Oxygen 11.0.3.3.IN11BA with the latest Magisk (I just patched it today)
Edit: I just used the Viper4Android that i found inside Magisk if that makes any sense.
I'll try your links and see if i have to re-flash again..
Cheers
runing step16
fastboot reboot
Click to expand...
Click to collapse
But this boots to normal boot with completely purple not working screen.
And I couldn't figure out that it is normal install is broken but not recovery boot.
To more confusion, before accassing lineage recovery or TWRP loads common LG recovery and offers delete all user data.
This creates impression TWRP or lineage recovery is not installed and is broken.
Now everything works.
I used key combination VolumeDown Power release power on LG Logo and hold Power again. Chose erase user data / factory reset and this let me boot to custom recovery mode and flesh rom with sideload command.