Database Users

[Q] How to Root?

Hi guys,
Anyone know a way to make root in Moto X Play it work?
Or can you use the method of CF-Root Moto X (2014)?
I did unlock the bootloader through the website of Motorola. It worked.
Tks.
(Sorry for my bad english)
Obs. ROOT process in post # 14

No TWRP/Root available as of yet. Give it some time, I guarantee you that XDA will basically be the first place it's posted when it happens. Keep in mind that the phone is just starting to roll out, but not in the US so it might take a while longer for somebody to get on it.

nourez said:
No TWRP/Root available as of yet. Give it some time, I guarantee you that XDA will basically be the first place it's posted when it happens. Keep in mind that the phone is just starting to roll out, but not in the US so it might take a while longer for somebody to get on it.
Click to expand...
Click to collapse
Tks nourez, In Brazil it was released on August 12. I'll wait longer.

lmsantiago said:
Hi everyone. ?Just a point: When doing 'Unlock the bootloader' for root ou flash custom roms, you agree to void your warranty.
Click to expand...
Click to collapse
Most people on this site could care less about warranty... Its a developer site after all
Sent from my Nexus 6 or Note 4

Even still, unless you REALLY screw something up, most of the time you can get away with it. (not sure how Moto X devices show the unlocked bootloader status and such).
....Note: Don't take that comment as fact. Your mileage may vary

Curious how developers figure out how to root. Is there something that's needed (besides having the phone, obviously), do we need kernel images from Motorola?

Devhux said:
Curious how developers figure out how to root. Is there something that's needed (besides having the phone, obviously), do we need kernel images from Motorola?
Click to expand...
Click to collapse
I don't have the device, so I won't be making a recovery for it, but it's not a particularly difficult process to make one. It took me around an hour to port TWRP to the 2015 Moto G, and it should be similar for this device. You can use a prebuilt kernel if sources are not available, but I think the 2015 Moto G kernel will actually work on this device. Moto will be releasing the proper kernel sources for this device soon anyway.
You just need to create a device tree and compile a recovery (such as TWRP). The recovery device tree doesn't need to be very thorough (the way ROM device trees are). It just needs to specify information about partition names and locations and kernel boot parameters etc. It should be a trivial modification to make my 2015 Moto G TWRP device tree work on this device.
Once you have a working recovery, just flash SuperSU with it and you'll be rooted.

squid2 said:
I don't have the device, so I won't be making a recovery for it, but it's not a particularly difficult process to make one. It took me around an hour to port TWRP to the 2015 Moto G, and it should be similar for this device. You can use a prebuilt kernel if sources are not available, but I think the 2015 Moto G kernel will actually work on this device. Moto will be releasing the proper kernel sources for this device soon anyway.
You just need to create a device tree and compile a recovery (such as TWRP). The recovery device tree doesn't need to be very thorough (the way ROM device trees are). It just needs to specify information about partition names and locations and kernel boot parameters etc. It should be a trivial modification to make my 2015 Moto G TWRP device tree work on this device.
Once you have a working recovery, just flash SuperSU with it and you'll be rooted.
Click to expand...
Click to collapse
This makes me happy and sad. Lol. Looking forward to root so I can drop DPI.

I would love to root it. I miss Viper4Android
Sent from my Golden Zenfone 2

I would love to root it too, I'm just wondering if we'll still have the possibility to install firmware upgrade if you root it and unlock the bootloader?

Nico3d3 said:
I would love to root it too, I'm just wondering if we'll still have the possibility to install firmware upgrade if you root it and unlock the bootloader?
Click to expand...
Click to collapse
A quick glance through the other Moto forums here on XDA would give us a good clue. I'm too tired to check at the moment, but if nobody else does by the time I wake up, I'll check then.

Good News! My Moto x play is rooted with the Moto G 2015 method.
Below process we did and it worked:
1- Through the forum: http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
I downloaded "TWRP-osprey-2.8.7-test1.img"
2 UPDATE-SuperSU-v2.46.zip downloaded at: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
[Copy to your internal SDcard]
3 Place your Moto-x in fastboot mode [Power + Vol. down]
3- install TWRP-osprey-2.8.7-test1.img with the command: fastboot boot TWRP-osprey-2.8.7-test1.img
[Installation is temporary, I tried to permanently install but did not work].
4. The recovery will open automatically, browse to the location where you saved the SuperSU and flash UPDATE-SuperSU-v2.46.zip
5. Restart.
I did this procedure and managed to get root, I'm not responsible for any damage caused to your phone.

Did you have to unlock bootloader before installing it? On my phone, I have an unlocked bootloader and it did work but perhaps people would be interested in trying it with a locked bootloader (less risk of voiding the warranty).

Nico3d3 said:
Did you have to unlock bootloader before installing it? On my phone, I have an unlocked bootloader and it did work but perhaps people would be interested in trying it with a locked bootloader (less risk of voiding the warranty).
Click to expand...
Click to collapse
My bootloader is also unlocked.
I believe you can not do without unlocking the OEM. since it would not be possible to install recovery.
If someone is on a locked bootloader and want to test, we can see if it works. But I believe that is not possible.

I'll gladly test it with a locked bootloader when I get home in a few hours, if it hasn't already been tested by then.

Just tried it with locked bootloader, no joy. Device downloads the boot.IMG but errors booting it and just stays in bootloader mode. Guessing needs the bootloader unlocking first.
Sent from my Nexus 9 using XDA Premium HD app

Good to know. Thanks @CharlesW123 for checking!
Anybody know if we are able to flash a logo to replace the unlocked bootloader warning on the X Play yet?

Sevael said:
Good to know. Thanks @CharlesW123 for checking!
Anybody know if we are able to flash a logo to replace the unlocked bootloader warning on the X Play yet?
Click to expand...
Click to collapse
Yep the method shown here does work on the Moto X Play, you will get back to the normal boot logo.

has anyone tested installing Xposed after rooting yet? I'm assuming the same procedure should work (fastboot boot recovery.img > flash xposed.zip)?

nourez said:
has anyone tested installing Xposed after rooting yet? I'm assuming the same procedure should work (fastboot boot recovery.img > flash xposed.zip)?
Click to expand...
Click to collapse
The Xposed is a .zip file, you need to install the TWRP via flash.
But still I am not the courage to try. I have no backup ROM error.

Nexus 6P on boot loop after an OTA update

Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?

.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.

Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!

.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.

Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.

.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.

Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!

.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.

So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.

Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.

I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?

bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?

I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.

TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.

Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.

This happened to my wife's phone, sent back to Bell. Will see what happens.

TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?

You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.

bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?

TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.

Should I update my Moto G5 Plus from 83 to 93?

My old Moto G5 Plus suddenly shutdown and was stuck in a bootloop after an update install (not sure if that caused it), is there a risk that the same thing will happen if I update to 93? I RMAd my old phone and Motorola sent me a completely new one after 3 days. My old phone didn't have OEM unlocked so I couldn't even unlock its bootloader, so my only choice was to send it back to Motorola.
Would it be a better option to unlock bootloader, root and install twrp instead? If the same thing happens to my new phone, since I have it rooted and all I can flash new ROMs and firmware so it works again, right? Is it not worth it to void my warranty?

cidlc said:
My old Moto G5 Plus suddenly shutdown and was stuck in a bootloop after an update install (not sure if that caused it), is there a risk that the same thing will happen if I update to 93? I RMAd my old phone and Motorola sent me a completely new one after 3 days. My old phone didn't have OEM unlocked so I couldn't even unlock its bootloader, so my only choice was to send it back to Motorola.
Would it be a better option to unlock bootloader, root and install twrp instead? If the same thing happens to my new phone, since I have it rooted and all I can flash new ROMs and firmware so it works again, right? Is it not worth it to void my warranty?
Click to expand...
Click to collapse
Should you take the update? Yes, there is no reason not to.
Is there a risk it could brick in the process? Yes, but honestly if your device is stock that risk is minimal
Would it be a better option to unlock bootloader, root and install twrp instead? No, it will void your warranty
The question is, what do you want in the end, a stock device with a warranty or a modified device without one? If you want a modified device without a warranty, go for it. If you want a stock device with one, although I understand your hesitation due to previous issues, go ahead and take the OTA, worst case scenario Moto will replace it again, although you are unlikely to have issues.
You do have the option to make that decision later... Enable Developer Options and go into it and enable OEM Unlocking but DO NOT actually unlock the bootloader, then take the upgrade. If it succeeds, just turn off OEM Unlocking, if it fails you have option to try something to recover it. Be aware if actually unlock the bootloader the warranty is gone, so if on the off-chance it does fail don't panic and try to think clearly.

Is Cricket LG V35 bootloader unlockable?

If yes, the phone must be rootable. Is Lineage OS 16 support this phone?
I have done some researches on this forum but couldn't find an exact answer.
Thanks.

From what I've read and heard, no. It seems like the carrier-branded phones and Amazon phones are far less likely to be able to unlock the bootloader in order to root or flash different firmwares, but on different models some people have had luck performing "Frankenstein" flashes by temporarily flashing a different firmware using a hacked version of LGUP, performing the bootloader unlock, and then flashing back to the original. You don't want to flash a KDZ to go back to the original firmware from what I've gathered though as it could relock the bootloader -you'd need to find a flashable ZIP file or something that has all of the firmware and use TWRP to flash back to the normal firmware. You might have to use LGUP to flash some modem firmware and such back, but those guys will be able to better explain the situation than I would. I considered doing this with My LG V30+ H932 using lafexploit but decided that it was too much work for not enough reward and just stuck with stock firmware. Honestly as long as PDANet/FoxFi still works in non-root mode there's not much of an incentive for me to unlock the BL since I might lose the ability to pay with Android Pay or some other NFC payment apps.

oneplus 8 pro crashdump/fastboot brick, again

i know there are a ton of discussions on this but it seems that every thread just dies off and nothing in depth gets discussed. oneplus is useless in this, and it also figures that the phone would wait for me to pay it off before it self bricks for no reason.
i know im gonna have to wipe it at some point, but i REALLY need to get some data off of it. the bootloader claims its locked when i know i unlocked it forever ago, and nothing that fastboot offers is doing anything for me. i cant use oem unlock, i cant flash anything to it, and unlike earlier today, multiple reboots no longer bring it back to life.
so, is there a way i can force this paperweight to take a dirty software load? or can i get fastboot to dump all my data into a folder or something? i havent been around really since the CM days, and Im very sure I simply cannot search for the right terms in the right places.
ive also made posts in the xda and oneplus discords with little reply (it is late in the US so im not overly surprised about that at all.

as an update, it booted into recovery this morning, i backed everything, unlocked the bootloader, and got about 5 hours out of it.
after getting fastboot to finish the oem unlock, i tried flashing twrp recovery which did nothing, flashed carbon, which did nothing, used the MSMdownload tool, which has done nothing but relock the bootloader again. im at a huge loss here.
is this motherboard level?

Alright mate. Sounds like you're having a mare.
Personally I haven't had a single bootloop besides, OnePlus do provide tools that a lot of companies don't, like MSM, so be grateful for that. Plus it's super easy to unlock and relock the bootloader, also OnePlus will allow you to retain warranty even if it has been unlocked.
So go easy on OnePlus. Believe me it could be worse, naming no names.........
Samsung. LG, Motorola, Sony, apple.
As for your issue, when and how did it bootloop, it is quite rare for a phone to simply behave that way on its own
Are you / were you rooted?
Did you confirm that the bootloader was unlocked? If you're rooted then I think that confirms that you did.
The only way I know of to relock the bootloader is the fastboot command to relock and or the MSM tool.
So can you fill in the gaps as to how you managed to get there??
Finally, if you are indeed bootloader locked and unable to get into your device then yep you're screwed, however you could wipe system from recovery, this will nuke your apps, but your storage will remain intact .
So if that suits your needs then go for it.
Let me know about the bootloader before you commit