Problems rooting Xt-1952-1 - Moto G7 Play Questions & Answers

Hey guys,
Hope someone can help me or point me in the right direction, I am having serious issues trying to root my 1952-1.
I followed the guide in this post to install TWRP
https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
I followed all the guidelines but when i tried rebooting to recovery I ended up in having TWRP splash screen bootlooping, but was still able to fastboot boot twrp.
I then flashed Magisk, it completed and then i booted the phone back up, no magisk was in the app drawer. So i installed the Magisk Manager apk and this told me I was not rooted. Repeated the whole thing and still the same result.
I have also tried patching the boot.img file using magisk but same as before the phone is not rooted, on top of this I have also clean flashed the stock rom but again still not rooted.
Anyone got any ideas ?

Yeah the rooting process can be a little bit frustrating. You will have to copy the original boot.img file to your phone. In the magisk app make sure you enable recovery mode. Then you can patch the boot.img file. Copy it back to your computer and flash it via fastboot. But there is a catch. The phone will be rooted only if you boot the phone through recovery.

Related

Bootloop help

Hi guys, this morning I decided to root ny tablet. I flashed CWM custom recovery and then installed universal android root zip file through the recovery. My goal was to unlock the full potential of Lucky Patcher by having unlocked Root permissions. I succeeded in installing the zip file, and everything was perfect. Unfortunately after custom patching Google play with LP, it kept crashing on startup. So (my bad) I decided to revert to factory settings. By doing this I'm now stuck in this never ending bootloop. I tried reinstalling .zip file through the use of ADB sideload, but when I exit that menu to reboot the device after having installed the .zip the device boots in CWM recovery mode. I really need your help as I'M very new to these type of things. Thand you
Back to stock ROM and start all over again

Pixel C OTA using Flashfire - stuck on "waiting for fastboot command"

I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.

A70 Bootloop after Magisk flash *not enough posts for Dev*

Hey guys:
FIRST OFF: I don't have enough posts in order to stick this in Dev, SORRY!!!
I have read all related posts and stickies but still can't get this sorted out.
Let's get some background... I'm looking at rooting the phone with Magisk. This did not work directly and I was guided by another "how-to" to do it via TWRP instead.
Flashed the vbmeta and TWRP without issues. Booted into TWRP and tried to flash Magisk, which gave me an error at first. It was an old version so I tried a later version, which flashed "successfully," but after a reboot I'm stuck in a loop that reaches the SAMSUNG Galaxy A70 screen, then reboots to show that the bootloader is unlocked, and again and again and so forth...
What did I do wrong? And is there any way for me to fix the boot loop?
Holding in Volume Up does allow me to boot into TWRP so I don't feel as though the phone is bricked.
Any help will be appreciated, preferably that that gets my phone rooted, but even just getting it back to normal will work for me
Thanks in advance,
ShOrTyNoLeGs
Follow this guide
https://forum.xda-developers.com/ga...root-galaxy-a70-twrp-los-17-1-magisk-t4100655
After flashing magisk using twrp, you should reflash stock recovery, Reboot into it then select reboot system BEFORE 1ST BOOT to prevent bootloop.
Factory reset after flashing magisk in twrp will fix all bootloop.
Or follow the guide in my signature for successful root. But you wouldn't have twrp that way, just stock rooted rom

After trying to root with Magisk...

After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
killer23d said:
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
Click to expand...
Click to collapse
already done, if i flash it again will it work? because im still stuck in the bootloop
Nicster205 said:
already done, if i flash it again will it work? because im still stuck in the bootloop
Click to expand...
Click to collapse
if you reflash the factory boot.img then you'll get out of bootloop.
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse
reflashing the factory boot.img seems useless. you can long-press the power button to force power down. then power up to the fastboot mode,and reflash the full factory image(11 or 10). the nomal methon working on 10 seems dizzy in 11 now.
fwiw, heres the path i used...i hate making it more steps than needed (tranferring boot image to device and back again for magisk patching for example)...
1) flash-all.bat (with wipe enabled - because clean install)
2) Immediately on reboot from 1 and before it gets anywhere near to beginning of setup: fastboot boot twrp-3.4.0-1-taimen.img
3) adb push Magisk-e66b0bf3(20425).zip /tmp
4) adb shell twrp install /tmp/Magisk-e66b0bf3(20425).zip
5) adb reboot
6) after reboot, install canary magisk manager (for whatever reason doesnt install from TWRP flash)
7) open canary magisk manager and enable magiskhide
This is caused by twrp
Use android toolbox, just boot twrp, flash magisk
boot into twrp go to advanced fix bootloop option reboot
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse

Boot issues after removing magisk

Got the notice there was an OTA. As per instructions I tried uninstalling magisk and restore images. Got a toast notification saying no backups found.
Tried a complete removal of magisk, now stuck at the Bootloader unlocked screen.
Tried flashing the patched boot.img in fast boot and rebooting. Now I'm stuck on the boot animation.
Done with root on this phone, not worth the headaches. (TiBU was the only thing I use it for these days) Get me back to no magisk without loosing data.
[edit]
Ended up having to wipe litterly everything via recovery then it finally booted. :/
The patched image you're flashing won't work because you updated to 10.0.14. When updating, you're not supposed to uninstall Magisk, just disable the modules you have downloaded in the "Modules" section.
You need the updated root boot.img. I'll try to upload it later.
Snaxe123 said:
The patched image you're flashing won't work because you updated to 10.0.14. When updating, you're not supposed to uninstall Magisk, just disable the modules you have downloaded in the "Modules" section.
You need the updated root boot.img. I'll try to upload it later.
Click to expand...
Click to collapse
Thanks. At that point I hadn't installed the OTA update yet. I had just prepped by going into Magisk manager and (mistakenly) hit completely remove magisk. Which it did, then rebooted but left me hanging at the unlocked bootloader warning.
I tried flashing the patched boot.img from fastboot, and reflashing magisk from inside of the temporary twrp, but after a reboot I was left with the boot animation that never went away.
After I wiped it and got back in, I let it download the latest OTA and installed it.
So currently I'm at 10.0.14 now, but without root.

Categories

Resources