Database Develop

[Q] Getting from really old firmware to JB?

As some of you may know my Razr i had mysteriously ended up stuck on 29004 retail.en.GB, which is apparently earlier than what GB phones shipped with (blame ebay).
I'm happy to unlock the bootloader etc but it would help if I knew exactly how to get from my current version to the latest JB release. I wasn't sure about flashing the upgrades as usual since none of them have a step to get from this version to any further.
Any help?:silly:
Thanks,
Addam.

addam360 said:
As some of you may know my Razr i had mysteriously ended up stuck on 29004 retail.en.GB, which is apparently earlier than what GB phones shipped with (blame ebay).
I'm happy to unlock the bootloader etc but it would help if I knew exactly how to get from my current version to the latest JB release. I wasn't sure about flashing the upgrades as usual since none of them have a step to get from this version to any further.
Any help?:silly:
Thanks,
Addam.
Click to expand...
Click to collapse
Just flash the fastboot files from Mattgrof, they are very safe to use and you don't have to worry about updating in a specific order.

arceles said:
Just flash the fastboot files from Mattgrof, they are very safe to use and you don't have to worry about updating in a specific order.
Click to expand...
Click to collapse
Thank you. It was mainly the order I was worried about.:good:

is .257 rootable?

Hi everyone. I tried finding info on my firmware, but somehow i couldn't find wether or not it is "rootable" it is 12.0.A.1.257, global version. Can someone confirm if it is indeed rootable. Thanks!

skojevac said:
Hi everyone. I tried finding info on my firmware, but somehow i couldn't find wether or not it is "rootable" it is 12.0.A.1.257, global version. Can someone confirm if it is indeed rootable. Thanks!
Click to expand...
Click to collapse
YES its rootable all you need to run the doomloard's event exploit from original dev section.. happy rooting

ok, I checked that thread and now have additional question for anyone who can have a time and knowledge to answer. obviously there is a new stock rom 12.0.A.2.245 for our bellowed SP. now, I have that older version 12.0.A.1.257 and though I tried updating device firmware I receive message that my phone is up to date. so I assumed this is probably due to some drug deal sony have with my operator ( the one the phone came from) and now for some reason sony would not let me update firmware (yet). so my question is next, actually there are several questions:
A. am I'm going to brick my phone if I manually download and update new firmware via flashtool regardless of sony saying my device is up to date?
B. Is this new firmware 12.0.A.2.245 so much better that is actually worth updating? (this should be A)
C. if i root this old firmware and perhaps install CW as well, and than update to the new one, am I'm going to loose both root and CW, or perhaps only CW after updating? or i will get to keep root and CW?
D. is it better to update and than root, or root and than update?
i hope this is not too much. thanks! :angel:
ps. i forgot to say, though my phone came from an operator, it is not sim locked and boot unlock status is YES

skojevac said:
ok, I checked that thread and now have additional question for anyone who can have a time and knowledge to answer. obviously there is a new stock rom 12.0.A.2.245 for our bellowed SP. now, I have that older version 12.0.A.1.257 and though I tried updating device firmware I receive message that my phone is up to date. so I assumed this is probably due to some drug deal sony have with my operator ( the one the phone came from) and now for some reason sony would not let me update firmware (yet). so my question is next, actually there are several questions:
A. am I'm going to brick my phone if I manually download and update new firmware via flashtool regardless of sony saying my device is up to date?
B. Is this new firmware 12.0.A.2.245 so much better that is actually worth updating? (this should be A)
C. if i root this old firmware and perhaps install CW as well, and than update to the new one, am I'm going to loose both root and CW, or perhaps only CW after updating? or i will get to keep root and CW?
D. is it better to update and than root, or root and than update?
i hope this is not too much. thanks! :angel:
ps. i forgot to say, though my phone came from an operator, it is not sim locked and boot unlock status is YES
Click to expand...
Click to collapse
A. no unless u r on unlocked bootloader that should brick our phone.
B. every firmware bring new advantages and disadvanteges..so i think u should upgrade it because camera has been improved! (low light photography)
C no u will loose both root and cwm
D both first update than root !! ROOT IS AWSM!!! it makes u feels that device is actually yours!!

thanks for a quick reply. so, I am going to update first and than do that "flash old kernel - root - flash new kernel" thing. and than backup the TA partition from here http://forum.xda-developers.com/showthread.php?t=2292598
I would like to save the BE and DRM keys 'cause I'm sure I'll unlock bootloader as well that entire process is what makes android so much better that sh**pple. like you said, you actually get to own your device. thanks again and thanks XDA!

Preparing for Lollipop! Please read before upgrading.

Hello Developers!
Here I will put forth instructions required for successful upgrade to lollipop. (These instruction are based on my own experience. I have been using Sony Xperia and Nexus phone for quite a while and I have flashed lot of roms. I may not have much experience in developing but definitely lot of experience in flashing! )
So, motorola has officially put up release notes here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/102639
So the questions that are bugging most people are:
1. When will the OTA be available in particular country?
2. Will I be able to smoothly able to upgrade and gain root access on Android L?
For first question: I really can't help you there. It depends on motorola. Android upgrades are rolled out region by region. So OTA will hit your phone when it is available in your region.
Second question:
To answer that, let us first consider few things.
New bootloader:
The very first note on release notes put out by Motorla says that: You cannot downgrade to a previous software version after installing this update. It means that new bootloader has been included in the update which does not allow downgrading.
ART runtime:
Android L uses new Android Runtime (ART). Some applications have not yet been optimized for ART and have problems with ART. To make sure the apps which you require daily work fine with ART, read the changlog given by its developer. If it has not yet been optimized then request the developer to optimize it for ART. If I am not wrong tools to develop apps using ART were released when Google released L preview. So you can expect many apps have been already optimized for ART.
When will the upgrade fail and when will it won't?
1. Locked/Unlocked bootloader:
If you have locked/unlocked bootloader but HAVE NOT CUSTOMIZED or HAVE NOT MESSED WITH RECOVERY AND KERNEL partition then don't worry. OTA upgrade will definitely hit your phone and you will be able to smoothly upgrade to L.
2. Modified kernel/recovery partition and root:
If you have rooted your moto g then it means you unlocked your bootloader, flashed a custom recovery and flashed the superuser binary. In this case you won't be able to upgrade to android L. According to few article I have read, you have to be completely stock before update. Completely as in you shold have never rooted your phone or flashed a custom kernel. Even if you have unrooted after rooting or flashed a stock kernel/recovery after flashing custom kernel/recovery is NOT allowed for Android L upgrade.
3. Unstable internet connection while downloading OTA.
Unstable connection might corrupt the OTA upgrade file. Make sure you have stable internet connection while downloading OTA.
Considering all these there you are in one of the following scenarios:
1. Locked/unlocked bootloader with no customizations to any partitions:
Don't worry. You won't face any problems with OTA upgrade. Just make sure all your apps work fine on ART.
2. Unlocked bootloader with stock/custom rom and sotck/custom kernel with root or unrooted after root:
You will need to flash official kitkat firmware. Official firmware images for Moto G 2014 are located here: http://sbf.droid-developers.org/phone.php?device=36
Then you can upgrade via OTA.
3. Unlocked bootlaoder, root but do not want to lose root priviliges:
Then you will need to wait till developers modify new custom roms based on android L. Then you can flash those by following their instructions. To root stock android L build, a custom kernel is required and also according to chainfire the system.img will be need to be patched. So it is not possible to root sotck android L unless motorola release kernel sources and some developer pathces the system.img.
I have no experience in handling/using/modifying carrier locked phones. So I cannot help you with those.
I WOULD HIGHLY RECOMMEND NOT TO FLASH STOCK/CUSTOM LOLLIPOP ROM OF DIFFERENT MOTO G VARIANT.
Enjoy and happy flashing!

Nice info, thanks!

Also: you need 850 MB of available space or the OTA update will refuse to download.

Thanks man!
It the only thing you did is unlock boot loader and no more... And do the ota update, might boot loader stay unlocked?

El_Froz said:
Thanks man!
It the only thing you did is unlock boot loader and no more... And do the ota update, might boot loader stay unlocked?
Click to expand...
Click to collapse
Yes it will stay unlocked.

Any disadvantage in unlocking boot loader other than voiding the warranty? We will still get future OTA updates?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.

Trekker56 said:
Any disadvantage in unlocking boot loader other than voiding the warranty? We will still get future OTA updates?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
Click to expand...
Click to collapse
Yes. I have confirmed this by chatting with motorola assistant.

AD9295 said:
Yes. I have confirmed this by chatting with motorola assistant.
Click to expand...
Click to collapse
I know about the warranty.
What about future OTA updates?

Trekker56 said:
I know about the warranty.
What about future OTA updates?
Click to expand...
Click to collapse
I said "YES"! You will get the future OTA updates. Make sure that you don't mess with the partitions in any way. I have confirmed this by chatting with motorola assistant.

AD9295 said:
I said "YES"! You will get the future OTA updates. Make sure that you don't mess with the partitions in any way. I have confirmed this by chatting with motorola assistant.
Click to expand...
Click to collapse
Thanks. Good to know.

-------------------------

axl409 said:
Hey, this seems the right thread to ask.
I'm not so hyped about lollipop (doesn't see all these big changes), but sooner or later I will upgrade of course.
My plan on upgrade is when some custom rom with lollipop will come out.
So my questions are:
-will I be able to flash a lollipop rom from my rooted Moto g with philz recovery and stock/custom kernel?
-do I have to upgrade (somehow) the bootloader or the recovery? And if I have, do I need to return to stock KitKat and then upgrade to official lollipop and then unlock bootloader again and flash recovery again?
Thanks for your answers!
Click to expand...
Click to collapse
Well waiting for lollipop custom rom is actually the best solution yet!
You need following things to upgrade to lollipop:
New bootloader
Recovery compatible with that bootloader
Kernel comatible with lollipop rom which you want to flash
New baseband (radio)
And system and data partition image
When a developer creates a flashable zip, it generally includes:
System and data partition image
Kernel
So before flashing that lollipop rom. You just need to flash
New bootloader
Recovery
Baseband(radio)
Then from recovery you can flash the zip file.
Your bootloader needs to be unlocked to do all this.
Only problem is, it takes time for motorola to release factory images like google releases for nexus phones.
So you will need to wait till some developer captures OTA, extract all the partition images and share it online. (Make sure the uploaded partition images are of the same moto g variant which you have)

axl409 said:
Hey, this seems the right thread to ask.
I'm not so hyped about lollipop (doesn't see all these big changes), but sooner or later I will upgrade of course.
My plan on upgrade is when some custom rom with lollipop will come out.
So my questions are:
-will I be able to flash a lollipop rom from my rooted Moto g with philz recovery and stock/custom kernel?
-do I have to upgrade (somehow) the bootloader or the recovery? And if I have, do I need to return to stock KitKat and then upgrade to official lollipop and then unlock bootloader again and flash recovery again?
Thanks for your answers!
Click to expand...
Click to collapse
Actually it is easier to flash official kitkat images and update to lollipop with ota update. Then you can flash any custom lollipop rom just by following rom developer's instruction. It will be easier.

Thanks for this thread Bro.

-------------------------

axl409 said:
Thanks a lot @AD9295!
So, I was searching around for returning stock, because you said in the end I'll have to and also because I want to be prepared in time!
I found the thread "restore to stock" and in the end, there's written this at q18 (I made a screenshot).
It's good to do this even if I have philz recovery? Will I get the update or I need to flash also the stock recovery? I know there's written, but it's cool? Or maybe something could go wrong?
Click to expand...
Click to collapse
If you are using rooted custom rom:
Flash the complete official kitkat image. images are located here:
http://sbf.droid-developers.org/phone.php?device=36
If you are just using rooted stock rom then follow the instruction in response to that q18. You do need to flash stock recovery as mentioned there. That's what is meant by returning to "stock".

-------------------------

axl409 said:
No I'm just rooted, and of course have installed some apps that need root.
So in order to restore stock I should:
- uninstall the root apps
- do the q18 (but where I found the stock recovery image?)
- waiting for the ota lollipop upgrade that will update all (bootloader, recovery, radio, system and data).
Am I correct?
And then from lollipop do again root and install future lollipop compatible recovery.
Click to expand...
Click to collapse
Yes you are correct. the zip files located here: http://sbf.droid-developers.org/phone.php?device=36 contain all the official .img files. You can download it from there (I understand file size is large but it's worth downloading coz you will always be able to return to stock even if you mess up your phone pretty badly ) or you can ask on forum

-------------------------

AD9295 said:
I said "YES"! You will get the future OTA updates. Make sure that you don't mess with the partitions in any way. I have confirmed this by chatting with motorola assistant.
Click to expand...
Click to collapse
What benefit gives just unlocking and not rooting?

need to revert to 5.0 or 5.0.1 not sure how

I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance

pokedroid said:
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
Click to expand...
Click to collapse
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.

You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?

ac3theone said:
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
Click to expand...
Click to collapse
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
rootSU said:
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
Click to expand...
Click to collapse
I just installed it as an update.zip using adb. No unlock required.

pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
FYI, AT&T have no control over the update process. The update comes directly from Google, for all carriers. As long as you didn't install M or I, you're fine. There is nothing that AT&T could do to prevent anyone getting the update. Except maybe sending a memo out to a staff saying "you'll receive an update from Google. Please, please, please don't accept it"

pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.

ac3theone said:
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
Click to expand...
Click to collapse
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung

rootSU said:
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
Click to expand...
Click to collapse
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?

ac3theone said:
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
Click to expand...
Click to collapse
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0

rootSU said:
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
Click to expand...
Click to collapse
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*

pokedroid said:
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
Click to expand...
Click to collapse
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,

rootSU said:
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
Click to expand...
Click to collapse
Oh, I was thinking the boot loader status would show "relocked" when in fastboot

Help on XT1254 OTA

Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!

mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
me too
i updated to 6.0.1 via recovery with update.zip. This process had successfully done and re-updated via recovery again (still the same update.zip) and i factory reset tin recovery so it stuck screen 'erasing...'They could not enter system, except bootloader and recovery vesersion (6.0.1),can not into apply update sdcard , it turn e:\unkown volum path [sdcard]... and I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?

longbin said:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Click to expand...
Click to collapse
1. I have never heard of anyone selling bootloader unlock keys for the XT1254. If you want to unlock your bootloader, Sunshine is your only option, and as of right now it will only work on lollipop builds. If your phone is on marshmallow, Sunshine will not work. If your phone cannot boot, it won't work no matter what build you're on.
2. If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.

mr_5kool said:
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
unlock the bootloader and install TWRP BEFORE doing any updates, while still on Lollipop. That is the only safe, logical answer. An unlocked bootloader -- especially with custom recovery -- will let you do lot of things and is more forgiving of mistakes than a locked bootloader.
We keep telling people that and they won't believe us.
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
TheSt33v said:
If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
Click to expand...
Click to collapse
Right. Several people who didn't like Lollipop but preferred the original Kitkat "speed", "battery life" or whatever successfully downgraded back to 4.4.4 -- but only AFTER they unlocked their bootloader. Even then you have to make sure you don't flash the old gpt.bin in ADB, but downgrading is possible with an UNlocked bootloader.
Even when flashing XT1250 firmware over XT1254 or vice versa, it CAN be done with a locked bootloader, but if you mess something up you are in big trouble. UNlocked bootloader? Just do it again, correcting your mistake the next time.
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
TheSt33v said:
1. I have never heard of anyone selling bootloader unlock keys for the XT1254.
Click to expand...
Click to collapse
There was a guy on some website who was selling some Verizon keys a long time ago, known as "the Chinaman". He disappeared.
China Middleman Back??
http://forum.xda-developers.com/moto-x/moto-x-qa/china-middleman-t2751177
dschill said:
Well the china man added me back on skype today. And sadly said that he can no longer get the codes and refunded my 45$ via paypal.
Heres a little bit of the skype transcipt
[12:08:22 PM] live:dschillinrecovery: k i just got the refund
[12:08:25 PM] live:dschillinrecovery: so you cant get the code any more?
[12:12:41 PM] VIP-UNLOCK: No time to deal with the accident, we default to a refund
[12:13:08 PM] VIP-UNLOCK: Sorry, goodbye
[12:13:32 PM] live:dschillinrecovery: Its alright. Thanks for the refund though. Let me know if you can ever get the codes again
Guess the best we can do for now is to wait for jcase and sunshine to release the 3.0 version.
Click to expand...
Click to collapse
and another thread discussing same guy:
http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651
The process seems to involve sending approximately $45 to a Chinese middle-man via eBay and another website, along with your IMEI and cell phone number, and you will receive an unlock code.
It seems like this is all one guy handling this process. Turnaround time seems to be 24-48 hours beginning to end.
Click to expand...
Click to collapse
Theory was that someone with access to Motorola's engineering software had a side business going. You know they unlock their bootloaders for testing and such. Someone with access to that software could make some money if they made sure they covered their tracks.
Also people who visited China were able to buy unlocked bootloader Droid Turbos well before Sunshine was released. One guy posted in this forum. In that case, it was probably pilfering some phones from the factory -- but again with unlocked bootloaders. So, there is some software out there somewhere, just kept under wraps.

Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.

TheSt33v said:
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
Click to expand...
Click to collapse
I updated my post to include XDA links. I can't find any examples of Droid Turbos being unlocked via this eBay "purchase" only other Verizon phones, but there are the legitimate reports of unlocked Droid Turbos for sale in China in the year prior to Sunshine being released November 2015. One guy even posted on here because he was trying to install CM12.1 at the time on his BOOTLOADER UNLOCKED Droid Turbo he had purchased in China.
Note the Chinese middleman guy was charging $45 for bootloader unlock at the time, and Sunshine only charges $25.

xml flash file is the last solution =))

@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250

Doesn anybody know how much does usually takes for Verzion ( or whoever does it ) to release xml sbf firmware file? And do they release every? I need latest MCG24 or at least system file (s) is enough.
I have everything except system files, if anybody can provide system files or knows hot to convert ones from ota , I can make complete fastboot xml zip.
EDIT: System from OTA is not enough. If somebody can provide system / backup from MCG24 phone, I might be able to make it.

mr_5kool said:
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Click to expand...
Click to collapse
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.

ChazzMatt said:
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
Click to expand...
Click to collapse
Can you give little more info on this. Changed cid? Unlocked bootloader? Maybe we can use x1250 xml fastboot files until they release Marshmallow fastboot. I need one for backup , I know I'll brick the phone sooner or later , as guys above did lol..

Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
Flashed the Verizon radio and 5.1 FW (firmware)
The only problem I have right now is upload speeds are super slow.
gonna try wiping the radio and re-writing the radio
Click to expand...
Click to collapse
I then asked him a couple of questions and he answered this:
Yes I flashed the Verizon Radio to the device
not the bootloader image, for obvious reasons
I wanted 5.1, so I didn't test until I had the VZW 5.1 with my SIM card
I'm going to try an reflash soon, and then get a new SIM just in case
I hope Verizon doesn't give me any trouble getting a new SIM at my local store
Click to expand...
Click to collapse
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.

ChazzMatt said:
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
I then asked him a couple of questions and he answered this:
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
Click to expand...
Click to collapse
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..

Ej?iSixo said:
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Click to expand...
Click to collapse
That's been done, too. I didn't know that was the question.
One guy didn't want Verizon bloatware and his solution was to flash the "pure" Motorola firmware from the XT1250 over his XT1254.
Yes, he had unlocked bootloader and could have just uninstalled the bloatware. I'm not saying it was logical, I'm just telling you what he did.
So there's no question these two phones are exactly the same device, with exactly the same FCC ID.
The issue is the XT1250/XT1254 being flashed needs to the other needs an unlocked bootloader. And you can't downgrade (gpt.bin) when you flash.
So, for the purposes of this thread that information doesn't help you, if your XT1254 bootloader isn't unlocked.

mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
Conclusion: Wait for the 6.0.1 flash file (xml) then flash via RSD.
Thanks guys!!!!
Click to expand...
Click to collapse
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571