Database Users

[Q] n900w8 Won't boot into recovery mode

A few months ago I rooted my N900w8, installed custom recovery (cwm), and flashed Android L. Today I tried to update the recovery, planning on updating the ROM as well. But now no custom recovery works at all, even the one I had running before. When trying to boot into recovery it says booting recovery... like it should, and then the screen just goes blank, then the phone restarts. Sometimes getting stuck in a bootloop trying to boot to recovery, but usually just regularly booting and boots normally to Android L. So now I am unable to update my ROM because not a single custom recovery has worked and therefore I cant flash the .img files. Please Help!

Ryan_407 said:
A few months ago I rooted my N900w8, installed custom recovery (cwm), and flashed Android L. Today I tried to update the recovery, planning on updating the ROM as well. But now no custom recovery works at all, even the one I had running before. When trying to boot into recovery it says booting recovery... like it should, and then the screen just goes blank, then the phone restarts. Sometimes getting stuck in a bootloop trying to boot to recovery, but usually just regularly booting and boots normally to Android L. So now I am unable to update my ROM because not a single custom recovery has worked and therefore I cant flash the .img files. Please Help!
Click to expand...
Click to collapse
I had the same issue except when I try to load recovery it would "forward" itself to download mode.
This may work for you, try re-flashing the latest CWM update with Odin. Place your phone in download mode by powering it off and holding Volume Down + Home + Power. Press volume up to proceed.
1. Download and extract
2. Run Odin as Administrator (Download if you don't have already)
3. Select CMW file from your download folder and place it in the "AP" section.
4. Start
When finished, Reboot holding Volume UP + Menu + Power Button. Vola!
Let me know if this works for you.

MmoFanatic said:
I had the same issue except when I try to load recovery it would "forward" itself to download mode.
This may work for you, try re-flashing the latest CWM update with Odin. Place your phone in download mode by powering it off and holding Volume Down + Home + Power. Press volume up to proceed.
1. Download and extract
2. Run Odin as Administrator (Download if you don't have already)
3. Select CMW file from your download folder and place it in the "AP" section.
4. Start
When finished, Reboot holding Volume UP + Menu + Power Button. Vola!
Let me know if this works for you.
Click to expand...
Click to collapse
Yeah depending on which recovery I flash it'll either forward to download mode, get stuck in a boot loop trying to start recovery, or restart and load the ROM.
Unfortunately it still isn't working :/ I used the tool from this page (http://forum.xda-developers.com/showthread.php?t=2446269) to convert the .img to a flashable odin file. Used the proper Canadian touch recovery (also tried recovery without touch) from this page (https://www.clockworkmod.com/rommanager) and no luck. Tried to enter recovery mode, it says entering recovery mode, goes black for a few seconds, vibrates then restarts the phone in regular boot mode :/ Any more idea's?
Do I need to be flashing a recovery that supports Android 5.0.2 for it to work? Im so puzzled.

YES!! Finally I was able to get a TWRP 2.8.5.0 working. Downloaded latest version from the main TWRP site and flashed using ODIN, did not use the converting tool above, downloaded the TWRP as a .tar flashable file from their site. Thanks for the help!
Do I need to close this thread or anything? This is my first time posting on xda

Ryan_407 said:
YES!! Finally I was able to get a TWRP 2.8.5.0 working. Downloaded latest version from the main TWRP site and flashed using ODIN, did not use the converting tool above, downloaded the TWRP as a .tar flashable file from their site. Thanks for the help!
Do I need to close this thread or anything? This is my first time posting on xda
Click to expand...
Click to collapse
Congratulations on solving your own problem! ^_^
I just figured to share my part when i experienced the same issue. I feel like it has somehow corrupt itself after it finished flashing which results in an empty directory for the recovery mode.
Warm Regards,
MmoFanatic

"no command" after installing TWRP in recovery mode

hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.

No one knows?

kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
What is the model number of your Note 4? When you are at the "no command" screen, try holding the volume up button and then press the power button to take you to recovery. I'd that doesn't work try holding the power button and tapping the volume up button quickly and release all buttons and see if it allows yoj to access recovery. I'd these do not work keep trying different button combinations. I'd you still cannot access the recovery menu you may have to Odin the factory firmware and start over. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app

none of those button combinations work. I will install stock firmware on it again and see if that fixes the recovery.

I had this problem in the past, I think the problem was that when I was installing TWRP via Odin that I had not powered off the phone so it looked like it installed but actually didn't, try taking out the battery and then boot into recovery or download mode whatever it is that is used for Odin and install again

kratos0605 said:
none of those button combinations work. I will install stock firmware on it again and see if that fixes the recovery.
Click to expand...
Click to collapse
If you cannot get into recovery with any button combination boot to download mode and use Odin to flash all 4 files of the factory firmware. That will give you a fresh start. Let me know how it goes.
Sent from my Nexus 6 using XDA-Developers mobile app

Same here
After holding volume up+middle button+power bar
I get into recovery mode but right after recovery mode it goes into “installing system update….” and then “No command” shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
— Appling Multi-CSC…
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Any sort of help would be appreciated, thank you.

amk58 said:
Same here
After holding volume up+middle button+power bar
I get into recovery mode but right after recovery mode it goes into â??installing system updateâ?¦.â? and then â??No commandâ? shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
â?? Appling Multi-CSCâ?¦
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Any sort of help would be appreciated, thank you.
Click to expand...
Click to collapse
Use the VOLUME UP/DOWN BUTTONS to scroll to WIPE DATA/FACTORY RESET and let it do its thing. When it's done select REBOOT SYSTEM NOW.
Tell me what that does.

fast69mopar said:
Use the VOLUME UP/DOWN BUTTONS to scroll to WIPE DATA/FACTORY RESET and let it do its thing. When it's done select REBOOT SYSTEM NOW.
Tell me what that does.
Click to expand...
Click to collapse
but this will erase all my data from the phone

Yes it will but it is the most likely way out of your bootloop. Before you wipe, connect your device to your PC and boot to recovery. Once your PC recognizes your device internal storage, transfer everything that you can think of.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Yes it will but it is the most likely way out of your bootloop. Before you wipe, connect your device to your PC and boot to recovery. Once your PC recognizes your device internal storage, transfer everything that you can think of.
Click to expand...
Click to collapse
I'm not in bootloop
My phone is working normally.
I'm trying to root my note 4 N910H (Android 6.0.1 Marshmallow) device
I flashed TWRP recovery using Odin
now I need to boot into TWRP recovery so I can to Flash SuperSu.zip downloaded in my device
what is happening after holding volume up+middle button+power bar
I should expect a menu with install option so I can flash the SuperSUfile in the device internal memory, instead this is happening:
it goes into “installing system update….” and then “No command” shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
— Appling Multi-CSC…
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Click to expand...
Click to collapse
If i choose reboot system, the phone will work fine, but I need a way to access TWRP recovery so I can to Flash SuperSu

amk58 said:
I'm not in bootloop
My phone is working normally.
I'm trying to root my note 4 N910H (Android 6.0.1 Marshmallow) device
I flashed TWRP recovery using Odin
now I need to boot into TWRP recovery so I can to Flash SuperSu.zip downloaded in my device
what is happening after holding volume up+middle button+power bar
I should expect a menu with install option so I can flash the SuperSUfile in the device internal memory, instead this is happening:
If i choose reboot system, the phone will work fine, but I need a way to access TWRP recovery so I can to Flash SuperSu
Click to expand...
Click to collapse
That looks like TWRP didn't stick when you flashed it using Odin. Try a different version of Odin and flash TWRP.
Sent from my Nexus 6 using XDA-Developers mobile app

kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
So idk if you've gotten it fixed, but what worked for me was: I had been turning on the phone after odin did its thing, and that caused the oem recovery to reinstall itself. So instead of letting odin auto boot be ready to push the volume up button to put it into twrp recovery. I had to remove my battery to keep it from booting fully.

We need to try another time flash. Conditions - old Odin 3.06, configured to remove reboot.

swhockey347 said:
So idk if you've gotten it fixed, but what worked for me was: I had been turning on the phone after odin did its thing, and that caused the oem recovery to reinstall itself. So instead of letting odin auto boot be ready to push the volume up button to put it into twrp recovery. I had to remove my battery to keep it from booting fully.
Click to expand...
Click to collapse
thanks you saved me lot of time today !!!

Thanks - this helped me too

i have same problem
my phone is samsung j2lte
have you try untick /uncheck the "auto reboot" option on odin app. instead reboot manually after flashing twrp??
my problem not solved either

Thank you. This helped me too.

kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
In ODIN go to 'options' and uncheck 'auto-reboot', then flash TWRP. When it's done, it won't reboot, just pull the battery for several seconds, reinsert it and boot into TWRP Recovery.
Enjoy!

When I try to flash any thing it gets stuck on boot.img

TWRP and Root gone for me on Z1 Compact and my USB port is broken. Please help

Hi, I see a lot of posts everywhere, here and on reddit talking about how the latest PA wipes TWRP and root. I've never flashed a rom that did that. I'm not a newbie and would have been able to fix it, but my USB port is broken. I've been charging via the magnetic port. I don't like that people aren't being taken seriously with this request because in most cases, sure you could use flashboot, but in my case I'm locked out of my device.
I would use something like Rashr, but I don't have root. The only way I can think of to get root is to use one of those sketchy apps like KingoRoot and then install Rashr but I have a feeling that would probably brick my device and since it's "usable" (but I can't get into recovery or root it) I should probably cut my losses and sell it.
I think this release should be pulled if it's causing this many problems. If the release is updated with a working TWRP, would I be able to fix it through the PA updater, or is that only system files and no recovery?

We haven't shipped with root in a LOOOOONG time.
I've never seen a ROM flash remove recovery. The ROM itself has nothing to do with recovery, and doesn't actively remove it.

I tried Paranoid Android on my Xperia Z3 Tablet Compact, I liked it a lot, but P.A. breaks TWRP so I'd be forced to reinstall the rom from scratch with every rom update so I can't use P.A.

thommcn said:
I tried Paranoid Android on my Xperia Z3 Tablet Compact, I liked it a lot, but P.A. breaks TWRP so I'd be forced to reinstall the rom from scratch with every rom update so I can't use P.A.
Click to expand...
Click to collapse
Not required . It is very easy to get twrp after flashing PA. It is a problem with sony devices. Follow my guide on how to get twrp, but download the twrp for your device and not for z3 compact
http://forum.xda-developers.com/z3-compact/general/twrp-z3-compact-unlocked-bootloader-t3476868
---------- Post added at 07:11 AM ---------- Previous post was at 07:07 AM ----------
bananabytes said:
Hi, I see a lot of posts everywhere, here and on reddit talking about how the latest PA wipes TWRP and root. I've never flashed a rom that did that. I'm not a newbie and would have been able to fix it, but my USB port is broken. I've been charging via the magnetic port. I don't like that people aren't being taken seriously with this request because in most cases, sure you could use flashboot, but in my case I'm locked out of my device.
I would use something like Rashr, but I don't have root. The only way I can think of to get root is to use one of those sketchy apps like KingoRoot and then install Rashr but I have a feeling that would probably brick my device and since it's "usable" (but I can't get into recovery or root it) I should probably cut my losses and sell it.
I think this release should be pulled if it's causing this many problems. If the release is updated with a working TWRP, would I be able to fix it through the PA updater, or is that only system files and no recovery?
Click to expand...
Click to collapse
Im not a 100% sure this will work, it mostly wont work, but try using kingroot to get root on the device, then use flashfire to flash recovery to boot/FOTA/Recovery partition depending on your device. Then try getting into recovery. But how did you get recovery in the first place if you had a broken USB? Why would you take chances?

Hi panzerox123, Thanks for link to guide but no go - I followed that guide five times and failed five times. It fails at 'To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.', it boots stock android instead. I tried flashing to Recovery and to the FOTAKernel - both failed. Recovery doesn't work with stock or Paranoid Android on this Z3TC but does with CM12 and FreeXperia.

thommcn said:
Hi panzerox123, Thanks for link to guide but no go - I followed that guide five times and failed five times. It fails at 'To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.', it boots stock android instead. I tried flashing to Recovery and to the FOTAKernel - both failed. Recovery doesn't work with stock or Paranoid Android on this Z3TC but does with CM12 and FreeXperia.
Click to expand...
Click to collapse
Really? This is how I got recovery back when I flashed pa. Are you sure fastvoot is working in your device? When you hold vol- and power button for around 10 seconds, you shoyuld see Sony logo, and then screen flashes and enters recovery.
Another question, did you download the correct twrp for your device? The link in the thread is for z3 compact phone

My tablet is the SGP611 'scorpion_windy'. Firmware: SGP611_23.5.A.1.291_UK.ftf TWRP: twrp-3.0.2-0-scorpion_windy.img (https://dl.twrp.me/scorpion_windy/twrp-3.0.2-0-scorpion_windy.img)
Vol- and power buttons are pressed until I get the Sony logo but it doesn't enter recovery - instead the tablet boots. Unlike with CM12, I don't get to see the violet led either.

thommcn said:
My tablet is the SGP611 'scorpion_windy'. Firmware: SGP611_23.5.A.1.291_UK.ftf TWRP: twrp-3.0.2-0-scorpion_windy.img (https://dl.twrp.me/scorpion_windy/twrp-3.0.2-0-scorpion_windy.img)
Vol- and power buttons are pressed until I get the Sony logo but it doesn't enter recovery - instead the tablet boots. Unlike with CM12, I don't get to see the violet led either.
Click to expand...
Click to collapse
Hmmmm very weird... are you on stock or pa?
Wait... Flash the latest firmware available for your device using flashtool. It updates bootloader so you can enter recovery using the above.
If all else fails, there is another method to update pa without starting from scratch every time. Can't explain it right now, I'm on Mt phone, when I get to lapptop , I'll explain

23.5.A.1.291 is the latest firmware that I downloaded with XperiFirm http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Either stock or P.A. won't enter recovery.

thommcn said:
23.5.A.1.291 is the latest firmware that I downloaded with XperiFirm http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
Weird... I'll get back alright... Don't know why there are problems

The only method that will work for stock on this tablet to get recovery right now is this one: http://forum.xda-developers.com/z3-...torial-stock-android-marshmallow-6-0-t3409486 using RecRoot.
As for P.A. - attempting to enter recovery results in continuous bootloops until reset.

thommcn said:
The only method that will work for stock on this tablet to get recovery right now is this one: http://forum.xda-developers.com/z3-...torial-stock-android-marshmallow-6-0-t3409486 using RecRoot.
As for P.A. - attempting to enter recovery results in continuous bootloops until reset.
Click to expand...
Click to collapse
That only happens when the wrong recovery is flashed...

RecRoot is only used with stock because it was designed for the Z3 phone so obviously that is no good for our purposes as would still have to flash the correct version of twrp.
So I either flash the base.img from CM12 (lollipop) scorpion_windy or FreeXperia 6.0.1 (marshmallow) scorpion_windy, then flash TWRP scorpion_windy. Then get into recovery, then wipe dalvik, system, data, cache, then install paranoid android, then wipe dalvik + cache and finally reboot. Well it boots fine but booting in to recovery just ends in bootloops.

thommcn said:
RecRoot is only used with stock because it was designed for the Z3 phone so obviously that is no good for our purposes as would still have to flash the correct version of twrp.
So I either flash the base.img from CM12 (lollipop) scorpion_windy or FreeXperia 6.0.1 (marshmallow) scorpion_windy, then flash TWRP scorpion_windy. Then get into recovery, then wipe dalvik, system, data, cache, then install paranoid android, then wipe dalvik + cache and finally reboot. Well it boots fine but booting in to recovery just ends in bootloops.
Click to expand...
Click to collapse
Same here.
Entering Recovery from ADB or standard hard buttons (USB + Vol-Up several time at boot) caused the boot loops.
The only way I found to enter the Recovery mode is: Unplug USB, Vol-down + Power press at the same time until the sony logo comes up.

igiona said:
Same here.
Entering Recovery from ADB or standard hard buttons (USB + Vol-Up several time at boot) caused the boot loops.
The only way I found to enter the Recovery mode is: Unplug USB, Vol-down + Power press at the same time until the sony logo comes up.
Click to expand...
Click to collapse
That is not how you enter recovery, that is how you enter fastboot mode... To enter recovery, you need to have a recovery installed on the recovery partition. To enter it, press vol-down+power button until you see sony logo and then leave the buttons

panzerox123 said:
That is not how you enter recovery, that is how you enter fastboot mode... To enter recovery, you need to have a recovery installed on the recovery partition. To enter it, press vol-down+power button until you see sony logo and then leave the buttons
Click to expand...
Click to collapse
When the device is normally powered up, the status led turns purple/pink. There if the Volum-up (down as well?) is pressed a couple of time, the LED changes color and the device enters the Recovery mode.
Of course you need a recovery image to be flashed in the recovery partition.
The problem here is that with some ROMs (i.e. AOSPA) is not possible to enter the recovery mode via "purple/pink led" procedure. The device will enter a reboots loop.
This procedure works properly with CM12.1 and CM13.
from "theandroidsoul" (I cannot post outside link yet, sorry).
How to boot into recovery
Switch off your Xperia Z first
Switch it back on and the time when you see your phone’s LED notification light turn purple or pink — start pressing either the Volume UP or Volume Down key a couple of times and your phone will reboot into recovery
Click to expand...
Click to collapse

igiona said:
When the device is normally powered up, the status led turns purple/pink. There if the Volum-up (down as well?) is pressed a couple of time, the LED changes color and the device enters the Recovery mode.
Of course you need a recovery image to be flashed in the recovery partition.
The problem here is that with some ROMs (i.e. AOSPA) is not possible to enter the recovery mode via "purple/pink led" procedure. The device will enter a reboots loop.
This procedure works properly with CM12.1 and CM13.
from "theandroidsoul" (I cannot post outside link yet, sorry).
Click to expand...
Click to collapse
That is when your recovery is embedded with the kernel. If you have the latest marshmallow build for Sony, it allows to to boot into recovery partiton .

What Have I done.... Soft Bricked A7G

Hello All
I have problem with my Axon7 G. I had 8.00 version installed and tried to make a system write option with using a method mentioned in
Official (Beta) Android 8.0.0 V1.30B01 EU Version by NFound thread. I flashed zip mentioned in this tread -ZTE_A7_UniversalBootStack.
Then restart devices and...whats happened....soft (or hard) bricked my phone!!!!!
1. After restart i had a standard warning about unlocked bootloader with yellow fonts . After 5 sec yellow fonts changed into red and wrote my device is corrupt...
2 using vol down i can enter into bootloader mode - then i can choose option like fastboot, recovery,restart and power off.
- pressing recovery and restrt , phone restart and again boot into bootloader mode with option above (cant get into twrp or stock recovery mode)
-pressing fastboot i can enter into this mode .
3 . Use fastboot mode to flash recovery and boot ( fastboot flash recovery recovery.img and fastboot flash boot boot.img)
everything seems ok but...nothing changed , i cant boot into recovery -twrp or stock. Still go back after restart to bootloader menu
4. edl mode.....i can`t enter . Use vol + and vol- and power button then after 3 sec phone went black screen with red light upper left. Applications cant recognize phone in this mode...
somene can help me ???

I also get the warning but I can just continue with the boot. I can't access recovery however. Don't know hot to fix that.

Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works

Antistar said:
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Click to expand...
Click to collapse
did you manage to get the error message away?
I got it recently after installing LOS 15.1, but for me everything works fine .
I'm just afraid if the device randomly reboots at night my alarm won't go off in the morning since it's the device is shutting itself down after the 30 second warning.
If you've fixed this can you please detail me through the steps.

Bootloop after Viper4Android

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