Database Info

5.0.2-010 05 update downloaded should I use

Just got this phone new from cricket. I'm having issues making calls. I downloaded the update. But am wondering should I use it. I'm wanting to do custom roms exc. I have not unlocked boot loader or anything yet. If I do the update will I still be able to unlock the boot loader and root custom roms exc? 6045o is the type

First of all I suggest unlocking the bootloader, because if you update to MM you will lose fastboot commands (you can have them back but it's tedious). Then maybe install the latest TWRP, update to MM and then systemless root or custom ROM If you want to update to latest official firmware but don't want to lose TWRP/root just download the update without installing it and then flash it with chainfire's FlashFire.

thanks
plumbe0 said:
First of all I suggest unlocking the bootloader, because if you update to MM you will lose fastboot commands (you can have them back but it's tedious). Then maybe install the latest TWRP, update to MM and then systemless root or custom ROM If you want to update to latest official firmware but don't want to lose TWRP/root just download the update without installing it and then flash it with chainfire's FlashFire.
Click to expand...
Click to collapse
thanks i have twrp recovery and unlocked boot loader. next step. im wanting to b able to play pokemon go. chainfire requires root. i havent rooted yet. because i know pokemon go wont work. any ideas what i can do? p.s. already backed up system image boot and efs. thanks again.

Luckeyleo said:
thanks i have twrp recovery and unlocked boot loader. next step. im wanting to b able to play pokemon go. chainfire requires root. i havent rooted yet. because i know pokemon go wont work. any ideas what i can do? p.s. already backed up system image boot and efs. thanks again.
Click to expand...
Click to collapse
First of all make sure you never mount /system as rw when using TWRP.
Then just do a systemless root (download SuperSU from chainfire website on your phone, launch TWRP's terminal and type "echo SYSTEMLESS=true>>/data/.supersu", then flash SuperSU as usual), systemless root won't be detected by apps/os. Will probably be detected by SafetyNet but i'm not sure PoGo uses it. In case you have problems with root detection you can try suhide by Chainfire.
Also note that systemless Xposed (rootcloak, etc) and V4A are possible via Magisk (just search it on XDA).

Transition from SuperSU to Magisk

So I'm currently using Honor 8 FRD-L09432 on B394 build. I have unlocked bootloader and am rooted with SuperSU. I wish to remove SuperSU root and switch to Magisk. From Magisk thread instructions I'm supposed have unrooted device and intact boot image.
When I try to unroot with SuperSU I'm greeted with "Uninstallation failed!" window. As an alternative to unroot I decided to just use Huawei Firmware Finder and download latest(B394) update.zip and extract stock boot.img from that. After successfully managing the extraction I tried to flash the newly extracted boot.img via TWRP. My device fails to boot with said boot.img so I had to restore the back up.
So my question is what am I missing here? Or is there some other alternate way to switch to Magisk without rollbacking to stock packages and having all my data wiped. Thanks for your assistance.

Osmosis' unsupersu script should work to remove it, then reboot, then flash magisk.

Hi,
I have the FRD-L04 with the B389 update. I am currently root with SuperSU, and I would like to change to Magisk. I have been reading some guides and posts but I want to be sure before proceeding. I found this guide for the Pixel and I would like to know the opinion from the experts if this would work for my honor 8. Thanks!

juanboja said:
Hi,
I have the FRD-L04 with the B389 update. I am currently root with SuperSU, and I would like to change to Magisk. I have been reading some guides and posts but I want to be sure before proceeding. I found this guide for the Pixel and I would like to know the opinion from the experts if this would work for my honor 8. Thanks!
Click to expand...
Click to collapse
You will need stock boot image, that's pretty much all. So you can try to restore the stock boot image via unroot from SuperSU which is a bad idea and I would highly discourage it. So you either extract the stock boot image for B389 from UPDATE.zip or you restore stock boot image from your own backup if you have it.
After obtaining and flashing stock boot image, flash the Magisk zip from main Magisk thread. I can not verify that latest version works (16.0), I havent tried it. I'm personally on 15.3 and if you really want it I can test 16.0 for you.
After flashing Magisk install Magisk manager which you can obtain again from main Magisk thread. Ofc unistall SuperSU app as well.
You can't brick your device in any way as long as you make a full TWRP backup before attempting any of the above. If you run into any of the errors just restore it and ask for further instructions.

Thanks for the set of instructions, I did as instructed and it worked as a charm! Thanks for everything. I'm in B389 with Magisk now!
Sent from my FRD-L04 using Tapatalk

juanboja said:
Thanks for the set of instructions, I did as instructed and it worked as a charm! Thanks for everything. I'm in B389 with Magisk now!
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Hide function works well with apps that don't work with root, like Google Pay or home banking?

zinko_pt said:
Hide function works well with apps that don't work with root, like Google Pay or home banking?
Click to expand...
Click to collapse
Sorry but I don't use those apps... maybe somebody else can give you feedback.

Can I just Flash TWRP (already unlocked, rooted with Magisk installed)

I cannot find anything on point to this direct question (all the guides/forums seem to have you flashing/installing TWRP first then installing Magisk).
I am already unlocked and installed Magisk/rooted with Magisk SU by using the Magisk Manager method with stock recovery.
At this point can I just flash/install TWRP to have a custom recovery without issue? I ask because I want to try out J to the 4n's Active Edge plus but want to make a backup first before tinkering with it. Loved his stuff as a long HTC viper guy.
Thanks in advance.

bakemcbride21 said:
I cannot find anything on point to this direct question (all the guides/forums seem to have you flashing/installing TWRP first then installing Magisk).
I am already unlocked and installed Magisk/rooted with Magisk SU by using the Magisk Manager method with stock recovery.
At this point can I just flash/install TWRP to have a custom recovery without issue? I ask because I want to try out J to the 4n's Active Edge plus but want to make a backup first before tinkering with it. Loved his stuff as a long HTC viper guy.
Thanks in advance.
Click to expand...
Click to collapse
I cannot find the specific thread (if I do find it I will update) but from what I recall you will need to flash an unpatched boot img and then flash twrp. After that you can reinstall Magisk. I know TWRP modifies the boot so that will interfere with Magisk. I hope this was helpful.

xBlu3 said:
I cannot find the specific thread (if I do find it I will update) but from what I recall you will need to flash an unpatched boot img and then flash twrp. After that you can reinstall Magisk. I know TWRP modifies the boot so that will interfere with Magisk. I hope this was helpful.
Click to expand...
Click to collapse
Extremely helpful! Sounds like I would boot loop the phone if I just flashed TWRP in my current configuration.
I'll uninstall magisk, reboot, then flash the stock boot.img and then follow the twrp/magisk install directions.
Much appreciated!

Here's what I did:
1) Boot twrp img file from fastboot
2) Flash the latest twrp zip in twrp. DON'T REBOOT. If you are going to use a custom kernel, you must do step 3 below. Don't later reboot and flash a custom kernel or you can run into bootloader signature issue. If you ARE NOT going to use a custom kernel, jump to step 4.
3) Flash your custom kernel.
4) Flash the latest Magisk zip to root again
5) Reboot.
Enjoy

update to 9.5.9 bootloop, only fix was twrp bootloop fix but removed root

As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data

https://forum.xda-developers.com/on...-to-uninstall-magisk-module-t3940369#poststop
Just had the same issue an hour ago. Do this then re-root your phone again. Easy. Then re-install magisk modules.

spart0n said:
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
Click to expand...
Click to collapse
Had the same issue.

Same here. I just reflashed TWRP (flash boot command), flashed the TWRP installer zip, rebooted recovery and then flashed Magisk. That solved it.
By the way, theres a new TWRP out for the 7 Pro.

I got the same problem but my internal storage is encrypted (it shows 0kb). TWRP is not asking for PIN to unencrypt the partition. What can I do now?

Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)

dude9946 said:
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
Click to expand...
Click to collapse
Your best bet is to use the oxygen updater app, download 9.5.9 and then copy it to a PC then use boot.img extract thingy and then use magisk to patch it and then use fastboot to to root it

Root broken after forced update on t-mobile.

So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!

Honestly not sure how you got the update with twrp installed it always failed for me. Had to restore original boot.img to install.
But the update relocks the bootloader ... At least it did for me so hopefully you still have your unlock bin. Just unlock the bootloader and root as usual.
Unfortunately unlocking wipes.
If your bootloader didn't relock just root per the guide

nujackk said:
If your bootloader didn't relock just root per the guide
Click to expand...
Click to collapse
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
StrawHatZakk said:
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
Click to expand...
Click to collapse
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
StrawHatZakk said:
Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp.
Click to expand...
Click to collapse
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.

StrawHatZakk said:
So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!
Click to expand...
Click to collapse
Just reflash twrp/magisk with powershell
Go to settings developer mode turn off auto install updates.

redpoint73 said:
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.
Click to expand...
Click to collapse
I took my sweet time trying it but wanted to get root back as I just moved and won't have internet for a while. Everything seemingly went fine, got TWRP going then after installing Magisk it would just hang at the t-mobile screen indefinitely. Attempted to do a restore with TWRP and must have hit a leftover restore from the previous android version now the only thing it does is boot to the fast boot section. Might make a new topic but I'm searching everywhere for a fix, can't seem to get this MSM tool thing to recognize it... thinking I might just be boned. If you know of any fixes let me know lol.