Database Users

Moto G Rooted! Root Tool Inside

GO GO GO!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
YOU NEED YOUR BOOTLOADER UNLOCKED TO CARRY OUT THIS PROCESS. It's easy using fastboot, which is included in the download below. The instructions on the Motorola site are very straightforward - visit this page to get started. Unlocking the bootloader will wipe your device.
This Superboot installs SuperSU version 1.80. Note that rooting may affect your ability to receive future OTAs, reverting back to stock is easy enough. We'll cross that bridge when we come to it.
Click to expand...
Click to collapse
Full Guide
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/ (Thanks to helinhof)
http://t.co/7icWLuTwSW (Thanks to munchy_cool)
"PaulOBrien 3h
Nobody has rooted the Moto G yet? Well that won't do will it. Superboot uploading now... pic.twitter.com/6B9qcA6kfs"
"Moto G root tool online soon. It's my usual process, a Superboot image..."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/PaulOBrien

Greaatt.. wainting for this..

bgochoa said:
Greaatt.. wainting for this..
Click to expand...
Click to collapse
We are two!

Moto G - Rooted
Here we go guys!
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/

its a go http://t.co/7icWLuTwSW

http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/

Nice one...I´ve been waiting for this...the process took less than 10secs. Thanks!

Does it works in the german version?

FighterFX said:
Does it works in the german version?
Click to expand...
Click to collapse
It worked for me on my German Retail Moto G.

alex1301 said:
It worked for me on my German Retail Moto G.
Click to expand...
Click to collapse
Mine too, 14.71.8.Retail.en.DE

has anyone got this to work with the tesco version?

so how much space is there for system and for the apps
on 8 gb version

Props and thanks to [email protected], i can now consider buying this phone

i have a problem .... mmy cel is unblock but no rooting u.u

Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption

can confirm that this is working, done in under a minute

burma said:
Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption
Click to expand...
Click to collapse
I was able to get it working only after reflashing stock http://forum.xda-developers.com/showthread.php?t=2542219&page=3 then encrypting and then reflashing superboot.
So maybe it is worth updating instructions:
1) Unlock bootloader (wiping all data)
2) Encrypt your phone
3) Flash superboot

Thanks! only a question... If i unlock the bootloader and root the moto g, will I still receive the kitkat OTA update?

still not rooting
unlocked the boot loader, tried to root with super boot, but didnt work, flashed to generic uk, tried to root again and it still wont say rooted or show the su app, please can someone help?!

Rooted...wireless tether working with wifi router app. However, I got notified of 4.4 update today and it downloads, starts install, then fails.

Moto X No service error

After i flashed Twrp my phone wont get any service and i have checked imei and it is at 00000000. Is there a way to fix this?
I have my original imei number with me
Any help would be appreciated

R0gueThund3r said:
After i flashed Twrp my phone wont get any service and i have checked imei and it is at 00000000. Is there a way to fix this?
I have my original imei number with me
Any help would be appreciated
Click to expand...
Click to collapse
You pure or style? Try pulling sims card and reinsert? Not heard that one just from flashing twrp.
Sent from my XT1575 using Tapatalk 2

milski65 said:
You pure or style? Try pulling sims card and reinsert? Not heard that one just from flashing twrp.
Sent from my XT1575 using Tapatalk 2
Click to expand...
Click to collapse
I am using the pure and i have tried reinserting the sim card , and i checked the sim card in another phone and it works

R0gueThund3r said:
I am using the pure and i have tried reinserting the sim card , and i checked the sim card in another phone and it works
Click to expand...
Click to collapse
You've done nothing else but unlock bootloader and twrp via adb?
Sent from my XT1575 using Tapatalk 2

milski65 said:
You've done nothing else but unlock bootloader and twrp via adb?
Sent from my XT1575 using Tapatalk 2
Click to expand...
Click to collapse
That and adding super Su

R0gueThund3r said:
That and adding super Su
Click to expand...
Click to collapse
I'll keep looking, but I haven't seen that mentioned.
Sent from my XT1575 using Tapatalk 2

I've got the same issue, unlocked the bootloader and flashed TWRP via the command line (as well as SuperSU via TWRP). Rebooted and re-inserted the SIM multiple times to no avail.
Edit: I've tried looking for the APN settings on my device, but that seems to have disappeared as well? here's a screenshot of what my settings screen looks like: https://gyazo.com/90f9ab027357cea8009bdae1a0346690
Edit 2: I checked my IMEI, and it's weird...I see every digit except for the last one when I look for it via the *#06# dialer command (I know because I cross-referenced with the IMEI printed on the box the phone came in).
---------- Post added at 11:46 AM ---------- Previous post was at 11:24 AM ----------
R0gueThund3r said:
That and adding super Su
Click to expand...
Click to collapse
have you had any luck resolving the issue?

Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.

rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
I used that to reset but i still get the problem

R0gueThund3r said:
I used that to reset but i still get the problem
Click to expand...
Click to collapse
Did you solve your problem??
im getting no service after Unlock bootloader and flash TWRP.

rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
I also have lost service after flashing some ROMS on my VZ MXP. Reinserting the SIM, reflashing other ROMs or reflashing the radio haven't helped. I'll give this a try. Thanks.

What ROM are you using? Did you recently upgrade from lollipop to marshmallow or marshmallow to nougat? Have you ran fastboot erase all (if not DO NOT that causes the imei to be permenantly erased). Have you tried flashing files from the factory image? This is very strange.

thebaconbox said:
What ROM are you using? Did you recently upgrade from lollipop to marshmallow or marshmallow to nougat? Have you ran fastboot erase all (if not DO NOT that causes the imei to be permenantly erased). Have you tried flashing files from the factory image? This is very strange.
Click to expand...
Click to collapse
The loss of service occurred after flashing the 11/11/16 nightly of AICP, which I believe is Nougat. I had already had the 11/09 and 11/10 nightly installed. The 11/10 seemed to perform OK, except battery life was short. The 11/11 version caused a bunch of com.android.phone errors. I then reflashed the stock ROM posted here, but the problem persists. I haven't tried the factory image. Do you have a link to the process to do that?. I'm currently using my GS3 and that phone is way too slow, definitely would like to go back to my MXP.

rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
OK, I used this tool. It fixed the problem, and have restored service. Had to also do the wifi fix, which is discussed later in that thread. Thank you.

can u please me how you fix that , i have few units same issue no service

Gsm UK said:
can u please me how you fix that , i have few units same issue no service
Click to expand...
Click to collapse
Your units are not the same, they are XT1578 engineering units which were intended for Verizon specific service, but never came to fruition... those units are likely fancy paperweights now, no ROM or radios were ever released for them since they used a special chipset.

This may be a stupid question, but did you clean flash or dirty flash the stock ROM and/or aicp? Make sure you fully wipe/format system, boot, cache, data, and dalvik cache when flashing new ROMs.

I also have problems with the network, no signal, plus my appears the normal imei, Moto X Style Brazil.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anyone from you guys with no service devices got the solution or not?

Can't Re-Unlock the Bootloader

I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!

deleted

So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app

have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems

I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.

I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!

scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)

[RECOVERY] TWRP 3.1.1-0 for Yotaphone 2 [YD201/YD206]

TWRP 3.1.1-0 for Yotaphone 2​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial custom recovery for Yotaphone 2, built from source by me.
This recovery has kernel built from source, MTP and all bells and whistles should be working. Bug reports are always welcome
Download:
V6.0:
https://forum.xda-developers.com/showpost.php?p=73379148&postcount=91
Old versions:
https://mega.nz/#!CEIQSZiI!qA6hJOY5aZhsX05xkqXEHAPlN7IvE1BGTOzxU62j1qk
Flash at own risk!
I take no responsibility for anything you do to your device.
Installation:
You must have unlocked bootloader to install TWRP!
Install using Fastboot:
Code:
fastboot flash recovery twrp_yotaphone2.img

thanks, going to test it ^^
---------- Post added at 12:57 PM ---------- Previous post was at 12:18 PM ----------
Seems unstable, took lots of time to apply option, when boot to recovery, switch auto to backup .... when select backup its switching to wipe cache....

satsuki_yatoshi said:
Seems unstable, took lots of time to apply option, when boot to recovery, switch auto to backup .... when select backup its switching to wipe cache....
Click to expand...
Click to collapse
Are you touching the back screen? I noticed that it is taking input from both screens.

Amazing! I guess it does not support data partition decryption though.. Does it?! Hope to see it someday! NTFS support for OTG would be last missing thing.
Hope people will report soon if backup AND restore work fine.. I'm testing backup, but don't dare to try erase/restore! I confirm back screen controls main (reverse).

ok, full tested with backup, restore .... working great as long a the EDP screen ins't pressed ^^

Works.
Confirmed the bug with touches on e-ink display, so be carefully.

I'll make an updated version with the e-ink screen disabled.
Is encryption working?

I don't use it myself so not tested so far ^^

Côme on, be brave, test it.. ?
Sent from my Umi Super

Please someone!
Sent from my JY-S3 using Tapatalk

Why don't you test it yourself if encryption is the feature you want...

Okay, new version with rear touchscreen disabled is up:
https://mega.nz/#!LR5EDJQS!kkshqaRPs5YUZrApvy-6Wi9xkqk0EB0CDYXOuFPbZBQ

satsuki_yatoshi said:
Why don't you test it yourself if encryption is the feature you want...
Click to expand...
Click to collapse
Because there is no way to decrypt and I don't have time to reinstall all.
Sent from my JY-S3 using Tapatalk

can't you do 2 backups one decrypted and one encrypted .... so you can test and restore ?

The data partition where backups are is what's going to be encrypted.
You didn't get the point. I never talked about encrypted backups.
I just talked about encrypted DATA PARTITION, and it's decryption in TWRP.
Sent from my JY-S3 using Tapatalk

So make a backup > copy backup to computer > make test > if bugs then reset phone from yotaflasher, flash recovery TWRP, copy backup from computer, then restore

I had issue restoring backups and Yota flasher seem troublesome (see related thread), which means lots of time required for all that. It's the reason I don't try it.
Sent from my YD201 using Tapatalk

evilracer123 said:
I'll make an updated version with the e-ink screen disabled.
Is encryption working?
Click to expand...
Click to collapse
I tested it and decryption of data partition on TWRP don't work, it doesn't mount the encrypted data partition.
goja said:
Because there is no way to decrypt and I don't have time to reinstall all.
Click to expand...
Click to collapse
You can make a backup prior to encrypt the data partition, move it to a usb pendrive (or make to it directly), and restore it after encrypt data partition using the format data partition option in TWRP

Thanks for testing ! Evilracer, could you add that feature?
Sent from my Umi Super

I'll see what I can do. :fingers-crossed:

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.