Related
Hello, since i bought a Dev edition i noticed that there's no helpfull links to start with, so i though on making this thread to make other peoples life Easier.
Don't Forget to Thank All People of XDA on the Links on This Post, they deserve recognition for their help
Jaocagomez said:
First: Unlocking Bootloader
{
"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"
}
Once you got your Developer Edition Droid Maxx You'll have to unlock the Bootloader so you can flash recoveries, roms, themes and some other stuff. Remember that only in Dev edition you Don't lose your warranty if you unlock your bootloader.
Be careful, the process of unlocking your bootloader ERASES ALL YOUR DATA, so the first thing i recommend you to do is unlock your cellphone bootloader then use it.
To enter in fastboot mode with your phone off, press Power + Vol Down
Here's the Link to Unlock Your Bootloader: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
To get Fastboot on your pc you can Download Minimal Adb and Fastboot which is lighter and faster than downloading full android SDK.
Also a Tip, when copying your device id, paste each line on the field one after another, and dont put spaces, sometimes when you copy-paste your device id you left a space and it shows as error.
If everything went ok, you are now fully unlocked and ready for the party.
Click to expand...
Click to collapse
Jaocagomez said:
Second: Get a Custom Recovery
Custom Recoveries remplace the stock android recovery and the main use of this is to flash roms, themes, backup, restore and some other things, Flashable Roms are always a .Zip Format
Theres lots of recoveries and they have different advantages and fails, but most of them can do the work.
To install you'll need just one line on fastboot.
Here's a List of Recoveries That work on our Device:
TWRP. (its Moto x Forum, dont Worry)
Safestrap
Philz Touch (based on CWM advanced 6)
The most user friendly i know and the one i use is TWRP
Now, if you want to stay on stock Rom i Recommend installing Xposed and Gravity Box
Click to expand...
Click to collapse
Jaocagomez said:
Third: Root in TWRP
For me the fastest Metod to root is Entering TWRP your first time, then Just exit
and before you exit TWRP will ask to install SU, swype to your right to install and then boot your phone again.
update the app, and thats all you are rooted.
There are other metods but the one i post here for me is faster and easier. you can look on the forums for more metods.
Click to expand...
Click to collapse
Jaocagomez said:
Optional: Installing Xposed And Gravity Box
Xposed its an app that modifies the look and actions of your stock rom (or any rom) without the need to be flashing things, just by overriding on boot the stock files. Its pretty useful and Great for customization.
You can learn more about it Here and Here
iB4STiD from the Moto x Forum has a Flashable Xposed and Gravity Box Module, which is the easiest way to install it.
Just Download it and flash it on your recovery. after that, update the app and install the framework and reboot again, it should be working.
Click to expand...
Click to collapse
Jaocagomez said:
Fourth: Flashing Moto X Firmware.
Here comes the interesting Part, you can flash the Moto x Firmware and work with it.
the upside down? if you have a verizon sim card and flash a moto x tmobile firmware it will not work and so on, they are sim locked as it were a retail at&t/tmob/verizon device, so you are pretty much limited to flash the moto x verizon firmware and/or the sim card your carrier is. i currently dont know how to change that but i believe its posible.
the list of all the Moto x Firmware is here: http://sbf.droid-developers.org/phone.php?device=0
in order to flash these firmware you have to put all the contents of the firmware in the minimal adb folder and copy paste this commands to flash:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
just copy the code and paste it on the fastboot command line on your pc and you are all set.
it will boot as a moto x.
When you Install Moto X Firmware, soft keys will stop to work and you'll have on-screen keys just like moto x, in order to fix this you can flash this fixed framework-res by Skrilax_CZ and uploaded by Gundabolu SC on your recovery and you'll have a moto x firmware and soft keys working, that framework only works on android 4.4.
To come back to Droid Maxx Stock Verizon 4.4, download the Droid maxx firmware here: http://sbf.droid-developers.org/phone.php?device=4
put your phone on fastboot mode and
and run the flash_all.bat inside the .zip file, it will boot up again as a normal droid maxx.
If you do something wrong, your phone force closes, or you screw up, remember that you can always flash firmware back to Droid Maxx Stock Rom, so Dont worry.
Click to expand...
Click to collapse
Jaocagomez said:
Five: Installing Moto X Roms
You can install Moto X Roms, from moto x forum, just flash the required Moto X firmware, install a recovery then download the Rom .zip and finally to flash the rom on the recovery, and you are all set to enjoy a custom rom. oh dont forget the capacitive keys fix if you want your keys working.
Currently there is Kangakat, PAC, Eclipse, CM11, Gummy, Liquid smooth kitkat and some others, you can check them out here:
http://forum.xda-developers.com/moto-x/development
Click to expand...
Click to collapse
Jaocagomez said:
Six: Staying on Stock Verizon Rom
If you decided to stay on verizon's 4.4 stock rom, i recommend you to install Gravity box, change your status bar to white and install this moded Sistemui.apk by erishasnobattery so you stay as close as AOSP as you can.
you can also install the google now launcher located HERE for a closer look to a nexus 5
Or you can install my Debloated stock rom here: http://forum.xda-developers.com/showthread.php?t=2716824
Click to expand...
Click to collapse
Don't Forget to Thank All People of XDA on the Links on This Post, they deserve recognition for their help
Edit1:
Changed Thread name to accomodate Moto x, mini, ultra
Edit2:
Added Quotes to the steps to make reading easier.
Reserved
Thank you for this, i actually just finished going through all of this a few days ago and have gravity box and xposed going on the stock 4.4 Verizon Rom...
Do you have twrp and Safestrap going at the same time?
spiral777 said:
Thank you for this, i actually just finished going through all of this a few days ago and have gravity box and xposed going on the stock 4.4 Verizon Rom...
Do you have twrp and Safestrap going at the same time?
Click to expand...
Click to collapse
no, i dont use safestrap
SafeStrap is for "Locked" bootloader only..TWRP is for "UnLocked" bootloader..
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
My current setup with the modes system ui, Google now launcher and gravity box.
Sent from my XT1080 using Xparent BlueTapatalk 2
BladeRunner said:
My current setup with the modes system ui, Google now launcher and gravity box.
View attachment 2588597
Sent from my XT1080 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Sweet setup.!!
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
BladeRunner said:
My current setup with the modes system ui, Google now launcher and gravity box.
View attachment 2588597
Sent from my XT1080 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
thats the look!
ignore
Is anyone having issues with 4.4? i have read on the forums that it's better to stay with 4.2.2 camera fix. and that you can't downgrade after 4.4 ota.
I am looking for a do's and dont's from experienced DE users.
thanks
xkwwwx said:
Is anyone having issues with 4.4? i have read on the forums that it's better to stay with 4.2.2 camera fix. and that you can't downgrade after 4.4 ota.
I am looking for a do's and dont's from experienced DE users.
thanks
Click to expand...
Click to collapse
I, personally, haven't had any issues on 4.4 yet. You can downgrade the boot, system and recovery images as well as the modem, but the bootloader and gpt.bin stays on 4.4. If you DO decide to downgrade I would highly recommend freezing the OTA as there is a possibility of bricking the device if you take an OTA. If you downgrade to 12.7.7, the pre camera update, and try to take an update to 12.15.15 you WILL hard brick. I am unsure of what happens if you downgrade to 12.15.15 and update to KitKat.
Why is it saying my device does not qualify for device unlock?? this is really pissing me off
AshyKnuttz said:
Why is it saying my device does not qualify for device unlock?? this is really pissing me off
Click to expand...
Click to collapse
Sir..be absolutely sure there are no spaces in the line after you paste to the box..
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
NWKENT said:
Sir..be absolutely sure there are no spaces in the line after you paste to the box..
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
i did, i even copied and pasted one line at the time to make sure there were no spaces
AshyKnuttz said:
i did, i even copied and pasted one line at the time to make sure there were no spaces
Click to expand...
Click to collapse
Be sure there is no space in the very front of the line also..
Also..is your device new out of the box.? Maybe you will need to call Motorola.?
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
AshyKnuttz said:
i did, i even copied and pasted one line at the time to make sure there were no spaces
Click to expand...
Click to collapse
double check that, happened to me too try to write it over
NWKENT said:
Be sure there is no space in the very front of the line also..
Also..is your device new out of the box.? Maybe you will need to call Motorola.?
sent by my 4.2.2_12.15.15
XT1080MDEV (aka) Droid Maxx DE
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
I just typed it out number/letter by number/letter so its not spaces. it is fresh out of the box, i just got it earlier today
AshyKnuttz said:
I just typed it out number/letter by number/letter so its not spaces. it is fresh out of the box, i just got it earlier today
Click to expand...
Click to collapse
Sir..did you manage "Unlock".. what has been your path, results.?
I found that copy/paste worked really well..then after paste, go to the box and carefully delete any space..even in front, delete that space also..
I mention this eventhow you may have yours Unlocked..So others will see the correct procedure when pasting to the site box..and avoid troubles (possibly)..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Please donate to: jcase & Hashcode (if you can)
NWKENT said:
Sir..did you manage "Unlock".. what has been your path, results.?
I found that copy/paste worked really well..then after paste, go to the box and carefully delete any space..even in front, delete that space also..
I mention this eventhow you may have yours Unlocked..So others will see the correct procedure when pasting to the site box..and avoid troubles (possibly)..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
yes sir --right where i want to be thanks to you jcase and hashcode! thanks to all!!
NWKENT said:
Sir..did you manage "Unlock".. what has been your path, results.?
I found that copy/paste worked really well..then after paste, go to the box and carefully delete any space..even in front, delete that space also..
I mention this eventhow you may have yours Unlocked..So others will see the correct procedure when pasting to the site box..and avoid troubles (possibly)..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Please donate to: jcase & Hashcode (if you can)
Click to expand...
Click to collapse
I talked to online costumer support Thursday night, and they set me up with a ticket for the "level 2" technicians. I was going to call yesterday but couldn't because of work. Then, just now this morning, I tried again, same key, just copy and paste, and it worked. I can only assume it didn't work at first because I had just received and activated the phone earlier that day, it must take some time before it registers in their system or something.
First of all this is one of my firsts threads in XDA Forums. And this does not mean I don’t have any experience on Android, in fact, I have a lot, in the past I have the Galaxy S1 Captivate, MyTouch 4G and the Galaxy S2 T989 Hercules. I root all of them, change to different roms, kernels, stock roms, etc etc. I don’t always post because when I want to post something, someone already answer the question. Now I have the Moto 4G LTE XT1045 US version of single sim card (not the dual one), I have root it, I made some mistakes playing with the /system and /data partition with some apps that use root access and I soft brick the device. I turn it back on and the device was always in the “bootloader warning” screen. So I need in some way to go back to stock. Now that successfully restore the device I will not play with the partitions.
Click to expand...
Click to collapse
I find a few threads (which I give credits) and I restore the device back to stock. The problem is that what I do to restore back to stock, require me to go to different threats and different sites, I just can’t find one threat explaining everything in a nice and good looking way like the one that I am going to show you. Here in XDA we have experts, users and newbies, this is just an easy method for any of them.
(If you want to only Root the device in a safe way that don’t change your recovery, or the bootloader, just let me know, I am thinking in creating an easy-guide for root this device).
And second, thanks the users of the following threads, that are the ones responsible of almost all the things that I am going to say. (not in a specific order).
1. http://forum.xda-developers.com/moto-g/4g-development/xt1045-stock-rom-dump-t2794145/page2 (post # 14 by suhridkhan led me to an excellent guide).
2. http://forum.xda-developers.com/showpost.php?p=53660639&postcount=1&nocache=1&z=2567116348072886 (who led me to Firmware Factory).
3. http://www.firmware-team.com/showthread.php?t=1146 (post where I choose my stock rom XT1045 and I proceed to download).
4. http://forum.xda-developers.com/showthread.php?t=2542219 (the excellent guide, I mainly use the 3b instructions)
5. http://forum.xda-developers.com/showpost.php?p=53765029&postcount=83&nocache=1&z=3906391665805131 (I confirm the order of the flash process)
Disclaimer:
Follow these instructions at your own risk. If something goes wrong don't blame me!
I have only tested this on a US Retail Moto G XT1045 with an unlocked bootloader.
There is a high chance that his guide will work will the others LTE variants(XT1039, XT1040 & XT1042), however, I don't have a proof of this since I only have the XT1045 and the threads that I use don't say anything about if it works or not in that variants. If it works, the only difference will be the .xml.zip file from your specific device. If you use this guide for one of those variants, please let me know so I can update the guide with that device that at this moment I don't have proof if it works or not, thanks.
OLD STATEMENT, THE ZIP IS OUT, READ GUIDE CHANGELOG. Users of the XT1045. We already have receive the OTA update of KK 4.4.4. If you already have updated your device to 4.4.4, please, do not use the 4.4.3 files to downgrade and restore your device to stock. The files from 4.4.3 are not going to work, I repeat, the files from 4.4.3 (the link I provide below) are not going to work. If you update to 4.4.4 via OTA and mess (or something inexplicable happen) with your device and now your device doesn't boot, then you must search in other threads for a solution. To follow this guide for a 4.4.4 stock, we need to wait for for the 4.4.4.xml.zip file, and as far as I know, that file is not yet available to download. I have search in everywhere and the file is not available, once I know that the file is available, I will download it and I test it with this guide and my device, and if it works I will update the guide with the new download link.
Guide Change-log:
I decide to create this "Guide Change-log" section to post the short-length changes that I have made to the guide, so that the old ones a new ones can understand everything. Everything that I post are things that I personally have tested, I will not post something without testing because I don't want to brick any phone (and if that happen I am not responsible, this is XDA, everyone in XDA know that and all the risks), if for some reason I post something not tested, I will let you know. If someone test something and it works, I update the guide with that user name because that are his credits, which ones I am really grateful. A grateful thanks to @NWKENT for the help you brings to the users while I wasn't in here.
01. The original post.
02. 19/Ago/2015:
A. I create this section.
B. The 4.4.4 update xml.zip is out. They two are both the same as far as I know. I have not test them in my phone for the reason that I already have my XT1045 in Lollipop, I am not going to try to go back to KitKat, there's a significant change in versions, I can't risk my device, I am planning to buy another XT1045 for rabbit-tests like this, but for now I only have one device. I will search some info and let everyone know what I can find. In case someone want to try, these are the links of the 4.4.4 xml.zip.
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
http://forum.xda-developers.com/showpost.php?p=61789810&postcount=41
LET START
Pre-requisites:
a) Unlocked bootloader.
b) Download and install Motorola Drivers:
http://www.mymotocast.com/download/MDM?platform=windows
c) Download the stock firmware:
In our case (XT1045) is the RETUS_XT1045_4.4.3_KXB21.14-L1.23-4_cid9_CFC.xml.zip from https://mega.co.nz/#!kFYC0DbD!yNkcJbtMlEEM6kBOeVwYCRp3Fcv9gwKvC3EtgC-Du-k
d) Have the ADB active in your computer. In my case I already have installed the Android SDK and configured the ADB in the “Path” of my Windows 8.1 x64 system.
To do that right click the “This PC” or “Computer” icon on the start button and click “properties”, from there go to “advanced system settings”, click “environment variables”, from the system variables find the “Path” variable, click edit but DON’T delete anything, at the very end of the “Variable Value” add a “;” and add the path of your adb platform-tools folder. In my case is C:\android-adt-bundle\sdk\platform-tools
For example:
The end of my PC Variable Value is: C:\Program Files (x86)\QuickTime\QTSystem\
You must make this:
C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-adt-bundle\sdk\platform-tools
Now you click OK, click OK again and test if it works, to do that go to any windows explorer and press the shift button and right click, and click “Open command window here”. Write “adb” and click enter. If it say Android Debug Bridge version XX.X.XX and a lot of letters then you’re good to go, if your press adb and it say not found or something like that, then something is wrong.
e) Extract the RETUS_XT1045_4.4.3_KXB21.14-L1.23-4_cid9_CFC.xml.zip to a new folder in the desktop of the PC. Or your preferred folder.
f) The firmware we download earlier end with .xml.zip, for this reason we are going to need to download the Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract only the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). *User @darknomad23 finds out that mfastboot does not work with USB 3.0, so, use only USB 2.0. Thanks man.
Steps to restore stock firmware:
1) Reboot the phone into bootloader mode.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' and ‘Power’ button on the phone for around three seconds and let go the two at the same time.
You should now see the Moto G LTE bootloader screen with the following options:
Normal Powerup
Recovery
Factory
Barcodes
BP Tools
QCOM
c) Connect USB cable to your computer. Wait for the driver to be installed.
2) Open a command prompt (Start -> cmd.exe in Win7,8) and browse to the folder with the extracted firmware. Simply go to the folder with the extracted files and press the shift button and right click, and click “Open command window here”. In that folder you must have all the .img and .bin files and others, plus the mfastboot.exe file.
3) Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY].
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
In the: “mfastboot flash system system.img_sparsechunk.(0,1,2)” you must have the dot, the dot before the number. In some of the other guides I see that they do not add the .0 .1 .2 and it creates an error because the file is never found.
If you want the device to reboot automatically to bootloader mode each time you restart the device you can use this command:
Code:
mfastboot oem fb_mode_set
If you don’t want to reboot automatically to bootloader mode you can use this command to clear that option on the device.
Code:
mfastboot oem fb_mode_clear
That’s all. I hope it works to you like it works to me, anything just let me know in the thread.
I've seen a lot of threads explaining the same thing, but not a single one specifically meant for the LTE, and being this complete. I have seen a few LTE owners panicking after following the steps in those threads too literally.
These are errors that are easily made, and could have been avoided if this thread had been up here earlier.
It might not be original development, but still very useful in the LTE threads?
You can see he put a lot of time in trying to make it as noob-friendly as possible, and even mentions and credits the original threads he used info from.
Many OP's don't even bother, or steal other's ideas making it look like it's their original idea. Tweaks anyone? [emoji13]
I wish all were as honest as this guy is, so kudos to the OP of this thread [emoji106]
Verstuurd vanaf mijn XT1039 met Tapatalk
did anyone receive a 4.4.4 update? xt1045 seems in the dark.
Somcom3X said:
did anyone receive a 4.4.4 update? xt1045 seems in the dark.
Click to expand...
Click to collapse
At this point all Moto G (US, EU, UK, BR and ASIA) have 4.4.4, but only Moto G 4G EU has 4.4.4.
Somcom3X said:
did anyone receive a 4.4.4 update? xt1045 seems in the dark.
Click to expand...
Click to collapse
Still on 4.4.3 here.
Thanks for posting this thread.
It's definitely worth posting here as far as I'm concerned. I don't wish to wade into the vanilla Moto G forums if I can avoid it.
Hopefully I'll never need these instructions, but good to know they're here if I ever need them.
I have a US retail XT1045 Moto G bought from Amazon. It's running Android 4.4.3.
I unlocked my bootloader, replaced the warning screen, and rooted it. Looking forward to putting TWRP and a custom ROM on it when I get my PC back.
Sent from XT1045 running XDA Premium app. Peace!
danny8 said:
Thanks for posting this thread.
It's definitely worth posting here as far as I'm concerned. I don't wish to wade into the vanilla Moto G forums if I can avoid it.
Hopefully I'll never need these instructions, but good to know they're here if I ever need them.
I have a US retail XT1045 Moto G bought from Amazon. It's running Android 4.4.3.
I unlocked my bootloader, replaced the warning screen, and rooted it. Looking forward to putting TWRP and a custom ROM on it when I get my PC back.
Click to expand...
Click to collapse
Nice to see you here. Got one of these for the wife. She likes it way better than the t679! I would get one too if the Nexus 6 wasn't around the corner.
rkuijpers said:
I've seen a lot of threads explaining the same thing, but not a single one specifically meant for the LTE, and being this complete. I have seen a few LTE owners panicking after following the steps in those threads too literally.
These are errors that are easily made, and could have been avoided if this thread had been up here earlier.
It might not be original development, but still very useful in the LTE threads?
You can see he put a lot of time in trying to make it as noob-friendly as possible, and even mentions and credits the original threads he used info from.
Many OP's don't even bother, or steal other's ideas making it look like it's their original idea. Tweaks anyone? [emoji13]
I wish all were as honest as this guy is, so kudos to the OP of this thread [emoji106]
Verstuurd vanaf mijn XT1039 met Tapatalk
Click to expand...
Click to collapse
That’s right. There is a lot of threads about the Moto G, but for the LTE there isn’t lots of them. In a matter of time the community will grow. Now I just want to help the users, and I think that I am doing right.
I know about the errors, when I try to restore my phone to stock I try a few times before I can succeed, I succeed by my own and reading a lot. Once I successfully restore to stock I decide to make a thread so the others don’t make the same mistakes and errors that I made.
When I was going to post the thread I think and I was something confused if I post the thread in Moto G Q&A, Help & Troubleshooting or Moto G 4G Android Development section. I decide in the Development because I as a user when I first search for my 4G version, I search in the 4G threads. Not the Q&A or General. I am looking for the 4G, not the “Not 4G version”. And since that there is not lots of threads in here, it would be better for the users. This is not the first thread of “back to stock” in Development section in XDA.
Yes, I like to give credits. I prefer to give credits. I know I could make this as totally mine and my ideas. But no, I am here to help, and being helped, that’s all. In a future I don’t want to have some “discussion” or “problem” in here about the info that I use, or something about their thread, stealing info, etc etc, you understand. I prefer to give credits.
And thanks for being sincere about what you think.
danny8 said:
Thanks for posting this thread.
It's definitely worth posting here as far as I'm concerned. I don't wish to wade into the vanilla Moto G forums if I can avoid it.
Hopefully I'll never need these instructions, but good to know they're here if I ever need them.
I have a US retail XT1045 Moto G bought from Amazon. It's running Android 4.4.3.
I unlocked my bootloader, replaced the warning screen, and rooted it. Looking forward to putting TWRP and a custom ROM on it when I get my PC back.
Sent from XT1045 running XDA Premium app. Peace!
Click to expand...
Click to collapse
You're welcome.
In my case I only have one phone right now, this one. I need a stable phone and rom. I am running stock KK 4.4.3, I unlock my bootloader, and I root my device. In my personal thinking, I don’t want another rom or recovery, only the 4.4.4, the one that as far as I know it is not available to our devices yet. As I know there is not a really stable recovery to our devices, I only want root.
Why don’t you do what I do?
I unlock the booloader, root the device, and install the Xposed Framework.
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
With the Xposed Framework installed and Gravity Box KK module from their repositories in the Download section I make almost everything of what I use to do in the custom roms. With Xposed, and Gravity Box I don’t need a custom rom for now.
I think this is a good thread. The information is tailored for the XT1045 user. I am not new to Android, but I am new to the XT1045 and I sure don't want to read about other Moto G devices that have nothing to do with the XT1045.
With that, the only criticism I have is using terms that the new guys will not fully understand, or instructions without steps to complete the instruction. Like boot into bootloader mode. I will have to research that to find the way to do it. However, if you say boot in bootloader mode and then give instruction on how, the battle is won.
I know this may sound silly, but having step by step is valid. I just ordered the XT1045 and should have it in a few days. I have at this time no plans to root or anything else. Not until I understand the device. I did the same with my SGT3 10" tablet. I had no problems because there were good step by step instructions on how to root.
The other device I was look at before buying the XT1045 was the Nexus 5. I found a thread that gave such detail instruction that it was not needed to look anywhere else. Here is the link so you see what I mean: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
I am sure this info is available elsewhere, but it was all right in one posting. I have never seen anything like it before. It was well written.
Thanks for you set of instructions for the XT1045.
headcheese said:
Still on 4.4.3 here.
Click to expand...
Click to collapse
Yep, still on 4.4.3. Even the Verizon version has it now :|
I've had a cleanup in here guys and I'd prefer not to have to return for the same reasons.
If you've got nothing constructive to add to the discussion, don't even bother posting.
I'm not going to single anyone out at this stage but the negativity and sense of entitlement around here is ridiculous.
Everyone has a right to their opinion but that's where your entitlement ends as far as I'm concerned.
Your right does NOT extend to posting your negative opinion here and derailing a thread from it's original intent - TO HELP PEOPLE.
If you think you can do a better job, by all means - make your own thread.
PLEASE..XT1045 Stock 4.4.4 OTA firmware link..
Has this device taken an OTA for 4.4.4, Been away for a few days..
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
NWKENT said:
PLEASE..XT1045 Stock 4.4.4 OTA firmware link..
Has this device taken an OTA for 4.4.4, Been away for a few days..
Click to expand...
Click to collapse
I'm still on 4.4.3, XT1045 TMOUS - no OTA available as of yet.
Forgive me if I'm being ignorant, but why would you want to flash 4.4.4 firmware given all the problems that update seems to be causing many 4G devices?
FoneWatcher said:
I'm still on 4.4.3, XT1045 TMOUS - no OTA available as of yet.
Forgive me if I'm being ignorant, but why would you want to flash 4.4.4 firmware given all the problems that update seems to be causing many 4G devices?
Click to expand...
Click to collapse
No Sir, not ignorant..LOL
I like to test, I usually purchase two of each device, and I have just purchased another XT1045 a few days ago, and I'd like to do some testing now..as long as one can revert, then I enjoy testing..
If you'all where to see a zip OTA or a Factory FXZ (when available) please post a link..thank you..
The XDA firmware pages (XT1045) doesn't even have 4.4.3 posted yet.?
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
NWKENT said:
No Sir, not ignorant..LOL
I like to test, I usually purchase two of each device, and I have just purchased another XT1045 a few days ago, and I'd like to do some testing now..as long as one can revert, then I enjoy testing..
Click to expand...
Click to collapse
Ah, okay. I (like a lot of us here do) have a slight phone fetish, as well (as you can see in my sig.)
Normally, I buy last year's flagships so I can get two phones for the price of one current flagship.
Originally I had bought a Moto G, then traded up to a 4G - to use a "backup" weekend phone.
Then two strange things happened: 1. I started carrying around my virginal white-on-white 4G LTE more than my flagship phones because it's so incredible and beautiful, so I became paranoid. The I realized that at $229, it cost almost as much as my used flagships G2 D801 and One M7 (275 and 300, respectively), so I'm as nervous about the 4G.
So last week I bought a cheap unlocked used 8GB MotoG for $119 as my "beater" and test mule. Rooted, Xposed GEL and - you guessed it - now this is my new favorite daily driver.
Not sure if this thread is still active, but I need help with this. I follow all the steps exactly and then when I try to boot up normally for the first time it says:
USB connected
Invalid boot image header!
Boot up failed.
What does this mean in terms of this guide?
2 questions.
Is there a cwm flashable zip of the stock rom for the moto g 4g lte?
Do updates work if youve unlocked the bootloader and rooted your phone?
Voiding said:
Not sure if this thread is still active, but I need help with this. I follow all the steps exactly and then when I try to boot up normally for the first time it says:
USB connected
Invalid boot image header!
Boot up failed.
What does this mean in terms of this guide?
Click to expand...
Click to collapse
Sir..Friend..what did you flash.?
What procedures did you use to flash.?
Assuming you have an XT1045.?
Sent from my 4.4.4_21.11.56_peregrine
(Unlocked) XT1045 Moto G 4G LTE #1
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
---------- Post added at 07:32 AM ---------- Previous post was at 07:19 AM ----------
ivesdotkom said:
2 questions.
Is there a cwm flashable zip of the stock rom for the moto g 4g lte?
Do updates work if youve unlocked the bootloader and rooted your phone?
Click to expand...
Click to collapse
Here is my OTA 4.4.4_21.11.56 peregrine (XT1045).. I have not seen a full (factory) FXZ for the XT1045, Nore have I ever seen it posted to the firmware pages..
One would flash this zip in TWRP or CWM..onto the existing (4.4.3)..
Here >> https://docs.google.com/file/d/0B67RS0BDBp_iOWhZdGlmWXpOQW8/edit?usp=docslist_api
Sent from my 4.4.4_21.11.56_peregrine
(Unlocked) XT1045 Moto G 4G LTE #1
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Fixed. Installed mfastboot incorrectly. I fixed this and used mfastboot, all is good now.
Sorry for my late reply.
@NWKENT
We have the 4.4.4 OTA update for the XT1045 a few weeks ago, I know. But at this time I have not find the .xml.zip file of the KK 4.4.4, I mean the one of around 500MB or 600MB. If you find it please let me know so I can update the guide, thanks.
@Voiding
Yes the guide still active. Because of the university I only connect when I have the time but yes it will be always active. Once I found new things I will keep updating the guide.
Glad that you can fix the problem.
Hey guys and girls,
I'd look for testers who could check if the merges at the kernel source I've done are working properly.
I'm currently working on building a unified repository of kernel source with which hopefully all variants can be served and from which other developers can start from without having to worry about if the base source does work or has errors.
But even while I look deep into the source and hopefully don't miss anything, i can't really verify if it's working properly, except of compiling, for other variants than the D855, because that's the only device i own, so I need testers that could verify it's functionality.
Prerequisites
Knowledge about fastboot and how to temporarily boot kernels with it (WARNING! always take backups before trying to get to or mess with fastboot)
Knowledge about logcat and how to provide logs
Knowledge about dmesg and how to provide it's information
Note: I'm just integrating other variants at the stock source, there won't be any bells or whistles added, that's not the purpose of this project, so don't expect me to add any overclocking or other features! This may come with another project in the future, but this doesn't matter for now.
The project itself can be found here.
Thanks in advance to those willing to test
Hey,
I've now integrated the LS990 variant, so I'd need testers for this variant to
Ls990 doesn't have root yet
Sent from my LGLS990 using XDA Premium 4 mobile app
I would be happy to test the D851 kernel.
If I'm not mistaken you need to unlock the boot loader to change the kernel? If so the d850 is locked
Sent from my LG-D850 using Tapatalk 2
Tectas said:
the op
Click to expand...
Click to collapse
could you add to the op that it is Advised that they make a twrp backup(of everything but especially modem) before they begin messing with fastboot to minimize the chance of bricking
screwyluie said:
If I'm not mistaken you need to unlock the boot loader to change the kernel? If so the d850 is locked
Sent from my LG-D850 using Tapatalk 2
Click to expand...
Click to collapse
you boot this kernel temporary and not permanently and aslong as you just boot the kernel and don't try to flash it you will not have a problem
evodon84 said:
I would be happy to test the D851 kernel.
Click to expand...
Click to collapse
Great, thanks, unfortunately I'm short on time over the weekend, I'll send you a pm with instructions and the image within the next days (latest on Monday), thanks in advance for testing
suljo94 said:
could you add to the op that it is Advised that they make a twrp backup(of everything but especially modem) before they begin messing with fastboot to minimize the chance of bricking
Click to expand...
Click to collapse
Well, I intentionally added nowhere an image to avoid people not knowing what they're doing going through the steps to get fastboot working and trying to flash the kernel, but probably you're right and I should add an additional warning, it's just a bit tricky on other variants than the D851, because fastboot is needed to get to twrp , but thanks
Sent from my LG-D855
You can add F400 it?
If you support the F400, then I will be very happy
姚鑫海 said:
If you support the F400, then I will be very happy
Click to expand...
Click to collapse
It's not yet supported, but I'm planning to add support for it, as soon I've merged it, I'll send you a pm for testing, thanks in advance
Sent from my LG-D855
Could someone owning the F400 variant please post the value of ro.product.name from their build.prop?
Thanks in advance.
Edit: Nevermind
F400 added, just VS985 missing and it's done so far. When that's done and feedback is well from the testers, I'll start a new project based on this and add features.
I'd btw need testers for D850 still.
Edit: all variants except of d852 are added now, if i haven't missed any.
Edit2: all variants should be merged now.
Tectas said:
Hey,
I've now integrated the LS990 variant, so I'd need testers for this variant to
Click to expand...
Click to collapse
Does this suggest you have root for the Sprint variant? Tia
Sent from my Gunmetal Lg G3
Tectas said:
F400 added, just VS985 missing and it's done so far. When that's done and feedback is well from the testers, I'll start a new project based on this and add features.
I'd btw need testers for D850 still.
Edit: all variants except of d852 are added now, if i haven't missed any.
Edit2: all variants should be merged now.
Click to expand...
Click to collapse
a quick idea yesterday i received an update and accidentally pressed on “update now” button I had the tethered twrp installed so it kept booting in fastboot I couldn't boot normally it always booted in fastboot. now my idea is if you would be able to find what is forcing the phone to boot to recovery and change the command/target file to something on your sdcard and to just boot that, you could set it up to boot into a custom kernel every reboot without a problem.
good
Tectas said:
Could someone owning the F400 variant please post the value of ro.product.name from their build.prop?
Thanks in advance.
Edit: Nevermind
Click to expand...
Click to collapse
Hey buddy I'm very pleased to see F400 haha What can I help you? O(∩_∩)O~
suljo94 said:
a quick idea yesterday i received an update and accidentally pressed on “update now” button I had the tethered twrp installed so it kept booting in fastboot I couldn't boot normally it always booted in fastboot. now my idea is if you would be able to find what is forcing the phone to boot to recovery and change the command/target file to something on your sdcard and to just boot that, you could set it up to boot into a custom kernel every reboot without a problem.
Click to expand...
Click to collapse
Sounds good, but I don't think it's that easy unfortunately. I guess the updater sets an indicator that an update has to be applied, which simply forces a recovery reboot. The rest of it is more or less the dual boot functionality of Siyah, with one exception, we can't change the boot partition without triggering the security, means this functionality would have to reside within system and would have to replace a already booted kernel with another one in memory. That's not an easy task. Another way would be a hacked fastboot which boots an predefined image from the sd, but this would only be helpful if we at least can change the fastboot partition, what probably also triggers the security, but I'm not sure about that. Sorry.
姚鑫海 said:
Hey buddy I'm very pleased to see F400 haha What can I help you? O(∩_∩)O~
Click to expand...
Click to collapse
I'll send you instructions and the image to test tomorrow, if it's OK for you.
Sent from my LG-D855
Tectas said:
Sounds good, but I don't think it's that easy unfortunately. I guess the updater sets an indicator that an update has to be applied, which simply forces a recovery reboot. The rest of it is more or less the dual boot functionality of Siyah, with one exception, we can't change the boot partition without triggering the security, means this functionality would have to reside within system and would have to replace a already booted kernel with another one in memory. That's not an easy task. Another way would be a hacked fastboot which boots an predefined image from the sd, but this would only be helpful if we at least can change the fastboot partition, what probably also triggers the security, but I'm not sure about that. Sorry.
Click to expand...
Click to collapse
ow well back to the cm11 kernel on top of the orriginal to not trigger security idea
So, I've packed Images for D855 and D851 for public testing, there are no bells or whistles added, default behaviour, only difference to complete stock is, they are build with the linaro toolchain, though not with -O3 optimization (it builds fine with it, but won't boot, but just freezes at fastboot, so I left it out for now).
I won't add a guide how to apply those images over fastboot though, if you know how, try it, if not, let it be!!! (but as a hint to those capable of doing it, but just not knowing the exact steps, it's the same as with the tethered twrp, you just have to boot the boot.img instead of the twrp.img)
DON'T TRY TO FLASH IT THROUGH RECOVERY, it won't work, but you for sure can build a flashable zip for yourself from it for the D851, but please don't share it publicly, there are probably some which would try to flash it on other variants and brick their devices because of the locked bootloader.
D855 Test Image
md5sum: 60c062e1d57a51a19fd19151e610a6fc
D851 Test Image
md5sum: ba496fca56c831f078210e8dcd3f8df4
If people with other variants like to test it also, I need the stock boot.img of your device to repack it with the kernel, post it here or send me a pm with it and I'll build and repack one for this device as well.
fgcchevy said:
Does this suggest you have root for the Sprint variant? Tia
Sent from my Gunmetal Lg G3
Click to expand...
Click to collapse
No, I don't have root for sprint, sry.
Tectas said:
If people with other variants like to test it also, I need the stock boot.img of your device to repack it with the kernel, post it here or send me a pm with it and I'll build and repack one for this device as well.
Click to expand...
Click to collapse
Hello I've tried to boot your D855-boot.img in my D855P with success (I've asked you before since my build.prop says global D855 and TWRP was working) but I've noticed that your file is 3.5mb lighter than my stock boot... can you please give a check to my boot.img??
I got this screen, don't know if can help.
badtzo said:
Hello I've tried to boot your D855-boot.img in my D855P with success (I've asked you before since my build.prop says global D855 and TWRP was working) but I've noticed that your file is 3.5mb lighter than my stock boot... can you please give a check to my boot.img??
I got this screen, don't know if can help.
Click to expand...
Click to collapse
That's just because it is better compressed when it's repacked, my stock image has 16,8 mb
It's almost the same, just two small differences in the ramdisk
This is at your init.g3.rc but not at mine:
Code:
#[BEGIN][[email protected]]
chmod 0660 /sys/bus/i2c/devices/0-0036/lm3697_bl_max
chown system system /sys/bus/i2c/devices/0-0036/lm3697_bl_max
#[END][[email protected]]
That's at my init.lge.usb.rc but not yours:
Code:
# vzw llk mode
on property:persist.sys.store_demo_enabled=1
write /sys/class/power_supply/battery/store_demo_enabled 1
on property:persist.sys.store_demo_enabled=0
write /sys/class/power_supply/battery/store_demo_enabled 0
They are the same
Hello Guys!
I'm waiting for my new Moto X to arrive! Meanwhile, I'd like to start with a little contribution for the unlocked bootloader early adopters!
Just like the old Moto X thread, I present you the removed Warning Message logo.bin!
Simply flash it with:
Code:
fastboot flash logo logo.bin
Happy Flashing!
Helvio88 said:
Hello Guys!
I'm waiting for my new Moto X to arrive! Meanwhile, I'd like to start with a little contribution for the unlocked bootloader early adopters!
Just like the old Moto X thread, I present you the removed Warning Message logo.bin!
Simply flash it with:
Code:
fastboot flash logo logo.bin
It's untested, since I am still waiting for it to arrive. But it's safe to flash, since it's a harmless file for Android as a whole
Please post results, and ENJOY!
Click to expand...
Click to collapse
And I have already added support to my boot logo maker utility for the Moto X 2nd gen. What is a pity though, is that despite larger screen size, motorola insisted on keeping the logo partition at 4MiB, which puts constraints on how complex a logo can be made. (Worst case of every pixel of the 1920x1080 display being unique, would result in a picture that will not fit the partition.) It does mean you can have at creating some custom boot logos for when you eventually do get the device.
Will try as soon as mine arrives
Will be visiting here often as soon as I get mine too.
Just flashed....it works perfectly! Thanks.
is the logo.bin file from the new Moto X or the old one?
0.0 said:
is the logo.bin file from the new Moto X or the old one?
Click to expand...
Click to collapse
new only, this is the 2014 forum :silly:
if you need for the 2013, see this thread:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Helvio88 said:
new only, this is the 2014 forum :silly:
if you need for the 2013, see this thread:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I was only wondering since the OP said he didn't have the new Moto X, so I didn't know if he was able to get his hands on the new one or not
Sent from my Nexus 4
0.0 said:
I was only wondering since the OP said he didn't have the new Moto X, so I didn't know if he was able to get his hands on the new one or not
Sent from my Nexus 4
Click to expand...
Click to collapse
I see your point, please don't take me seriously
Since day 1, a dump has been available at http://sbf.droid-developers.org/phone.php?device=37
I just downloaded it, extracted the logo file and hacked it up. Even untested, it was the same old layout that Motorola has used.
Worked here. Thank You!
i'm really hoping this thread grows to become what the old one was, with many different boot logos. i still use the 2013 Moto X box prism one
Thanks for your work!
My simple white on black Pure Beast Mode with moto logo flashable zip
https://www.dropbox.com/s/yzwcnc21uv5lt1u/PureMoto.zip?dl=0
bhp090808 said:
My simple white on black Pure Beast Mode with moto logo flashable zip
https://www.dropbox.com/s/yzwcnc21uv5lt1u/PureMoto.zip?dl=0
Click to expand...
Click to collapse
How to apply? Pictures?
Thank You!
thiagodm said:
How to apply? Pictures?
Thank You!
Click to expand...
Click to collapse
Flash in custom recovery or extract zip, place logo.bin in fastboot directory, boot to bootloader and use
Fastboot flash logo logo.bin
Screen shot of the first one
And the new one
https://www.dropbox.com/s/glitjkx8rqaulr0/AwesomePure.zip?dl=0
Just Andy
https://www.dropbox.com/s/i6kqf4t7bwxu701/justandy.zip?dl=0
Green moto
https://www.dropbox.com/s/6tyxtz4tjgiclc5/greenmoto.zip?dl=0
Red moto
https://www.dropbox.com/s/wtd7rfyy40sbqwc/redmoto.zip?dl=0
Hi everyone!
I unlocked my bootloader and remove the "Bootloader Unlock Warning" following the tutorial "remove-bootloader-unlocked-warning-on-moto-x-and-moto-x-2014" from droidviews.
But the logo.bin in there isn't the original Moto x Play logo, actually is from Moto x 2014.
Could anyone give me the original logo?
Best regards! :good:
I would go here http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
Download the appropriate rom, unzip it and take a looky loo for the logo.bin
Chances are that it's not here right now but that's how I would go about it.
If you find it you can use ES file Explorer or your app of choice to swap it out.
renanr2 said:
Hi everyone!
I unlocked my bootloader and remove the "Bootloader Unlock Warning" following the tutorial "remove-bootloader-unlocked-warning-on-moto-x-and-moto-x-2014" from droidviews.
But the logo.bin in there isn't the original Moto x Play logo, actually is from Moto x 2014.
Could anyone give me the original logo?
Best regards! :good:
Click to expand...
Click to collapse
Tim3tripp3r said:
Download the appropriate rom, unzip it and take a looky loo for the logo.bin
Chances are that it's not here right now but that's how I would go about it.
If you find it you can use ES file Explorer or your app of choice to swap it out.
Click to expand...
Click to collapse
I already tried that approch because I wanted the original X Play logo. I downloaded the original ROM for the Moto X Play, I opened the zip file and there it was: a logo.bin file. Then, I used fastboot to flash it into my phone, but instead of having the original logo when I rebooted the phone, it showed me the unlocked bootloader warning again. That's why I reverted to the logo.bin from the Moto X 2014.
Actually I have found that there is more to it than I first suggested.
The process here should give you the info needed to accomplish the job
www.droidviews.com/get-rid-unlocked-bootloader-warning-moto-g/
Nico3d3 said:
I already tried that approch because I wanted the original X Play logo. I downloaded the original ROM for the Moto X Play, I opened the zip file and there it was: a logo.bin file. Then, I used fastboot to flash it into my phone, but instead of having the original logo when I rebooted the phone, it showed me the unlocked bootloader warning again. That's why I reverted to the logo.bin from the Moto X 2014.
Click to expand...
Click to collapse
Tim3tripp3r said:
Actually I have found that there is more to it than I first suggested.
The process here should give you the info needed to accomplish the job
Click to expand...
Click to collapse
I flash the original logo.bin but the unlock bootloader warning reappeared, like Nico3d3 said. I think the flag of this warning affect just the original logo.bin, so, the logo of moto x 2014 do not show this warning.
I just wanna that black and white logo back, i really like it!
I got it! I extracted the original logo.bin images, found on Moto x Original rom thread thanks to XMoDuLeSx, using the boot logo command line tool, found on marmottepoilue thread, i picked logo_boot.png, rename it to logo_unlocked.png and replaced into logo.bin the logo_unlocked with the new one.
I flashed and original logo is back!
Thanks for everyone who helped! :highfive:
Id like to do this too seems a bit complicated. Can you post the modified file ready to flash. Also it is the original X Play boot logo isn't it?
Sent from my XT1562 using Tapatalk
ephumuris said:
Id like to do this too seems a bit complicated. Can you post the modified file ready to flash. Also it is the original X Play boot logo isn't it?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
I have to post more 6 times to be allowed to post links, sorry... :crying:
When I can, I'll post here.
Just edit the link add some special characters we can remove
Sent from my XT1562 using Tapatalk
ephumuris said:
Just edit the link add some special characters we can remove
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Here you have it
Just extract the file and flash it with fastboot
eskamhl said:
Here you have it
Just extract the file and flash it with fastboot
Click to expand...
Click to collapse
Thanks eskamhl!
Worked perfectly.
Sent from my XT1562 using Tapatalk
You Da Man!
eskamhl said:
Here you have it
Just extract the filHey hey, and flash it with fastboot
Click to expand...
Click to collapse
Just wanted to say thanks so much for posting the flashable logo.bin for X Play. I can confirm it's working sexually as well. Very...sexually...
Best to you all,
--Mike
eskamhl said:
Here you have it
Just extract the file and flash it with fastboot
Click to expand...
Click to collapse
Super easy flash and worked perfect, thanks a bunch for putting that together.
Tim3tripp3r said:
I would go here http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
Download the appropriate rom, unzip it and take a looky loo for the logo.bin
Chances are that it's not here right now but that's how I would go about it.
If you find it you can use ES file Explorer or your app of choice to swap it out.
Click to expand...
Click to collapse
Hi, I know this is a few months old but wouldn't it be possible to get a logo.bin from the original firmware and just flash that?
Many thanks,
Rob
rob54321 said:
Hi, I know this is a few months old but wouldn't it be possible to get a logo.bin from the original firmware and just flash that?
Many thanks,
Rob
Click to expand...
Click to collapse
Yes it's possible. It's what we do after rooting to remove the "unlocked bootloader" warning .
Here you go http://forum.xda-developers.com/moto-x-play/themes-apps/boot-logo-stock-disable-bootloader-t3257606
Thanks, sorry I hadn't read the rest of the thread before I posted. Lol!
Sent from my XT1562 using Tapatalk
Unlocked the bootloader and flashed the logo from first try!
You can also remove it yourself, there's a tool somewhere on this forum called MotoBootLogoMaker. It works pretty well.