Remember! Rooting the Moto G 4G LTE will void your warranty! Neither I, nor the XDA-Developers Forum is responsible for bricked devices!
What you'll need
Code:
1. A Moto G 4G LTE running Android 4.4.3 KitKat. (Codenamed peregrine or xt1045)
2. The Moto G xt1032 TeamWin Recovery Image (attached to this post, Thanks TeamWin)
3. ADB and Fastboot Drivers. You can get these from the regular Moto G Toolkit.
4. The [URL="http://download.chainfire.eu/supersu"]SuperSU[/URL] zip (thanks Chainfire)
5. A brain.
First, you'll need to unlock the bootloader on your Moto G. This can be done from the Motorola bootloader unlock website. This will delete all your data!
Reboot your Moto G, and plug it into your computer with the USB cable, then copy the SuperSU zip to the Internal Storage(NOT the sdcard)
Next, copy the TeamWin Recovery image to the same location as your installed ADB and Fastboot.
Open a command prompt, or terminal in Linux/Mac, and execute the cd command.
Code:
cd /path/to/folder/with/recoveryandadb
Next, boot into the bootloader by powering down, and pressing the power and volume down buttons simultaneously.
Then, type this exactly
Code:
fastboot boot recovery.img
Finally, when TWRP loads, go to install and navigate to the location of the SuperSU zip in the internal storage.
Reboot, and enjoy a rooted Moto G 4G LTE
Why u fastboot boot instead of installing? Wont hurt your device. Also if TWRP is overwritted by stock recovery u can disable that function.
Delete or rename "recovery-from-boot.p" from /system
Enviado desde mi Moto G mediante Tapatalk
ChavitoArg said:
Why u fastboot boot instead of installing? Wont hurt your device. Also if TWRP is overwritted by stock recovery u can disable that function.
Delete or rename "recovery-from-boot.p" from /system
Enviado desde mi Moto G mediante Tapatalk
Click to expand...
Click to collapse
The reason is because when I tried fastboot flash, it damaged the recovery partition, and since the stock images for the 4G LTE version haven't been released yet, I couldn't get a stock recovery image. So, recovery would just say "boot failed"
Hitorijanae said:
The reason is because when I tried fastboot flash, it damaged the recovery partition, and since the stock images for the 4G LTE version haven't been released yet, I couldn't get a stock recovery image. So, recovery would just say "boot failed"
Click to expand...
Click to collapse
How did u "damage" recovery partition?
Enviado desde mi Moto G mediante Tapatalk
ChavitoArg said:
How did u "damage" recovery partition?
Enviado desde mi Moto G mediante Tapatalk
Click to expand...
Click to collapse
I probably should've stated that better. Basically, the image flashes, but going into recovery doesn't work anymore.
EDIT: Nevermind. I figured it out and it worked great! Wahoo!
When I type in "cd /path/to/folder/with/recoveryandadb", it says "the system cannot find the path specified"?
Hitorijanae said:
Open a command prompt, or terminal in Linux/Mac, and execute the cd command.
Code:
cd /path/to/folder/with/recoveryandadb
Next, boot into the bootloader by powering down, and pressing the power and volume down buttons simultaneously.
Then, type this exactly
Code:
fastboot boot recovery.img
Finally, when TWRP loads, go to install and navigate to the location of the SuperSU zip in the internal storage.
Click to expand...
Click to collapse
So after typing in exactly "fastboot boot recovery.img", it didn't work.
EDIT: Nevermind, got it to work. Not too confusing actually, thanks.
Worked! Restore ?
Hi
Your instructions worked properly on both G 4Gs I recently purchased.
However, one of the phones is having problems with the SD card. Keeps saying it was
removed unexpectedly.
I want to restore the phone to factory with boot loader locked so I can ship it back for warranty.
2 Questions:
How do I restore it?
Has unlocking boot loader and rooting it left a trace that the show ?
Thanks
Edit: worked on my xt1039 as a temporary solution If anyone is feeling experimental
bigjackt said:
One of the phones is having problems with the SD card. Keeps saying it was
removed unexpectedly.
I want to restore the phone to factory with boot loader locked so I can ship it back for warranty.
2 Questions:
How do I restore it?
Has unlocking boot loader and rooting it left a trace that the show ?
Thanks
Click to expand...
Click to collapse
The sdcard issue is a known problem with some cards, check this thread: http://forum.xda-developers.com/showthread.php?t=2783238 supposedly motorola is working on a fix. Do note that this phone will not use UHS-1 or UHS-2 speeds so buying those cards is a waste of money. Check this out aswell:https://forums.motorola.com/posts/7e59cc7baf
If you still have your receipt maybe you can return the card for a different model and try it in store? Depending on how/when you purchased it also I would avoid class-10 or UHS cards as those seem to be less likely to work in this device currently.
1. Turn the phone off hold power and volume down for a few seconds let go and you should instantly see a menu pop up. Navigation: Volume down scrolls down then goes back to the top of the list, volume up selects power... reboots.
You voided the warranty when you unlocked the bootloader, unless your in UK you can't return it. Returning it probably won't fix the issue anyway, they did say they were working on a fix but until that is available I doubt they can help you.
2.You input your device code when you unlocked it on motorola's website unless there is a way to change that to a legitimate one then no, I highly doubt you can hide that you unlocked the bootloader.
XT1045?
I have the Moto G 4G LTE XT1045. This file is from the other Moto G, the original one (falcon). Doing this in my phone will not brick it?
jensen2112 said:
I have the Moto G 4G LTE XT1045. This file is from the other Moto G, the original one (falcon). Doing this in my phone will not brick it?
Click to expand...
Click to collapse
Note for the new ones here:
XT1045 is code name "peregrine" the other Moto G's, with exception of the UK, and probably other 4G LTE..All other models are code name "falcon"..the two are NOT compatible..
Moto X code name is "ghost"
Droid Maxx code name is "obake"
The above mentioned are NOT interchangeable.. (UNLESS) you are a Dev and experienced in Porting..
Sent from my 4.4.3_21.23.4
(Unlocked) XT1045 Moto G 4G LTE
http://waynekent.com/page6.html
NWKENT said:
Note for the new ones here:
XT1045 is code name "peregrine" the other Moto G's, with exception of the UK, and probably other 4G LTE..All other models are code name "falcon"..the two are NOT compatible..
Moto X code name is "ghost"
Droid Maxx code name is "obake"
The above mentioned are NOT interchangeable.. (UNLESS) you are a Dev and experienced in Porting..
Sent from my 4.4.3_21.23.4
(Unlocked) XT1045 Moto G 4G LTE
http://waynekent.com/page6.html
Click to expand...
Click to collapse
XT1039 is Peregrene as well.
jensen2112 said:
I have the Moto G 4G LTE XT1045. This file is from the other Moto G, the original one (falcon). Doing this in my phone will not brick it?
Click to expand...
Click to collapse
So far as I can tell, no. The command being used with that image is "fastboot boot", not "fastboot flash". The former is (so far as I can tell) a "download this image and use it to boot once" command; it (if I'm reading correctly) wouldn't actually overwrite the recovery on your phone. The latter, OTOH, would surely overwrite your recovery, and would probably be ill-advised here (judging by some other posts, the OP gave it a try and subsequently recovery on the OP's phone stopped working).
So unless that recovery image is so horribly broken that even just booting with it will release the magic smoke (unlikely, as I doubt TeamWin would release it in that state ), I suspect it'd be fine. Probably. Just make sure you get the command right!
DISCLAIMER: I'm not actually fully familiar with fastboot myself, but I've worked with similar utilities on similar devices before (in particular, for my old Nokia N900). Have seen similar distinctions between "use this image this one time only" and "flash this image to the device and use it", though, so I'm feeling good about what amounts to an educated guess here.
Fully working CWM Recovery (Unofficial) Now Available Here for Moto G 4G/LTE. ie. can 'fastboot flash' this version.
Hey guys so I did this fully, seemed to work, but when I go back and launch bootloader and try to run recovery it says "boot failed"
Initially I installed SuperSU through TWRP like stated and functions, but I feel like I dont actually have a recovery installed..?
Viqsi said:
So far as I can tell, no. The command being used with that image is "fastboot boot", not "fastboot flash". The former is (so far as I can tell) a "download this image and use it to boot once" command; it (if I'm reading correctly) wouldn't actually overwrite the recovery on your phone. The latter, OTOH, would surely overwrite your recovery, and would probably be ill-advised here (judging by some other posts, the OP gave it a try and subsequently recovery on the OP's phone stopped working).
So unless that recovery image is so horribly broken that even just booting with it will release the magic smoke (unlikely, as I doubt TeamWin would release it in that state ), I suspect it'd be fine. Probably. Just make sure you get the command right!
DISCLAIMER: I'm not actually fully familiar with fastboot myself, but I've worked with similar utilities on similar devices before (in particular, for my old Nokia N900). Have seen similar distinctions between "use this image this one time only" and "flash this image to the device and use it", though, so I'm feeling good about what amounts to an educated guess here.
Click to expand...
Click to collapse
Thanks. I notice that once I did the process. "fastboot boot" only boot the device, it don't flash anything. In my case I only want the root, this works perfectly for me.
XT1039, here. Worked fine for me!
Now I can actually install apps without worrying about the internal memory evaporating. It's almost as good as Gingerbread! :silly:
install 4.4.4 after root.
Thanks for this guide it worked perfectly.
But what is the newbiest way to remove root, install 4.4.4 update.
And return to root. I tried using the supersu app to un-root but it didn't work.
Has anyone tried this method? http://www.droidviews.com/root-moto-g-4g-lte/
Seems I am torn between fastboot boot as described in this tread, or the fastboot flash described in the droidviews instructions. Although I am not interested in ROMs, I do want the ability to backup and restore the way TWRP does it. I have TWRP on my Samsung Galaxy Tab 3 10.
The two files associated with this TWRP boot/flash are:
twrp-2.7.1.0-peregrine-201407161845.img (from droidviews instructions)
openrecovery-twrp-2.7.1.1-xt1032 (from this thread)
Thanks
Brian D said:
Has anyone tried this method? http://www.droidviews.com/root-moto-g-4g-lte/
Seems I am torn between fastboot boot as described in this tread, or the fastboot flash described in the droidviews instructions. Although I am not interested in ROMs, I do want the ability to backup and restore the way TWRP does it. I have TWRP on my Samsung Galaxy Tab 3 10.
The two files associated with this TWRP boot/flash are:
twrp-2.7.1.0-peregrine-201407161845.img (from droidviews instructions)
openrecovery-twrp-2.7.1.1-xt1032 (from this thread)
Thanks
Click to expand...
Click to collapse
fastboot boot --> temporary boot from computer, no files modified on device
fastboot flash --> files are modified on device
This thread (OLD) --> The recovery in this thread is actually for Moto G (falcon). Do NOT fastboot flash - it will not work for our devie (Moto G 4G - peregrine). Only fastboot boot works. It was useful for installing SuperSu and gaining root (but you couldn't boot into custom recovery again without computer as it remained stock recovery)
Moto G 4G Development Thread on CWM, TWRP and Philz recoveries (NEW) --> These are fully functional recoveries specific for the Moto G 4G (peregrine) - Our device! Thus we can 'fastboot flash' onto our device and it will work. Droidviews has done a nice guide on how to 'Fastboot flash' with TWRP. But you can flash the otehr two recoveries too (just download the file from the thread and flash like droidviews says). Choose whichever you prefer!
You can then install SuperSU for root, and reboot into recovery at any time to install/backup/restore etc with recovery.
Related
Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.
Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP
Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?
Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?
Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat
Thanks for the guide. I've already recommended it to someone who was having problems.
jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.
Updated root & TWRP installation guide for Moto XT1225 and XT1250
Plus other goodies! Also see posts #2 and #3.
[UPDATED GUIDE] How to unlock your MOTO MAXX/MOTO TURBO bootloader, install TWRP and gain root access
INTRODUCTION/EXPLANATION
I own three Moto XT1225 and the original root/recovery thread from 2014 is here. I rooted two of my XT1225 phones using that guide. However, it's a very OLD guide from 2014, made before we even had TWRP recovery and the phone was on KitKat 4.4.4. We now have factory Motorola Marshmallow firmware. You should be very cautious using it! The ADB steps are OK, but would be best to use TWRP recovery in place of the primitive recovery listed in that thread.
@alexcreto and @respider did an awesome job at the time, but a lot of dev work has happened since 2014! We have official TWRP. We are now two Android versions away from Kitkat 4.4.4.
Thus, the need for THIS updated guide. I wrote these steps as a post in that thread, but am now making it a standalone thread. @TheSt33v did a very good job writing up a similar guide for the Droid Turbo XT1254, and while the bootloader unlock portion is different for that Quark model, the TWRP installation and root are the same. With his permission, I have copied those portions of his guide, editing slightly to clarify (in my opinion) or adding some more instructions or combining a few steps for convenience.
The bootloader unlock portion for every Motorola Quark -- except the Droid Turbo XT1254 -- is very easy and free. If you have a Droid Turbo XT1254, go here. IF you have any other Quark -- Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, keep reading...
________________________________
Section 1: UNLOCK YOUR BOOTLOADER
Before anything, go to the Motorola website and unlock your bootloader.
Unlocking the Quarks -- "international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250 -- is FREE, via the Motorola website.
UNLOCK YOUR BOOTLOADER
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You release Motorola from any liability, get a code and unlock your bootloader.
If you get an error message at this step that your phone is not eligible, then you have typed in something wrong (or you have a Verizon Droid phone). Helps if you Google how to copy and paste from Windows command window. There's a LOT of alphanumeric characters you have to type. First time I tried to unlock my bootloader I mis-typed something. :crying: Copying and pasting from the Windows command window fixed that problem! :good:
You'll get an email with the bootloader unlock code. The email will also have a link back to the instructions. But the code is what's important.
{
"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"
}
You will receive this fairly instantly. If you don't get it, make sure you checkmarked you agree to all the conditions. Also check your spam folder.
Of the Quark series, only Verizon's Droid Turbo XT1254 is exempt from this free Motorola bootloader unlock and this guide is NOT for the Droid Turbo XT1254.
This Motorola bootloader unlock guide will help you:
HOW TO UNLOCK MOTOROLA BOOTLOADERS
https://androidmtk.com/unlock-bootloader-on-any-motorola-device
_____________
Once you have unlocked your bootloader, follow THESE steps:
Section 2: INSTALLING TWRP
Team Win Recovery Project is arguably the most important tool to have on a bootloader-unlocked phone. This is how you install it:
0. If you haven't already, go click the Android Build number in About Phone several times to become a "Developer". Then go into Developer Options and allow USB Android Debugging. If it asks you to allow your PC one time or always, check mark always. In Kitkat it looked like this:
alexcreto said:
YAY...thats an easy one...
So, whenever you plug your phone in your PC with the USB Debugging on, it prompts you to accept the fingerprint of the PC.
You have to accept it...in your phone...
It's like this:
Click to expand...
Click to collapse
It's still very similar.
1. Download and install Minimal ADB and Fastboot to your PC.
Download from here:
http://forum.xda-developers.com/showthread.php?t=2317790.
2. Go ahead and download SuperSU from the attached file at bottom of this post. It's an older version of SuperSu but works well on the Quark Motorola Marshmallow ROM. You can always update to newer version later. We'll install this after we install TWRP. Transfer that file to a convenient location on your phone. If you downloaded the file with your phone, it's in your "Downloads folder". You can keep it there.
BETA-SuperSU-v2.62-3-20151211162651
Attached to this post or download from here:
https://download.chainfire.eu/751/SuperSU/
3. Download the latest Quark TWRP .img file from this page (courtesy our Quark maintainer @bhb27:
https://www.androidfilehost.com/?w=files&flid=39562
(USE THE FILE ON THAT PAGE WITH THE MOST RECENT DATE)
The file visible in that folder is the always the very newest modded TWRP by our official maintainer @bhb27. Make sure you use the one with the most recent date. I strongly suggest you use his modded TWRP file over the TWRP from the official TWRP website. He's an XDA recognized dev who knows what's best for our Quark phones, and he's added stuff to make TWRP very compatible with the latest ROMs, whereas the "official" unmodded TWRP does not have that. @bhb27 helped us get official status with TWRP, but for some reason they won't post his modded versions. Ignore them. His modded TWRP is much better (more compatible with newest ROMs) than the TWRP available on the official TWRP site.
4. Download and install the Motorola Device Manager from here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481.
5. Rename the TWRP recovery file that you downloaded in step 3 to TWRP.img.
(Make sure you enable viewing file extensions in Windows! The file already has an ".img" extension! You are merely re-naming it TWRP. The .img extension is already there. If you don't see, then enable viewing all file extensions until you do see it.)
6. Copy TWRP.img to the directory that you installed Minimal ADB and Fastboot to. The default location on an installation of 64-bit Windows is C:\Program Files (x86)\Minimal ADB and Fastboot.
7. Turn off your phone.
8. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Poor little guy...
9. Plug your phone into your PC.
10. Double click on the Minimal ADB and Fastboot shortcut that's on your desktop. It will open a command prompt.
11. Type "fastboot devices" without quotes and press enter. If it gives you your phone's serial number, you're good to go. If it gives you nothing, your device is not detected. This can happen for several reasons, and I won't discuss them here. However, if you followed these directions and all of your hardware is functioning properly, you should be good to go.
12. Type "fastboot flash recovery TWRP.img" without quotes and press enter. It should tell you that the flash was successful. (If fastboot can't find the file, go back to point #5 and make sure you re-named it correctly. Make sure you have Windows extensions visible. You may have accidentally named it TWRP.img.img.)
13 Highlight "Recovery mode" on your phone using the volume up and down buttons.
(Because you will still be on the bootloader screen after flashing TWRP. AFTER you flash it, you will then use your volume button to arrow up or down -- doesn't matter -- through the choice until you see "recovery". THEN, in the next step you will press the power button to choose that selection -- recovery.)
14. Press the power button to choose "boot into TWRP. < THIS IS IMPORTANT! Do not reboot normally after flashing TWRP. Reboot directly to recovery by selecting recovery from the bootloader menu on the phone. After the first TWRP boot, it will be there permanently.
15. TWRP will boot, and it will ask you if you want to allow write access to the system partition. IT IS VERY IMPORTANT THAT YOU ALLOW THIS. Check the box that says to never ask this question again.
____________
Section 3: GAINING ROOT ACCESS
16. Select Install from the TWRP main menu.
17. Navigate to the location where you saved the SuperSu file that you downloaded in step 2, and select it.
18. Swipe the bar at the bottom of the screen to flash this zip file.
19. When it finishes, select Reboot System to boot your phone normally.
_______________
BETA-SuperSU-v2.62-3-20151211162651
Attached to this bottom of this post or download from here:
https://download.chainfire.eu/751/SuperSU/
Flash this version initially. You can update to newer version later. (People had problems flashing the very newest SuperSu for initial root, but this version works good. Again, you can update to newer version later, after you gain root.)
Also, here's some common mistakes people make when flashing TWRP and SuperSU:
(Read these first if you have any problems.)
http://forum.xda-developers.com/showpost.php?p=68211093&postcount=302
http://forum.xda-developers.com/showpost.php?p=68212100&postcount=306
http://forum.xda-developers.com/showpost.php?p=68222204&postcount=309
http://forum.xda-developers.com/showpost.php?p=68224106&postcount=311
_______
BONUS TIP - SuperSu Setting
After you reboot, go into SuperSu settings and UNcheck this box. Mount namespace separation.
Uncheck that. Disable that. Then, reboot.
If it's enabled it will conflict with Titanium Backup which you will use at some point, or should. And you will have no idea why Titanium Backup is saying you are out of space, when you are not -- but it's due to this setting in SuperSu!
STRONG SUGGESTION: After successfully unlocking bootloader, installing TWRP and rooting, when you finally boot back to stock firmware, install THIS app (needs root permission) to easily facilitate rebooting to TWRP recovery in the future. Recovery Reboot
Remove annoying bootloader unlocked warning
Motorola insists upon telling you that you unlocked your bootloader every time you reboot your phone. This is the static logo you see before the moving boot animation starts, and Motorola replaces it with an UNLOCKED bootloader warning. Yes, I know -- I unlocked it on purpose!
Replace that annoying warning with something cool looking... I have attached FIVE choices with Motorola logo!
* Black and White
* Dark Google ATAP
Graphic for this above was used from this Moto X Pure thread by @XDleader555 -- but I adapted it for our Quark so it wouldn't be upside down. All the other bundled graphics in the bin file like "recovery", "bootloader" are taken from the Black & Teal logo below. However the "splash screen" is this artistic black & white boot logo.
* Black and Teal
*White and Teal
* Black and Red
(The last three with color are custom graphics made by @fenix3nk0r3 from this thread. I am using the black and teal on my daily phone.)
And here's two ways of installing the new boot logos...
REMOVE ANNOYING BOOTLOADER UNLOCKED WARNING
1. FASTBOOT ADB
Jaocagomez said:
Prerequisites:
Bootloader Unlocked
Fastboot and ADB On your PC (i personally recommend Minimal ADB and Fastboot )
Installation:
Assuming you already have Fastboot on your pc just flash it with the following command:
Code:
Fastboot flash logo "name_logo".bin
(Replace "name_logo" bin with whatever the .bin file is named, without quotes. IF you simply re-name it logo.bin, remember you will be typing the word logo twice in that command. Just remember to actually type it twice!)
Click to expand...
Click to collapse
2. FLASH LOGO IN TWRP
Courtesy @bhb27, here's a boot logo flasher app for use in TWRP:
bhb27 said:
This can be used to flash the logo via TWRP. No need to fastboot or PC
Logo_Flasher.zip
This zip must be used with a logo.bin file. The file can be find on stock Moto ROM and modified using the logo flasher app.
Place the logo.bin on the root of this zip, the file name must be named logo.bin
Then just flash the zip via TWRP.
Click to expand...
Click to collapse
Great tool, once I figured out "place the re-named logo.bin on the root of this zip" meant INSIDE the zipped logo flasher folder.
I first placed it in the same folder as the zipped file (my Download folder). Didn't work. Then, I re-read and realized it meant the logo.bin file had to placed INSIDE the zipped folder. My fault. So, I did that and worked smoothly!
Note that whichever .bin image you use, it MUST be re-named simply "logo.bin" to work inside this logo flasher app.
____
EDIT: SEE POST #5 FOR TWRP FLASHABLE ZIP FILES WITH LOGO ALREADY PREPARED! NO PC NEEDED!
Flash new boot animation
FLASH NEW BOOT ANIMATION.
1) Google Bootanimation 60fps for all QUARK
There are plenty of boot animations available. I like this one...
Google Bootanimation 60fps for all QUARK
Looks like this:
But a LOT smoother in real life
See attached file. This is a TWRP flashable zipped file. Download and flash it in TWRP.
Do NOT unzip it! Just boot into TWRP recovery and flash it.
Thanks to @LuanGuima14 for the file!
LuanGuima14 said:
[emoji23] I made a zip containing the bootanimation that google uses the nexus at 60fps and also bootlogo the Droid turbo has dark background
Click to expand...
Click to collapse
____________________
Also we now have this:
2) Motorola stock "Spinnning World"
Thanks to @metpolds from this post.
Yes, it works on our Quarks. I just flashed it in TWRP recovery to test.
Men I Like your post, thanks for adding my publication
No pc needed to flash these boot logos!
TWRP-FLASHABLE: REMOVE ANNOYING BOOTLOADER UNLOCKED WARNING
This is the static logo you see before the moving boot animation starts.
Due requests, I have attached TWRP-flashable files with boot logos already inside. No need for a PC!
NOTE: Flash one of these boot logos as a separate TWRP session if you are also flashing the boot animation. For some reason both cannot be flashed in the same session.
___________
Motorola insists upon telling you that you unlocked your bootloader every time you reboot your phone.
Replace that annoying warning with something cool looking... I have attached FIVE choices with Motorola logo!
* Black and White
* Dark Google ATAP
Graphic for this above was used from this Moto X Pure thread by @XDleader555 -- but I adapted it for our Quark so it wouldn't be upside down. All the other bundled graphics in the bin file like "recovery", "bootloader" are taken from the Black & Teal logo below. However the "splash screen" is this artistic black & white boot logo.
* Black and Teal
*White and Teal
* Black and Red
(The last three with color are custom graphics made by @fenix3nk0r3 from this thread. I am using the black and teal on my daily phone.)
Boot animation zip worked but not the logo bin zip Sir.
Steve One said:
Boot animation zip worked but not the logo bin zip Sir.
Click to expand...
Click to collapse
EDIT: We figured out these boot logos have to be flashed in a separate TWRP session if you are also flashing the boot animation.
______________
Works for me. How are you downloading? How are you flashing?
I flashed the white and teal before I uploaded the zipped files, as I was already using the black and teal.
Now I just reflashed the black and teal from the exact same file I attached to post #5.
Using Chrome browser, I just re-downloaded the red and black -- even though I already had it stored on my phone. I used the one from this post and flashed it. It works.
So, that's 3 of the 4 I've personally flashed...
Boot into TWRP and "install" (flash) the zipped file you downloaded.
Just reflashed and it worked great. Maybe it didn't work the first time because I flashed both the logo bin zip and boot animation together.
Thank you very much for your continued support kind Sir.
Hola, thanks for this exceptional guide to root MM in XT1225!
Im having same issues making backups with TWRP.
First its not backing up in my OTG device, i get error 255.
If i make backup in internal memory then i cant see it in root explorer or in windows.
I see TWRP folder but nothing inside, but in TWRP i can restore it.
Hope you understand me.
Sorry for my bad english and thanks for you work again!
ramiro128 said:
Hola, thanks for this exceptional guide to root MM in XT1225!
Im having some issues making backups with TWRP.
First its not backing up in my OTG device, i get error 255.
If i make backup in internal memory then i cant see it in root explorer or in windows.
I see TWRP folder but nothing inside, but in TWRP i can restore it.
Hope you understand me.
Sorry for my bad english and thanks for you work again!
Click to expand...
Click to collapse
You are welcome. I am not a TWRP expert. I would suggest you re-flash the latest version of TWRP and see what happens. But you will get a better answer in the TWRP thread run by @bhb27... Good luck!
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
correct me if I'm wrong..
5. Rename the file that you downloaded in step 2 to TWRP.img. (Make sure you enable viewing file extensions in Windows! The file already has an ".img" extension! You are merely re-naming it TWRP. The .img extension is already there. If you don't see, then enable viewing all file extensions until you do see it.)
Click to expand...
Click to collapse
Are you sure you're refering to step 2 and not 3? The file downloaded at step 2 has zip extension. The file downloaded at step 3 has img extension.
moriturim said:
Are you sure you're refering to step 2 and not 3? The file downloaded at step 2 has zip extension. The file downloaded at step 3 has img extension.
Click to expand...
Click to collapse
Yes, you are correct since I specifically mentioned TWRP.
I wrote this guide then went back and added another step (downloading SuperSu) between #1 and #2 (TWRP), thus making the TWRP download step actually #3. It made more sense to download SuperSu first, to have it ready. So, in the revision, the TWRP download became step #3.
Then, I didn't change the TWRP file re-naming/windows extension warning to reflect that number change, still referring to "step #2".
I'll change it now. Thanks.
I was trying to get the bootloader unlocked, but I still haven't received any code by Motorola. How long do they usually take to send it?
I tried to contact them too, but their site is terrible, every device that I try on that site has issues, in can't even send a question or get into the chat, the buttons don't work
Garden98 said:
I was trying to get the bootloader unlocked, but I still haven't received any code by Motorola. How long do they usually take to send it?
I tried to contact them too, but their site is terrible, every device that I try on that site has issues, in can't even send a question or get into the chat, the buttons don't work
Click to expand...
Click to collapse
It's fairly instant. Did you agree to the conditions?
You'll get an email with the bootloader unlock code. The email will also have a link back to the instructions. But the code is what's important.
Check your spam folder.
ChazzMatt said:
It's fairly instant. Did you agree to the conditions?
You'll get an email with the bootloader unlock code. The email will also have a link back to the instructions. But the code is what's important.
Check your spam folder.
Click to expand...
Click to collapse
Thanks, it worked. I can't believe I had to try three times.
Motorola site is still sh*t for help ahah
Stock in the boot animation
Hi.
First thanks for you complete guide.
Now, I did all the steps correctly, but in the final, when I tryed to flash de boot animation logo TWR show me that is all ok, but my phone don't boot... It's stock in the animation all the time. What happend?
What can I do for return at before steps?
The last moment that my phone works, was before to flash the SuperSU. After that, the phone stock it in the big M screen (the white one), then I flash the animation logo zip.
I need my phone D:
EDIT: I add the next --> When I connect my phone to PC, while the first is in the TWRP mode, the windows explorer showme 2 folders: "TWRP" and "0". Is this Correct?
EDIT 2: I flashed the Resurrection Remix ROM (http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232) using TWRP and my phone works, but I losed the active display
Pd: sorry my english, but I larning yet.
Quark Ambient Display settings
sebamerca said:
Hi.
First thanks for you complete guide.
Now, I did all the steps correctly, but in the final, when I tryed to flash de boot animation logo TWR show me that is all ok, but my phone don't boot... It's stock in the animation all the time. What happend?
What can I do for return at before steps?
The last moment that my phone works, was before to flash the SuperSU. After that, the phone stock it in the big M screen (the white one), then I flash the animation logo zip.
I need my phone D:
EDIT: I add the next --> When I connect my phone to PC, while the first is in the TWRP mode, the windows explorer showme 2 folders: "TWRP" and "0". Is this Correct?
EDIT 2: I flashed the Resurrection Remix ROM (http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232) using TWRP and my phone works, but I losed the active display
Pd: sorry my english, but I larning yet.
Click to expand...
Click to collapse
From all your edits it seems you actually figured most of it out? You have now flashed Resurrection Remix Marshmallow ROM. If you did that, then you unlocked your bootloader, installed TWRP, rooted and rebooted successfully!
I'm not sure exactly the steps you did, but for some reason the TWRP-flashable boot animation and TWRP-flashable boot logos cannot be flashed in the same TWRP session. If you try to flash both in the same TWRP session, one will not flash and you will still have the logo or animation you were trying to replace. I provided two versions of boot logos -- either ADB or TWRP-flashable. You can either flash the boot logo via ADB and then boot animation via TWRP... OR you can flash the TWRP-flashable boot logo via TWRP, reboot to ROM, then go back into TWRP recovery, and then flash the TWRP-flashable boot animation in a separate session.
QUARK AMBIENT DISPLAY SETTINGS
sebamerca said:
EDIT 2: I flashed the Resurrection Remix ROM (http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232) using TWRP and my phone works, but I losed the active display
Click to expand...
Click to collapse
For the active display, in CM-based ROMs it's called "Ambient Display". Our CM dev @Skrilax_CZ, put a lot of effort into coding it so it works with the the Quark (Moto Maxx/Moto Turbo/Droid Turbo) IR sensors very much like Moto Display.
All the other ROMs, like Resurrection Remix, Bliss, etc use the same coding.
It's a lock-screen notification system. You will not see any notifications if you display is not locked when it is off/dark/sleeping.
In Settings,
First, you need to turn on Ambient Display.
Then, you need to configure the actions of Ambient Display. For example, some want to see notifications when they wave their hands over the phone, some do not want that action.
Below are the Ambient Display settings screenshots I took when I was using CM12.1. I am now using Resurrection Remix Marshmallow, like you. The settings are either identical or very, very similar.
____________
_____________
2)
___________
3)
______________
______________
4)
In Lock Screen, you need to have some sort of of screen lock, even if it's just swipe/slide lock. Either swipe, pattern or PIN. You can't choose "none". I choose pattern, but it's up to you.
IF you choose swipe, you may accidentally unlock your phone if you keep it in your pocket. PIN or pattern is better, in my opinion.
In RR, these settings below are under "Security". In CM12.1 it was under "Lockscreen".
Also, helps if you have "Automatically Lock" and "Power Button Instantly Locks" Some people put a delay on those for some reason, and then Ambient Display isn't going to show you notifications on the dark screen because the Display isn't actually locked.
NOTE: After you turn on all the other options, sometimes it's best to then turn off Ambient Display, then turn it back on to make sure it recognizes the other settings you have enabled.
You are awesome.
Works perfectly (just check one time).
Thanks again from Chile.
And sorry for my English, I expect understand me
Sent from my Moto MAXX using Tapatalk
Thank you man.
I had troubles to root with SuperSU 2.78, but with your tip, now it's working again.
MusashiBR said:
Thank you man.
I had troubles to root with SuperSU 2.78, but with your tip, now it's working again.
Click to expand...
Click to collapse
Yes, the beta SuperSu 2.62 I have in post #1 works great for initial root. Then, after that you can update to newest SuperSu if you wish.
I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition
ElectroJoe said:
I've done a lot of research on a reliable way to root my Moto X Pure Edition XT1575 and want someone to check my plan before I pursue this. I'm gonna download TWRP for Clark and superSU 2.78 and put them in the same folder and open up the command prompt in that folder. Then hook up to the PC and enter the following command "fastboot boot twrp.img" then I'm gonna replace the twrp.img with the name of the twrp file and backup to the SD. Then reboot into the bootloader again and flash twrp with fastboot "fastboot flash recovery twrp.img" then start recovery and go to reboot into recovery again to lock it in. Then I'm booting back into twrp and going to Advanced & Terminal and entering the following command "echo SYSTEMLESS=true>>/data/.superSU then back home then flash superSU 2.78.
Please correct me on everything that may be wrong. If there's a better way to root, tell me how to do it your way.
My device info:
Moto X Pure Edition XT1575 (clark)
Build# MPH24.49-18
Kernel version 3.10.84
Android version 6.0
Bootloader OxAo48
Sent from my Moto X Pure Edition
Click to expand...
Click to collapse
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Thanks for taking the time to educate me on this. I'm gonna give it a try in a few minutes. Will I be a developer if I get it right? Hahaha I'll let you know how it goes
Sent from my Moto X Pure Edition
annoyingduck said:
You've researched well. Couple things: The command is "echo SYSTEMLESS=true>>/data/.supersu", you added capitols on supersu. Next your first command of "fastboot boot twrp.img (or whatever you rename the TWRP recovery image to)" will live boot TWRP, which for our device is not necessary. Live booting is essentially booting into a custom recovery environment without actually installing the recovery. This is useful for devices that DO NOT have factory images available, which allows you to make a backup in the live environment prior to altering your device. We have factory images and factory recovery images, so you can skip this step and go right into "fastboot flash recovery twrp.img (or again, whatever you rename the recovery image to). Then after the recovery flash from within fastboot, you must reboot into recovery using the button select options within fastboot or your recovery will be overwritten by the stock recovery. Upon first boot of TWRP you'll have an option to keep your device read only or read/write. I personally choose NOT to keep it read only, rather read/write, because I don't care about taking OTA's with a custom recovery, but this is up to you. Then you'll want the supersu.zip on your device already (you want the regular standard current version, not a modded one from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703), either on your internal or external sd. And yes, prior to flashing supersu enter the command in TWRP without quotes "echo SYSTEMLESS=true>>/data/.supersu" (this prevents the bootloop that our device gets when flashing supersu in systemless mode). And your good to go. I just did this a few weeks ago from clean fastboot flashing the latest factory image, works perfectly.
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk
ElectroJoe said:
It worked! I'm rooted and looking for a stable rom with a lot of features and customizations that works with Verizon LTE. I also want viper4android. I'm glad I backed up because I tried flashing a viper4android zip and it caused my phone not to boot. It just sat at the unlocked bootloader warning so I just restored it. Evidently, I was supposed to unzip the file in esfile Explorer and install the apk. I think I also needed the selinux mode changer app.
What would I gain by installing a custom Kernel to my rooted stock rom? Can I even do that?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Flash ViPER4Android from here, no SELinux changing app needed: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
As for custom kernel, Frankenclark. Features available is in the post: http://forum.xda-developers.com/moto-x-style/development/kernel-frankenclark-t3289939
annoyingduck said:
Now for some clarity, I'd like someone else to chime in on the TWRP command "echo SYSTEMLESS=true>>/data/.supersu" that has to be entered. I know for sure entering the command prior works, and roots properly, but I have also read that the latest 2.78 version of supersu does not require this. I'd really like someone that KNOWS FOR SURE (no opinions) if this step can now be bi-passed, or if our device requires and will always require this step now and in the future. This will help solve a ton of questions about this issue that are spread throughout the forums so users don't have to dig to get a simple answer.
Click to expand...
Click to collapse
I literally did this to a fresh MXPE two weeks ago... misspelled the filename so it wasn't recognized (it isn't supersy apparently), and flashed SuperSU 2.78-SR1, rebooted and stuck at boot logo for 20 minutes. Rebooted into TWRP and entered the correct echo command to create the .supersu file and reboot, it looped twice quickly and then went to the lockscreen after a 2-3 minutes.
I just got my Moto G5 Plus today, and ran Motorola's official Bootloader unlock guide.
Upon starting up, I am now receiving an error that says "Your device has been unlocked and can't be trusted. ID: bad key"
I confirmed multiple times that I provided the correct unlock_data and entered the correct unique key provided.
Because of this I cannot flash TWRP.
"(bootloader) Image not signed or corrupt"
What can I do here? Is there a way to re-do the unlock?
Do I have to flash stock back to the phone? I cannot seem to find any guide on how to perform that properly.
Are you sure TWRP didn't flash because it gave me that same generic error (because it's no longer stock recovery) but it had installed fine. Did you try selecting 'Recovery Mode' in the bootloader and see if it loads? Hopefully you're following the rooting tutorial in this forum because you need to follow it closely to correctly gain root.
That 'bad key' message on startup is normal after unlocking and can be removed by flashing another 'logo.bin' as shown in this video, so actually seeing it shows that you probably did unlock successfuly.
Correct, as everyone has stated, this is normal for a bootloader unlocked device. You can flash a logo.bin to make your boot up look better
Sent from my Moto G (5) Plus using Tapatalk
Were you able to fix this? I have a similar problem.
I am also having this problem. Everyone saying this is normal, is wrong.
donjuro said:
I am also having this problem. Everyone saying this is normal, is wrong.
Click to expand...
Click to collapse
The "normal" message once it's bootloader unlocked is "Your device is unlocked and can't be trusted...Your device will boot in 5 seconds." - it doesn't say anything about a "key".
EDIT: oh, and where his said "ID: bad key" mine says "ID: n/a"
Yes I found out my problem was that I was using a later version of twrp and you have to first use an initial build on one of the rooting threads.
I'm having the same issue. Got the unlock key from Motorola and successfully unlocked bootloader from CMD. The phone then booted up as if it were new. I access the recovery mode and get "device has been unlocked and can't be trusted". No other option. I've tried manually and through CMD. I've downloaded all necessary files including the kernel, ADB, fastboot and twrp. Nothing works. Phone operates as if I factory reset it.
I just rooted my Moto G5s plus last night...here were my steps:
1.) Do the Motorola unlock B.S.
I had fastboot.exe and adb.exe from the Android SDK installed
I did find that I had to unlock my phone or adb could not see it
2.) After unlocking, you get the "untrusted phone" screen
3.) Use fastboot to flash a new boot image: fastboot flash boot logo.bin (I built a logo with MotoBootLogoMaker), this gets rid of the untrusted screen
4.) I do have the "bad key" message show up during boot, but it hasn't impacted anything...it is in white, my boot logo is in white, so you don't see it.
5.) Get a copy of SuperSU.zip on your sdcard and load into your device
6.) I installed TWRP (twrp-3.11-sanders.img) to the recovery partition, but that caused an issue: fastboot flash recovery twrp-3.11-sanders.img)
* Recovery wouldn't boot after this, so I successfully booted the image directly with: fastboot boot twrp-3.11-sanders.img
6.) TWRP successfully loaded....
7.) Use TWRP to install SuperSU.zip (this roots the device)
* I wiped the dalvik cache, but that hung and I ended up powering off...but fortunately it didn't brick the device
8.) After reboot, I logged in with "adb shell" and did an "su" to prove I was rooted.
9.) I replaced bootanimation.zip with one more to my liking than the Lenovo one (/system/media/bootanimation.zip I think was the location)
That was it...
TWRP Custom Recovery for the Onn Android Tablet series
This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you probably have some idea of what it is and what it's used for. This TWRP build does not need the bootloader unlocked or VBMeta verification disabled, although it's recommended that you at least unlock the bootloader.
DISCLAIMER
Everything described in this thread is done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
FEATURES
Decrypted data partition
All USB modes functional: MTP, ADB, Mass Storage, OTG, Charging
Fast boot time
Adoptable storage mounting
Firmware image backup and restore
Works under locked bootloader
Android 9 build fits within the 16MB recovery partition -- no compromises or partition resizing necessary
INSTALLATION METHOD 1
Download the recovery to your PC and unzip the image
Unlock the bootloader (skip if you have already done this)
Enable OEM Unlock in Developer Options in Android Settings
Boot into fastboot mode either by holding vol. up+power to power it on and selecting "Fastboot mode", or by running the 'adb reboot bootloader' command from within Android.
Install fastboot and appropriate drivers on your PC if you have not set those up
Unlock the bootloader with the command
Code:
fastboot flashing unlock
...and follow the instructions on the screen. This will wipe your data.
Flash the custom recovery with
Code:
fastboot flash recovery twrp-3.3.1-ONA19TB002.img
(use the right file name path for your device)
Reboot to recovery with
Code:
fastboot oem reboot-recovery
INSTALLATION METHOD 2
This assumes you are familiar with SP Flash Tool or can figure it out on your own
Download the recovery to your PC and unzip the image
Get the appropriate scatter file for your device. The scatter file may be found in the device's firmware under /system/data/misc.
Set up SPFT Download tab as Download Only. Load your scatter file.
Under the recovery line, double-click Location and open your TWRP image.
Click Download and connect your powered-off tablet to your PC. SPFT will automatically flash the recovery to the emmc and disconnect when finished.
INSTALLATION METHOD 3
Head over to Amazing Temp Root for MediaTek ARMv8, read the requirements and directions, and grab the latest mtk-su.
Open a root shell with mtk-su
Flash the (unzipped) recovery with the command:
Code:
dd bs=1048576 if=twrp-3.3.1-0-ONA19TB002.img of=/dev/block/by-name/recovery
(replace the if= file name with your appropriate recovery image path)
Exit root shell
START RECOVERY
Three methods:
On a powered off tablet, hold Vol. up+power for about 3 seconds. In the menu that appears, select "Recovery mode"
With Android ADB, use the command 'adb reboot recovery'
From Android root shell, use the command 'reboot recovery' or just use any root app with OS reboot features
NOTES
Kind of important: Make a backup of your Crypto Footer as soon as you can. This is the encryption key to your data partition. When accessed from TWRP, this key can get "upgraded" so that you will get locked out of Android. TWRP uses a hacky workaround that saves and restores the original footer on every /data decrypt. But that method is not what I would call 100% reliable.
Make sure you have a backup of the untouched stock system and vendor images. There are no official firmware packages available to download.
Only mount system/vendor partitions in read/write mode if you have unlocked the bootloader. It is recommended to choose to leave system read-only at the startup prompt unless you have a specific reason to modify it. If the bootloader is locked, then dm-verity is enforced.* So merely mounting it once in r/w will cause a boot loop.
It's currently not possible to install incremental OTA updates using this TWRP. Use the stock recovery to update the FW. That will only work if you have never mounted system/vendor in write mode.
DOWNLOAD (Nov. 30, 2019)
Current version: 3.3.1-1
ONA19TB002 - Onn 8" model
ONA19TB003 - Onn 10.1" model
ONA19TB007 - Onn 10.1" w/keyboard model
Source code
ONA19TB002 | ONA19TB003 | ONA19TB007
ACKNOWLEDGEMENTS
The team behind TWRP & OmniROM
@tek3195 for testing and feedback on the 8" model
Please post feedback since these are still pretty new and not exhaustively tested. Let me know if I should port it to other models in the series.
Reserved also
grabbing this one too cuz why not
Very nice! I'll download and test the 003 one soon.
I also have a 007 model to experiment with.
I tried about a dozen times to build TWRP and failed miserably LOL. Closest I got was one that would boot but the rotation was all messed up, USB wouldn't work, didn't mount some partitions... Yeah, it was a hot mess.
Do you happen to have sources available?
Hi @NFSP G35,
I'll have the source code soon. Most of the tricks involved patching bootable/recovery. So I need to commit those changes and include the proper patch set from my tree....
Amazing!! Gonna install and test 8" right now.
Has anyone tried a GSI on these tablets yet?
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I do know @tek3195 , the Onn 8 thread starter, has tried many of them as well as others here, somewhere on that thread he listed his tests and opinion of several of them.
I'm pretty sure others on that thread have also tried GSI's.
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I did try both Phhuson vanilla and also Liquid Remix (I'm keeping this one for now). I didn't flash them through twrp, but using fastboot via bootloader.
WoW! AwEsOmE! I cannot wait to try this! THANK YOU!!!!!!
Hey,
This is a neat thing to see for the Onn tablets. I have a question though. I own a device based on the mt8163, and am trying to help people with another device I don't own (the powkiddy x18 which also uses the mt8163). One of the things I wanted to do was to make a custom rom for the x18, since it's stock firmware is horrible. And of course, one of the first steps to custom roms is twrp. So I have a question for you that I hope you can answer for me. How did you make this build of twrp? I have seen no device trees for this device so I was kinda curious. If you can help me in any way, I'd be so grateful, and I'm sure the other people with the x18 would be grateful for help.
@diplomatic
Is there a different procedure for installing TWRP on a locked bootloader?
I can confirm that using SP Flash to load your TWRP.img will produce a bootloop when installing to a device with the BL locked. Reflashing the original recovery.img makes the problem go away. You mentioned in the OP that this TWRP will work on a locked BL so I thought I would share my case study with you in following the procedure you defined.
MY SINCERE GRATITUDE FOR YOUR EFFORTS IN PORTING THIS TO THE ONN!
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
diplomatic said:
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
Click to expand...
Click to collapse
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
At one time I did run with the bootloader unlocked (with --disable-verification on stock vbmeta) and I ran Phusson's AOSP, Liquid Remix and Bliss. I found there was no benefit to me in running the other mods so I reverted back to stock courtesy of @CaffeinePizza and the bootloader re-locked to get rid of that annoying 5 second orange state.
In each instance, I always used SP Flash tools to load all .img files. I only used fastboot to install magisk_patched.img onto the stock installation. Unlocking the bootloader erases all data and I did not feel like reinstalling everything again, so I figured I would try to install TWRP per your instruction to see if it would work while the BL was still locked... Restoring the original recovery got rid of the bootloop. I do want to try your TWRP so I will try it with BL unlocked when I get some free time to do so.
Spatry said:
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
Click to expand...
Click to collapse
This sounds like you might have flashed a wrong/corrupt image to recovery. It may have to do with AVB checks rather than bootloader lock. But those conditions might be interdependent somehow so I can't tell you for sure. The fact that you are able to boot a patched image on a locked BL says it doesn't care too much about verification. I can tell you for sure that any recovery image must have avb metadata, not necessarily the required hash, for both Android and recovery to boot. Can you try to unzip the image file and flash it over again?
Hmm, the situation with the bootloader lock sounds eerily similar to the Nabi SE. The latter also had a similar implementation where there's not much in the way of locking things down, other than an (easily circumvented) SP Flash Tool signature check and different preloader keys. And here's the real kicker: the nearly-identical Fisher Price Nabi also ran on the MT8163, so it makes me wonder if it's possible to boot Pie on it, or perhaps a GSI assuming that Treble can be tacked onto it.
Also, do you have the source repo to this TWRP port of yours?
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Where do I find crypto footer to backup
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Kinda cool without the ads isn't it. I know I sent one about a week ago or so. I think everybody ought to send you one, you deserve it. THANKS and AWESOME work.