Related
Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part
You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2
Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!
Next time don't be a twrp and use twrp
dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
I installed the update like i normally did. Went into magisk and installed Magisk on the "After OTA" setting. Now it's boot looping. I'm NOT using TWRP. This is the first time this has happened. Normally I update the OTA, DONT RESET, install Magisk on OTA setting and reboot and it works fine. Anyway to fix this? It boots 90%, but once it gets to main screen RIGHT before it asks for my PIN, it goes to 'rebooting'. Do I need to wipe my phone and start over?
I'm not rooted but From my experience you have to delete modules folder in twrp
RISHI RAJ said:
I'm not rooted but From my experience you have to delete modules folder in twrp
Click to expand...
Click to collapse
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
whitak3r said:
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
Click to expand...
Click to collapse
Only disabling modules won't help,You have to delete the folder,Next time when you update
RISHI RAJ said:
Only disabling modules won't help,You have to delete the folder,Next time when you update
Click to expand...
Click to collapse
Thank you. I'll do that next time, would of saved me a bunch headache if I would of just read a little bit lol
I ended up cleaning my system and everything went back to stock root. So I updated magsik and magisk man. And it fixed everything. I'm in the processes of reinstalling all my stuff now though
For me, there is only one module causing problems - the OOS call recorder enabler.
I simply remove that module and reboot before starting the OTA and all was fine.
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Is this a bug of Magisk?
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
Hi, can you use this command on adb shell? OnePlus 7T Pro doesn't have TWRP yet. Thanks.
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
This. But the module clearly says REMOVE before attempting upgrade!
And like I suppose most people here - I also did not follow that instruction and ended up with a bootloop. lmao. :good:
If you have TWRP you can remove modules if you have a bootloop.
I upgraded to Android 10 using a guide from someone who successfully kept root when upgrading from Android Pie to 10. I followed the steps exactly, but I still lost root. I'm using the latest version of TWRP Guacamole for the OnePlus 7 Pro. I fully understand that it's not fully compatible with my phone so I'm wanting to roll back to Pie. My phone currently does not have an OS on it because another guide I followed said to flash TWRP as the boot in the bootloader in order to reboot into TWRP to then reflash the OTA and then TWRP. I did this because TWRP would not mount my storage and therefore could not install or flash anything because it couldn't access storage. That didn't work. So now when I boot normally or into TWRP, it only boots into the bootloader. I need help fixing this because now I'm out of a very nice phone.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
unrated87 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
That did not work. Everytime I hit the hyperlink for the tool, it redirected me to an ad for a network monitoring software called solarwinds.
BUZzZERBeater00 said:
That did not work. Everytime I hit the hyperlink for the tool, it redirected me to an ad for a network monitoring software called solarwinds.
Click to expand...
Click to collapse
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
blas4me said:
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
Thank you. I'm going to try it when I have time. I had to go through a few links that your initial link let me to. I found this thread. I'm hoping this will work. Sounds a lot like my problem.
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
blas4me said:
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
I tried using the MSMDownloadTool, but the Qualcomm HS-USB QDLoader 9008 (COM3) driver was grayed out in the device manager. When I would open the MSMDownloadTool, it would not recognize my device, and would not download anything. Any suggestions?
BUZzZERBeater00 said:
Thank you. I'm going to try it when I have time. I had to go through a few links that your initial link let me to. I found this thread. I'm hoping this will work. Sounds a lot like my problem.
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
Click to expand...
Click to collapse
I fixed it. These links helped me along the way. Thanks again for the initial suggestion!
https://forum.xda-developers.com/one...t3896765/page2
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
BUZzZERBeater00 said:
I fixed it. These links helped me along the way. Thanks again for the initial suggestion!
https://forum.xda-developers.com/one...t3896765/page2
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
Click to expand...
Click to collapse
Suggestion, when you get to stock, stay there. If it's taking you this long to figure things out, this is not your thing.
blas4me said:
Suggestion, when you get to stock, stay there. If it's taking you this long to figure things out, this is not your thing.
Click to expand...
Click to collapse
Sorry. It's too late. I already have Magisk installed and Edxposed.
I just installed Edxposed
blas4me said:
I just installed Edxposed
Click to expand...
Click to collapse
Ya. It worked perfectly as long as I flashed Riru - Core, rebooted, then flashed Riru - Edxposed, rebooted. Then installed the Edxposed apk. Flashing both Riru -Core and Riru - Edxposed back-to-back before rebooting put my OnePlus 7 Pro into a bootloop. I had to boot into TWRP and flash a "Magisk in TWRP" module and then in the terminal type "mm for first time" hit enter, and type "c" which put takingmy phone in Core Only Mode. This disabled the modules it out of the bootloop. But then after it reboots, attempt to uninstall the modules, which won't fully work. So basically you'd just have to flash the magisk uninstaller and flash the magisk installer to get rid of the bad modules. Moral of the story is don't flash both Riru - Core and Riru -Edxposed without rebooting between each install. Also, don't just flash the magisk uninstaller and flash the magisk installer to get rid of the bad modules and then not later flash the "Magisk in TWRP" module and disable Core Only Mode. Or just turn it off in Magisk Manager. Modules will install, but they won't work. And they won't uninstall either.
Folks,
I had rooted my RM 3S with Magisk which worked fine for couple of days until I installed Edxposed zip via Magisk. Device is in boot loop.
Can access recovery..
Any suggestions or help greatly appreciated. Please help.
Device from India running on 1.16 (I guess)
Aru
B01070 said:
Folks,
I had rooted my RM 3S with Magisk which worked fine for couple of days until I installed Edxposed zip via Magisk. Device is in boot loop.
Can access recovery..
Any suggestions or help greatly appreciated. Please help.
Device from India running on 1.16 (I guess)
Aru
Click to expand...
Click to collapse
Can you access internal memory from recovery on comp? If so, load the latest update.zip from rm on root of memory, then in recovery, hit install update
suzook said:
Can you access internal memory from recovery on comp? If so, load the latest update.zip from rm on root of memory, then in recovery, hit install update
Click to expand...
Click to collapse
Thanks suzook for your quick response. I don't have access to comp, but I doubt I will have access to internal storage. However, can I connect an otg with the zip and install via Recovery Vol up + power, I see that there is an option tk do it?
Any advise?
Aru
Also I only have an option to install from. Otg and not from internal storage..
B01070 said:
Thanks suzook for your quick response. I don't have access to comp, but I doubt I will have access to internal storage. However, can I connect an otg with the zip and install via Recovery Vol up + power, I see that there is an option tk do it?
Any advise?
Aru
Click to expand...
Click to collapse
That will work
Do yourself a favor, and install twrp, so you can restore a backup incase of a bootloop
suzook said:
That will work
Do yourself a favor, and install twrp, so you can restore a backup incase of a bootloop
Click to expand...
Click to collapse
It's mid night in here.. Will try morning and will keep you informed. Thanks.
I have not seen twrp for 3s and was skeptical.. But looks like I need it...
Aru
B01070 said:
It's mid night in here.. Will try morning and will keep you informed. Thanks.
I have not seen twrp for 3s and was skeptical.. But looks like I need it...
Aru
Click to expand...
Click to collapse
The twrp for the rm3 here, works fine. Been using it for 3 days.
suzook said:
The twrp for the rm3 here, works fine. Been using it for 3 days.
Click to expand...
Click to collapse
Can you please help me with the twrp link? It is missing in your reply.
Aru
B01070 said:
Can you please help me with the twrp link? It is missing in your reply.
Aru
Click to expand...
Click to collapse
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
suzook said:
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
Click to expand...
Click to collapse
Thanks suzook... I now got back access to my phone.. Obviously, lost root access... Will install the patched boot img... Post that will install twrp..
Finally, still curious why Edxposed caused bootloop..
Aru
B01070 said:
Thanks suzook... I now got back access to my phone.. Obviously, lost root access... Will install the patched boot img... Post that will install twrp..
Finally, still curious why Edxposed caused bootloop..
Aru
Click to expand...
Click to collapse
suzook said:
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
Click to expand...
Click to collapse
Though I got access to my phone, I am not able to obtain root... I install the patched img through fastboot, but end up in bootloop..
I believe the EdExposed module that I installed in Magisk is the culprit.. I tried uninstalling and reinstalling Magisk Manager.. Same bootloop issue..
Any idea on how to resolve this issue.. Cheers!
Aru
B01070 said:
Though I got access to my phone, I am not able to obtain root... I install the patched img through fastboot, but end up in bootloop..
I believe the EdExposed module that I installed in Magisk is the culprit.. I tried uninstalling and reinstalling Magisk Manager.. Same bootloop issue..
Any idea on how to resolve this issue.. Cheers!
Aru
Click to expand...
Click to collapse
Module installed in Magisk was the reason for bootloop.. Once after acquiring root, when the phone is in bootloop, entering the below command from computer will remove all modules in Magisk...
adb wait-for-device shell magisk --remove-modules
Hope this helps someone in need..
Aru
suzook said:
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
Click to expand...
Click to collapse
suzook, how did you install twrp? I tried to install with the below commands, commands executed successfully, not no TWRP recovery.. Any thing did I miss?
adb devices
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
Aru
B01070 said:
suzook, how did you install twrp? I tried to install with the below commands, commands executed successfully, not no TWRP recovery.. Any thing did I miss?
adb devices
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
Aru
Click to expand...
Click to collapse
I have major issues....reboot to twrp, as soon as you flash it...then flash magisk to keep it flashed......MY Rm3s is F'd.
suzook said:
I have major issues....reboot to twrp, as soon as you flash it...then flash magisk to keep it flashed......MY Rm3s is F'd.
Click to expand...
Click to collapse
I can't reboot to twrp.. I go only into stock recovery.. Don't know if it good or bad.. For now, everything is in order.. Hopefully nothing would go wrong.. I restarted atleast dozen times...
Aru
some magisk modules gave me bootloop many times, i used twrp file manager to remove xxxx
location is data/adb/modules/xxxx
Is anyone running xposed modules? I see this "Xposed modules with Taichi" and edxposed which caused you to bootloop. I guess i can just backup with TWRP and try it...
I mainly want to remove all ads for now.
Any recommendations for magisk/xposed modules?
crusnikmachine said:
Is anyone running xposed modules? I see this "Xposed modules with Taichi" and edxposed which caused you to bootloop. I guess i can just backup with TWRP and try it...
I mainly want to remove all ads for now.
Any recommendations for magisk/xposed modules?
Click to expand...
Click to collapse
I don't have an answer to your question but I wanted to ask you about your rooting process. When I flashed either twrp or installed magisk I lost wifi connectivity. Logcat confirms something's going on. Have you run into this by any chance?
I was worried about installing edxposed after reading this thread and a few others, but I went ahead and went on with the install and it works for what wanted. Granted I don't install many modules I only use xinsta...
I installed the riru core and riru edxposed in magisk. At first restart the edxposed manager said it was installed but not activated. I went ahead and installed a edXposed module, ignoring the notification that edXposed framework was not active but installed(also in settings check the setting for "Skip status check"), activated my module and restarted. Later the edxposed manager would say edxposed framework is active and my module works.
As for wifi not working, I had ran into that problem as well, only because I skipped the part in the root/twrp guide for the rm3 about downloading the firmware, extracting the boot.img, having magisk patch it, then reflashing the patched boot image with adb. I did just that and wifi works. I have yet to have a bootloop problem or a need for the rm3s "unbrick tool." ?
Only issue im having is cellular connection, but that is probably due to this phone lacking band 13 on Verizon.
B01070 said:
Folks,
I had rooted my RM 3S with Magisk which worked fine for couple of days until I installed Edxposed zip via Magisk. Device is in boot loop.
Can access recovery..
Any suggestions or help greatly appreciated. Please help.
Device from India running on 1.16 (I guess)
Aru
Click to expand...
Click to collapse
The same thing happened to me, I had to do the following:
1-download official filmware (NX629J-update)
2-once loaded unzip using winrar or 7 zip
3-search through the folders and take out the recovery.img file and flash it through adb
3-copy filmware at the root of a USB and look for a USB OTG
4-go to recovery and install the filmware the first time it will not boot
Restart recovery again and perform wipe data and cache. I hope it serves you greetings.