dual boot patcher - Sprint Samsung Galaxy S7 Guides, News, & Discussio

I have successfully flashed dual boot patcher without bootloops through flashfire , unsure though if working correctly , and tests ,I have app installed and utilities zip flashed through flashfire ,I used the s7 edge files to make this flash

Related

Magisk safety net not working

Yesterday i fully rooted my phone using magisk . Before rooting it i switched OEM Unlock normally. So heres my questions:
1. Why the safety net not working , im using modified magisk 16.3 ( Also 16.7 not working properly )
2. Why the OEM Unlock still need to factory reset my phone , and after it , OEM Unlock still stay locked.
3. Also i was trying to flash custom kernel but phone wasnt booting .
4. Before i rooted my phone i flashed newest android update via odin . This might be option i facing this problems?
Officially fixed my problem with flashing rom TeamExyKings ROM N8.0 BRGA.

Bootloop caused by xposed Module

—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Master Luca said:
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Click to expand...
Click to collapse
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
Still in boot loop ( I let it boot for 18 min )
Did you tried to disable xposed on booting?
There is key combination when system boots up, to disable xposed, and so all modules.
Go into recovery, and boot up again from there (normal boot), and when logo appears click at least 3 times power button, and xposed will understand it need to disable itself.
That should work.
And if you have some data in phone, you can make app backup from recovery and if you have files you can connect to PC and copy those files on PC.
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
brasscupcakes said:
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
Click to expand...
Click to collapse
go in twrp and to android/adb/modules.. module there reboot phone
bilausdaniel said:
go in twrp and to android/adb/modules.. module there reboot phone
Click to expand...
Click to collapse
delete that module in there

Bootloop cause magisk

I had a boot loop trying to install a module.I am in build 11.0.11 without twrp.I used the command adb wait ... to remove modules via adb but the problem didn't solve.After that I reinstalled the stock rom and the phone reboots. But when I tried to reinstall magisk using the patched img via adb I had bootloop again so I reinstalled again the rom. What can I do to solve the problem?
You are probably flashing the wrong boot.img for the firmware you are on perhaps?
Make sure it is the patched.img from here you flash https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/post82207833
Credits: @Sapper Morton
Thanks for the answer, but it isn't the boot.img, the specific module (sony music!) was the problem..
At last I installed twrp using the q- base twrp.img and I disabled this module via twrp and the magisk manager for recovery....The phone booted normally with the others modules to work fine...

Question about installing TWRP

I have an already rooted galaxy a105m with magisk installed, however twrp didn't exist for the a10 when I rooted and installed magisk so I still have the stock recovery. How do I go about installing twrp? Preferably I'd like to not have to wipe my phone but If I have to it's ok.
Edit: Welp I'm dumb, all I had to do was dl the twrp img off of the main root guide, download the twrp official app from playstore, and flash.
Alex_x90 said:
I have an already rooted galaxy a105m with magisk installed, however twrp didn't exist for the a10 when I rooted and installed magisk so I still have the stock recovery. How do I go about installing twrp? Preferably I'd like to not have to wipe my phone but If I have to it's ok.
Edit: Welp I'm dumb, all I had to do was dl the twrp img off of the main root guide, download the twrp official app from playstore, and flash.
Click to expand...
Click to collapse
Hiii I wanted to ask if the twrp official apk worked on your Samsung a10s...As am speaking I have it installed for some time now but it didn't work,it just on loading mode forever.
If you're already rooted you can download the TWRP img I used here (literally copied from the root guide) and flash via the twrp app (or whatever flashing app you want, that's just the one I used). However, if you're not already rooted I definitely suggest you follow the whole guide so you don't make any mistakes/mess anything up here.

LG2 - D802 - Magisk BootLoop

Hello ,
I have a LG2 D802. My LG2 is rooted and i have TWRP. I installed its with "LGG2-D80230d-OneClickRootRecovery", witch i found on XDA. Thanks so much.
Next step , I tried to install Magisk v20.4 with TWRP. After that i have a boot loop. I restored my boot partion with TWRP and my backup. After that my apk SuperSu isn't correctly install.
I would like to kown with Magisk's version works fine on LG2 ?. What i made wrong ?
Can i install again SuperSU (zip "UPDATE-SuperSU-v2.46" finds in LGG2-D80230d-OneClickRootRecovery) with TWRP ?. No bootloop risks ?
Thanks.

Categories

Resources