Related
Is it okay to flash the newest image (LMY74I) coming from LMY47O? I won't do any harm in skipping 5.0.1 will I?
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
mymusicathome said:
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
Click to expand...
Click to collapse
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Forerunner326 said:
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Click to expand...
Click to collapse
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
rootSU said:
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
Click to expand...
Click to collapse
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Forerunner326 said:
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Click to expand...
Click to collapse
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Is this because oem unlocking was unchecked for those people?
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Even if the device is rooted, all it will do is cause root to be lost correct?
Forerunner326 said:
Is this because oem unlocking was unchecked for those people?
Click to expand...
Click to collapse
See this post on relocking instructions:
http://forum.xda-developers.com/showthread.php?p=59699095
Forerunner326 said:
Even if the device is rooted, all it will do is cause root to be lost correct?
Click to expand...
Click to collapse
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
rootSU said:
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
Click to expand...
Click to collapse
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
theDXT said:
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
Click to expand...
Click to collapse
Flash everything from the factory image except the userdata.img
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.
So I purchased a used Nexus 6 on Swappa that came with an unlocked bootloader and a custom ROM... Just so I can start totally clean (and party my OCD), I want to flash a stock image, relock the bootloader, and then do any OTA updates I may need... The problem is that since it's a custom ROM it doesn't tell me inside "About Phone" which device I have... When I go to google's site for the stock images it has several carries listed etc... I also went into the bootloader but I didn't see anything that resembled the device ID.
My question is, does it matter which stock image I flash? I'm T-Mobile.. so if I flash a stock T-Mobile image, will that matter if the device is not from T-Mobile? The other thing that's throwing me off is there's two stock T-Mobile 5.1.1 images on google's site, with different device ID's... so I have a feeling it does matter which version you flash.
Thanks!
Looking for the same answer.
Sent from my Nexus 6 using Tapatalk
intruda119 said:
Looking for the same answer.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I just found this article:
http://www.tmonews.com/2015/08/nexu...d-to-lmy48i-are-losing-cellular-connectivity/
which makes me think it really doesn't matter which device you have, just flash the image you need. I personally am going to flash the E version and then accept the OTA for the stagefreight patch. I'm weird about getting latest, official update, via OTA.
Yeah just that thinking of selling mine. Wanted to flash to stock
Sent from my Nexus 6 using Tapatalk
itll always match, its the exact same device. you can flash the tmobile, verizon, att, then the basic stock android, itll all work. and fi as well!
Powell730 said:
So I purchased a used Nexus 6 on Swappa that came with an unlocked bootloader and a custom ROM... Just so I can start totally clean (and party my OCD), I want to flash a stock image, relock the bootloader, and then do any OTA updates I may need... The problem is that since it's a custom ROM it doesn't tell me inside "About Phone" which device I have... When I go to google's site for the stock images it has several carries listed etc... I also went into the bootloader but I didn't see anything that resembled the device ID.
My question is, does it matter which stock image I flash? I'm T-Mobile.. so if I flash a stock T-Mobile image, will that matter if the device is not from T-Mobile? The other thing that's throwing me off is there's two stock T-Mobile 5.1.1 images on google's site, with different device ID's... so I have a feeling it does matter which version you flash.
Thanks!
Click to expand...
Click to collapse
Don't lock your bootloader! There is a high chance of bricking your device and making it useless
Sent from my Nexus 6 using Tapatalk
BigDig said:
Don't lock your bootloader! There is a high chance of bricking your device and making it useless
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
why? how/why would flashing a stock image that relocks the bootloader and unroots brick it?
Powell730 said:
why? how/why would flashing a stock image that relocks the bootloader and unroots brick it?
Click to expand...
Click to collapse
You mentioned in your post " I want to relock my bootloader " - Don't do that!
Sent from my Nexus 6 using Tapatalk
Powell730 said:
why? how/why would flashing a stock image that relocks the bootloader and unroots brick it?
Click to expand...
Click to collapse
BigDig said:
You mentioned in your post " I want to relock my bootloader " - Don't do that!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I concur. Device can be relocked successfully if on stock and it boots. I tried once with custom kernel and TWRP. It bricked. Both the kernel and TWRP crashed. I was lucky it was still unlockable and fastboot saved the day. I don't suggest ever locking a custom build.
BigDig said:
You mentioned in your post " I want to relock my bootloader " - Don't do that!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
prdog1 said:
I concur. Device can be relocked successfully if on stock and it boots. I tried once with custom kernel and TWRP. It bricked. Both the kernel and TWRP crashed. I was lucky it was still unlockable and fastboot saved the day.
Click to expand...
Click to collapse
Oh yeah, I wouldn't re lock it over custom recovery, rom or kernel!
Powell730 said:
Oh yeah, I wouldn't re lock it over custom recovery, rom or kernel!
Click to expand...
Click to collapse
Hahaa. I did it just to prove a point. Luckily just had to reflash TWRP and the kernel. I run stock rooted odex with mods I want hard coded.
Just got a new XT1095 Pure with 4.4.4 pre-loaded. I've already gone through the 'unlocking bootloader' routine from the Moto website. What's next? Should I be taking OTA to 5.1 first or rooting first? Thanks for any help!
dcoaster said:
Just got a new XT1095 Pure with 4.4.4 pre-loaded. I've already gone through the 'unlocking bootloader' routine from the Moto website. What's next? Should I be taking OTA to 5.1 first or rooting first? Thanks for any help!
Click to expand...
Click to collapse
OTA first, you can't upgrade if you are rooted.
Sent from my XT1095 using Tapatalk
dcoaster said:
Just got a new XT1095 Pure with 4.4.4 pre-loaded. I've already gone through the 'unlocking bootloader' routine from the Moto website. What's next? Should I be taking OTA to 5.1 first or rooting first? Thanks for any help!
Click to expand...
Click to collapse
The 4.4 bootloader is fine with every rom out there. I wouldn't take the OTA since you are unlocked bootloader just flash the stock roms via twrp on the android develop section there is one for 4.4, 5.0, and 5.1. its the best way to not risk hard bricks. I have switched back and forth several times going this route. AGISCI posted them.
I also just got an xt1095, is this the latest ROM http://www.filefactory.com/file/5d66szhobgmx/VICTARA_TMO_XT1095_5.1_LPE23.32-21.6_cid9_CFC.xml.zip ?
Also, I have unlocked my bootloader but didn't root yet (this is with 4.4.4 installed). If i simply DL this image and flash it using TWRP (which i have installed) will it overwrite TWRP or break it in any way? Can I then simply root via TWRP ( assuming it is ok) and boom have a fully rooted Lollipop phone ?
Brutal_Master said:
I also just got an xt1095, is this the latest ROM http://www.filefactory.com/file/5d66szhobgmx/VICTARA_TMO_XT1095_5.1_LPE23.32-21.6_cid9_CFC.xml.zip ?
Also, I have unlocked my bootloader but didn't root yet (this is with 4.4.4 installed). If i simply DL this image and flash it using TWRP (which i have installed) will it overwrite TWRP or break it in any way? Can I then simply root via TWRP ( assuming it is ok) and boom have a fully rooted Lollipop phone ?
Click to expand...
Click to collapse
You can't flash firmware files with TWRP, it won't work.
You have to flash it with RSDLite or fastboot.
As far as if it overwrites TWRP. If you use RSDLite, yes it will erase TWRP and replace it with the stock recovery. If you use fastboot to flash just skip the recovery image when you are flashing.
Sent from my XT1095 using Tapatalk
AGISCI said:
You can't flash firmware files with TWRP, it won't work.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Why? Is this limitation only for stock images or ANY custom ROM too?
Brutal_Master said:
Why? Is this limitation only for stock images or ANY custom ROM too?
Click to expand...
Click to collapse
Because the firmware files are just standard images which get flashed and overwrite the partitions. The zips you run in TWRP are instructions on what to do and install. They are completely different things/formats.
Sent from my XT1095 using Tapatalk
Please help, my moto x 2014 wont boot what so ever. This first started from when I tried to root my XT1097 on android 5.1 using this: http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264 not realizing it wasn't for android 5.1. Then it was acting weird so I booted into fastboot and used a factory image which was for AT&T devices. Realizing this was the wrong image (No service or wifi what so ever) I flashed the proper image to return to stock, but now my device simply sits at the M logo and wont boot. Any help to get this device back up and running is appreciated!
Kevin_Desousa said:
Please help, my moto x 2014 wont boot what so ever. This first started from when I tried to root my XT1097 on android 5.1 using this: http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264 not realizing it wasn't for android 5.1. Then it was acting weird so I booted into fastboot and used a factory image which was for AT&T devices. Realizing this was the wrong image (No service or wifi what so ever) I flashed the proper image to return to stock, but now my device simply sits at the M logo and wont boot. Any help to get this device back up and running is appreciated!
Click to expand...
Click to collapse
Did you wipe data/factory reset when you reflashed your firmware?
Sent from my XT1095 using Tapatalk
xKroniK13x said:
Did you wipe data/factory reset when you reflashed your firmware?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Yep, I wiped them both as per usual. If it helps, I can still access fastboot and recovery.
If it is sticking at the M, its failing to boot Android at all. Does it roll into recovery automatically? Which firmware did you flash? Also, was the version flashed older than the one you previously had?
Sent from my XT1095 using Tapatalk
xKroniK13x said:
If it is sticking at the M, its failing to boot Android at all. Does it roll into recovery automatically? Which firmware did you flash? Also, was the version flashed older than the one you previously had?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It doesn't seem to roll into recovery automatically. I flashed this initially : VICTARA_ATT_5.0.2_LXE22.46-34 (AT&T zip), and then I flashed this one: RETCA_XT1097_5.0.1_LXE22.46-22. I forgot which version I had before I tried rooting, but I do know it was android 5.1.
Kevin_Desousa said:
It doesn't seem to roll into recovery automatically. I flashed this initially : VICTARA_ATT_5.0.2_LXE22.46-34 (AT&T zip), and then I flashed this one: RETCA_XT1097_5.0.1_LXE22.46-22
Click to expand...
Click to collapse
Is your bootloader unlocked? If you went to the 5.0.2 AT&T and your bootloader is locked, you won't be able to downgrade back to 5.0.1. Try getting a firmware that is the same version or newer.
Sent from my XT1095 using Tapatalk
xKroniK13x said:
Is your bootloader unlocked? If you went to the 5.0.2 AT&T and your bootloader is locked, you won't be able to downgrade back to 5.0.1. Try getting a firmware that is the same version or newer.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
My bootloader is unlocked, and when I say that I'm stuck at the M, I mean I'm stuck at the bootloader warning. (I didn't know what to call it)
Kevin_Desousa said:
My bootloader is unlocked, and when I say that I'm stuck at the M, I mean I'm stuck at the bootloader warning. (I didn't know what to call it)
Click to expand...
Click to collapse
Yeah, that's where I figured it was hanging. All signs just point to a bad flash/firmware. I'd try downloading a different version (even 5.1 since you're unlocked) or verifying the hash on the firmware you flashed. You can use HashMyFiles to check the md5 or SHA hashes.
Sent from my XT1095 using Tapatalk
xKroniK13x said:
Yeah, that's where I figured it was hanging. All signs just point to a bad flash/firmware. I'd try downloading a different version (even 5.1 since you're unlocked) or verifying the hash on the firmware you flashed. You can use HashMyFiles to check the md5 or SHA hashes.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Would you know of a place where I can obtain the factory images then? The one I was using only had a couple of them, none of which were 5.1
Kevin_Desousa said:
Would you know of a place where I can obtain the factory images then? The one I was using only had a couple of them, none of which were 5.1
Click to expand...
Click to collapse
This thread has a link that has the 5.1 firmwares. You have to do some digging, but they should be there... http://forum.xda-developers.com/showthread.php?t=3148211
Sent from my XT1095 using Tapatalk
xKroniK13x said:
This thread has a link that has the 5.1 firmwares. You have to do some digging, but they should be there... http://forum.xda-developers.com/showthread.php?t=3148211
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Sorry to be such a pain, but would you have flash instructions for the official firmware? I'm just afraid of messing something up
Kevin_Desousa said:
Sorry to be such a pain, but would you have flash instructions for the official firmware? I'm just afraid of messing something up [emoji14]
Click to expand...
Click to collapse
I am personally a huge fan of House of Moto, it will generate automatic scripts to flash the firmware for you. Check out the thread here: http://www.droidrzr.com/index.php?/topic/61124-House-of-Moto-[4.3]
Also, MotoFirmware has some firmwares for the X2, I used to use them for my RAZR M. http://motofirmware.center/files/category/46-moto-x-2nd-generation/
Sent from my XT1095 using Tapatalk
xKroniK13x said:
I am personally a huge fan of House of Moto, it will generate automatic scripts to flash the firmware for you. Check out the thread here: http://www.droidrzr.com/index.php?/topic/61124-House-of-Moto-[4.3]
Also, MotoFirmware has some firmwares for the X2, I used to use them for my RAZR M. http://motofirmware.center/files/category/46-moto-x-2nd-generation/
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried to use the House of Moto with this firmware: http://motofirmware.center/files/file/249-victara_tmo_51_lpe2332-213_cid9_cfcxmlzip/ but when I load it into the HOM it displays this: "Custom recovery not found.
Using factory image: VICTARA_TMO_5.1_LPE23.32-21.3_cid9_CFC.xml.zip
ERROR: XML script not found in this factory image. This is not yet supported."
Kevin_Desousa said:
I tried to use the House of Moto with this firmware: http://motofirmware.center/files/file/249-victara_tmo_51_lpe2332-213_cid9_cfcxmlzip/ but when I load it into the HOM it displays this: "Custom recovery not found.
Using factory image: VICTARA_TMO_5.1_LPE23.32-21.3_cid9_CFC.xml.zip
ERROR: XML script not found in this factory image. This is not yet supported."
Click to expand...
Click to collapse
That firmware looks like the one for xt1095/T-Mobile/Pure Edition. Also, that error sounds like the HoM instructions weren't followed right. I've flashed my device a bunch with HoM.
Sent from my XT1095 using Tapatalk
xKroniK13x said:
That firmware looks like the one for xt1095/T-Mobile/Pure Edition. Also, that error sounds like the HoM instructions weren't followed right. I've flashed my device a bunch with HoM.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Would this one work: VICTARA_NIIBR_XT1097_5.1_LPE23.32-14.2_cid12_CFC.xml.zip? I'm just confused with the "NIIBR" in the firmware name.
Kevin_Desousa said:
Would this one work: VICTARA_NIIBR_XT1097_5.1_LPE23.32-14.2_cid12_CFC.xml.zip? I'm just confused with the "NIIBR" in the firmware name.
Click to expand...
Click to collapse
I'm not sure, to be honest.
Sent from my XT1095 using Tapatalk
xKroniK13x said:
I'm not sure, to be honest.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
So the phone booted up, thank you so much for the help, but for some reason it wont detect my sim card, the wifi doesnt work on it, and it occasionally reboots. I also noticed that the baseband version is unknown. Is there a way to fix this?
Kevin_Desousa said:
So the phone booted up, thank you so much for the help, but for some reason it wont detect my sim card, the wifi doesnt work on it, and it occasionally reboots. I also noticed that the baseband version is unknown. Is there a way to fix this?
Click to expand...
Click to collapse
Sounds like whatever firmware you flashed had the wrong radios. You should be able to download the Canadian firmware and just flash the radios.
Sent from my XT1095 using Tapatalk
xKroniK13x said:
Sounds like whatever firmware you flashed had the wrong radios. You should be able to download the Canadian firmware and just flash the radios.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I did flash the Canadian firmware to my knowledge. RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml?
I was browsing the xda threads and saw this thread: http://forum.xda-developers.com/moto-x-2014/general/guide-xt1097-to-xt1095-nextel-t2972693 where it states: "IMPORTANT. From 5.1 update, the modems included on the update are FULLY compatible with all models, XT1097, 1092 and 1093 and all carriers ,so, you don't have to worry about losing IMEI, signal or data." So, should I be able to flash the brazilian xt1097 firmware and have the proper radios installed from this thread: http://forum.xda-developers.com/moto-x-2014/general/ota-android-marshmallow-6-0-final-t3248315 ?