Related
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
Magisk comes with a ton of benefits, including a powerful systemless interface, as well as keeping device certification and SafetyNet intact, allowing you to use apps like Snapchat, Pokemon Go, Super Mario Run, and so forth.
Credit to @mcopeland1003` for the heads up on Magisk.
PREREQUISITES
A PC
Odin
Galaxy Core Prime not rooted by any other method, and has the stock kernel intact. (If you want to OTA update your phone be sure to do that before you root your Core Prime with this method!)
Unofficial TWRP SM-G360T1
Installing TWRP Recovery
Enable OEM Unlocking in developer options if you haven't already.
Then, put your device in download mode by pressing Power+Volume Down+Home Key.
Launch Odin on your PC, then connect your device to your PC.
Click on the AP Button and browse for your downloaded TWRP file.
Hit Start.
In my experience, my Core Prime for some reason did not let TWRP install on my phone; when I decided to boot into recovery it booted into Samsung's stock recovery. To get around this: before flashing TWRP, go into the options tab of Odin and uncheck Auto-Restart. Then flash TWRP and then remove the battery of your phone and unplug your device. This will not damage your device.
Now, boot your phone into recovery by pressing Power+Volume Up+Home to make sure TWRP's there. You can now boot back into android.
Installing Magisk
Sideload the Magisk Manager APK from this link onto your device.
Now we need to download the latest Magisk zip file to flash through TWRP. Open up Magisk Manager. Press the giant Install button, then Install, and finally Download Zip Only. The latest Magisk flashable zip will start downloading.
Once the file has finished downloading, boot into TWRP by powering off your phone then pressing the Power+Volume Up+Home keys simultaneously. Head into Install, and browse to /sdcard/MagiskManager. You should find a .zip file with a name like "Magisk-v16.0(1600).zip". Flash that, then reboot into system.
By the way, don't let TWRP install SuperSU. It'll pretty much defeat Magisk.
And there you have it, Magisk giving you root in a systemless fashion, without breaking Wi-Fi, device certification, and SafetyNet. Hope this guide helped you guys out.
Be still my heart
Glad you found it useful. I use it so my 7 year old can play his pokemon games and stuff like that, but use root for the extra storage.
twrp has official release for this phone i seen and used its app to add to recovery once rooted .. wish i didnt use first root method i seen as phone no wifi and cant get reconition from pc
It worked for a while then went belly up !
FazPhantom said:
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
.
Click to expand...
Click to collapse
Hello,
Using your method which worked for me initially on an SM-G360T1 then on bootup I got the dreaded Wrong Binary FRP enabled message. Since then I have flashed back to the stock ROM but the minute I install TWRP it won't boot past the Metro PCS screen. It just sits there and won't go any further. I have done this multiple times in hopes that it will somehow 'fix' itself...(yeah right) but that never happens.
One of the membes in the Androidcentral group sent me here to ask about the problem. I can't undestand if the frp was tripped by something, why did the phone work OK for 2 weeks and then quit? It would seem to me it would have done it right away but yet it worked fine with TWRP and magisk. I did NOT install any more apps or ROM's to the device that's what puzzles me.
Can you help me with some ideas? You guys are the decided experts and I am a newbie to all this but trying hard to learn as I go.
Many thanks in advance,
W T
I'm trying to get Magisk to work on a Samsung S2 Tablet SM-T713. I don't think it's relevant, but I'm running LineageOS 16.0 (the 4/5/19 nightly), and TWRP 3.2.3. I had enabled OEM Unlocking before I installed either of those.
I installed Magisk Manager 7.1.1on the tablet. I pulled the stock boot.img from a stock installation image (T713XXU2BRB2_T713OXA2BRA1, which was the same firmware I had before upgrading to LineageOS). I then used Magisk Manager 7.1.1 to create a patched boot.img. I then used TWRP to flash the patched boot image to the boot partition.
The result is that my tablet is now bricked at the initial boot screen (the one that says "Samsung Galaxy Tab S2") with an error in the corner that says "Set Warranty Bit: kernel".
I'm assuming that once the battery runs down I'll be able to boot into either recovery or Odin download mode and re-flash the boot image. Since having a non-removable battery makes trial and error very slow (since I need to let the battery run down before I can reboot), I'd really like to understand what I'm doing wrong before I try installing Magisk again.
All of the threads I've seen about people installing Magisk on the T713 are from last year. Is anyone still using that combination? Even if you're not, I'd appreciate any suggestions!
Thanks in advance for any help.
Dr. Drax said:
I'm trying to get Magisk to work on a Samsung S2 Tablet SM-T713. I don't think it's relevant, but I'm running LineageOS 16.0 (the 4/5/19 nightly), and TWRP 3.2.3. I had enabled OEM Unlocking before I installed either of those.
I installed Magisk Manager 7.1.1on the tablet. I pulled the stock boot.img from a stock installation image (T713XXU2BRB2_T713OXA2BRA1, which was the same firmware I had before upgrading to LineageOS). I then used Magisk Manager 7.1.1 to create a patched boot.img. I then used TWRP to flash the patched boot image to the boot partition.
The result is that my tablet is now bricked at the initial boot screen (the one that says "Samsung Galaxy Tab S2") with an error in the corner that says "Set Warranty Bit: kernel".
I'm assuming that once the battery runs down I'll be able to boot into either recovery or Odin download mode and re-flash the boot image. Since having a non-removable battery makes trial and error very slow (since I need to let the battery run down before I can reboot), I'd really like to understand what I'm doing wrong before I try installing Magisk again.
All of the threads I've seen about people installing Magisk on the T713 are from last year. Is anyone still using that combination? Even if you're not, I'd appreciate any suggestions!
Thanks in advance for any help.
Click to expand...
Click to collapse
any luck?
pointbob said:
any luck?
Click to expand...
Click to collapse
I wound up having to let the battery run out. Then I had to do finger acrobatics to hold down the buttons for download mode while I plugged in a USB cable attached to my computer. That allowed me to use Odin to install a stock boot image.
I ultimately figured out that the problem was that my data partition had automatically re-encrypted itself. I found I had to use TWRP to wipe my data partition, then immediately use TWRP to install Magisk so that my bootloader wouldn't force encryption. A reboot between those two steps screws things up.
So i had my f1 rooted with magisk and had a few enhancements active like adaway and afwall to keep advertisments and nosy apps at bay.
The system offered me an update which i happily installed. Now that the device has rebooted, i cannot get out of the boot animation.
it keeps saying "pocophone: by Xiaomi powered by android and the 3 little dots keep progressing forever.
All i can do is power it off and go to fastboot mode, but it seems that my usb cable and the device do not connect properly other than charging power.
What could have gone wrong in that update? ADB logcat isn't filled either.
selemine said:
So i had my f1 rooted with magisk and had a few enhancements active like adaway and afwall to keep advertisments and nosy apps at bay.
The system offered me an update which i happily installed. Now that the device has rebooted, i cannot get out of the boot animation.
it keeps saying "pocophone: by Xiaomi powered by android and the 3 little dots keep progressing forever.
All i can do is power it off and go to fastboot mode, but it seems that my usb cable and the device do not connect properly other than charging power.
What could have gone wrong in that update? ADB logcat isn't filled either.
Click to expand...
Click to collapse
i am unable to understand how did u apply OTA with twrp? or without twrp? if you had never flashed twrp but BOOTED in to twrp via fastboot and applied magisk and now have applied OTA ( and miui recovery intact) this means /system paritions have changed, now OTA has replaced new kernel with DM varity in place, the device will never boot, it will stuck and boot screen!
SOLUTION ?
connect fastboot and boot in to twrp recovery "fastboot boot twrp.img" (assuming that recovery is in the fastboot folder with name "twrp.img" ) and FLASH MAGISK19.3 and reboot!
if this doesnt work,
download full recovery rom of miui (1.8gb) (boot in to twrp and FLASH it again!
there is hight posibility that YOU MAY LOOSE ALL YOUR DATA
The update was offered by MIUI and installed inside android itself. Yea i think there was trouble getting twrp to stick so i think it never was saved permanently to the device.
selemine said:
The update was offered by MIUI and installed inside android itself. Yea i think there was trouble getting twrp to stick so i think it never was saved permanently to the device.
Click to expand...
Click to collapse
after boot unlock and twrp flashed!
you should NEVER OTA your device! MIUI updater doesnt know your boot lock status! so it will always notify you for updates!
its your job to download FULL 1.8gb recovery rom from https://mirom.ezbox.idv.tw/en/phone/beryllium/ and FLASH it via TWRP and NEVER update via OTA
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
>>> *** UPDATED (see 5. ) *** <<<
Installation guide: (pay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
Code:
fastboot boot twrp-3.4.0-0-evert.img
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
!!! 5. Disable HAB verification by flashing this .zip hab_disabler.zip !!! (*)
6. Flash the TWRP installer.zip
7. Install Magisk (optional)
8. Reboot to system and enjoy!
(*) HAB (High Assurance Boot) is a second verification process/service. It checks /system and /oem partition. The hab_disabler.zip will delete/patch the related files. (for further information see "update-binary")
During first boot...
...your device will reboot once. Don't panic, that's quite normal!
...animation after "Hello Moto" will take 2-3 min.
*** tested on PPWS29.116-20-23
WoKoschekk said:
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
Installation guidepay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
5. Flash the TWRP installer.zip
6. Install Magisk (optional)
7. Reboot to system and enjoy!
During first boot your device will reboot once. Don't panic, that's quite normal!
Edit: Tested on build PPWS29.116-20-23
Click to expand...
Click to collapse
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
I tried it on my own. First boot runs fine but the second one ends in a bootloop. I already know whats wrong. Give me a few hours to fix this.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
The problem has been fixed!!
I rebooted several times from system to recovery and vice versa. Magisk and TWRP (installed permanently) work fine. No issues known yet.
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
It works fine fir me. I enabled Magisk Hide to hide some apps but my device doesn't loop after that.
Did you use the updated method?
- Magisk was repacked with new name
- Magisk Hide enabled
- modules installed
- rebooted to recovery and then to system => no looping
- rebooted the device normally => no looping
At this moment I'm using my G6+
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
WoKoschekk said:
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
Click to expand...
Click to collapse
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Dk Gautam said:
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Click to expand...
Click to collapse
Great!! Thanks for your reply!
I'm using neither Lineage nor VoLTE so I don't know if it's supported.
hello OP
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
d_g_m_2000 said:
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
Click to expand...
Click to collapse
Are you trying to boot TWRP?
WoKoschekk said:
Are you trying to boot TWRP?
Click to expand...
Click to collapse
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
ok, ia my pc, i try in another and it boot up... i got ryzen 5 2600 just if anyone else find out what da f*ck is going on... thanks in advance for your comments.
d_g_m_2000 said:
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
Click to expand...
Click to collapse
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
WoKoschekk said:
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
Click to expand...
Click to collapse
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
d_g_m_2000 said:
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
Click to expand...
Click to collapse
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
WoKoschekk said:
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
Click to expand...
Click to collapse
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
d_g_m_2000 said:
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
Click to expand...
Click to collapse
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
WoKoschekk said:
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
Click to expand...
Click to collapse
that's is a real bummer... thank you for your comments!
Hi i install pixel experence rom and im having a problem i canflash anything from my device, storage dont shows corrrct size and, shows binders with aleaty names with nothing inside, and i can't transfer with USB