[Q] Security Settings crash - Moto X Q&A

I just bought a new VZW Dev Edition and rooted/unlocked the BL on it. After this, I flashed several different ROM's and on every one, I can't access the "security" menu in settings. This is the only menu in my entire settings that I cant open.
I have no idea whats going on, so any help would be appreciated.
Current setup: Latest TWRP with Eclipse 4.4.2

I had an exact same issue after flashing my xt1053 to t-mobile (original was some mexian customer) without modem.
After I flashed original modem from t-mobile - 'security' option began to work.
Hope this helps you in some way.

Thanks! I have looked all over this forum and google searched...where can I find the stock VZW modem to flash?

@bigw34 First... Boot into bootloader/fastboot mode on the phone.
Which of the following does it say for the second line?
30.70
30.71
30.B2
30.B4
30.B7
If it says 30.b7, and you are using a 4.4.2 or lower rom based rom, that is your issue. If it says 30.b4 and you are using a 4.4 or lower based rom, that is your issue.

KidJoe said:
@bigw34 First... Boot into bootloader/fastboot mode on the phone.
Which of the following does it say for the second line?
30.70
30.71
30.B2
30.B4
30.B7
If it says 30.b7, and you are using a 4.4.2 or lower rom based rom, that is your issue. If it says 30.b4 and you are using a 4.4 or lower based rom, that is your issue.
Click to expand...
Click to collapse
I ended up flashing back the stock 4.4.2 image from Motorola since I have the Dev Edition. I then flashed Eclipse ROM again and it all worked perfectly. Thanks so much for your help! I will keep this post around for the future. I always appreciate learning something new from people like you on here!

Related

[Q] Another way to get 4.4.2?

Question: Rather than incrementally update from 4.4 to 4.4.2 by OTA, can I just wait until the full 4.4.2 image is available and flash the full image?
I see a nice list of firmwares here, for example:
http://sbf.droid-developers.org/phone.php?device=0
I'm reluctant to do the update incrementally via OTA or manually, because I don't want to revert from TWRP to stock recovery. As things stand, I believe have a non-stock recovery is preventing me from receiving the OTA that TMobile is currently rolling out.
I have a DevEd GSM and am using TMobile. I'm entirely stock except for TWRP.
Thanks.
Once the US TMobile is available for 4.4.2 you should be able to fastboot (or mfastboot for the system.img) flash the update without losing your recovery. I'm sure someone will post specific steps to update unlocked bootloader, custom recovery phones once the 4.4.2 image is released. I have seen posts warning about not flashing the boot image because it can't be reverted, but I don't know if that affects phones with an unlocked bootloader.
Groid said:
Once the US TMobile is available for 4.4.2 you should be able to fastboot (or mfastboot for the system.img) flash the update without losing your recovery. I'm sure someone will post specific steps to update unlocked bootloader, custom recovery phones once the 4.4.2 image is released. I have seen posts warning about not flashing the boot image because it can't be reverted, but I don't know if that affects phones with an unlocked bootloader.
Click to expand...
Click to collapse
It does affect the unlocked bootloader people, that is why some people are waiting for the sbf. If you update via the OTA, it will install the new bootloader, regardless of lock status. Once on this new 4.4.2 bootloader, it is impossible to flash any stock images before 4.4.2 (you cannot go back to 4.4 or 4.4.2).
But why would you want to go back if you have an unlocked bootloader already? I don't really see any reason to flash an image that is earlier than the latest... if I were Moto, I would let people flash the earliest system image of that version of android (4.4 kitkat in our case). This would rectify the root situation (because 4.2.2 isn't kitkat), and it would keep the people happy as well.
varxx said:
Question: Rather than incrementally update from 4.4 to 4.4.2 by OTA, can I just wait until the full 4.4.2 image is available and flash the full image?
I see a nice list of firmwares here, for example:
http://sbf.droid-developers.org/phone.php?device=0
I'm reluctant to do the update incrementally via OTA or manually, because I don't want to revert from TWRP to stock recovery. As things stand, I believe have a non-stock recovery is preventing me from receiving the OTA that TMobile is currently rolling out.
I have a DevEd GSM and am using TMobile. I'm entirely stock except for TWRP.
Thanks.
Click to expand...
Click to collapse
You absolutely can manually flash the system image while having the 4.4 bootloader, you can also flash any 4.4.2 stock based ROM such as the 1052 European ROM that showed up today.
I was actually running the gummy ROM 4.4.2 while still on the 4.4 bootloader without any issue
Sent on my Gummy running Lenoto X

XT1053 : Returning to stock & changing locale

Hi,
I own a Moto X Developer Edition, so a XT1053 device.
After some issue, I decided to return to full stock, 4.4.2, and possibly changing the locale to get a full French support.
I followed the instructions from this thread to return to stock. And instead of choosing the original firmware, I took the French one from this list.
Everything run smoothly without any issue, except one annoying problem for a phone, the radio doesn't work, so no GSM connectivity. The phone says the radio is unactivated.
I think there is a way to "mix" some img files from the original Dev Edition and the FR one to get things working, but I don't know exactly. Any help would be greatly appreciated.
Thanks.
Hi,
Really need some help on this one because as I didn't get any answer, I decided to reflash the official 4.4 firmware to get my radio back. But as the Moto X has been flashed with the French 4.4.2 rom, it refuses to be downgraded to 4.4.
Any idea? Thanks.
Please please please please read up on these things before you end up flashing!
I'm glad I could answer before you ended up hard bricking your phone, your current bootloader is based on the 4.4.2 rom, so it is impossible to downgrade to previous images. If you were stubborn and skipped this information, you would have tried to manually flash the 4.4 image with mfastboot commands and just purposely left out the bootloader, if you did this, then as soon as you got the 4.4.2 OTA to update and accepted it, you would have hard bricked your phone.
Now with all that said, it may be possible to take the NON-HLOS.bin and fsg.mbn from the 4.4 SBF T-Mobile/Dev Edition image and try to flash that radio/modem to your phone. I would make a backup before doing this though. just follow the fastboot commands for the modem and you should be okay. Remember to follow them exactly.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I am not entirely sure that you can use the 4.4 modem with a 4.4.2 rom. There may have been some firmware changes that prevent this from working, but you are welcome to try, I would personally wait until a T-Mobile/Dev Ed SBF 4.4.2 image appears and try the same procedure with that instead, but you are welcome to "chance" it
Thanks for the help.
In the meantime, I've read this thread and this one. So, I tried to flash the Rogers Canada 4.4.2 image. Everything runs fine, but still no radio.
But, I currently run the instructions from here to return to stock, and so I didn't know I had to flash NON-HLOS.bin file. I'm going to try this right now.
Thanks again.
Just tried to flash the NON-HLOS.bin file by following your instructions. Tried with both Rogers Canada sbf and with the Official 4.4 image. Same, no radio.
Wait for the official Developer Edition 4.4.2 or I'll contact Motorola. Does somebody know if an there is some ETA from this official image?
Thanks.
romut said:
Thanks for the help.
In the meantime, I've read this thread and this one. So, I tried to flash the Rogers Canada 4.4.2 image. Everything runs fine, but still no radio.
But, I currently run the instructions from here to return to stock, and so I didn't know I had to flash NON-HLOS.bin file. I'm going to try this right now.
Thanks again.
Click to expand...
Click to collapse
Just to give you a heads up, the NON-HLOS.bin file is where most of the modem actually is (all 50-60MB of it), I'll send a PM to the topic creator, because it's not giving the community the right information, they are missing that critical piece.
Be careful with your bootloader, the FR version may be the same as the UK bootloader (30.B3), the Rodgers version is (30.B4) meaning you would no longer be able to flash the whole SBF for the FR version because it would have a lower bootloader. However, you would be safe by just flashing the system image, but I would recommend not taking any OTA updates if you flash it.
Also remember that radios require a reset/power down, because it needs to get the information from the SIM card to use the particular radio frequencies. Also make sure the APN is correctly configured, this may also cause an issue.
There may be another Developer Edition 4.4 image directly from Moto that you could try, I think it takes 24 hours for them to get back with you giving you the link to their google drive though, however, it may be the same as the T-Mobile one on SBF.
You could also attempt getting the patched files from a 4.4.2 OTA image and merging it with a 4.4 radio (basically over-writing some of the files in the 4.4 version), I am unsure if this would work, but in theory it should, since that's what is happening during the update. However, I don't know if there are checks or anything, don't brick your phone because of me
Thanks for your message.
I've tried to flash the modem part only, then switch off/on the phone. No way, no radio. As I flashed the Rogers firmware, yes, my bootloader has been upgraded to 30B4.
Only way now is to wait for the official Developer Edition 4.4.2 zip, or to contact Motorola.
romut said:
Thanks for your message.
I've tried to flash the modem part only, then switch off/on the phone. No way, no radio. As I flashed the Rogers firmware, yes, my bootloader has been upgraded to 30B4.
Only way now is to wait for the official Developer Edition 4.4.2 zip, or to contact Motorola.
Click to expand...
Click to collapse
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
flashallthetime said:
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
He wouldn't have been able to flash a 4.4 image anyways because he used the 4.4.2 FR image. The only reason to upgrade via OTA/SBF is if you are certain that your phone matches the SBF. Otherwise there are too many possible complications to list here. His best bet is the NON-HLOS and fsg from that 4.4.2 version since it has the 4.4 modem and the fixes/modifications of the 4.4.2 as well. Or he could try to "manually" update the T-mobile 4.4 SBF modem, by copying the T-mobile 4.4.2 OTA modem patches and overwriting the select few files in the SBF, then flashing the new image.
However, in reality, it's probably best to wait for the "official" SBF anyways.
mastarifla said:
He wouldn't have been able to flash a 4.4 image anyways because he used the 4.4.2 FR image. The only reason to upgrade via OTA/SBF is if you are certain that your phone matches the SBF. Otherwise there are too many possible complications to list here. His best bet is the NON-HLOS and fsg from that 4.4.2 version since it has the 4.4 modem and the fixes/modifications of the 4.4.2 as well. Or he could try to "manually" update the T-mobile 4.4 SBF modem, by copying the T-mobile 4.4.2 OTA modem patches and overwriting the select few files in the SBF, then flashing the new image.
However, in reality, it's probably best to wait for the "official" SBF anyways.
Click to expand...
Click to collapse
No just wait for the sbf firmware
Sent on my Gummy running Lenoto X
flashallthetime said:
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I know you're doing a dawn good job at warning people :good: I should have read some threads before flashing, my stupidity ! :laugh:
I'll try to contact Motorola and see what can be done. Problem is this is a DE bought in USA, and I'm in France. Not the best case.
romut said:
I know you're doing a dawn good job at warning people :good: I should have read some threads before flashing, my stupidity ! :laugh:
I'll try to contact Motorola and see what can be done. Problem is this is a DE bought in USA, and I'm in France. Not the best case.
Click to expand...
Click to collapse
Your screwed, the European boot loader is 30.b3 and America is 30.b4, the modem aren't compatible, you can't run European modems with american boot loader and visa versa , call moto
Sorry for your situation. Have you tried flashing the French firmware?
Sent on my Gummy running Lenoto X
flashallthetime said:
Your screwed, the European boot loader is 30.b3 and America is 30.b4, the modem aren't compatible, you can't run European modems with american boot loader and visa versa , call moto
Sorry for your situation. Have you tried flashing the French firmware?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yes that's what I wrote, I've seen the bootloader has been upgraded. As the official ROM for the Moto X DE already includes the french, it's not a big deal for me to get stuck with the ghost.en.US ROM. But as I've already flashed a 4.4.2 (the french one), I need the official 4.4.2 which is not yet available.
I've read in another thread, Motorola has accepted to exchange some phones in that case, I cross my fingers.
Hi,
I had a chat yesterday with the Motorola Service. This issue can be covered by the warranty only for Developer Edition. Now my problem is the cost to send the Moto from France to the US, but I think this may be interesting for people with the same issue.
Or we have to wait for the official release of the T-Mobile 4.4.2 ROM, but I couldn't get an ETA.
stock 4.4.2 boot.img
i flashed faux123 custom kernel and was not aware it was for 4.4 the updater app allowed me to install it
now my phone is screwed up
does anyone know where I can find the stock kernel image for 4.4.2 on unlocked xt1053 dev edition

[Q] Go from 4.2.2 to 4.4.2 Unlocked, rooted, twrp

I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
If all you want to do is update, you could install Custom ROM although you will lose Motorola's Active Display, Always Listening etc...
If you want complete stock and have to reflash TWRP and root your phone, you will need to flash the stock firmware using fastboot or a utility.
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Alecegonce101 said:
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
Click to expand...
Click to collapse
Um, all VZW Moto Xs are SIM-unlocked.
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
I hope it wasn't the pre-camera 4.2.2....or you might be in a tough spot now.... Risking a brick. ?
---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------
Unless the first firmware was also pre camera... Then you're OK.
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
Taking OTA's is incremental, so if you are the initial shipping 4.2.2 you need to take the first 4.2.2 w/camera OTA, then the 4.4 OTA, then the 4.4.2 OTA... a real time waster and pain in the rear.
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
Since you have a Dev Edition, why not just go to 4.4.4? it has a few bug fixes, and is stable. For me and many others its no worse than 4.4.2 as far as performance and battery.
Once you arrive on the ROM you want, you can flash TWRP and root.
KidJoe said:
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
t.
Click to expand...
Click to collapse
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
Yup! ?
As long as it's not a lower version.
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
OTA = Incremental. Only patches the changed/updated parts.
SBF/FXZ = "all inclusive" or "image files".. and overwrites entire partitions/parts.
So yes. You can just flash the newer SBF file. (As @Darth said... as long as the SBF you are flashing is NEWER than the version on your phone... i.e. NEVER DOWNGRADE)

[Q] Downgrading from 5.0 CM12 unofficial to any 4.4.x official moto firmware?

I have a bootloader-UNLOCKED Moto X XT1058 and I'm running one of the really old CM lollipop builds that came out back in November.
I love Lollipop but I miss my Moto Display, and I was wondering if there was a safe way for me to downgrade back to a 4.4.x firmware so I could get it back.
My bootloader is unlocked, but I'm concerned about any issues that would arise from downgrading from a 5.x to a 4.x firmware. Is this safe?
Thanks
mspadam said:
I have a bootloader-UNLOCKED Moto X XT1058 and I'm running one of the really old CM lollipop builds that came out back in November.
I love Lollipop but I miss my Moto Display, and I was wondering if there was a safe way for me to downgrade back to a 4.4.x firmware so I could get it back.
My bootloader is unlocked, but I'm concerned about any issues that would arise from downgrading from a 5.x to a 4.x firmware. Is this safe?
Thanks
Click to expand...
Click to collapse
I used one of the first CM12 ROMs available in november and then returned to an official ROM for XT1058 (KitKat 4.4.4) and it worked flawlessly, so you should be ok.
mspadam said:
I have a bootloader-UNLOCKED Moto X XT1058 and I'm running one of the really old CM lollipop builds that came out back in November.
I love Lollipop but I miss my Moto Display, and I was wondering if there was a safe way for me to downgrade back to a 4.4.x firmware so I could get it back.
My bootloader is unlocked, but I'm concerned about any issues that would arise from downgrading from a 5.x to a 4.x firmware. Is this safe?
Thanks
Click to expand...
Click to collapse
I believe that CM only flashes /System. IF so, to return to a stock Moto rom, just boot into fastboot/bootloader, check the bootloader version, and the corresponding Moto rom, or a newer Moto Rom.
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
Umm. Custom ROMs have nothing to do with anything technically speaking. Unless it's an official Moto update that was pushed to the device via OTA or RSD, then it might change things depending on your carrier device. Downgrading is nothing more than flashing a ROM or restoring a nandroid in the case of ROMs via TWRP/CWM or whatever you use.
Problem one. The fact you asked this means you probably goofed up and never made a nandroid backup. If you did make one. Just restore that stock nandroid and you're set. If not. Time to RSD or fastboot back to stock.
You can always flash back to stock with RSD however, I too missed ambient display until I tried Dynamic Notifications. Totally replaces ambient display for any of the CM based ROMs I have tried.
Thanks for all the help, guys!
One last question, I'm retarded. I have the Rogers Canada version but the Rogers firmware (ROGERS-CA_GHOST_KXA20.16-1.26_cid14_CFC_1FF.xml) is apparently 4.4.2 - will it matter if I use a different firmware that is 4.4.4 (which corresponds to my Bootloader version)?
mspadam said:
Thanks for all the help, guys!
One last question, I'm retarded. I have the Rogers Canada version but the Rogers firmware (ROGERS-CA_GHOST_KXA20.16-1.26_cid14_CFC_1FF.xml) is apparently 4.4.2 - will it matter if I use a different firmware that is 4.4.4 (which corresponds to my Bootloader version)?
Click to expand...
Click to collapse
NEVER use a firmware that is for an older bootloader.. i.e. NEVER DOWNGRADE.
If bootloader version on your phone is 30.B7, then it corresponds with 4.4.4, so you MUST use a STOCK Moto 4.4.4 SBF!!!!
But if your bootloader version is 30.B4, that corresponds with 4.4.2, and you MAY use either 4.4.2 or 4.4.4 SBF. Just know that if you use 4.4.4, you will not be able to downgrade to 4.4.2 in the future.
If you can't find your rom.. check ALL of the sources linked in this thread -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Use the motox toolkit to downgrade your phone/return back to stock
Sent from my XT1053 using XDA Premium 4 mobile app
Thanks for the help - so if I use a different 4.4.4 firmware that isn't Rogers it won't matter? I'm just concerned that there's a difference between them, my phone is Rogers but if I use a 4.4.4 firmware that isn't Rogers will it make any difference or is it not a big deal?
mspadam said:
Thanks for the help - so if I use a different 4.4.4 firmware that isn't Rogers it won't matter? I'm just concerned that there's a difference between them, my phone is Rogers but if I use a 4.4.4 firmware that isn't Rogers will it make any difference or is it not a big deal?
Click to expand...
Click to collapse
Are you asking about flashing a 3rd party rom, like CM? or a Stock Moto rom for a different carrier/model?
I would recommend against flashing a ROM not meant for your carrier/model... There are several possible outcomes which I've seen.
It works, but GPT.BIN version is slightly different and prevents your ability to flash back to the correct ROM for your carrier/model.
Flashes "correctly", but renders your cellular radio unusable.
works ok, but no differently, and no added functions.
Keep in mind, the above only holds true for flashing a different STOCK MOTO ROMS..
NOW, if you are asking about flashing a 3rd party ROM, like CM, or other, you should be relatively safe, and be able to flash back to stock if/when you wish.
KidJoe said:
NEVER use a firmware that is for an older bootloader.. i.e. NEVER DOWNGRADE.
If bootloader version on your phone is 30.B7, then it corresponds with 4.4.4, so you MUST use a STOCK Moto 4.4.4 SBF!!!!
But if your bootloader version is 30.B4, that corresponds with 4.4.2, and you MAY use either 4.4.2 or 4.4.4 SBF. Just know that if you use 4.4.4, you will not be able to downgrade to 4.4.2 in the future.
If you can't find your rom.. check ALL of the sources linked in this thread -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Click to expand...
Click to collapse
KidJoe said:
Are you asking about flashing a 3rd party rom, like CM? or a Stock Moto rom for a different carrier/model?
I would recommend against flashing a ROM not meant for your carrier/model... There are several possible outcomes which I've seen.
It works, but GPT.BIN version is slightly different and prevents your ability to flash back to the correct ROM for your carrier/model.
Flashes "correctly", but renders your cellular radio unusable.
works ok, but no differently, and no added functions.
Keep in mind, the above only holds true for flashing a different STOCK MOTO ROMS..
NOW, if you are asking about flashing a 3rd party ROM, like CM, or other, you should be relatively safe, and be able to flash back to stock if/when you wish.
Click to expand...
Click to collapse
I was hoping to reflash to my carrier's specific firmware, but I can't seem to find one higher than 4.4.2 on the ROM list or anywhere else
That explains a bunch though, thank you!
mspadam said:
I was hoping to reflash to my carrier's specific firmware, but I can't seem to find one higher than 4.4.2 on the ROM list or anywhere else
That explains a bunch though, thank you!
Click to expand...
Click to collapse
I'm sure Rogers 4.4.4 is found in one of the sites listed at http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
i've an xt1052 indian version can anyobdy tell which rom to use, i tried all that i could get, none of it worked

[Q] How to revert back to stock KK?

I've been running LP 5.1.1 using a custom rom but I've been getting tired of the instability of the roms I've tried. I'm wanting to go back to stock KK, am I able to? If so, how? I have a XT1053 and running XenonHD rom. Thanks!
First, start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
Take note of the Bootloader version on the 2nd Line. If its 30.B7, then you are fine to just flash the Stock 4.4.4 SBF for the XT1053. To do this, you can use the Requirements and Option 5 listed in the 2nd post of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
If your bootloader is NOT 30.B7, then see -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 before doing any flashing.
My bootloader seems to be 30.B4, is that still safe to use? From what I can tell it's 4.4.2 bootloader.
bloodletting284 said:
My bootloader seems to be 30.B4, is that still safe to use? From what I can tell it's 4.4.2 bootloader.
Click to expand...
Click to collapse
You can always flash NEWER.... so if your bootloader is 30.B4 or 4.4.2, you are perfectly fine flashing 4.4.4 over top.
You just don't want to flash OLDER..
NOTE: Your situation is slightly different than someone running a STOCK 5.x rom. Because you are running a Custom rom that didn't touch your bootloader and other parts, you can flash back to the stock 4.4.4 ROM. If you had installed a full Stock 5.x ROM (like the leaked test versions), it would be a different matter because your bootloader, partition table, trusted zone, and other parts would have been updated too, and would cause issue if you try to downgrade them.

Categories

Resources