Related
Hi all,
Didn't find anything on this, hoping for some clarification.
Shell snippet(terminal on phone):
$su
#reboot
not permitted!
in short - reboot and reboot recovery commands do not work via terminal. want this ability for GScript.
i installed the super boot image from modaco, i've re-installed the superuser.apk and also ran the commands manually from /superboot/superboot.sh on the phone...is any one else having this problem or has anyone found a solution to the issue? please also note that i have in fact reflashed the superboot image twice now, still no resolve. halp!
Same issue
I still have the same issue... I can't do it
check permissions in SuperUSER.apk and see if you have it enable to do so
Hi all,
i get the same issue on my EVO 4G. not permited! when i type reboot or reboot recovery and i know for a fact that supersuer allowed root access to TU. this used to work before on superuser 2.1 now i have SU 2.3.5. anyone ?
i have the same problem -.-
Do you have the toolbox binary in /system/bin as well as a symlink named reboot pointing to it? 'reboot' is not a native command and you'll find that most (if not all) "shell commands" are actually binaries and shell scripts. Even something as simple as 'mv' (move) is a binary, not built into the shell. Ensure that you have a reboot symlink that points to toolbox. It's quite possible that your rom (or superboot) doesn't include it.
You can also download Quick Boot by Sirius Applications Ltd. From the market. It lets you reboot, reboot into recovery and reboot into fastboot, plus you can make shortcuts to each different reboot on your home screen. (market link)
Have busybox installed..(think thats what Chains jus said)
if you do.. try this
Busybox reboot
ilostchild said:
Have busybox installed..(think thats what Chains jus said)
if you do.. try this
Busybox reboot
Click to expand...
Click to collapse
I was using the extended controls widget but that stopped working.
running su, reboot, gives not permitted!
running su, busybox reboot, gives no error but doesn't reboot the phone.
trying the quickboot app now ...
*** quickboot works great ... I don't know what the problem is though ..
this command work well!
command : busybox restart -f
i can use this command to restart samsung and htc phone
here's the latest--
http://dl.dropbox.com/u/28338566/Superuser-3.0.7-efghi-signed.zip
Had same issue till I flashed this
I forget if I just flashed or extracted the apk and pushed--sorry--just had sugery and not remembering all that well
I flash different roms so hope someone can ok this for any rom--not sure why not
Anything new on this? I am having the same issue with my HTC one. With busy box installed there is a reboot bin in /system/bin that gives the "Not permitted!" Message when ran from the phone.
Busy box installs reboot in /system/xbin and when you disable or remove the reboot binary in /system/bin it executes the one in /system/xbin however it does nothing unless you add a -f to the command' and all you can do is regular reboot (no bootloader or recovery)
Works:
/system/xbin/reboot -f
Reboot recovery command using adb shell on computer
Does not work:
/system/bin/reboot [anything]
/system/xbin/reboot -f recovery (boot loader,etc)
This stinks because rebooting to recovery from apps won't work
There must be a way to hack this into a working reboot recovery command
Ok
Sent from my SGH-M919G using xda premium
orthonovum said:
Anything new on this? I am having the same issue with my HTC one. With busy box installed there is a reboot bin in /system/bin that gives the "Not permitted!" Message when ran from the phone.
Busy box installs reboot in /system/xbin and when you disable or remove the reboot binary in /system/bin it executes the one in /system/xbin however it does nothing unless you add a -f to the command' and all you can do is regular reboot (no bootloader or recovery)
Works:
/system/xbin/reboot -f
Reboot recovery command using adb shell on computer
Does not work:
/system/bin/reboot [anything]
/system/xbin/reboot -f recovery (boot loader,etc)
This stinks because rebooting to recovery from apps won't work
There must be a way to hack this into a working reboot recovery command
Click to expand...
Click to collapse
I'm having the same problem. I did notice that my system/xbin folder is missing quite a bit of the files as the system/bin folder, including the reboot file. I assume it doesn't need to mirror it exactly, but should it have the reboot file also? If not, should there be a symbolic link in the xbin folder to link the reboot file in the bin folder? Thanks in advance for any and all help.
By the way, I am rooted, boot unlocked, and s-off running the Android Revolution HD rom.
I had this issue now reboot works (in a way)
This might be naughty of me to bring up an old thread but others have done and its only a few weeks sincle last post...
Anyways I had this issue from what I have read it only happens to people to certain people on certain phones.
I was able to reboot though a mobile terminal emulator, ssh, and though the shell while in usb.
I noticed that only though ADB would it accept reboot (security reasons?) so I read a nifty article on using ADB though tcp and to make it more secure I used it though localhost since only I can use it.
here is the commands that I used:
Code:
stop adbd && stop adb && setprop service.adb.tcp.port 5555 && start adbd && sleep 4 && adb connect localhost && adb reboot
It feels more like a work around but my personal goal was reboot my phone though a remote sms (remote terminal) and it worked within a shell so wohoo. I hope it helps someone and setting ADB to listen on usb is
Code:
setprop service.adb.tcp.port -1
I had to use sleep to make sure ADB started before I tried to connect... you can add reboot bootloader...etc..adb commands....
I guess you can make this into a file called myReboot.sh and link it to make it a "command"
My solution
To root, updated version of Android Gingerbread, from there, I downloaded the same version, but Japanese, walked into the boot, and updated to version japonsa from there to root nexus one and go.
Download quick reboot form the play store
Sent from my Nexus 7 using XDA Premium 4 mobile app
SU - Reboot - not permitted! solved
SOLVED:
Not all linux commands r available on andriod(depends upon rooting how u did that), to do that just install BUSYBOX.
After installing busybox u have every command. Enjoy
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
i have the exact same issue, is there any answer for this??
Wettpassat said:
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
Click to expand...
Click to collapse
i have the exact same issue, is there any answer for this??
Well it's been well over a year since I did that but let's see if I can help..... Before I start I'm hoping you've already enabled adb debugging on the gear and downloaded adb onto your computer. I believe you run the commands after you've run cygnia but before you flash twrp. You run the task from a command prompt from your pc. I'm pretty sure you don't include the $ or #. Before you start try the adb command- adb devices from the command prompt on your pc. That'll let you know if the gear is connected. I remember being a bit intimidated by it all as it was different to any other flash I'd done. In reflection it's very easy, type the line in a command prompt, press enter, wait for the cursor to come up again, type the next line. As for guides..... I can't remember which one I used but there's plenty out there.
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
Any luck?
Thank you very much
Jayfreshh said:
Any luck?
Click to expand...
Click to collapse
Did you ever find anything for this device?
remarkablecow913 said:
Did you ever find anything for this device?
Click to expand...
Click to collapse
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?
Jayfreshh said:
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?
Click to expand...
Click to collapse
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
Click to expand...
Click to collapse
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying
remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying
Click to expand...
Click to collapse
Okay if anything works out when you try let me know
The bootloader can be opened in developer mode for this devise if I'm correct
You can unlock bootloader in developer options but from there. I'm stuck and really want to get root and see what "deleted" files I can recover from a factory reset. Anybody ever try twrp for same chipset like someone was talking about doing?
rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
[Update Anyone?]
I picked up a Coolpad 3632a yesterday and I've been trying to ROOT it for quite a while nowl; trying Kingroot v5.3.7 without PC, and KingRoot 3.5 on PC both failed to ROOT. I've been out of the loop for quite a while regarding Android devices and OS - the last Android Phone i owned was the LG G3 if i remember correctly. According to the available info I've found searching for Rooting Options for the coolpad 3632a it all seemed almost %100 easily rootable with or without PC mainly using Kingroot.
If anyone was successful in rooting this device (Coolpad 3632a / Android 7.1.1) - please let me know, my main goal is to find a good custom ROM and load it replacing the Bloat/Malware filled phone!
Thanks again to anyone who has taken the time to read and respond with any news (good or bad) on getting this device successfully rooted.
-=Mac3lite=-
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
EDIT: I just obtained temporary root.. seeing if it sticks.
Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.
phonecapone said:
Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.
Click to expand...
Click to collapse
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?
dwaipayan774 said:
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?
Click to expand...
Click to collapse
It gets detected just the commands fail. There is a white "Secure Phone" line of text across the bottom left. Im going to try loading an sdcard to see if it will auto update anything.
I can't even use Flash Programmer in QFIL or many other apps in QDLOADER 9008 mode. I know the firehose is the correct one yet it never wants to boot. I don't know why.
MTKLogger might have before unless i'm thinking of a different handset here. But as of the moment it doesn't.
No luck with the sdcard. I think it's about time to factory reset this device and put it up for sale. I'll post the firmware here shortly.
Here is the firmware - https://forum.xda-developers.com/android/general/rom-coolpad-defiant-3632a-stock-t3855692
Temporary Root
phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
What did you do? I've been trying for months now.
dwaipayan774 said:
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
Any chance on a repost of the file?
dwaipayan774 said:
Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
hey the link is dead. could you make a new link?
I just want to run a couple of 'setprop' commands to enable cam2api and eis.
To install twrp, we need oem unlock, of course. Once installed, would I be able to connect via usb and run 'adb root', to then do the setprop commands?
I'm just trying to keep it simple, enable cam2api and eis, and go back to stock, if possible.
Sound do able?
Actually, now that I think about it, maybe twrp isn't needed at all for 'adb root'? Maybe just unlock bootloader, device resets, enable dev and adb, connect usb and then 'adb root'?
without oem unlock (iow, as it is now); 'adb root' returns 'adbd cannot run as root in production builds'. But with oem unlock then it may work?
AsItLies said:
I just want to run a couple of 'setprop' commands to enable cam2api and eis.
To install twrp, we need oem unlock, of course. Once installed, would I be able to connect via usb and run 'adb root', to then do the setprop commands?
I'm just trying to keep it simple, enable cam2api and eis, and go back to stock, if possible.
Sound do able?
Click to expand...
Click to collapse
You do not need twrp. You need root access. Even then you cannot just run "adb root" because debugging and secure flags in the default.prop (which is compiled into vendor and boot images) disable that exact command. I was able to find a workaround though. You still need root (systemless should allow ota updates so don't worry about that) but in place of "adb root" run the following.
adb shell
su
mount -o rw,remount -t ext4 /system
exit
This will do the same thing, just through adb shell instead of straight adb.
If you really want to go stock, (no root) you can root the device and download a build prop editor (tons of them on the play store) edit the values you want, then unroot by flashing the stock boot.img. Just keep your bootloader unlocked. You're welcome!
For those following along on this adventure
One thing you can do now, if you haven't already, is be sure you have the (one of the) recent versions of fastboot installed. Older versions don't recognize multiple 'slots' (The A & B slots on the MiA2). The following link has the packages for Linux, Windoh's, and Mac.
To test your fastboot just use 'fastboot -h' and you'll want to see options like '--slot' and '--set-active[=SLOT]. If you have that already, at least this part is accomplished, if not, need to update your fastboot.
https://developer.android.com/studio/releases/platform-tools
Great info @Daha3ker - looking for a simple systemless root now. Trying to keep it all as simple as possible
AsItLies said:
For those following along on this adventure
One thing you can do now, if you haven't already, is be sure you have the (one of the) recent versions of fastboot installed. Older versions don't recognize multiple 'slots' (The A & B slots on the MiA2). The following link has the packages for Linux, Windoh's, and Mac.
To test your fastboot just use 'fastboot -h' and you'll want to see options like '--slot' and '--set-active[=SLOT]. If you have that already, at least this part is accomplished, if not, need to update your fastboot.
https://developer.android.com/studio/releases/platform-tools
Great info @Daha3ker - looking for a simple systemless root now. Trying to keep it all as simple as possible
Click to expand...
Click to collapse
My tool installs systemless and removes it. If you choose root, do what you need to do, then unroot you should be good. The toolkit is about as simple as it gets right now when it comes to rooting.
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Otherwise you can use https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-root-xiaomi-mi-a2-magisk-t3831586
root your phone, do what you like then follow the same steps to flash the stock boot.img instead of the rooted version.
P.S. All root options available right now are systemless unless you install a custom rom.
P.P.S. Setprop commands are used systemlessly (Applied at boot using magisk). so if you unroot, your custom values will not stay. You must edit the actual build.prop
A set of steps to try:
1. Root the device. Toolkit or Manually
2. Install https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US or similar on your phone.
3. Add the following to the end of the build.prop
persist.camera.HAL3.enabled=1
4. reboot phone and verify it is enabled using https://play.google.com/store/apps/details?id=com.airbeat.device.inspector or similar. If level 3 is green then you are good, if not then I may be missing another value that needs changing.
5. unroot the device using the same method you used earlier to root the device. Toolkit or Manually
6. reboot and see if the settings stuck. I am curious to see if it works..
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- rooted phone with magisk installed
- usb data cable
First you have to boot into safe mode which will disable the loading of all magisk modules:
- Turn off the smartphone completely.
- Turn it on normally and when the MIUI logo appears, press and hold the volume down button until the system boots completely, and you see the lock screen, it should also display "safe mode" in the bottom left corner.
Next enable USB debugging on your phone and connect it to a pc, then run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes 'unauthorized' then accept the prompt for authorization on your phone.
Now open an ADB shell from your pc:
adb shell
su
cd /data/adb/modules
ls
This will list all your installed magisk modules. Remove the problematic one with:
rm -r problematic_module
Done, reboot normally!
------------------------- If su command freezes the command line------------------------------
If somehow this does not work, for example you have not granted shell superuser rights before, then you have the following backup options:
run:
adb wait-for-device shell magisk --remove-modules
This should remove all installed modules, and reboot the phone. If it does not work from safe mode, you can try it during the boot animation. (After MIUI logo comes up adb gets enabled (check with 'adb devices' command, if adb is running))
If so far nothing worked you still have a third option to recover you phone/data:
--------------------- Nothing working ---------------------------
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Gorg2331 said:
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- usb debugging already enabled and authenticated (preferrably)
- rooted phone with magisk installed
- usb data cable
all you have to do is connect your phone to your PC and when it shows the MIUI logo during normal boot run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes unauthorized then skip to the "Other Method" section below. If you get back nothing try to run it a couple times during boot. I am not sure when adb gets enabled during the boot but should be around the MIUI logo appearing.
next write:
adb wait-for-device shell magisk --remove-modules
This will delete all magisk modules from your phone, and it reboot it automatically. It should boot up just fine, and all your magisk modules will be deleted.
---------------- Other method --------------------------
If you really need access to the phone, but do not have adb enabled:
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Click to expand...
Click to collapse
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
pjottrr said:
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
Click to expand...
Click to collapse
That is a great suggestion, tho you cannot use any root applications since they will not be loaded. (Even if you install them during safe mode) But it should help sidestep the adb not authorized issue possibly! I incorporated safe mode in the post.
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
pjottrr said:
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
Click to expand...
Click to collapse
Oh you are totally right! You can use safe mode to remove the problematic modules with rm -r. But I think this only works if you have previously granted shell superuser rights. (Since in safe mode you will not get prompts to give SU rights)
I confirm, your guide Is correct. Now i have installed a modules called magisk bootloop saver. Works fine. Do the same thing without digit the adb command.
i'd also suggest in case of BOOTLOOP (cause of bad magisk module)
you can still fastboot
Code:
fastboot flash boot boot.img
the ORIGINAL boot.img of your actual ROM ( so everytime you root keep a copy of the original BOOT.IMG)
in that case you'll be able to reboot your phone ( without root ) and without losing any data !
yes, all these suggestions are good and 100% work! great thread
Booting into Safemode, adb shell and deleting the bad module worked great, thank you!