as the title says, whenever my phone dies or crashes, i cant get it to boot into magisk.
Key combos dont work, only way i can get it to boot back into magisk is by reflashing with odin.
sorry if this is the wrong place, any help would be much appreciated, thank you very much.
(S10 EXYNOS, ANDROID 11)
You may need to connect it to your PC with ADB, and use the command: "adb reboot recovery"
Unit ZER0 said:
You may need to connect it to your PC with ADB, and use the command: "adb reboot recovery"
Click to expand...
Click to collapse
This worked!! But is there any way I can do this without having to connect to a pc everytime?
reaps said:
This worked!! But is there any way I can do this without having to connect to a pc everytime?
Click to expand...
Click to collapse
Install the app "Root Essentials". It has a set of buttons you can put in the top bar, one of which is a reboot interface, where you can then select "Reboot Recovery". There is also a direct "Reboot Recovery" Button.
Unit ZER0 said:
Install the app "Root Essentials". It has a set of buttons you can put in the top bar, one of which is a reboot interface, where you can then select "Reboot Recovery". There is also a direct "Reboot Recovery" Button.
Click to expand...
Click to collapse
I meant more that on crashes or battery dying I then have to reboot and this is where I have the issue with magisk disappearing. I'm fine rebooting after I have booted into magisk but once it's gone it's impossible to get back without reflashing.
If in root mode, Magisk offers a button to reboot which reboots into root mode. Unfortunately this works only from root mode, as root is necessary to allow this functionality. I guess it is the same with the root essentials app.
Related
So I am trying to manually sideload the OTA update for 5.1 on my phone and adb and fastboot work just fine but when I reboot to TWRP and choose adb sideload it says 'error device not found' and I'm not sure why as adb devices finds my phone normally so the drivers can't be the issue.
Thanks for the help.
joshua.justice said:
So I am trying to manually sideload the OTA update for 5.1 on my phone and adb and fastboot work just fine but when I reboot to TWRP and choose adb sideload it says 'error device not found' and I'm not sure why as adb devices finds my phone normally so the drivers can't be the issue.
Thanks for the help.
Click to expand...
Click to collapse
Because you need stock recovery to do that...
BigDig said:
Because you need stock recovery to do that...
Click to expand...
Click to collapse
Just in case I tried that too and even with stock recovery it does not load completely. The android is just on his back with a red exclamation mark. And why would twrp put sideload in there if it would not work?
joshua.justice said:
Just in case I tried that too and even with stock recovery it does not load completely. The android is just on his back with a red exclamation mark. And why would twrp put sideload in there if it would not work?
Click to expand...
Click to collapse
you need to press the power button and volume up to get the menu in stock recovery.
simms22 said:
you need to press the power button and volume up to get the menu in stock recovery.
Click to expand...
Click to collapse
I reflashed everything and now the recovery icon is an android with moving ears and spinning gears and when I hit vol up and power it just says formatting data and sits there.
It shouldn't be this hard. I've flashed plenty of ROMs before.
Edit: Stock recovery works just fine but it still cannot find my device with a completely stock phone and when adb works when the phone is on and I Just updated the drivers so I'm at a loss.
Edit #2: For some reason MTP must be turned off which apparently throws the phone for a loop (not literally) if it is on.
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.
rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process
TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:
I tried to reboot and it is stopped at the LG screen as shown in the attach photo. I dont know what to do now, as I think it cant even connect and to the dock (still charging but not recognised at all by the PC). It would be great and very appreciated if anyone knows what I need to do? Otherwise it is an expensive paperweight now.
Thanks in advance.
P/S: This is my 1st post in XDA, so if anything wrong with my post please let me know, I will change. Thanks again.
Update
I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
Link to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this helps.
This may not help, but try pressing the side button in for 20-30 seconds. Shortly after it stops vibrating, it will start rebooting again and then you can stop pressing the button.
JimSmith94 said:
This may not help, but try pressing the side button in for 20-30 seconds. Shortly after it stops vibrating, it will start rebooting again and then you can stop pressing the button.
Click to expand...
Click to collapse
Hi, I think I messed up with the wrong kernel is the reason of this issue, and I have been able to get to the fastboot menu, do you know how revert it back to the factory/out of box condition? Thanks.
I haven't tried this, but it may work for you: http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452
JimSmith94 said:
I haven't tried this, but it may work for you: http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452
Click to expand...
Click to collapse
Thanks for ur help. I have manage to make it works again.
johnnyle7 said:
Thanks for ur help. I have manage to make it works again.
Click to expand...
Click to collapse
Please let us know how you did it, in case or when I or others need to do the same.
JimSmith94 said:
Please let us know how you did it, in case or when I or others need to do the same.
Click to expand...
Click to collapse
should I update my post with the solution?
johnnyle7 said:
should I update my post with the solution?
Click to expand...
Click to collapse
Either that or post a new reply. I know we would appreciate it.
johnnyle7 said:
I tried to reboot and it is stopped at the LG screen as shown in the attach photo. I dont know what to do now, as I think it cant even connect and to the dock (still charging but not recognised at all by the PC). It would be great and very appreciated if anyone knows what I need to do? Otherwise it is an expensive paperweight now.
Thanks in advance.
P/S: This is my 1st post in XDA, so if anything wrong with my post please let me know, I will change. Thanks again.
Update
I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this helps.
Click to expand...
Click to collapse
Hi There,
I have the same problem after the update.
I followed your steps but to enter into recovery mode I had to enable USB debugging mode which cannot be done as the watch keeps on rebooting.
Please let me know is there any other way to enable usb debugging mode to enter into recovery?
I get this error on my pc when I enter into recovery " error device '(null)' not found adb"
rayyansyed said:
Hi There,
I have the same problem after the update.
I followed your steps but to enter into recovery mode I had to enable USB debugging mode which cannot be done as the watch keeps on rebooting.
Please let me know is there any other way to enable usb debugging mode to enter into recovery?
I get this error on my pc when I enter into recovery " error device '(null)' not found adb"
Click to expand...
Click to collapse
Can anybody help me out in bringing my watch to life?
Great post. . . .
Driver Issue
I can get into the fastboot menu but my pc cannot recognize it. What is the appropriate method to connecting it. I have tried different cables, google driver, adb driver but the device doesnt even show up.
hey guys this is my first time making a thread in this is im really sorry if i posted in wrong place.
ok when i follow any guide to root my phone and before i need twrp and twrp doesn't wanna get installed on my phone for some reason u guys might help me
ok after unlocking bootloader i use adb to install the twrp and this is what i do
1pen cmd in adb folder and type "adb reboot bootloader" and it opens bootloader
2:then i place the recovery in same folder and name it recovery and type following command "fastboot flash recovery recovery.img" after this it says okay
3:then i reboot using adb or manually with phone with any kind of way to get into recovery first i see this stupid message "the bootloader is unlocked you can't be trusted"
4: 1)then it says press volume up to enter erecovery 2)press power button to continue and 3rd) "if no option has been selected the phone will boot automatically" or something like that
whatever option i choose i either endup in stock erecovery or boot the phone.
im so frustrated that i wanna throw the phone outa window please help...
honor 6x BLN-L21C185B361
Hi,
I can understand your frustration. You can use two methods:
01- Switch off phone. Press Volume Up and Down buttons together and Press and hold Power Button for 3-5 seconds. Phone will boot and take you to TWRP.
02- Instead of using buttons, use "adb reboot recovery" it will take you to TWRP.
Regards,
Aero
Aerocaria said:
Hi,
I can understand your frustration. You can use two methods:
01- Switch off phone. Press Volume Up and Down buttons together and Press and hold Power Button for 3-5 seconds. Phone will boot and take you to TWRP.
02- Instead of using buttons, use "adb reboot recovery" it will take you to TWRP.
Regards,
Aero
Click to expand...
Click to collapse
Now i adb commands stopped working idk why
My phone also has the same problem ،
I waited for the battery to finish. Then, with a chance to connect the charger cable and playing with the buttons, I was able to enter the main rom
plz help me . How can I fix the boot loader?
Is it possible to install the original ROM on the bootloader again?
So i accidentally flashed a magisk zip file to my p20 using a program called "TOOL ALL IN ONE" AS a recovery it showed that the process was completed but when i wanted to boot to fastboot it just shows that my phone is booting, same thing with recovery mod.
so basically i need a software that can let me install any recovery or repair my fastboot status as I am no longer capable of doing anything.
have you tried flashing it in ADB? i mean most of these tools are nice but when you type in the commands in adb to get things done then you will understand more and more about how everything works.
Eclipse.0 said:
So i accidentally flashed a magisk zip file to my p20 using a program called "TOOL ALL IN ONE" AS a recovery it showed that the process was completed but when i wanted to boot to fastboot it just shows that my phone is booting, same thing with recovery mod.
so basically i need a software that can let me install any recovery or repair my fastboot status as I am no longer capable of doing anything.
Click to expand...
Click to collapse
Did you solve this? I'm on the same situation. no recovery no fastboot!
Turn off your phone then press and hold power down button and don't press or hold nothing more. Hold power down and at same time connect your phone by USB to pc. Whoa, you are in a bootloader. It helped for me. Then you can reflash recovery and all will work again.