:crying:Hi guys,
I have rooted my OnePlus 7 with magisk and twrp installed.
I'm on latest oos 10.0.2.
I tried to install Edxposed framework via magisk and I ended I bootloop.
I couldn't enter recovery in between the bootloop so I waited until a full power down.
During bootloop the phone got heated up and I'm worried that the overheat generated might have effected my device hardware.
Can someone pls tell me about this..
Will something happen or already happened to my device hardware with that overheat???
Phvr said:
:crying:Hi guys,
I have rooted my OnePlus 7 with magisk and twrp installed.
I'm on latest oos 10.0.2.
I tried to install Edxposed framework via magisk and I ended I bootloop.
I couldn't enter recovery in between the bootloop so I waited until a full power down.
During bootloop the phone got heated up and I'm worried that the overheat generated might have effected my device hardware.
Can someone pls tell me about this..
Will something happen or already happened to my device hardware with that overheat???
Click to expand...
Click to collapse
Hello, there are thermal sensors that will prevent overheating. cpu will throttle down for example if the temperature is too high
GuestD1057 said:
:crying:Hi guys,
I have rooted my OnePlus 7 with magisk and twrp installed.
I'm on latest oos 10.0.2.
I tried to install Edxposed framework via magisk and I ended I bootloop.
I couldn't enter recovery in between the bootloop so I waited until a full power down.
During bootloop the phone got heated up and I'm worried that the overheat generated might have effected my device hardware.
Can someone pls tell me about this..
Will something happen or already happened to my device hardware with that overheat???
Click to expand...
Click to collapse
You will be fine, but you could always get in bootloader mode by holding both Volume and power button to shut it down, and them boot into bootloader.
Once you are in bootloader, boot your phone in recovery using fastboot boot recovery-image.
Once you are in recovery, you can do magisk uninstaller.
If you don't have those files on phone, you can run from adb
Boot into twrp and flash magisk disabler file
https://forum.xda-developers.com/apps/magisk/magisk-v16-3-magisk-modules-remover-t3776718/amp/
Related
Not able to get into TWRP recovery, stuck on "Your device is booting now..."
Hey everyone,
I just unlocked my bootloader and now want to flash TWRP and SuperSU. My Phone is already Nougat with Emui 5.
The Problem is that I'm just not able to enter the recovery. When pressing volume down + power or trying "adb reboot recovery" in the command line, the phone starts in the "unlocked bootloader warning screen". But not like in the normal warning screen it doesn't give me options but just shows a white line saying "Your device is booting now..." and thats where it gets stuck. Only gets hotter...
The fun thing is I already was in the recovery but wasn't able to flash the SuperSU (r275). Maybe it was not compatible with Nougat. TWRP just couldn't mount various things. After reflashing the recovery below instead of some other version (don't know anymore) I'm not able to enter the recovery again.
Feels like I searched the whole Internet and there is nearly nobody with the problem or a solution. Tried this as well: https://forum.xda-developers.com/honor-8/help/honor-8-boot-to-twrp-recovery-lost-root-t3567462. It seems like nobody who published a Honor 8 + Nougat + TWRP + SuperSU "How To" acutally tried it himself.
I used this TWRP https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Please help me I can't use WhatsApp because I need to restore it with Titanium (Database way doesn't restore all chats... Other problem)
Thanks everybody I just can't stand this anymore
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
sysak said:
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
Click to expand...
Click to collapse
Thank you I got it!
So I got my L09 with Nougat/Emui 5 on it. Then just used TWRP from https://forum.xda-developers.com/showpost.php?p=70228949&postcount=252 (bootable, think ist ist 3.0.2.0) then flashed 3.1.1.0 from https://forum.xda-developers.com/honor-8/development/twrp-t3566563 (bootable) and finally flashed SuperSu from first Link again. Other SuperSU versions (like the phh r275) WERE NOT flashable.
Magisk is the most compatible root solution for the Honor 8 on Nougat. The only thing that doesn't work (seamlessly) is MagiskHide, but the root itself works and flashes fine from TWRP.
I have tried to flash twrp multiple times to no success. I have tried multiple variations of the tool but for some reason when I go try to boot into recovery it takes me to erecovery which fails to do anything.
Are you sure about button combination
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
sysak said:
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
Click to expand...
Click to collapse
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Dalg1991 said:
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Click to expand...
Click to collapse
Try adb reboot recovery in command line on your PC when phone is turned on
0mrwhatsupguy0 said:
Try adb reboot recovery in command line on your PC when phone is turned on
Click to expand...
Click to collapse
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Few problems with Binary SU and BusyBox
My phone seems to be rooted. Titanium Backup works but I have to accept every App instalation manually. With other settings restoring gets stuck. Also SuperSU reminds me every time that my BinarySU needs an actualisation but fails if it tries. And finally BusyBox just isn't able to get itself installed.
I'm thinking about restoring stock firmware, update to Nougat, and flash the two TWRP Versions and SuperSU again but hate to spend ours on my phone. OnePlus One rooting was sooo easy...
Dalg1991 said:
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Click to expand...
Click to collapse
Is there a number of times you have to do it? How should I transition from this stupid "Your device is an enemy of the state" screen to something that will connect to adb?
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
mavera said:
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
Click to expand...
Click to collapse
Magisk does not change anything in system folder. Magisk is not enabled therefore I cannot install busybox. In Emui9 there was a workaround but seems it doesn't work anymore.
You must press to volume up and power buttons when opening for magisk enabling.
SonOfTheRain said:
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
Click to expand...
Click to collapse
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
ante0 said:
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
Click to expand...
Click to collapse
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
SonOfTheRain said:
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
Click to expand...
Click to collapse
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
ante0 said:
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
Click to expand...
Click to collapse
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
SonOfTheRain said:
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
Click to expand...
Click to collapse
I haven't actually tested what happens if battery dies. It will loop if you shut down.
ante0 said:
I haven't actually tested what happens if battery dies. It will loop if you shut down.
Click to expand...
Click to collapse
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Azan Mughal said:
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Azan Mughal said:
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Click to expand...
Click to collapse
Here you go
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
Thanks bro
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
this file is for root?
Hi guys, so i have an untouched p10 on the version above, to install magisk is it as easy as asking one of you for the RECOVERY_RAMDIS.img (not yet in the firmware database) and patch it if it hasnt using pc then also on the pc rebooting to recovery and done? Also has restart and flat battery been tested? I read above that you must use shutdown
Its a vtr-l29 if it makes a difference
Hi all,
today I updated Magisk on my H830 (stock H83030c with TWRP) and now it's stuck in a boot loop.
Since the phone does not support flashing in fastboot, is there any way to fix this without re-flashing a stock kdz?
<edit>
The phone is showing the "bootloader unlocked warning", then flashes black and shows the warning again, over and over.
I can't enter TWRP, only fastboot and download mode.
Thanks,
schalli110
Never mind.
Mashing the power button like crazy finally got me into TWRP and I was able to reflash a stock boot.img and then an old version of Magisk.
Phew.
I'll leave this thread in the hopes it helps other poor souls.
I have the exact same problem (thanks Magisk team!). Can you expound on the power button technique that allowed you to access TWRP? By repeatedly pressing it?
Funny, I've seen multiple posts about this happening on G5 phones after the Magisk update, but nothing on the Magisk threads.
Good day, don't know if this is right place to ask, have searched site for similar threads to no avail? I have a Samsung A10s, (sm-a107f) with Android 10, Magisk 22.1 installed, no ramdisk, SAR yes, flashed stock kernel with patched AP. Boot into Magisk via recovery, all good , phone rooted, but will no detect sim card, aeroplane mode dimly lit, cannot toggle, if i boot phone normally (no magisk root ) the siim card is detected, making me think that the problem lies with Magisk, could someone kindly advise, Cheers in advance. Bruce
Confused: Magisk Recovery? Never heard of that.
jwoegerbauer said:
Confused: Magisk Recovery? Never heard of that.
Click to expand...
Click to collapse
sorry maybe not explaining it clearly, will to to explain as I understand it. Because of no ramdisk, you install magisk into recovery, to get to magisk root you have to push power and volume up buttons as though you were wanting to boot into recovery, hence me calling it magisk recovery, if you just push power button the phone boots into unrooted mode, hope that explains it.
i
Hi still need help with original request , would really appreciate it. simple steps if you could
My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?
Shahriar566 said:
My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?
Click to expand...
Click to collapse
Pixel with magisk and modules?
No I was just installing magisk via TWRP
try installing magisk via image patching, works for me everytime. Magisk creator himself warn against using TWRP to flash magisk.zip
I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk
Shahriar566 said:
I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk
Click to expand...
Click to collapse
Tried flash official MIUI recovery ROM with TWRP?
Tried official MIUI fastboot rom not recovery
Shahriar566 said:
Tried official MIUI fastboot rom not recovery
Click to expand...
Click to collapse
Put the fastboot ROM in C drive directly, then go into the folder, find the "flash_all.bat" to flash it under fastboot mode.
Don't use Mi-Flash.
Can try the recovery flashing method with TWRP.
Check if you still got mobile SIM card working, with the original intact IMEI.
I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear
Shahriar566 said:
I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear
Click to expand...
Click to collapse
Rename the folder name shorter, like "ROM."
Phone needs to be in Fastboot mode, before running that flash_all.bat.
There could be some issue connecting your phone with the PC. Could be driver issue, permission issue, AMD CPU issue and/or other reasons.
Try TWRP to flash the recovery ROM would be easier.
Remember to "Format data" in TWRP.
Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?
Shahriar566 said:
Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?
Click to expand...
Click to collapse
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.
Thanks for the advice
pl1992aw said:
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.
Click to expand...
Click to collapse
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?
Shahriar566 said:
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?
Click to expand...
Click to collapse
Unknown reason. Don't know if it's ROM issue or hardware issue.
Can try downgrade to old firmware versions.
Can also try older ROM versions.