1. you can reboot phone using edxposed / magisk's rebooter. it work for me.Hello guys!
Just got an S10 and of course, first thing I did was to root it
I installed this rom, but have few questions:
1) Is there any way to have it always boot in magisk root mode ? Instead of having to press bixby + vol up when powering on ?
2) Magisk was working good, I finished installing my programs and everything, and now when I launch magisk it closes directly. when I long press and go to "modules", it doesn't, it's just on main page. when I try to install a module it gives an error saying that I have to install magisk 2.4 first. Magisk seems to still root good because my approved apps still have root access. Any idea how to solve this ?solved by uninstalling/reinstalling magisk manager (cleaning settings was not working)
3) Does Riru EdXposed magisk module have negative effect on phone? Like slowing down or something ? I remembered on my S7 I had this problem because I was first using SandHook version, then it was better with YAHFA. What about S10 ?
Thanks guys, thanks dev
1. Well even the integrated reboot restart in recovery (ie magisk system) in this rom. But I was more talking about power on from powered off phone. Anyway it's true it's not often that it will be completely powered off so I guess it'll be ok to press the 3 buttons when it happens
Is booting in twrp because you didn't patch your twrp.
Is the only one tested. Other twrp might work also.
Ok. I have the SM-G970F. I used Samfrim to download the latest firmware. It downloaded SM-G970F_1_20201028044204_tm4iurcth4_fac.
dirty flashed 7.1 from 7.0 and could not get past lockscreen.??.. system always reverts to lockscreen... so I restored my 7.0 backup.BeyondRom V7.1
Based on Android 10 - G97xFXXU9DTJA
Devices Supported: G970F(D), G973F(D), G975F(D)
ROM Features
<*>Aroma choices: full/dirty wipe, debloating, Bixby key remapping, Emoji</*>
<*>Supports G970F(D), G973F(D) and G975F(D)</*>
<*>Base Android 10 G975FXXU9DTJA odex/deodex Nov 2020 patch level</*>
<*>Stock Samsung kernel</*>
<*>CSC features (camera sound menu, call recording, LTE only mod, camera during call, etc)</*>
<*>Knox partially removed, AppLock</*>
<*>Included the security bypass from Ian’s multidisabler</*>
<*>build.prop tweaks: multiuser, call ring delay, SHealth fix, BT passwords remember</*>
<*>Dual SIM + SD Card, allow screenshots in secure apps, mock locations</*>
<*>Reboot directly in rooted system from power menu (modded services), disable high volume warning</*>
<*>Possibility to choose in aroma to remove the boot warning</*>
Added/fixed in v7.1
<*>Updated to Nov 2020 FW</*>
To be added/fixed
<*>Fix the secure folder </*>
Credits
- John Wu for Magisk
- IanMacd for his multidisabler
- IanMacd and Oleg for the libbluetooth fix
- IanMacd & Geiti for the TWRP
- SuperR for the kitchen
- WinB33 for the FontPack
- All people who helped me with ROM testing (especially Alan, Carlos, Claude, Jay and others)
- S10e testers: Mathias and Ragaaci
Download Links for G970F(D)/G973F(D)/G975F(D)
[FONT="]Gdrive Link[/FONT]
[FONT="]Digi Link[/FONT]
ALWAYS CHOOSE REBOOT TO RECOVERY AFTER FLASHING THE ROM !!!
Installation procedure
1. If you are coming from Pie, please use the attached guide.
2. If you are already on Android Q rooted with stock patched recovery, flash Ian’s latest TWRP (3.4.0-3 or newer) (patch it with Magisk Manager before you flash it on your phone) in Odin (AP slot), Ian’s latest multidisabler (v2.6 or newer) then BR 7.x in TWRP
3. If you are already on Android Q rooted with Ian’s latest TWRP (3.4.0-3 or newer), just flash BR 7.x in TWRP
In any of the above cases, MAKE SURE THAT YOUR DATA PARTITION IN NOT ENCRYPTED!!!
If your /data partition is encrypted, flash Ian’s latest Q multidisabler (v2.6 or newer) and format your data in TWRP after flashing the multidisabler (Wipe data, reply YES when asked in TWRP). Beware that your ENTIRE internal SD will be wiped.
After the first boot, when you start Magisk Manager for the first time, reply with YES (agree to reboot) after MM have setup your root environment.
Advises
0. DON'T START FLASHING BRx WITHOUT A FULL TWRP BACKUP !!! Backup to PC your important files: documents, pictures, contacts, SMS, etc.
1. Is strongly advisable clean flash if coming from Pie. You can try to restore your previous saved data with TWRP but issues can arise.
2. If you have issues/errors flashing the ROM zip: check rom zip MD5 hash
3. If you consider that the modded services are the culprit for your SnapChat ban, use stock services.jar (dirty flash again the ROM)
4. If you like my work, consider buying me a coffee (PayPal link)
Helpful links
Telegram chat
PayPal link
Happy flashing good people!
Maybe you need to update also the bl, modem and other things flashing stock in odin if it doesn't work the above mentioned steps. We cannot test the update from all fw versions to latest fw.Hi all, I'm still on BR 6.2 with my s10+.
Read through all posts I think, but unsure: can I dirty flash to latest? Steps for that? Would this be correct:
0. Make full backup (titanium anyways, but also full twrp backup)
1. Get latest twrp zip onto phone.
2. Upgrade Magisk Manager
3. Use magisk manager to patch zip from step 1.
4. Reboot into current twrp.
5. Flash new patched TWRP from inside current twrp (is that possible? Or must it be done via Odin from PC?)
6. Reboot from twrp into new patched TWRP
7. Anything else (multi-disabler??) to re-flash before flashing latest BR?
8. Flash latest BR
9. ???
What about these after ashing flashing latest BR, do they all need a reinstall, or will they survive?:
Riru core, riru edexposed (sandhook version), smali patcher, nanodroid microg
Sorry if this sounds like "he hasn't got a clue" ... haven't done this with BR before (but 100 times on our previous S4s and various tabs with LOS) just don't wanna break our phones and end up spending hours to setup everything from scratch for me and my wife's.
Stay healthy
Gesendet von meinem unknown mit Tapatalk
And how would you want people to guess what version of twrp you have, patched or not, have you rebooted in recovery after flashing 7.1, etc. Usually I don't even reply to people that don't bother to give details of what they've done. You didn't even mentioned which device you have.
