Related
I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?
impinball said:
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?
Click to expand...
Click to collapse
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.
RikRong said:
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.
Click to expand...
Click to collapse
I have done absolutely nothing beyond rooting it, installing Superuser & SuperSU (both through a script I can attach, but I'm on the wrong computer), and backed up a slew of apps.
This first begun when I modified the script to fix a bug in it (ash in JB 4.2 doesn't have a -f switch in rm, and the script had a 'rm -f'). If that bug didn't exist, then it would've still happened the first of several times (I attempted it about 4-5 times, but only the last caused this). The rm -f was actually doing effectively (with successful root privileges) 'rm -f /system/install-script-2.sh', but the script actually had another script to be put into it at the location /system/install-script.sh.
???
Start by detailing steps in your 2nd paragraph.
Your boot is locked if it was never unlocked before you upgraded to ...79 or later
what a coincidence i just got a xt926 and im at the same spot.. 9.30.1 rooted but locked ... iguess we're screwed huh
impinball said:
I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.
Click to expand...
Click to collapse
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".
skeevydude said:
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).
impinball said:
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).
Click to expand...
Click to collapse
First, there is no Dev Edition Fastboot....the closest would be Bell ICS since Bell shipped unlocked/unlockable Atrix HD's.
You don't flash zip files with fastboot flash.....Why is this becoming an issue these days?* The kernel is "fastboot flash boot boot.img"
*just thinking out loud
EDIT: Just realized that this was the RAZR HD forums.....just replying to quoted posts this morning....Not sure about RAZR HD Dev Edition fastboots....
Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The shame is, I never cared about unlocking the bootloader, as I prefer to stick to OTA's, but I do require root. So that's all I've ever done. I'm successfully rooted with the locked bootloader on 9.30.1, but it seems (at least as far as I've read on here) that I'm stuck there as I can't go anywhere else and maintain root. Would love kitkat, but root is essential.
Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.
killrhythm09 said:
Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.
Click to expand...
Click to collapse
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk
iBolski said:
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
This. It's no coincidence that the xt925 can be unlocked through Motorola. Carriers are always the problem here in the US.
crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Well, in actual reality, the XT926 was never meant to be unlocked. It was only unlockable via an exploit, just like obtaining root for locked devices is an exploit in the security of the OS/device.
So, there never really was a "sunset" for unlocking this device as it wasn't meant to be. Only after the exploit was found did a patch come out to stop that exploit from being utilized on any remaining unlocked phones, current or future.
So, when there is an exploit to unlock a device, your best bet is to take advantage of it immediately.
When I got my RAZR HD, it was as a warranty replacement for my OG RAZR MAXX. When I fired it up, it stated there was an OTA available. I immediately told it no and then went straight to the forums here and on another site to investigate what my options were. When I found out that there was the possibility of my unlocking the bootloader, I immediately went to where the tool was and downloaded it. I then proceeded to read and then ask questions on if my phone couldn't unlock, would it hurt it. SamuriHL helped me out a great deal and that is how I found all his tools and how much help he provides. If it weren't for him, I wouldn't have discovered that I could unlock my bootloader.
Usually, I investigate the phone I'm interested in to see if:
1. Can the bootloader be unlocked (or is it already unlocked)?
2. Is there a known root exploit IF the bootloader cannot be unlocked?
3. What are the ROM options (safestrap, cwm, twrp recovery)?
It's definitely something I normally would look into, but I didn't know that I was going to receive the RAZR HD. Once I discovered the possibility of unlocking the bootloader, I was hoping beyond all hope that it could happen and it did. How I received a replacement phone that wasn't patched to the latest OTA was beyond me, but that is the reason I refused the OTA when I first fired up the phone. I had already read about other "horrors" of people taking an OTA and then finding they couldn't root or do other things with their phones.
Lesson learned is, NEVER take an OTA until you've fully researched what it does and what it might prevent.
I'm totally new to the Android world and i spent many hours to read this forum to learn as much as possible about my device and what i can do with it. But now, i need your help on a few things.
KitKat vs Lollipop, does it make sense to upgrade to Lollipop now or should i wait? Is there any major know bugs?
Since that i only have a 8gb device, i would like to clean the apps as much as possible. There's many apps that i don't need but they can't be uninstalled. For example, all the Motorola apps (is there something that we really need from them?), a few google apps like Google+, Google Play Films, Hangouts, etc that i will never use.
I want a stable ROM that i don't need to patch every day to solves problems. When i read about CM12 for Moto G, i see people that have problems here and there and wait for the next daily build to give it a try. I don't want to play that game!
If i install a custom rom, i guest that future updates will not come from Motorola. How the updates work afterward?
It's ok if i must have my device rooted
I have read about stock lollipop optimized version by lost101 but it don't think that the versions currently available will work for me. I'm in Canada and the versions that i see is Brazil or Asia.
thank you for you help!
You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.
Well what I will say is. I'm in the uk using lost101s BR optimized and I'm very pleased with it.
audit13 said:
You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.
Click to expand...
Click to collapse
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032
skoub2 said:
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032
Click to expand...
Click to collapse
You must unlock boot loader first then flash a custom recovery (manually or there is a tool in the development section) then rooting next.
Unlocking the bootloader allows you to install non-Motorola software. With a locked bootloader, the only software that can be loaded on your phone would have to be digitally signed by Motorola.
Rooting gives you administrative access to the system files.
You may not need an unlocked bootloader to get root and you do not need root to unlock a bootloader.
Start here to get the bootloader unlock code: https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
I tried to install TWRP (any version available) but it take like 1 minutes to show the home screen and im not able to "swipe to unlock". So i have installed Philz recovery and then installed lost101 Retail Brazil 5.0.2 Stock ROM (Optimized) v1.1a. I'm playing with it right now and so far so good.
Hello everyone! I didn't want to root my new MOTO G 2015 but I need more storage if I want to install more app's, I saw with root permissions we can transfer full sized app's to the sd, is it true? and how? I've seen already a guide how to root moto g 2015, but know I want to know how to transfer full sized app's to the SD and then i'll decide if I want to root or not.
Do you think I should root? It will be better If i want more storage?
Is it safe? The Lollipop will be automatically installed after the root? I have no need on install other Android OS.
Thank you!
Hey! I can see that you are new here, but rooting your phone isnt gonna delete anything of your data if you search on this forum for Link2sd than you will find a tuturial for how to do that. But if you dont understand any of the words "Brick" or "fastboot" you should do some research first.
success!
HelpMeruth said:
Hey! I can see that you are new here, but rooting your phone isnt gonna delete anything of your data if you search on this forum for Link2sd than you will find a tuturial for how to do that. But if you dont understand any of the words "Brick" or "fastboot" you should do some research first.
success!
Click to expand...
Click to collapse
Hello HelpMeruth! And thank you for replying my question!
Here's what I already searched this is , i've got alot of information already but the information I got says my phone will be formatted I think. Brick I remember that word a long time ago when the PSP Scene I know it's not android but I remember it, it's like having a non funcional phone, bricked.
Here's the guide I saw: (I can't post links, if you can search on the youtube : "Moto G 3rd Gen(2015) - How to Root - Unlock Bootloader & Custom Recovery") and tell me if that guide will not brick or format my moto g 3
Any chance of getting bricked? It will remove my SIM Service? I have the phone just for a week and the warranty it's 2 here's, If I root the warranty goes out, is it worth rooting?
Thanks for the reply sir and yes i'm really new in the android scene, just came from the iOS one, got mad at iOS
I can confirm that your phone will not be formatted
The word brick means that your phone wont start up.
Its a gamble for everyone to root, so when you are gonna do it try just booting Twrp. That is the safest way to test it.
But strart with unlocking your bootloader thats already a big step for rooting (unlocking bootloader will format your data!)
If you got any questions send me message!
Its your choise to root or not
HelpMeruth said:
I can confirm that your phone will not be formatted
The word brick means that your phone wont start up.
Its a gamble for everyone to root, so when you are gonna do it try just booting Twrp. That is the safest way to test it.
But strart with unlocking your bootloader thats already a big step for rooting (unlocking bootloader will format your data!)
If you got any questions send me message!
Its your choise to root or not
Click to expand...
Click to collapse
You do NOT need to unlock bootloader in order to root.
You DO need to unlock your bootloader for TWRP, unless booted temporarily.
Sent from my MotoG3
christopherrrg said:
You do NOT need to unlock bootloader in order to root.
You DO need to unlock your bootloader for TWRP, unless booted temporarily.
Sent from my MotoG3
Click to expand...
Click to collapse
What? you have to unlock the bootloader in order to boot/flash twrp.
and with twrp you can root, how do you root with locked bootloader?
HelpMeruth said:
What? you have to unlock the bootloader in order to boot/flash twrp.
and with twrp you can root, how do you root with locked bootloader?
Click to expand...
Click to collapse
Root toolkit
http://forum.xda-developers.com/showthread.php?p=62922929
Sent from my MotoG3
christopherrrg said:
Root toolkit
http://forum.xda-developers.com/showthread.php?p=62922929
Sent from my MotoG3
Click to expand...
Click to collapse
You shouldnt be able to root with a locked bootloader, i quote: 'A locked bootloader locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader.' found on this site https://www.quora.com/What-are-the-main-differences-between-Rooting-and-Unlocking-Bootloader
that tool just has a build in fastboot/adb and automate things for you.
(sorry for my bad english)
HelpMeruth said:
You shouldnt be able to root with a locked bootloader, i quote: 'A locked bootloader locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader.' found on this site https://www.quora.com/What-are-the-main-differences-between-Rooting-and-Unlocking-Bootloader
that tool just has a build in fastboot/adb and automate things for you.
(sorry for my bad english)
Click to expand...
Click to collapse
Yeah after doing some research motorola devices seem to have that in place. I was speaking generally from a vanilla aosp aspect. Good find.
Sent from my MotoG3
Btw, If I install CyanogenMod it will reset my moto g firmware? Or install another firmware version? Thanks
M05K said:
Btw, If I install CyanogenMod it will reset my moto g firmware? Or install another firmware version? Thanks
Click to expand...
Click to collapse
Installing cyanogenmod will still keep you on 5.1.1 your device will just be modified (custom tweaks etc..) so if you have to unlock your bootloader it will void any warranties you have. If you don't have one or don't care just make sure to read carefully as you sound relatively new to CM and you don't want to brick your device.
Sent from my MotoG3
christopherrrg said:
Installing cyanogenmod will still keep you on 5.1.1 your device will just be modified (custom tweaks etc..) so if you have to unlock your bootloader it will void any warranties you have. If you don't have one or don't care just make sure to read carefully as you sound relatively new to CM and you don't want to brick your device.
Sent from my MotoG3
Click to expand...
Click to collapse
Yes it will be modified to cyanogenmod firmware right? So the firmware updates from MOTO G 3 I had installed will go resetted to the cyanogenmod firmware right?
M05K said:
Yes it will be modified to cyanogenmod firmware right? So the firmware updates from MOTO G 3 I had installed will go resetted to the cyanogenmod firmware right?
Click to expand...
Click to collapse
Correct.
Cm12.1 is just 5.1.1 that's why I said it would.
You may see custom aosp 6.0 ROMs before any real factory builds.
Sent from my MotoG3
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Jut install SuperSU ZIP using TWRP recovery
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Could you read my post first?
squid2 said:
Your bootloader must be unlocked to use this recovery.
Click to expand...
Click to collapse
unlocking bootloader = voiding warranty.
shawly said:
Could you read my post first?
unlocking bootloader = voiding warranty.
Click to expand...
Click to collapse
If you're worried about voiding the warranty, you're on the wrong site.
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
I used to root in one click in just one method on my previous phone xperia sp but i dont know this phone have any toll which will work or not?
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
zephiK said:
Just unlock the bootloader and root. You're making it too difficult for yourself, the whole point of the bootloader being locked is to prevent changes being made to the system.
Its like saying, you're going to break your windows to get into your house when you can just unlock the door.
Just unlock the bootloader and flash supersu for root.
Click to expand...
Click to collapse
Also this.
Ragarianok said:
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
Click to expand...
Click to collapse
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, I also don't plan on using custom roms, I just want the root features so I can undervolt like I said and IF I could root it permanently without unlocking the bootloader, why not?
I'm not worried, it would just be convenient to have root without losing the warranty, that's it.
As far as I know you may be able to do it search kingroot in Google then download the apk and install it then open in and follow the instructions
shawly said:
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, ...
Click to expand...
Click to collapse
Then leave the device stock ...
If you want the best of both worlds (root & warranty), then go buy a Nexus. Motorola drew a line in the sand as to what they will support, while still empowering owners with the option to unlock the bootloader.
Sent from my MotoG3 using Tapatalk
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Not really. While I've unlocked my previous phones, my new g3 I'm leaving locked for the first year, while the warranty lasts. But this site still has a few helpful stuff.
Ragarianok said:
...You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever...if you're worried about voiding your warranty, you shouldn't be trying to modify your device...
Click to expand...
Click to collapse
He just wants the warranty, but he doesn't care about rooting it because there's not really anything wrong with rooting if you know what you're doing and how to fix it.
Sent from my MotoG3 using XDA Free mobile app
---------- Post added at 01:03 PM ---------- Previous post was at 01:03 PM ----------
And to answer the question; you need to unlock the bootloader to root
Sent from my MotoG3 using XDA Free mobile app
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Jdwright0819 said:
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Click to expand...
Click to collapse
Towelroot is exploiting a bug in the Linux Kernel in order to root a device. This bug was already fixed in June 2014.
On all Kernels with a later build date Towelroot will most likely not work.
For sure it will not work on the Moto G3 with a kernel build date more than one year after this bug was fixed.
Thanks!
shawly said:
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Click to expand...
Click to collapse
It's probably been answered already but those exploits are security flaws with the SE Linux system and so with each release of android these have been patched, by 5.1 these security holes have been fixed and now by locking the bootloader
It's like just locking down and modifications to the system partition so unfortunately you can't root without unlocking, unless you have android versions lower down
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
I have unlocked bootloader and i m on stock recovery amd on stock rom without rooted. Can i install twrp without pc
Are you root yet
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Ankur1 said:
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Click to expand...
Click to collapse
What version of TWRP did you use coz I know there were some bugs on the moto range with TWRP 2.X.
I would completely wipe device using stock recovery, including dalvic/cache/data everything just to be on the safe side, then download the TWRP zip to your computer and flash it on using ADB.
Boot up normally and move the superSU zip from the link to your phones internal storage. Then reboot to TWRP, select install and pick the zip file.
superSU.zip:
http://dl-1.va.us.xda-developers.com/3/6/5/5/4/0/1/BETA-SuperSU-v2.62-3-20151211162651.zip?key=u0OeGV4-4s02KJXqrXJ-gg&ts=1466705675
If you get stuck this might help:
https://motog3.com/unlock-bootloader-install-twrp-root-moto-g3/
No longer works
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Perhaps you can offer wisdom on this? I rooted my Moto G 3rd Gen once, wrecked something and had to go back to factory, then try to reroot again. Problem. No matter what I do in setting the device back to factory, the bootloader stays unlocked and reads the system software as "modified" which then seems to bork installing SuperSU. I install SuperSU via twrp and it goes fine, no errors, but when I reboot the system is lost in a loop of the "bootloader unlocked" screen.
So I cannot RE-lock the bootloader (ala setting the phone back to true factory) and after I flash SuperSU the phone refuses to successfully bootup.
Any aid? Ideas?
I had failed to backup my phone the first time with twrp and so to set to factory I downloaded the stock retail xml.zip for my phone and reflashed the entire thing via fastboot. Reinstall twrp, and try to root and the endless boot loop begins.
So I came to this thread to look into the possibility rooting my phone via another means that MIGHT work.
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.