Database Users

[Guide] Moto G 4G LTE XT1045. Restore To Stock 4.4.3 KK. Explained.

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.

[UNLOCK] Bootloader unlock for MotoX 2014 via Sunshine!

Greetings!
As of today there is a method to completely unlock the bootloader on all variants (yes, this includes the Verizon and AT&T models). The one stipulation is you need to have root.
DISCLAIMER #0: This is NOT MY WORK. I'm merely posting steps to use other peoples' work (with permission) in order to achieve an unlocked device. Do not donate to me for this. Any donations sent to me for this post will be promptly returned and you will be publicly shamed, most likely Game of Thrones style, for not reading the entire OP and following directions.
DISCLAIMER #1: Unlocking your device is dangerous! I am in no way responsible for anything that happens to you, your device, your significant other, or any random person that you feel the need to harm after this destroys your device! You are making the decision to run these tools and you alone are responsible for the consequences!
DISCLAIMER #2: As of right now this method has ONLY been tested on variants running kitkat (4.4) roms/bootloaders. Do not be the first to try it on a lollipop version without first understanding the risks. If you try and successfully use this method on lollipop (5.x) please let me know so I adjust this post accordingly.
DISCLAIMER #3: Do not attempt to re-lock your bootloader after using Sunshine. It is unclear how the device will act and you may end up with one of these.
PREFACE:
- You're going to want adb and fastboot set up on your computer. If you don't know what these are, or don't know how to set them up, google it. Having these tools is insanely helpful anyway for debugging and getting logs for developers later. You're going to want these in the long run.
- This method in the end is going to set you back $25. Sunshine is the tool used to unlock the bootloader and the people that develop this spend insane amounts of time developing/breaking/buying devices. Trust me, its worth it.
- Enable Unknown sources in Settings > Security before starting
STEP 1: Root (This root method only works on 4.4. If you are already rooted, say via mofo or another method, you may skip to step 2)
- You just skipped to this step didn't you? Go read the disclaimers and the preface. They are extremely important.
- Root your phone using KingRoot (obviously click the image with the little android guy on it) mirror
Code:
adb install -r <filename>.apk
- Run it from your app drawer and follow the prompts. I did have it fail a couple times, if that happens, try rebooting and running it again. I also had it say it failed a couple times, but still was able to gain root by typing 'su' in an adb shell.
- KingRoot is a temp root, which means upon a reboot, you will lose root and need to run it again. That's fine for our purposes here, it gives us the in we need for the bootloader exploit (see step 2)
STEP 2: Unlock That Bootloader
- This step involves running an app called Sunshine. Download the apk from there and install it:
Code:
adb install -r <filename>.apk
- Again, this unlock will cost you a one time fee of $25, more info on their FAQ. There seems to be a lot of animosity about this, but in the end the choice is yours. An extreme amount of development time goes in to these types of exploits and these guys do a fantastic job. It is worth it.
- Follow the prompts, get out the wallet, and enjoy an unlocked bootloader!
STEP 3: Install a custom recovery
- This could be considered an optional step, but there's really no reason to go through all of this if you don't plan to do some custom things. Custom recovery allows you to install/backup/restore ROMs on your phone.
- Follow the instructions here now that you have an unlocked bootloader in order to install TWRP.
STEP 4: Enjoy!
- You now have a completely unlocked phone! Start installing roms, enjoy yourself! Be careful though! Make sure you are only flashing things that are known to work on this device.

SunShine 3.1.16 is out, better support for MotoX 2014, including custom roms

Just ran Sunshine 3.1.17 on my 5.1 XT1097 rooted via MoFo, device is unlocked and working flawlessly.

invisiblek said:
(This root method only works on 4.4. If you are already rooted, say via mofo or another method, you may skip to step 2)
Click to expand...
Click to collapse
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?

JulesJam said:
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
Click to expand...
Click to collapse
Only way to know is try if okay with the risks.
We talked about it in the general thread. Sometimes it even works on other devices running 5.1.1 (even not officially supported). I cannot assume the risk being my only phone to try.
Visi0nofExcellence2 said:
There are posts of it working for other devices. It will fail a couple of times and then just work. Also cases where the phone won't boot anymore. More of the latter now.
Not attempting and I suggest others dont either. Risk outweighs rewards with this being my main phone.
Click to expand...
Click to collapse
Visi0nofExcellence2 said:
jcase said:
Kingroot shouldnt cause the phone to stop booting, odd. Thanks for makign the thread btw
Click to expand...
Click to collapse
Not bootng is horribly ambiguous wording on my part.
chicodelta said:
My shield is running 5.1..1. I tried kingroot 4.5, since others have reported success and now my tablet won't boot past the nvidia screen. Anyone else encountered this issue?
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/general/root-kingroot-t3112722/page4
Click to expand...
Click to collapse

JulesJam said:
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
Click to expand...
Click to collapse
I tried it (several times). It doesn't.
Sent from my XT1096 using Tapatalk

I did mofo yesterday and did SunShine today, worked great. I had 5.0 on my 1096.
Sent from my XT1096 using XDA Free mobile app

Any known root methods for 5.1 yet? AT&T Moto X via OTA.

I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online

christopher68369 said:
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
Click to expand...
Click to collapse
No
Sent from my XT1096 using Tapatalk

christopher68369 said:
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
Click to expand...
Click to collapse
It won't work. You can't flash the firmware from other carriers with a locked bootloader. It will fail when you try.
Sent from my XT1095 using Tapatalk

Only firmware you can flash with a locked bootloader has to contain the same signature of the firmware your on, which is literally only that firmware. EG. ATT 5.1 sig does not match any other sig.

Yes I realised that after doing research. Butbim wondering if we were able to change the cid to lets say the Brazil variant if we would be able to flash the firmware. If we could maybe change the cid from dfs software or GSM tools software and then try to flash the firmware if it would work. If someone knew how to change the cid without root I wouldn't mind trying it out to see if it would work. I'm planning on buying the moto x pure edition that comes out on Sept 2 but i f I was able to unlock the bootloader then I wouldn't really mind waiting on a new phone for another year since the moto x 2014 is really a great phone and with root has alot of potential

Same problem, you can't do that either without root and bootloader unlocked. There is no way to do it until someone can find a vulnerability in the 5.1 firmware. For now you are stuck.
Sent from my XT1095 using Tapatalk

I don't understand. Motorola officially provides the way to unlock bootloaders. Why does this method exist? Does this method help unlock bootloaders of devices that cannot be unlocked or something like that?

Yes, this is only for the Verizon xt1096 and the AT&T xt1097. Those 2 models cannot unlock their bootloader from motorola's website. This is a method to get around that and unlock it anyway.
Sent from my XT1095 using Tapatalk

So I have a Verizon model XT1096 running 5.0.
From the searches I've performed and from what I've read so far, Root can be achieved via Mofo (kingroot failed) and then I can unlock the bootloader via sunshine and then flash TWRP, flash a 5.1.1 ROM and I'm good to go?
There are several threads with a little info here and there, so I apologize for the questions. I just want to get my ducks in a row.

You are correct.
Sent from my XT1095 using Tapatalk

Ed Murray said:
So I have a Verizon model XT1096 running 5.0.
From the searches I've performed and from what I've read so far, Root can be achieved via Mofo (kingroot failed) and then I can unlock the bootloader via sunshine and then flash TWRP, flash a 5.1.1 ROM and I'm good to go?
There are several threads with a little info here and there, so I apologize for the questions. I just want to get my ducks in a row.
Click to expand...
Click to collapse
Kingroot said that it failed for me but sunshine still worked normally afterwards. If you haven't already paid for mofo then you can just pay for sunshine
Sent from my XT1095 using Tapatalk

Moto X 2013 (Verizon and ATT) got root on 5.1 with locked bootloader. Maybe we can use the same exploit?
http://forum.xda-developers.com/moto-x/general/root-moto-x-att-xt1058-5-1-lpa23-12-21-1-t3164125

[Help Thread] Droid Turbo 2 (XT1580 - XT1585) noob friendly

[SIZE=+2]This thread has been created for Questions & Answers/Troubleshooting[/SIZE]​ [SIZE=+2]Specific to[/SIZE]
Verizon Droid Turbo 2 XT1585
Mexican Moto X Force XT1580
Brasil Moto X Force XT1580
China Moto X Force XT1581
UK Moto X Force XT1580 N
​ Please feel free to share issues, questions and offer help. Noob questions are welcomed. It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters... ... ... ...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @. If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you! Supporters: If you want to be put on or off the list, just make a request here in the thread! Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Index for Device Thread Link
Please look for a similar thread when visiting another device forum. If you would like to create a [Help Thread] please Click Here. ​

save

as you can remove the message the sim is not verizon.
Enviado desde mi XT1585 mediante Tapatalk

Bricked my XT1580 UK N
Hey XDA Developers
I admit i am an idiot!
I tried to root my XT1580 with a tutorial (not able to post link) and of course i bricked my phone big time. Is there a nice developer wich would try to help me flash a stock rom to my phone and hopefully make it boot again?
I used: twrp-2.8.7.0-kinzie.img
And SuperSU v2.65
I now downloaded Stock Marshmallow 6.0.0 /// XT1580_KINZIE_RETMX_DS_6.0_MPK24.78-8_cid12_subsidy-DEFAULT_CFC.xml.zip as i tought this would be the fiting stock rom for this device and region i live (Switzerland) but i am not very shure how to do it and i just dont want to destroy my belved xt1580 more than it allready is.
I am happy for any response.
Best Regards

Luschikofski said:
Hey XDA Developers
I admit i am an idiot!
I tried to root my XT1580 with a tutorial (not able to post link) and of course i bricked my phone big time. Is there a nice developer wich would try to help me flash a stock rom to my phone and hopefully make it boot again?
I used: twrp-2.8.7.0-kinzie.img
And SuperSU v2.65
I now downloaded Stock Marshmallow 6.0.0 /// XT1580_KINZIE_RETMX_DS_6.0_MPK24.78-8_cid12_subsidy-DEFAULT_CFC.xml.zip as i tought this would be the fiting stock rom for this device and region i live (Switzerland) but i am not very shure how to do it and i just dont want to destroy my belved xt1580 more than it allready is.
I am happy for any response.
Best Regards
Click to expand...
Click to collapse
you flashed twrp?
you were able boot twrp?
Sent from my DROID Turbo using XDA Labs

sd_shadow said:
you flashed twrp?
you were able boot twrp?
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
Hey sd_Shadow!
Thanks for your reply.
Yes, i was (and still am) able to boot TWRP. But thats not a big deal in my eyes. I am not the first one who have this done. Was easy.
br

Luschikofski said:
Hey sd_Shadow!
Thanks for your reply.
Yes, i was (and still am) able to boot TWRP. But thats not a big deal in my eyes. I am not the first one who have this done. Was easy.
br
Click to expand...
Click to collapse
yes, just trying to understand the nature of the problem
you installed Supersu.zip and then...
Sent from my DROID Turbo using Tapatalk

sd_shadow said:
yes, just trying to understand the nature of the problem
you installed Supersu.zip and then...
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Aaah okay
yes, i then installed SuperSU. Went well, without errors. After that i reboot the phone as described in the tutorial. Now my XT1580 wont boot anymore. it is just stuck on the first boot image (Moto sign)
i tried with the same again and one time more with a difference version of TWRP and SuperSU. still no change

Luschikofski said:
Aaah okay
yes, i then installed SuperSU. Went well, without errors. After that i reboot the phone as described in the tutorial. Now my XT1580 wont boot anymore. it is just stuck on the first boot image (Moto sign)
i tried with the same again and one time more with a difference version of TWRP and SuperSU. still no change
Click to expand...
Click to collapse
I would try wiping the caches in twrp
Sent from my DROID Turbo using Tapatalk

sd_shadow said:
I would try wiping the caches in twrp
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
You mean wipe dalvik cache ? Did allready. No change I can try again as soon as i arrive at home

Luschikofski said:
You mean wipe dalvik cache ? Did allready. No change I can try again as soon as i arrive at home
Click to expand...
Click to collapse
http://www.theandroidsoul.com/marsh...ola-moto-x-force-droid-turbo-2-variant-88178/
there is nothing in this guide that should have caused any issues
Sent from my DROID Turbo using XDA Labs

maybe those twrp versions are not compatible?
if not should just be able to reflash stock recovery.img
Sent from my DROID Turbo using XDA Labs

sd_shadow said:
http://www.theandroidsoul.com/marsh...ola-moto-x-force-droid-turbo-2-variant-88178/
there is nothing in this guide that should have caused any issues
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
sd_shadow said:
maybe those twrp versions are not compatible?
if not should just be able to reflash stock recovery.img
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
i have to be honest. i have no idea about compatibility of twrp but I did a factory reset / Cache wipe in twrp. no change
I would really love to re-flash the stock recovery but i think its already obvious that there is now way i know how to do that Would it be possible for you to write a short step by step tut for this for me? Dont need to very detailed. I am a techie but not enough clue about where to get the right file
i would really appreciate

Luschikofski said:
i have to be honest. i have no idea about compatibility of twrp but I did a factory reset / Cache wipe in twrp. no change
I would really love to re-flash the stock recovery but i think its already obvious that there is now way i know how to do that Would it be possible for you to write a short step by step tut for this for me? Dont need to very detailed. I am a techie but not enough clue about where to get the right file
i would really appreciate
Click to expand...
Click to collapse
stock recovery.img would be flashed same as twrp.img
fastboot flash recovery.img
stock recovery.img is in the stock firmware xml.zip
just unzip
or just flash firmware with RSD Lite, just need to be sure that it's for your model, region and carrier.
I'm not sure how many options are available
Sent from my DROID Turbo using XDA Labs

sd_shadow said:
stock recovery.img would be flashed same as twrp.img
fastboot flash recovery.img
stock recovery.img is in the stock firmware xml.zip
just unzip
or just flash firmware with RSD Lite, just need to be sure that it's for your model, region and carrier.
I'm not sure how many options are available
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
Okay. I´ve tried with fastboot with no sucess. With RSD it starts and flashes until 20/29. It stops saying this:
on RSD: Failes flashing proces. 20/29 flash modem "NOH-HLOS.bin" -> Phone returned FAILS
On Phone it says: Image is too large
i was trying to dowload a rom from https://firmware.center:8081/firmware/Motorola/Moto X Force/Stock/XT1580/
but i am not shure wich ne to take. i tryed those with RETEU. Is this wrong? how do i find out wich rom is the right one?
br

Ive installed TWRP 3.0.2.0, then i backed up my stock android, then i installed cm13. And now, when i try to back up my cm13, i get error:
create tar fork error 255
and i cant add my log to post couse im new user(

Hi friends; is it possible to make a moto x force (vodafone), or any phone, no brand? please help me thanks

Hello,
I need some info on the chinese XT1581.
Is the bootloader unlockable? root? Are there any custom roms available for this device?
The only difference is the dual-sim?
Has anybody experience with this device?
Thanks!

I know I'm going to regret this and I probably already do so here goes:
I picked up a Motorola Droid Turbo 2 off craigslist tonight, traded another phone for it (LG Stylo 2 Plus) and everything was working fine during the actual meeting with the previous owner. He checked out the Stylo while I checked out the Turbo 2. Aside from scuffs and scrapes and whatnot I decided it was worth the trade - he said he was moving to Europe and just wouldn't need it anymore and he then showed me his Moto X Force (first time I'd ever seen one in person, verified it with the phone info, etc) and I figured what the hell, I'm good.
So he leaves, and me having not messed with a Verizon device for some time figured "Ok, I know all the Verizon devices are GSM unlocked from the factory since the summer of 2013 because of the FCC frequency auctions, no problem..." and then I power down and remove the T-Mobile nanoSIM from my Moto X 1st gen and power down the Turbo 2, etc, moving the nanoSIM over.
Power the Turbo 2 back up and of course I get the "SIM Card not from Verizon Wireless..." notification which I've seen in the past. I go into Settings and then set it for Global mode and... nothing, still doesn't work. Check the About phone info, it sees the nanoSIM, doesn't pull the APN data from the card so I put it in manually, still nothing. Reboot, still nothing, and so on and so forth.
I do some research and find out that Verizon - since some point in 2015 - now sells their devices technically unlocked for GSM operation but there's some funky network-specific lock on them for at least 1 year after the sale/purchase of the device so they guarantee they get something back on their investment. I called the previous owner, asked him what the deal was, he said he bought it December 1st 2015 and because he was moving that was that and it wasn't his problem anymore.
So yeah, I'm probably screwed on this for use with T-Mobile now but I figured I'd ask here anyway: not looking to rip anybody off but, I don't use Verizon, never have, never will, and I don't even know anyone that uses them either so I'm not sure how to proceed. In the good old days you could do the 4-corner trick and bypass the need to activate the phone with Verizon but obviously nothing is that simple anymore.
Is there any way to get this device up and running with T-Mobile since it should be unlocked? I called Verizon and they said because I'm not the original owner/purchaser (neither is the guy I got it from, apparently he got it used himself earlier this year) they won't provide me whatever info or method is required to make it truly GSM unlocked as it's supposed to be so I'm stuck there.
It's not blacklisted, at least that Verizon would tell me, nor stolen from what I gather - I checked the ESN against several sites like Swappa and CheckESNFree and it shows green/clear/ready for activation and yet it's just not happening.
Any advice or suggestions or straight out method to get past that aspect and make it work properly with T-Mobile is greatly appreciated if anyone can help.
If I end up using it as a Wi-Fi only device, so be it, but that wasn't the idea when I got it - my mistake was not doing research ahead of time on this new device. I've owned several Droid MAXX/Ultra/Mini smartphones - all Verizon devices of course - and never had to deal with this activation BS, I just put my T-Mobile SIM card in them and rebooted and wham, always worked without problems.
I should have known it wouldn't be that simple anymore.

br0adband said:
I know I'm going to regret this and I probably already do so here goes:
I picked up a Motorola Droid Turbo 2 off craigslist tonight, traded another phone for it (LG Stylo 2 Plus) and everything was working fine during the actual meeting with the previous owner. He checked out the Stylo while I checked out the Turbo 2. Aside from scuffs and scrapes and whatnot I decided it was worth the trade - he said he was moving to Europe and just wouldn't need it anymore and he then showed me his Moto X Force (first time I'd ever seen one in person, verified it with the phone info, etc) and I figured what the hell, I'm good.
So he leaves, and me having not messed with a Verizon device for some time figured "Ok, I know all the Verizon devices are GSM unlocked from the factory since the summer of 2013 because of the FCC frequency auctions, no problem..." and then I power down and remove the T-Mobile nanoSIM from my Moto X 1st gen and power down the Turbo 2, etc, moving the nanoSIM over.
Power the Turbo 2 back up and of course I get the "SIM Card not from Verizon Wireless..." notification which I've seen in the past. I go into Settings and then set it for Global mode and... nothing, still doesn't work. Check the About phone info, it sees the nanoSIM, doesn't pull the APN data from the card so I put it in manually, still nothing. Reboot, still nothing, and so on and so forth.
I do some research and find out that Verizon - since some point in 2015 - now sells their devices technically unlocked for GSM operation but there's some funky network-specific lock on them for at least 1 year after the sale/purchase of the device so they guarantee they get something back on their investment. I called the previous owner, asked him what the deal was, he said he bought it December 1st 2015 and because he was moving that was that and it wasn't his problem anymore.
So yeah, I'm probably screwed on this for use with T-Mobile now but I figured I'd ask here anyway: not looking to rip anybody off but, I don't use Verizon, never have, never will, and I don't even know anyone that uses them either so I'm not sure how to proceed. In the good old days you could do the 4-corner trick and bypass the need to activate the phone with Verizon but obviously nothing is that simple anymore.
Is there any way to get this device up and running with T-Mobile since it should be unlocked? I called Verizon and they said because I'm not the original owner/purchaser (neither is the guy I got it from, apparently he got it used himself earlier this year) they won't provide me whatever info or method is required to make it truly GSM unlocked as it's supposed to be so I'm stuck there.
It's not blacklisted, at least that Verizon would tell me, nor stolen from what I gather - I checked the ESN against several sites like Swappa and CheckESNFree and it shows green/clear/ready for activation and yet it's just not happening.
Any advice or suggestions or straight out method to get past that aspect and make it work properly with T-Mobile is greatly appreciated if anyone can help.
If I end up using it as a Wi-Fi only device, so be it, but that wasn't the idea when I got it - my mistake was not doing research ahead of time on this new device. I've owned several Droid MAXX/Ultra/Mini smartphones - all Verizon devices of course - and never had to deal with this activation BS, I just put my T-Mobile SIM card in them and rebooted and wham, always worked without problems.
I should have known it wouldn't be that simple anymore.
Click to expand...
Click to collapse
call Verizon, tell them the situation, worse case you waste some time on the phone
Sent from my sailfish using XDA Labs

Z5 Premium E6853 (Bell Mobility Canada)

So I am wondering if I am the only Canadian user that managed to buy a device with a locked bootloader? I contacted Sony Dev world and they stated there is no OFFICIAL way of unlocking this once it has been set to "BOOTLOADER UNLOCKABLE" = "NO". This is a dam piss off as I was a eager to build AOSP for this device and acquired it for this purpose.
So much for that plan!

frankbonatelli said:
So I am wondering if I am the only Canadian user that managed to buy a device with a locked bootloader? I contacted Sony Dev world and they stated there is no OFFICIAL way of unlocking this once it has been set to "BOOTLOADER UNLOCKABLE" = "NO". This is a dam piss off as I was a eager to build AOSP for this device and acquired it for this purpose.
So much for that plan!
Click to expand...
Click to collapse
---------
I have not heard from the general public yet on this and so far I have yet to find a way to unlock this boot loader. How is it I'm the only Bell user that found a locked boot loader? I've currently rolled back to 5.1.1 and am still unable to find a solution.
Odd if I'm the only Bell user in this situation.

I got one and it says same thing. Guess I have to sell the device. Very dissapointed.

Have you tried flashing "Customized XX" file via Flashtool instead and then try unlocking it? Usually carrier locked firmware prevents the device from being unlocked.

Yes I've gone all the way back to firmware it comes with pre release, as it would be for promotion to retailers. I've tried everything listed in xda nothing has changed the boot unlock to yes. Mine is now on the" for sale" list as I bought it specifically because Sony is supposedly selling open and unlocked devices for developer friendly experience. This is not the case with a Bell Mobility device.
Sent from my E6853 using Tapatalk

frankbonatelli said:
Yes I've gone all the way back to firmware it comes with pre release, as it would be for promotion to retailers. I've tried everything listed in xda nothing has changed the boot unlock to yes. Mine is now on the" for sale" list as I bought it specifically because Sony is supposedly selling open and unlocked devices for developer friendly experience. This is not the case with a Bell Mobility device.
Sent from my E6853 using Tapatalk
Click to expand...
Click to collapse
Changing firmware will never change your bootloader status...if it's locked to start with it's going to stay locked...
Carriers do special deals with oem's to have exclusivity or to sell their products and ask them to lock down the bootloader...
Don't buy from carriers to remedy to that problem...
Sony on the other hand sells its devices unlocked...!

I have the same infuriating problem - further to that, since a security update pm hide no longer works via adb. I was all ready for 7.1 as well and everything has just been a huge letdown.

Sorry fellas, you got the same un-rootable pile of Bell exclusive BS that I've been stuck with since last year.
Zero way to get root on these devices. Period.
Only suggestion is to toss an international ROM on it via Flashtool/Xperifirm and go from there - you'll at least get faster software patches/updates.

pattmyn said:
Sorry fellas, you got the same un-rootable pile of Bell exclusive BS that I've been stuck with since last year.
Zero way to get root on these devices. Period.
Only suggestion is to toss an international ROM on it via Flashtool/Xperifirm and go from there - you'll at least get faster software patches/updates.
Click to expand...
Click to collapse
Can we flash android 7 file which is available now straight?

i have this phone too.
this is my first and last Sony phone.
Also, the head phone Jack is weeeeeeeeak.

NEXUSg4 said:
Can we flash android 7 file which is available now straight?
Click to expand...
Click to collapse
Yes... I just did this myself to my Bell Z5 Premium

HappyDude69 said:
Yes... I just did this myself to my Bell Z5 Premium
Click to expand...
Click to collapse
Which country version you used and did you use xperifirm, I mean which app to use on PC? Thanks

NEXUSg4 said:
Which country version you used and did you use xperifirm, I mean which app to use on PC? Thanks
Click to expand...
Click to collapse
Used the one on the forums here..
https://forum.xda-developers.com/z5-premium/general/firmware-32-3-0-372-certified-android-7-t3537948
I used Sony Mobile Flasher by Androxyde v 0.9.23.2 (MUST be at least 0.9.23.x or you'll get an error)

HappyDude69 said:
Used the one on the forums here..
https://forum.xda-developers.com/z5-premium/general/firmware-32-3-0-372-certified-android-7-t3537948
I used Sony Mobile Flasher by Androxyde v 0.9.23.2 (MUST be at least 0.9.23.x or you'll get an error)
Click to expand...
Click to collapse
Thanks brother. I will flash as soon as I get home

NEXUSg4 said:
Thanks brother. I will flash as soon as I get home
Click to expand...
Click to collapse
Scratch that ... The firmware on that post is Russian even after selecting English on first boot. (there's still some stuff that shows in Russian)
https://depositfiles.com/files/yd5q2j22m <-- AU firmware posted on xperiafirmware.com
https://www.androidfilehost.com/?fid=529152257862696598 <-- Sony Mobile Flasher by Androxyde v0.9.23.1 ... takes a long time to download
Install the flashtool
http://www.flashtool.net/torrents/patches/windows/x10flasher.jar <-- Copy file to flashtool install folder (c:\flashtool) to upgrade to v0.9.23.2 (this step is not needed, but recommended)
Backup your phone and turn it off and don't plug it in to your computer yet
Now move the downloaded firmware to your c:\users\{username}\.flashtool\firmwares folder
Run the flashtool (exe in c:\flashtool)
Click on the Lightning bolt
Keep Flashmode selected and click OK
Click on the arrows in the left pane to expand the list until you get to 32.3.A.0.372 and click on that
In the Wipe section, check everything (best to do a clean install)
Click the Flash button
No just wait until a popup comes up telling you to plug the phone in and press the down volume button at the same time.
WAIT .... now it's flashing and takes a while.
Once done, the first boot take a while longer then normal.
You'd think that if you can flash a stock rom this way that you'd be able to flash a rom with a stock rooted kernel and use the flashtool to install root with out needing to unlock the bootloader .... But I'm sure people have already thought of this and for some reason or another, it didn't work.
Like the others on here... I'm not happy with not being able to root... Never buying a phone from the provider again :|

HappyDude69 said:
Scratch that ... The firmware on that post is Russian even after selecting English on first boot. (there's still some stuff that shows in Russian)
https://depositfiles.com/files/yd5q2j22m <-- AU firmware posted on xperiafirmware.com
https://www.androidfilehost.com/?fid=529152257862696598 <-- Sony Mobile Flasher by Androxyde v0.9.23.1 ... takes a long time to download
Install the flashtool
http://www.flashtool.net/torrents/patches/windows/x10flasher.jar <-- Copy file to flashtool install folder (c:\flashtool) to upgrade to v0.9.23.2 (this step is not needed, but recommended)
Backup your phone and turn it off and don't plug it in to your computer yet
Now move the downloaded firmware to your c:\users\{username}\.flashtool\firmwares folder
Run the flashtool (exe in c:\flashtool)
Click on the Lightning bolt
Keep Flashmode selected and click OK
Click on the arrows in the left pane to expand the list until you get to 32.3.A.0.372 and click on that
In the Wipe section, check everything (best to do a clean install)
Click the Flash button
No just wait until a popup comes up telling you to plug the phone in and press the down volume button at the same time.
WAIT .... now it's flashing and takes a while.
Once done, the first boot take a while longer then normal.
You'd think that if you can flash a stock rom this way that you'd be able to flash a rom with a stock rooted kernel and use the flashtool to install root with out needing to unlock the bootloader .... But I'm sure people have already thought of this and for some reason or another, it didn't work.
Like the others on here... I'm not happy with not being able to root... Never buying a phone from the provider again :|
Click to expand...
Click to collapse
Thanks! Yeah, my contract is up in August. I will only buy pixel or one plus phones going ahead. Cheers!

Unlocked Factory Image for Carrier locked STV100-1

Hello all,
Attached are modified factory roms that will flash an at&t or t-mobile phone to an unlocked phone. This means no more bloatware and in my case much better handoff between the lte bands.
These images reuse the carrier bootloader (I'm working on it) but everything else from the radio to the rom is from the unlocked priv.
Version: AAJ919
AT&T -> unlocked hybrid: https://www.androidfilehost.com/?fid=673368273298947044
T-Mobile -> unlocked hybrid: https://www.androidfilehost.com/?fid=457095661767153589
Directions: Unzip files. Hold power and volume down until phone reboots to fastboot. Launch flashall.bat. Follow instructions. This WILL delete your data so have a backup or don't I'm your boss. Wait. Done.
As usual I am not responsible for you bricking your phone. That being said even if the wrong file is flashed the phone gets stuck at the fastboot screen where you can flash the right file.
-Happy Modding

Can you provide more detailed instructions please

Im serious thats all there is to it.
What parts are you having problems with?

Didn't work for me, unfortunately. Phone promptly asked for SIM Pin.

zerocover said:
Hello all,
Attached are modified factory roms that will flash an at&t or t-mobile phone to an unlocked phone. This means no more bloatware and in my case much better handoff between the lte bands.
These images reuse the carrier bootloader (I'm working on it) but everything else from the radio to the rom is from the unlocked priv.
Version: AAJ919
AT&T -> unlocked hybrid: https://www.androidfilehost.com/?fid=673368273298947044
T-Mobile -> unlocked hybrid: https://www.androidfilehost.com/?fid=457095661767153589
Directions: Unzip files. Hold power and volume down until phone reboots to fastboot. Launch flashall.bat. Follow instructions. This WILL delete your data so have a backup or don't I'm your boss. Wait. Done.
As usual I am not responsible for you bricking your phone. That being said even if the wrong file is flashed the phone gets stuck at the fastboot screen where you can flash the right file.
-Happy Modding
Click to expand...
Click to collapse
Just out of curiosity, will this be possible to do on a Verizon model? Obviously not flashing the ones above but making a VZ version?
Sent from my Nexus 6 using XDA-Developers Legacy app

illitero said:
Didn't work for me, unfortunately. Phone promptly asked for SIM Pin.
Click to expand...
Click to collapse
This does not unlock your phone, this is an unlocked rom with no carrier bloatware.
You must already have an unlocked phone. If your phone is paid off call your carrier and ask for the pin.

ozzmanj1 said:
Just out of curiosity, will this be possible to do on a Verizon model? Obviously not flashing the ones above but making a VZ version?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
That one wont. This one might.
Disclaimer I dont have a vzw phone so can't test it, but pretty much I'm making the same modification I made to the others. It should work.
If you could give it a go and let me know.
If it doesn't work this file will get you back to where you should be

zerocover said:
That one wont. This one might.
Disclaimer I dont have a vzw phone so can't test it, but pretty much I'm making the same modification I made to the others. It should work.
If you could give it a go and let me know.
If it doesn't work this file will get you back to where you should be
Click to expand...
Click to collapse
I haven't bought a priv yet. But i came across a killer deal for a VZ model that's I'd be using on tmo. I'm going to be snagging it. But will test for sure and let you know. I am just trying to read up on the phone before ordering it on how to get rid of bloat and whatnot without root. Thank you very much for making the file.
Sent from my Nexus 6 using XDA-Developers Legacy app

zerocover said:
This does not unlock your phone, this is an unlocked rom with no carrier bloatware.
You must already have an unlocked phone. If your phone is paid off call your carrier and ask for the pin.
Click to expand...
Click to collapse
Haha, duh. I'm sorry. Very distracted, late night for me when I found this thread. plz4giv

zerocover said:
That one wont. This one might.
Disclaimer I dont have a vzw phone so can't test it, but pretty much I'm making the same modification I made to the others. It should work.
If you could give it a go and let me know.
If it doesn't work this file will get you back to where you should be
Click to expand...
Click to collapse
I tried it and it worked. However, once it boots it will install a software update which takes you back to the bloated VZW version. Perhaps there's a way to block that update?

dakota_96 said:
I tried it and it worked. However, once it boots it will install a software update which takes you back to the bloated VZW version. Perhaps there's a way to block that update?
Click to expand...
Click to collapse
Totally possible. If we had root just modify the host file and set the verizon server update ip to localhost. You should be able to install DNS66 and do something similar. This will take digging on your end to figure out what the update IP is though.

I have an ATT Priv, so if I flash this I'll get next time OTA from BlackBerry instead of ATT? Saw the one above with the Verizon update and went back to bloated version.

Reporting back in to verify that it worked flawlessly on both at&t and t-mobile variants I have. Now if only we could get root lol
Thank you so much for your effort

I have an ATT branded Priv which got unlocked from ATT directly and has successfully installed this ROM. It works perfectly without any ATT bloatwares, but this built is old and when I check for system update it shows my system is up to date. However the most recent built for unlocked factory image is AAL202 according to the blackberry official reload software website.
So does this ROM OTA updates via ATT server or directly from Blackberry server?

zerocover said:
Im serious thats all there is to it.
What parts are you having problems with?
Click to expand...
Click to collapse
dude what about the firmware version? and update status?

is there one available for the AAL230 update? and is the at&t version provided here applicable on my priv with AAL230 update installed?

zerocover said:
Hello all,
Attached are modified factory roms that will flash an at&t or t-mobile phone to an unlocked phone. This means no more bloatware and in my case much better handoff between the lte bands.
These images reuse the carrier bootloader (I'm working on it) but everything else from the radio to the rom is from the unlocked priv.
Version: AAJ919
AT&T -> unlocked hybrid: https://www.androidfilehost.com/?fid=673368273298947044
T-Mobile -> unlocked hybrid: https://www.androidfilehost.com/?fid=457095661767153589
Directions: Unzip files. Hold power and volume down until phone reboots to fastboot. Launch flashall.bat. Follow instructions. This WILL delete your data so have a backup or don't I'm your boss. Wait. Done.
As usual I am not responsible for you bricking your phone. That being said even if the wrong file is flashed the phone gets stuck at the fastboot screen where you can flash the right file.
-Happy Modding
Click to expand...
Click to collapse
Is this possible for the Verizon moto z play???

calistoz said:
is there one available for the AAL230 update? and is the at&t version provided here applicable on my priv with AAL230 update installed?
Click to expand...
Click to collapse
AT&T runs a newer version of android then the international. If you want stockish android with no carrier bloat go international.

jzamalot said:
Is this possible for the Verizon moto z play???
Click to expand...
Click to collapse
Send me a moto z play and we shall see. Otherwise sorry I can't test it.

With the very recent Verizon Priv update can the de-bloated image be updated?