Related
hi guys..i owning an atrix 2.3.4 which asia retail version. i try to find it at firmware thread at development there but most of that is 2.2.2. so is that anyway or any place i can find it ? the system info as below
System Version: 45.31.0.MB860.AsiaRetail.en.03
Android Version: 2.3.4
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0-133_38
Kernel Version: 2.6.32.9 [email protected]#3
APflex Version:
GAS_ASIA_USAOLYGBSEARET_P011
GAS_ASIA_USAOLYGBSEARET_A003
GAS_ASIA_USAOLYEMSEARET_M001
Build Number: 4.5.2A-74_OLE-31
http://www.filefactory.com/f/89f588286a560e39/
hmm..i just see the me retail only..is this the full sbf?
Am also from asia- manila.. im using an at&t us version atrix. Id recommend a cwm flashable firmware instead of an sbf based firmware. Running on cm7 nightly
Sent from my MB860
chonkit said:
hmm..i just see the me retail only..is this the full sbf?
Click to expand...
Click to collapse
There's a SEA-Retail sbf in there. Look for the one that ends with "-searet". And yes, it's the full stock sbf.
As has been warned many times in this forum, if you don't know what you're doing, DO NOT flash an sbf. It might brick your phone. Although 4.5.2A is the latest version for SEA (which means it should be safe - bricking only occurs when downgrading), I'd still recommend caution.
i c..so after i unlocked and flash custom rom, can i use this sbf to back to stock and perform ota? or after unlocked bl, i could not use ota if it is available..
Sent from my MB860 using XDA
You can use that to go back to stock, but only if you were on the same/earlier build. Do not use sbf to downgrade.
hmm..ok..mean that if i flash custom rom from 4.5.2A version of 2.3.4, if wan to go back stock, i only can flash this 4.5.2A sbf to get back to stock rite?
bigboy_r said:
Am also from asia- manila.. im using an at&t us version atrix. Id recommend a cwm flashable firmware instead of an sbf based firmware. Running on cm7 nightly
Sent from my MB860
Click to expand...
Click to collapse
i c..but i using international asia version..
chonkit said:
hmm..ok..mean that if i flash custom rom from 4.5.2A version of 2.3.4, if wan to go back stock, i only can flash this 4.5.2A sbf to get back to stock rite?
Click to expand...
Click to collapse
Yes.
that's nice..thank for the answer..by the way, can I still update to official ics through ota update if Motorola release it using this sbf? it won't brick my device right?
You *should* be able to update from stock ROM, but since official ICS isn't out yet, we still don't know if Moto changes anything in their update policy. They could in theory prevent the updates to be installed on unlocked devices.
In any case, when the official update hits, I'll bet the devs are gonna be all over it anyway...
ok..maybe i will just unlocked it and use because i not sure when is ics will release for international version..thanks for help ya..
ICS has only been confirmed for US (AT&T) devices. Other regions are still "under evaluation". Seeing how the US version is currently on 2.3.6 and other regions on 2.3.4, I wouldn't bet on Motorola releasing ICS internationally unless there's a huge pressure from users like with Milestone's Froyo update.
so there might had chance that international version might not get the ics upgrade?
Yes. Looking at Motorola's update history, there's a chance that the international version won't get ICS (at least officially).
i see..but motorola update schedule listed the asia retail as ics upgrade in planing. so it might fail during the process?
From Motorola's Upgrade News:
PHASE 1 – EVALUATION & PLANNING: During this phase, we evaluate the benefits, technical issues and user experience of an upgrade. Generally, we are not able to provide release dates in this stage. There are also some cases in which we can state that an upgrade will happen but are not able to provide a release date. Please note that some products that enter the Evaluation and Planning phase may not complete the upgrade cycle.
wow..seriously speechless..but then never mind. if its fail, I still can grab custom rom that based on at&t ics right?
Yes. I do hope we get an official ICS release, though.
As a last resort i have decided to downgrade my razxr m to earlier ics version
my current status is :
android
4.1.2
baseband :
SM_BP_1-1031.027.32.81P
build
9.8.1Q-66
build date
fri mar 22
can anyone help me how to do it as i want my phone to be used in India on gsm networks , which its is not working on right now
regards
is there no way to downgrade it ???
lord dredd said:
is there no way to downgrade it ???
Click to expand...
Click to collapse
have you tried flashing a 4.1.1 ROM? i think someone posted a TWRP-flashable file for Energy (which is 4.1.1).
BTW, 4.1.1 is JB, not ICS.
jco23 said:
have you tried flashing a 4.1.1 ROM? i think someone posted a TWRP-flashable file for Energy (which is 4.1.1).
BTW, 4.1.1 is JB, not ICS.
Click to expand...
Click to collapse
Thanks for the reply mate
As there was no help up until your reply on this matter , i tried to take it upon me to find a way , so i in the end was able to infact flash the ICS stock via rsd lite
but no success even that was fruitless as GSM radio was still locked in that too
so now after about a full month or so i can say i have tried each and every option and this phone is locked as far as gsm is concerned ,
ALL THE NEWER VERSIONS OF DROID RAZR M XT907 ARE FACTORY LOCKED NOW , they cant be used with gsm ooperators outside of th US , and may be inside too.
lord dredd said:
Thanks for the reply mate
As there was no help up until your reply on this matter , i tried to take it upon me to find a way , so i in the end was able to infact flash the ICS stock via rsd lite
but no success even that was fruitless as GSM radio was still locked in that too
so now after about a full month or so i can say i have tried each and every option and this phone is locked as far as gsm is concerned ,
ALL THE NEWER VERSIONS OF DROID RAZR M XT907 ARE FACTORY LOCKED NOW , they cant be used with gsm ooperators outside of th US , and may be inside too.
Click to expand...
Click to collapse
I've seen on some 4.2.2 ROM threads that there is a GSM fix. have you tried that yet?
jco23 said:
I've seen on some 4.2.2 ROM threads that there is a GSM fix. have you tried that yet?
Click to expand...
Click to collapse
haven't tried though , but the gsm fix in them is actually for those roms where switching to gsm options isnt there by default , it just adds a gsm option in the network settings
i alreday have that in mine stock , the issue it this damn thing just doesnt latch onto any GSM network
This post/thread is to summarize where to find full SBF files, leaks, etc for the Moto X (2013 or First Generation).
REMEMBER... Always flash the same ROM/SBF or Newer to your phone. NEVER attempt to downgrade your rom!!! for more info, see DOWNGRADING
Motorola posts their complete STOCK "Recovery Images" (aka SBF files) for the GSM and Verizon Developer Edition X at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
If you have the Retail and/or Moto Maker XT1053 (aka Unlocked ships with T-Mobile SIM, or Unlocked Ships with Net10 SIM), you can also use the GSM Developer Edition (XT1053) roms from Moto's site.
If you have the Retail and/or Moto Maker Verizon X (XT1060), you can also use the Verizon Developer Edition (XT1060) roms from Moto's site.
There might be a delay in Moto making an SBF available.
For other models of X, I know of 3 sites for "leaks" which contain the SBF files for nearly every model of X (2013). You may need to check EACH site to find the particular rom you are looking for. NOTE: None of the following sites are owned, operated, or sponsored by Motorola. They may be down or offline at any time, without warning.
http://sbf.droid-developers.org/ <- DEAD when checking on 8/22/15
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 <- seems to have the most 4.4.4 roms
http://motofirmware.com/files/category/9-ghost/ <- DEAD when checking on 8/22/15 once there, look under the GHOST folder. (as of 11/9/2014, its format and access has changed)
http://motofirmware.center/files/ <- Select Moto X 1St Generation from the list along the right side of the page
Are there any others?
@dagoban has linked a few other in Post #17 of this thread..
dagoban said:
..Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Click to expand...
Click to collapse
See Post #17 for more direct links.
As 5.1 SBF files become available, they are being collected and curated in this thread -> [OFFICIAL] Collection Full Firmwares (FXZ/SBF) Lollipop 5.1
FAQ:
1. How do I know which file to download?
- If you are NOT running a 3rd Party or Custom ROM... take a look on your phone, under App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until you find the SBF that matches. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
2. Where do all these SBF files come from?
As mentioned earlier, Moto does make the Dev Edition "recovery images" (in SBF format) available on their web site. For all others, the only way for us to get firmware files, is for a copy to be LEAKED to us.. The "Leaked" firmwares are files that are basically "stolen" by a Motorola or wireless carrier employee, who then posts the file on the internet for us... So we can't always count on this ever happening, nor can we have any expectations that a particular firmware will actually get leaked, or when it will be leaked.
There is some talk about using Motorla Device Manager (MDM) app to upgrade your phone, and how during the update process, the app downloads the full FXZ (another term for SBF) to your PC, so it could be copied/saved to another folder for use later. I have not done this with MDM.
EDIT: As of 12/12/14, Only the filefactory.com link is working. The others appear to be down. I don't know the owners of the sites, so I can't say if they will return or not.
EDIT2: As of 1/2/15, motofirmware.com seems to be back up, but sbf.droid-developers.org appears to be gone.
Great info! ??
SBF is my first choice, but when I needed the 4.4.4 retail firmware not found it in SBF, I had to turn to Google and found it.
FTP of Moto Firmware is empty, but the File Factory folder has many versions! Very cool.
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
x000x said:
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
Click to expand...
Click to collapse
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
edit: problem resolved. see my findings: http://forum.xda-developers.com/showpost.php?p=57122184&postcount=635
Thanks Kidjoe
x000x said:
well issue was I was rooted with twrp and silly me I tried to do the ota update. so now it won't get past the warning about unlocked bootloader. I read after the fact that you needed to revert back to stock before taking ota. mine is 30.71, but the other issue is I cannot find that firmware anywhere. my only option in regards to firmware is to use 4.4.2 that I found. I've posted the question here http://forum.xda-developers.com/showthread.php?t=2542219&page=123
Click to expand...
Click to collapse
BUT if you tried to take the OTA while TWRP was on your phone, just boot into fastboot mode on the phone, and do a mfastboot erase cache will get you out of the bootloop. Then you can flash stock recovery on there, take the ota.
Or you can just flash the 4.4.2 or 4.4.4 for your phone, when completed, flash TWRP on there, reboot hte phone to bootloader, enter Recovery/TWRP and root.
Yes, You can flash a higher/newer version without problems. You just can't flash older once 4.4.2 or higher has been flashed to your phone. (the only time its safe to flash older was when you had 4.4 on your phone, and you were Following the SlapMyMoto process to downgrade to 4.2.2. W/Camera Update as part of the process).
Thank you for this!
KidJoe said:
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
Click to expand...
Click to collapse
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
scryan said:
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
U can always flash newer images without a problem. It's flashing older images (downgrading) that's a problem.
scryan said:
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
The OTA updates are incremental, so you need to be on a certain level to take them. (to take 4.4.4 you need to be on 4.4.2, to take 4.4.2 you need to be on 4.4, etc)
Full SBF/FXZ files are complete roms. They are not incremental like the OTA Updates are. When flashing a FULL SBF/FXZ you can just flash it, so long as its the same version OR newer than what is on your phone, with no need to "step up." In other words, if you have 4.4 on your phone, you can flash directly to 4.4.4 using the full 4.4.4 SBF, without having to flash 4.4.2 on there first.
The risks to keep in mind would be, just like any update...
If you have a locked bootloader, the vulnerabilities exploited to root and disable write protection might be patched in the newer roms, that means you might not be able to root, or the processes may change for the newer rom. However, with an unlocked bootloader, there is no issue rooting and disabling write protection (lollipop is yet to be confirmed).
In either case, since you can't safely downgrade, if you find bugs, other issues (battery life, reception, etc), or there is something you don't like about the rom, you're stuck, since you can't safely downgrade.
THANK YOU SO MUCH every damn site I went to posted a link to a long dead server LIFE SAVER YOU ARE....
Method to go STOCK.
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
the_fiasco said:
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I suggest you use this : perfect compatible stock firmware for xt1052 asia retail first gen moto x. : http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip pl. check it with someone else just in case if I'm wrong. pm me if you have any problems
Hey, thanks for replying!
Yeah, I found this stock recovery a while ago and downloaded it and now back to stock 4.4.4. Thanks a lot!
Sent from my Moto X using XDA Free mobile app
@KidJoe since filefactory is really slow, I searched for some alternatives and found some good ones, maybe you could add it to your 1st post?
Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Some other alternatives:
XT1053 4.4.2; 4.4.3; 4.4.4 (downloading from mega server (fast!)), thx to OP (http://www.grupoandroid.com/topic/110743-aporte-firmware-t-mobile-retail-442/):
TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml.zip: https://mega.co.nz/#!7RJygbQI!Sbx-bGRV8NbRsqLKS-d33nM_SEgY81czr8rye2ROYb0
TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml.zip: https://mega.co.nz/#!HQ4l2JIT!LD1gf8m2GxBou3NDFD8lzuxSi2OCn37X7Vhbe-hjNqc
TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz: https://mega.co.nz/#!zIJhlSCS!o9B7xvRSJ9gTCdTYjXdmVActEmdWRBvhIVjs8JUHI8Q
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/M2H9LMFJbYiag
from mega (fast!):http://www.mega.co.nz/#!jZgjECZT!sG0-9Vqngms551gwv9PfejY1mw_5QCL8Pg48KTVx4m0
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/KLmLR43SbYiaX
XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/hDEHw2O-bYiae
For Brazilians user's
http://www.motoforum.com.br/topic/4...oto-g-2014-moto-e-moto-maxx-nexus-6-moto-360/
Does anyone know of a link that contains the Rogers 4.4.4 file? I need it to update to 5.1.
I have tried the filefactory link but after the countdown, the file is unavailable. I haven't seen any other links for it.
Thanks
I have the same problem. I've looked everywhere and cannot find the rogers 4.4.4 file.
If anyone has it download, could you please share with us.
Alternatively, would i be able to Flash XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml.zip since the build versions are the same?
I only need the 4.4.4 in order to install the Lolipop update.
Thanks
Hey folks, I created this thread just to separate this version of 4.4.4 which can't update to Lollipop using the current OTA file outhere. So I ask if someone which have this version receive the update to try to capture and share with the people.
Currently the only way to downgrade as I understand is downgrade the firmware to the KXB21.85.23 but for this you need to unlock bootloader, which will make you loose your warranty. So for people like me stuck with this version please you this thread to don't generate more doubts in the other threads. If you have other ways to downgrade without unlocking bootloader please share!
Best regards!:good:
same here stuck at .27
Is there any overview which software Version Runs on which xt106x hardwareversion and on which Country Variant?
There were that much discussions of Different version combinations that i am probably not the only one who has lost the overview..?
This KitKat version was never an official OTA. So you can't upgrade from this version. Officialy you can't have it. Downgrade to .23 and you'll be fine!
Edit:
About loosing your warranty: you've installed the .27 update with een unlocked bootloader. So your warranty was already void. Relocking your bootloader brought it to 'Status 2' meaning you had it unlocked in the past. Never unlocked is 'status 0'. You never will get your warranty back by relocking it.
I tried it not working
smitharro said:
This KitKat version was never an official OTA. So you can't upgrade from this version. Officialy you can't have it. Downgrade to .23 and you'll be fine!
Edit:
About loosing your warranty: you've installed the .27 update with een unlocked bootloader. So your warranty was already void. Relocking your bootloader brought it to 'Status 2' meaning you had it unlocked in the past. Never unlocked is 'status 0'. You never will get your warranty back by relocking it.
Click to expand...
Click to collapse
impossible to downgrade to 0.23 without unlocking your bootloader
adel pro said:
impossible to downgrade to 0.23 without unlocking your bootloader
Click to expand...
Click to collapse
That's what I said! It was impossible to instal .27 without a locked bootloader, downgrading with a locked bootloader is also impossible!
smitharro said:
That's what I said! It was impossible to instal .27 without a locked bootloader, downgrading with a locked bootloader is also impossible!
Click to expand...
Click to collapse
so we might recive the taste of official lollipop or not on .27 via ota on locked BL?? @smitharro
smitharro said:
This KitKat version was never an official OTA. So you can't upgrade from this version. Officialy you can't have it. Downgrade to .23 and you'll be fine!
Edit:
About loosing your warranty: you've installed the .27 update with een unlocked bootloader. So your warranty was already void. Relocking your bootloader brought it to 'Status 2' meaning you had it unlocked in the past. Never unlocked is 'status 0'. You never will get your warranty back by relocking it.
Click to expand...
Click to collapse
I bought a motog 1 month ago, i'm running stock, and the version that came instaled was in fact 21.11.27.titan_retaildsds.retaildsdsall.en.03reteu, KX21.85-27, it may not have been an ota but it is at least official, it came factory instaled. So, you are wrong...
fastmugen88 said:
I bought a motog 1 month ago, i'm running stock, and the version that came instaled was in fact 21.11.27.titan_retaildsds.retaildsdsall.en.03reteu, KX21.85-27, it may not have been an ota but it is at least official, it came factory instaled. So, you are wrong...
Click to expand...
Click to collapse
OK, possible... Where did you buy your phone and, more important, what is the bootloader status? If the bootloader status is 0, then you're right and I am wrong. If it's 2, then your bootloader has been unlocked in the past!
smitharro said:
OK, possible... Where did you buy your phone and, more important, what is the bootloader status? If the bootloader status is 0, then you're right and I am wrong. If it's 2, then your bootloader has been unlocked in the past!
Click to expand...
Click to collapse
Bought new from Fnac in Portugal on Dec. the 16th. How do I check the bootloader status?
Please note that i'm not a devoloper, so I don't know this things deeply, but I do know what is an OTA, factory images, root...etc, meaning I Know that I haven't unlocked or rooted the smartphone.... that's why I'm telling that .27 is official, probably came preinstaled in the latest batch for EMEA region.
fastmugen88 said:
Bought new from Fnac in Portugal on Dec. the 16th. How do I check the bootloader status?
Please note that i'm not a devoloper, so I don't know this things deeply, but I do know what is an OTA, factory images, root...etc, meaning I Know that I haven't unlocked or rooted the smartphone.... that's why I'm telling that .27 is official, probably came preinstaled in the latest batch for EMEA region.
Click to expand...
Click to collapse
1 - Shut down phone completely
2 - Press Vol down + power for 5 seconds
3 - Release both keys and device will boot up to fastboot mode where you can see this.
@smitharro
Got my device last week.
On .27
Device is LOCKED. Status Code: 0
pakatus said:
1 - Shut down phone completely
2 - Press Vol down + power for 5 seconds
3 - Release both keys and device will boot up to fastboot mode where you can see this.
@smitharro
Got my device last week.
On .27
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
Okay, my bad then! I was wrongly informed! So just wait and the lollipop OTA should be released in a while!
Send from my XT1068 using Tapatalk.
The main difference in this version is coming with more languages support, as I said we are stuck in this version and of course I'm not thinking in unlocking the bootloader because in case of something goes wrong in the phone I could have the luck of Amazon trade for another new or sent to Motorola and there I'am screwed ...
If someone Find anyway possible without have to unlock the bootloader fire it out!
same here...i guess we have to wait.
Actually 27 is an incremental update. Motorola has updated Moto G 2014 software page with the details.
Google launcher was update and some minor improvements.
My one was bought 2 weeks ago in Poland.
And 27 was preinstalled.
well, im in the same boat,
was using the xt 1063 version lollipop then migrated back to 4.4 stock
stuck on .24 titan retbr ds retbr en br oi br
So with the news of today saying will roll out the new update for lollipop any one if have this version and bootloader unlocked can make a favor of post here the file for this Version?
keb00 said:
So with the news of today saying will roll out the new update for lollipop any one if have this version and bootloader unlocked can make a favor of post here the file for this Version?
Click to expand...
Click to collapse
Humm... i think the official OVA that was released today it's only for version .23 (Brazil, India and US) and probably the same version of soak tests, but we will see
24/01 and still no OTA update for my xt1068 in France (phone bought on amazon, having a reteu firmware)
@oiej47 same here stuck at .27
Ok, I know what you're thinking, 5.1 thread, again???? No it's not.
This is for Non Droid Turbo devices, non US Verizon. So Moto Maxx, Latin America devices such as the XT1225
I am currently on official 4.4.4 and I have already opt in for the Moto Feedback Network, so I should get the Soak test update when available.
So let's keep this threat updated about 5.1 updates for our international Droid Turbo variants.
And by the way here are the DROID TURBO - Android™ 5.1 Lollipop - Release Notes
Kiwironic said:
Ok, I know what you're thinking, 5.1 thread, again???? No it's not.
This is for Non Droid Turbo devices, non US Verizon. So Moto Maxx, Latin America devices such as the XT1225
I am currently on official 4.4.4 and I have already opt in for the Moto Feedback Network, so I should get the Soak test update when available.
So let's keep this threat updated about 5.1 updates for our international Droid Turbo variants.
And by the way here are the DROID TURBO - Android™ 5.1 Lollipop - Release Notes
Click to expand...
Click to collapse
Did you receive the survey or something? Or are you just being proactive and already creating a topic for when it happens?
Proactive mate, I have already singed up for the program and waiting for the soak for the international version.
Here we can follow updates about different variants of the phone (except for the main Droid turbo USA branch), who gets Soak, or official and news regarding that. I am using a PR XT1225, stock firmware and unrooted sadly due to corporate software.
This is the thread I need...waiting like you. I know we could root and stick L on it, but I want to see what develops first (and KK has been fine for me). But hopefully something will develop soon.
GeodudeFFP said:
This is the thread I need...waiting like you. I know we could root and stick L on it, but I want to see what develops first (and KK has been fine for me). But hopefully something will develop soon.
Click to expand...
Click to collapse
You're lucky you have that option, I don't as I have to use corporate software and cannot be rooted (let's not start talking about root cloaking etc as it didn't work for me)
Let's keep this alive with updates and share stories and we should be fine, I am assuming since Droid US has got 5.1 it won't be far for us. I would give it a month or two.
People keep saying that Droid turbo and Moto Maxx are left behind but the reality is, we are getting the 5.1 update at the same time as the Moto X so we should use the Moto X as an indicator. I think once Moto X (international version) gets the official 5.1 update (currently in Soak testing as the Droid Turbo) we will get it as well.
I think some people won't even have to wait. Tomorrow Motorola will release a downloadable file of Droid Turbo 5.1 for use with RSD lite, and since the Droid Turbo KK worked on Moto Maxx (since it's bootloader can be unlocked), I'm betting this one will too, but with some adjustments (like no flashing the rádio partition/flashing the intl rádio partition afterwards)
That might work, but I won't risk it. I would wait for the official OTA, I have already returned 100% stock. I would have totally gone for it if I didn't have my work apps complications.
Kiwironic said:
That might work, but I won't risk it. I would wait for the official OTA, I have already returned 100% stock. I would have totally gone for it if I didn't have my work apps complications.
Click to expand...
Click to collapse
The apps are a problem indeed. I'll wait for the oficial release, then go backup to KK, restore my stuff with titanium and update.
DarkLey said:
The apps are a problem indeed. I'll wait for the oficial release, then go backup to KK, restore my stuff with titanium and update.
Click to expand...
Click to collapse
Titanium no go bro, remember I don't have root anymore. :crying: :crying:
Kiwironic said:
Titanium no go bro, remember I don't have root anymore. :crying: :crying:
Click to expand...
Click to collapse
I do remember, for you it's really a no go if you want/have to keep the apps/data. Rootjunkysdl already have the OTA file, I'm backing up now to test my hypothesis.
Well I can justify asking for a new access code for my corporate apps after full wipe, but if something goes wrong with root / backup or installing the OTA as Zip my device will be banned. Can't take that risk. So I will have to wait for official or Soak OTA.
But please let us know how that goes for you. Which device do you have? is it a PR XT1225 ?
Kiwironic said:
Well I can justify asking for a new access code for my corporate apps after full wipe, but if something goes wrong with root / backup or installing the OTA as Zip my device will be banned. Can't take that risk. So I will have to wait for official or Soak OTA.
But please let us know how that goes for you. Which device do you have? is it a PR XT1225 ?
Click to expand...
Click to collapse
BR XT1225. One time I flashed the 4.4 Stock ROM for the Turbo in my device and it worked allright, and since this time I will just do the same then update, I think it'll work the same. Still backing up (a lot of data here).
Keep us updated mate.
Here are some news:
http://www.tudocelular.com/android/noticias/n56970/droid-turbo-moto-maxx-android-5-1-lollipop.html
How did it go??
Kiwironic said:
How did it go??
Click to expand...
Click to collapse
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
DarkLey said:
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
:fingers-crossed: Hope it goes well, and thanks for the link.
Hope to see ;
İncreased earpiece and speaker volume.
Better camera
Better calibrated screen for a little colder and more brightness.
Fix memory leak
and i am done.
Sent from my XT1225 using XDA Free mobile app
And better battery performance too
DarkLey said:
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
Wow. You are brave!
I'm happy right now with CM 12.1 (5.1.1 Lollipop on my two XT1225 phones. I'm actually in Brazil right now for two weeks, using them.
Hope 5.1 files Motorola releases will help for custom ROMs for our phones.
When Motorola does release 5.1 for the XT1225 (Moto Turbo and international Moto Maxx), the kernel source code is the main thing, but won't come for awhile.
First it's the OTA, then the full image, then a month or so later the kernel code. At least that seems to be the pattern.