Hey,
I'm trying to install TWRP to root my G7 Play I've followed several different guides. Each time I try to install twrp the command shell shows permissions denied even though I've unlocked the bootloader. I've tried several versions of twrp for this device. Now I'm using a completely factory restored Moto G7 Play I'd appreciate some help as I'm a beginner to rooting.
Related
Instead of flooding the bootloader thread, I humbly ask for anyone's help in getting my N4 rooted so that I can unlock the bootloader.
1. I am able to use Kingroot to obtain temp root
2A. I open Root Checker and N4 reboots
OR
2B. Root checker OK then I get to ADB and enter a push command, the N4 reboots
This is where I am stuck.
Bootloader
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66371097&postcount=237
I had the same bootloop problem and following those directions fixed it for me. I had to use Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip as my kernel. Later versions didn't work (wrong phone version?).
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
Why don't you guys flash a ROM that is rooted instead of flashing SU?
Edit:
But if whatever you guys are doing works eventually, keep doing that.
thanks for everyone's help - I finally got DEV mode to stick!
Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!
My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.
Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised
thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything
I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device
I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Thanks, Mike01680. trying now
When i go into sideload i can see the device listed on adb devices!
Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!
So, long story short, I followed this tutorial: www . htcmania. com/showthread.php?t=1024045 (remove the spaces in w.h and .com) and it didn't go very well.
I flashed TWRP and SuperSU as told, using both download links (TWRP 2.8.7 & SuperSU 2.46), and my phone got stuck in a bootloop at LG bootloader unlocked logo. I recovered my phone by using LG Bridge and after that, when i tried to enter TWRP using the phone keys, it resulted in a factory data reset (no TWRP after recovery, didn't know that). I then followed the exact same steps but using what I thought was the lastest SuperSU archive (SR5-SuperSU-v2.82), flashed the archive and when finished, TWRP asked me to flash it again (so I did), then rebooted, passed LG bootloader unlocked logo, got into LG animation and... Bootloop again, so I recovered again with LG Bridge but I din't attempted to enter TWRP because this time i knew it wouldn't work and I ended it there, reinstalling all apps and configuring my phone as I had it before my unsuccessfull attempt. I continued using my phone as usual but sometimes, when I enter Pokemon Go, it says that it couldn't log in and that my phone's OS is not supported. As I said, the app does this sometimes whenever it wants, so I researched a bit and turns out it doesn't work with rooted android devices (I didn't know that). I knew my root attempt failed so I downloaded and app called Root Checker and checked: Root status-Not rooted; SafetyNet Status-Failed. I don't know what should I do know, last time I rooted my phone was a Sony Xperia XL and it wasn't so tricky.
I asked for advice in the forum and got no answer, so here I am, hoping for a solution. What I want is to have a permanent custom recovery, a rooted device and to have SafetyNet status passed. Any ideas, hints or whatever? Please, help
Hey,
I want to root my phone and install Lineage OS. I failed once before during the TWRP install and ended up having to get another phone. Previous phone would no longer power on or even go into fastboot. Not too sure why all i know is during the installation process of twrp it failed a bunch of processes and once rebooted would not boot. I assume my last try failed due to not being root and not having either magisk or superuser? Is there a fool proof noob friendly guide to doing this? Thanks in advanced.
Hello all,
I'm working on getting my bootloader unlocked. I bought what I thought was a ULM model off Amazon, but it appears to be a Sprint PM model that's been flashed with the ULM firmware. Sadly the EDL method doesn't seem to work on this phone (either the drivers aren't correct or some other issue is preventing me from getting past the Partition Manager step) so I was trying the old method Here. The issue I'm having is that the rootedboot image allows me to boot and Magisk comes installed, but any su commands never bring up a root prompt, including adb shell.
I also goofed and hit the "Install" from the magisk app and it appears to have made the bootloader angry, as the phone will no longer boot without my manually pushing the rooted image. I also cannot get LGUP to recognize the phone anymore (saying "Unknown model" so I can't flash it back to factory with the KDZ.
I still have access to Download Mode, fastboot, and system by pushing the rootedboot image.
Any help would be appreciated.
UPDATE:
I managed to get a root shell by re-patching the rootedboot image using the updated magisk manager application!
Bootloader is now unlocked, and I'm working on installing TWRP etc
Edit:
I'm still on the v35 abl at the moment, and that may explain why booting to the twrp recovery isn't working. Not sure yet
Use universal twrp ON any pie+ rom