Related
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.
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Why would you want to do this?
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Is there any way to remove the Bootloader unlock warning ⚠ without relocking bootloader?
Sent from my XT1572 using Tapatalk
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Theres no reason really to relock it. Once its unlocked, the bootloader will show that it was unlocked regardless if you relock it.
atishey23 said:
Is there any way to remove the Bootloader unlock warning without relocking bootloader?
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Yes
Pyramid Head said:
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Click to expand...
Click to collapse
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
psandeepn said:
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
Click to expand...
Click to collapse
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
jason2678 said:
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
Click to expand...
Click to collapse
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
The answer is maybe... it depends what you have changed and what this OTA updater script actually checks for.
We know that a stock bootloader (which can be unlocked, that is not relevant), stock recovery, and stock system image are required to take an OTA. If the system image has been modified it can fail, and we know the updater has the ability to see if /system has EVER been mounted R/W and can fail for that condition although so far it doesn't seem Moto is going that extreme.
We do know a modified logo does not affect an OTA, in fact, you can even relock the bootloader with a modified logo so it must not be a significant check.
jason2678 said:
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
Click to expand...
Click to collapse
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
iks8 said:
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
Click to expand...
Click to collapse
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
acejavelin said:
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
Click to expand...
Click to collapse
You're right sorry
While I am an advocate for device customization and modifications, I also believe there is an inherent need for locked bootloaders. When we unlock a BL and leave it that way so we can run custom ROMs, root etc, we sacrafice the security it provides allowing our devices to be tampered with or redistributed after a theft. I've seen the PSA advising people not relock their bootloaders on anything except stock. That is entirely true for Verizon and EE pixels that were never intended to be unlocked in first place. However I believe its entirely possible to boot properly self signed images on unlockable devices after re-locking.
Now, I'm not saying we should go around re-locking bootloaders with custom firmware installed there's a process. I've done a bit of reading on verified boot. I am interested in utilizing the "YELLOW STATE" so we can run self signed boot images using an "embedded certificate" along with dm-verity disabled. The problem is how can we self sign our boot images allowing boot to continue without compiling from source?
https://source.android.com/security/verifiedboot/verified-boot.html
https://mjg59.dreamwidth.org/31765.html
I found some information & maybe a more experienced DEV can shed some light on if its possible with our Pixel devices. That's really the goal of this thread, to start a discussion which I think is extremely important & hopefully turn into a guide or tool. We shouldn't completely sacrafice security to utilize root or custom ROMs. On my N5X I have a locked bootloader and modified boot/system with Allow OEM unlock disabled. Difference with our Pixels and Nougat BLs is verified boot is strictly enforced.
Please excuse me if this thread seems jumbled or all over the place. I really do want help with this idea tho to help inform and keep us secure. Any input is appreciated.
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
I still wouldn't do this. What's the point? You will still pass safety net with custom kernel.
As for security you, your device still needs to be decrypted to use TWRP. It should still be as secure. I guess someone can wipe your device if they get ahold of it but that's not really a security risk.
Risk is still huge locking your device with a custom OS.
Sent from my Pixel using Tapatalk
milan187 said:
I still wouldn't do this. What's the point? You will still pass safety net with custom kernel.
As for security you, your device still needs to be decrypted to use TWRP. It should still be as secure. I guess someone can wipe your device if they get ahold of it but that's not really a security risk.
Risk is still huge locking your device with a custom OS.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
It has nothing to do with passing safety net. TWRP can only access the data after the pin is input, true, but leaving a device with an unlocked boot loader leaves the ability to flash modified boot images (a huge attack vector). This is to keep your device yours if it falls into a theives hands. You can not have device protection features on a unlocked Allow OEM unlock device. You're right there is risk but being careful can alleviate the risk. I do this because I want my phone to be a trackable paper weight if somebody takes it. I have established my own chain of trust outside of googles. I have even modified my TWRP side of boot.img to only start with my PC using adb-keys.
Which risk is greater. The risk of losing an unlocked device and it falling into the hands of someone that knows what to do or bricking it relocking it.
I vote the latter.
Its not re-locking that bricks... Its disabling the allow OEM unlock in dev options & screwing with stuff afterwards that may cause a bootloop. As long as you have a signed boot image in place with TWRP or stock recovery that uses your own keys the risk is minimal.
Simple rule... With a locked boot loader on a device where verification is strictly enforced always leave that option ticked if modifying anything.
I'm sorry but people are misinformed. Locking the boot loader doesn't brick if you have a custom ROM in place any more than a stock ROM. Its screwing with things or using a poorly dev'd ROM. If you are like me and can set something up the way you like once and not screw with it you'll be fine. If you do wanna screw with something remember to check allow OEM unlock in dev opts. Don't uncheck until you're 100% sure. It really is that simple.
If you are leaving the toggle open what have you accomplished when it gets stolen? They just issue the fastboot command to unlock it. Yea, it wipes data at that point. But I honestly can't think of anything on my phone that is confidential.
When I'm out n about and using my phone normally (i.e. not modding, flashing etc) I put the toggle to off. If I'm planning on changing anything I toggle it back on & if something causes a bootloop (most probably user error) I can recover. I don't think most people who steal phones care about data either but I keep a lot of keys, passwords etc to networks in my devices storage. I admit its not for everybody, just a way to be more secure and protect a $700+ investment. My phones bootloader isn't just locked, its locked with a persistent root ssh backdoor integrated into system so I can maintain control in the event.
want to re-lock my boot loader ?
Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
hey,
I as well as plenty of others thought I was clever unlocking it as I mainly wanted to unlock it from EE UK network , its not been touched since ,no custom rooms or root but after reading people are trying to Re-lock it and getting bricked im too scared too try lol its only phone ive got ? Appreciate any help please x
---------- Post added at 10:57 AM ---------- Previous post was at 10:21 AM ----------
sally76 said:
hey,
I as well as plenty of others thought I was clever unlocking it as I mainly wanted to unlock it from EE UK network , its not been touched since ,no custom rooms or root but after reading people are trying to Re-lock it and getting bricked im too scared too try lol its only phone ive got ? Appreciate any help please x
Click to expand...
Click to collapse
Sorry Duhhhh !! Custom u said lol
Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
Geofferey, Do you happen to know if these commands are still right with LOS 17.1 / Android 10?
(Or does anyone else know?)
PS: Sorry everyone for pumping such an old thread
nullstring2 said:
Geofferey, Do you happen to know if these commands are still right with LOS 17.1 / Android 10
Click to expand...
Click to collapse
Unfortunately no. Now there is avbtool and the process is actually a bit more complicated. Somebody wrote a guide on how to use it externally for another device but I couldn't even follow. I actually find it easier to get the sources for whatever ROM it is I'm trying to sign and set the signing params in config before build.
Here is the guy who did it usually avbtool externally
https://forum.hovatek.com/thread-32664.html
Many instructions here
https://android.googlesource.com/platform/external/avb/+/master/README.md
Geofferey said:
...but I couldn't even follow. /QUOTE]
Well, thats an intimidating introduction, but I'll take look.
That guide appears to be talking about mediatek CPUs which makes it a little confusing.
Any hint on how to get the vbmeta signing key for the google pixel?
Click to expand...
Click to collapse
nullstring2 said:
Any hint on how to get the vbmeta signing key for the google pixel?
Click to expand...
Click to collapse
If you mean how to make your own key to perform signing then
Code:
openssl genrsa -des3 -out avb.pem 2048
If you're asking how to get the same key that Google used to sign vbmeta, it ain't ever gonna happen.
Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
Is there ANY way to do this on Xperias or LGs?
Geofferey said:
It has nothing to do with passing safety net. TWRP can only access the data after the pin is input, true, but leaving a device with an unlocked boot loader leaves the ability to flash modified boot images (a huge attack vector). This is to keep your device yours if it falls into a theives hands. You can not have device protection features on a unlocked Allow OEM unlock device. You're right there is risk but being careful can alleviate the risk. I do this because I want my phone to be a trackable paper weight if somebody takes it. I have established my own chain of trust outside of googles. I have even modified my TWRP side of boot.img to only start with my PC using adb-keys.
Click to expand...
Click to collapse
It has ALL to do with safetynet/play integrity.
I wouldn't care to leave my bootloader unlocked otherwise.
But I want a rom that passes all security standards without "tricks".
I've read the PSA about not relocking non-stock pixels, but it appears those are more directed towards Verizon unlocked pixels. Others also stating it's not safe to lock a non-stock device period... Can anybody explain this to me? Nicely I have systemless root and pass safetynet checks, the literal only reason I'd like to lock my bootloader is because it's kind of a security vulnerability isn't it? What's to stop someone from fastbooting and flashing to bypass my security and gain access to my data?
Or is fastboot not really an attack vector as long as the devices is passworded? Twrp seems to require my password, but what about fastboot booting a twrp image? will my data still be encrypted?
lucid888 said:
I've read the PSA about not relocking non-stock pixels, but it appears those are more directed towards Verizon unlocked pixels. Others also stating it's not safe to lock a non-stock device period... Can anybody explain this to me? Nicely I have systemless root and pass safetynet checks, the literal only reason I'd like to lock my bootloader is because it's kind of a security vulnerability isn't it? What's to stop someone from fastbooting and flashing to bypass my security and gain access to my data?
Or is fastboot not really an attack vector as long as the devices is passworded? Twrp seems to require my password, but what about fastboot booting a twrp image? will my data still be encrypted?
Click to expand...
Click to collapse
Well... It's advised not to relock a bootloader, in case something goes wrong...
Imagine your device doesn't boot, bootloop or gets corrupted for whatever reason?! You'll have no other choice than sending back your device for repair. Because you can't flash anything being locked. Also, your data are now encrypted. If i was you i wouldn't worry too much about it. The only reason you should think about relocking is: If you ever have to RMA your device. Flash a factory image and relock it before...
Cheers...
Being nice here, so don't misunderstand my bluntness. You are rooted, with a kernel from some other person and who knows what else you changed.
The one in a million that you lose your phone and it falls into the hands of someone that knows what to do AND wants your data is the least of your security concerns.
And for the record, my phone is set up much like yours. So not saying anything you did is wrong. I am saying if you want security flash it back to stock and lock it.
Anything less you are kidding yourself.
This! ^^
I want to remove 'Unlocked bootloader warning' which displays whenever I power on my phone(zenfone max pro m1 4gb). In one of my previous phone I overcome this problem by flashing logo.bin file. So, can this bootloader Unlocked warning be removed by flashing original splash partition?If yes, please provide the twrp flashable file or suggest some other method to do so.
+1
Yes we need it. I also had this on my moto x pure
i +1 this
the startup time is significantly increased by this
Same problem here..that warning kinda annoying.
up
we need it
Agree with you guys man. Wish we could do something about it!
Change the splash.img or something.
Relocking bootloader
Hello, I tried to root my lenovo k8 note twice but i was not successful to do so. Later, i discovered that banking apps didnt worked anymore even though my phone was not properly rooted(as per apps like root checker and universal unroot). I think its probably becuz of unlocked bootloader or may be encryption that i removed before formatting while in recovery. But i'm not sure and now, i dont want to root my device. Is there a way to make it as it was before i tried to root it? Any help is appreciated...
Bump