Does stock image have to match device? - Nexus 6 Q&A, Help & Troubleshooting

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.

Related

[Q] getting off 4.4.2

4.4.2 is a disaster for me on my verizon DE phone....bluetooth keeps disconnecting, calls are breaking up etc. I would like to downgrade to an earlier release that works. My phone is unlocked and rooted.
What can I safely revert to...and how do I do it without bricking the phone?
ghstudio said:
4.4.2 is a disaster for me on my verizon DE phone....bluetooth keeps disconnecting, calls are breaking up etc. I would like to downgrade to an earlier release that works. My phone is unlocked and rooted.
What can I safely revert to...and how do I do it without bricking the phone?
Click to expand...
Click to collapse
I would try a safe boot first. Long press on the power off screen button.
Downgrading is a dangerous affair. Highly NOT recommended.
There are ways, apparently... But most the knowledgeable members will say not to try. Unless its so important and your want outweighs the risk. The worst case scenario being a bricked phone.
Try backing up your data and apps, move the backup to a computer....and try a factory reset. Or flashing the firmware again with mfastboot.
4.4.2 is fine, not sure about your issues...but most are happy with 4.4.2. Your issues are likely app related.
Good luck!
I would recommend downloading the SBF package for your phone and flashing your phone to complete stock and then see how it works if you still want to downgrade after that you'll have to download a 4.4 SPF package and you're not to bypass the bootloader so you wouldn't just installed data system recovery and think that's it but like this previously said if you accidentally hit the OTA to update you could break your phone. sounds like your 4.4.2 install was corrupted. so I would download the 4.4.2 SBF package and do a complete reinstall
Sent from my XT1056 using XDA Premium 4 mobile app
Is this phone different as you can't just flash a 4.4 or 4.3 ROM? Auto downgrade?
Sent from my XT1056 using Tapatalk
r.storm85 said:
Is this phone different as you can't just flash a 4.4 or 4.3 ROM? Auto downgrade?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Downgrading from 4.4.2 can lead to a brick. There's supposedly a very careful way to do it....but anything can go wrong. Not worth the risk IMHO.
r.storm85 said:
Is this phone different as you can't just flash a 4.4 or 4.3 ROM? Auto downgrade?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Yes in that the bootloader doesn't allow itself to be flashed with an older version, signed or not. Trying to downgrade the bootloader can result in an unusable device.
You can flash the bootloader with a current or newer version but not an older version....locked or unlocked, it doesn't make a difference.
tcrews said:
Yes in that the bootloader doesn't allow itself to be flashed with an older version, signed or not. Trying to downgrade the bootloader can result in an unusable device.
You can flash the bootloader with a current or newer version but not an older version....locked or unlocked, it doesn't make a difference.
Click to expand...
Click to collapse
So I'm use to an evo4g and I could flash any ROM once I was rooted with s-off and recovery installed. It wouldn't mess with the boot loader at all. So this phone every ROM comes with a certain boot loader??
Sent from my XT1056 using Tapatalk
r.storm85 said:
So I'm use to an evo4g and I could flash any ROM once I was rooted with s-off and recovery installed. It wouldn't mess with the boot loader at all. So this phone every ROM comes with a certain boot loader??
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Doesn't matter about ROMs. They have nothing to do with the boot loader. And they don't flash boot loaders. But they made the 4.4.2 boot loader so it can't be downgraded. Why...who knows. But they did. Roms make no difference.
kj2112 said:
Doesn't matter about ROMs. They have nothing to do with the boot loader. And they don't flash boot loaders. But they made the 4.4.2 boot loader so it can't be downgraded. Why...who knows. But they did. Roms make no difference.
Click to expand...
Click to collapse
Right so he can't flash a ROM with a 4.4 or 4.3 base? Why would you need to downgrade the boot loader if your rooted and unlocked on 4.4.2 already?
Sent from my XT1056 using Tapatalk
The OP hasn't returned. So I assume he resolved his issues.
I don't know what happens trying to flash an older android version custom ROM actually. An error i would think....or hope anyway. On a nexus you get an error about the boot loader version...I think. But I've never seen it, cause on a nexus you can manually flash any boot loader you want. Older or newer.
I never flashed "ROMs" on my moto x. Just stock with xposed. Custom ROMs have issues, and no moto features.
The x really isn't a "flashing" phone. Definitely nothing like a nexus.
kj2112 said:
The OP hasn't returned. So I assume he resolved his issues.
I don't know what happens trying to flash an older android version custom ROM actually. An error i would think....or hope anyway. On a nexus you get an error about the boot loader version...I think. But I've never seen it, cause on a nexus you can manually flash any boot loader you want. Older or newer.
I never flashed "ROMs" on my moto x. Just stock with xposed. Custom ROMs have issues, and no moto features.
The x really isn't a "flashing" phone. Definitely nothing like a nexus.
Click to expand...
Click to collapse
Ya I jus remember on my evo I could flash back and forth between a 2.2, 2.3, cm6 whatever was available and it didn't matter. Like instead of taking a ota for 4.4.2 on my nexus 7 from 4.3 I jus found a stock rooted 4.4.2 ROM and flashed it. No need for ota or downgrades. And I have nandroids of 4.3 if I wanted to downgrade. Just trying to get a understanding of the ins and outs if this phone before and if I venture into rooting ya know
Sent from my XT1056 using Tapatalk
r.storm85 said:
So I'm use to an evo4g and I could flash any ROM once I was rooted with s-off and recovery installed. It wouldn't mess with the boot loader at all. So this phone every ROM comes with a certain boot loader??
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
S-off on the htc's is more "unlocked" than unlocking the boot loader on the X. With s-off, security checks, etc are bypassed.
I've posted the "long version" before, and I don't have time to retype it..so... The 4.4.2 update on the X changed the boot loader, gpt.bin and other things. They can not be downgraded. Attempts to do so will either fail, cause you problems, and will either brick the phone or set it up to brick if updating later.
KidJoe said:
S-off on the htc's is more "unlocked" than unlocking the boot loader on the X. With s-off, security checks, etc are bypassed.
I've posted the "long version" before, and I don't have time to retype it..so... The 4.4.2 update on the X changed the boot loader, gpt.bin and other things. They can not be downgraded. Attempts to do so will either fail, cause you problems, and will either brick the phone or set it up to brick if updating later.
Click to expand...
Click to collapse
Right I understand the boot loader cannot be downgraded. But if you have root and are unlocked with a custom recovery on the x you can't flash any android version ROM you want ?
Sent from my XT1056 using Tapatalk
r.storm85 said:
Right I understand the boot loader cannot be downgraded. But if you have root and are unlocked with a custom recovery on the x you can't flash any android version ROM you want ?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Its been said over and over. No offence.
No. You can't downgrade the os after you've got 4.4.2. Once on 4.4.2....always on 4.4.2.
Well, you may be able to if you research on how some say they have. But you can brick. Its always a strong risk. If you are ready to buy a new phone in case things go bad.....then search on the ways people have done it.
But none of the guys "in the know" here would recommend it, or help anyone do it.
Nothing else really to say.
Good luck!
r.storm85 said:
Right I understand the boot loader cannot be downgraded. But if you have root and are unlocked with a custom recovery on the x you can't flash any android version ROM you want ?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
first off, I'm on vacation with my family, typing this on my stupid iPad whose autocorrect is driving me batty so if my details seem sparse, sorry, I have typed this info with more details before, search.
if you are talking about custom, 3rd party rooms, maybe... As it depends on what parts they flash, and what their base is.
But if you are talking about moto roms, then NO. Do not, unless you don't mind turning your X into a brick or paper weight.
Again stop thinking about htc s-off and what you were able to do as it doesn't apply to moto. Coming from an Incredible and Thunderbolt with s-off, I know how it's hard to forget. And trying to compare the two will cause many questions,
Due to changes in the bootloader and gpt.bin included with 4.4.2 on the X, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2. If you have an unlocked boot loader you won't need to downgrade to root.
I've read, (not going to dig up the link right now cause I'm on iPad) of some who had 4.4.2 but successfully mfastboot flashed system.img only, and if they went into app drawer -> setting -> security -> they were kicked back out to settings. This is due to system parts relying on the other components. I'm not sure what other problems were found day to day.
Additionally there were/are many reports asking for help because their device won't boot. The common thread.... They had 4.4.2 and downgraded or tried to downgrade.
I'm not going to go into every possible scenario, what might happen, what causes it, what might be safe, etc. the general consensus is once you have 4.4.2 on your X do not try to downgrade!
kj2112 said:
The OP hasn't returned. So I assume he resolved his issues.
Click to expand...
Click to collapse
The OP has now returned and I have not resolved my issues
The advice here appears to be...don't try it so I will either continue to use the moto-x until hopefully 4.4.3 fixes the bluetooth issues, or I'll use my older galazy nexus until Motorola/Google figures out how to get the moto-x working.
ghstudio said:
The OP has now returned and I have not resolved my issues
The advice here appears to be...don't try it so I will either continue to use the moto-x until hopefully 4.4.3 fixes the bluetooth issues, or I'll use my older galazy nexus until Motorola/Google figures out how to get the moto-x working.
Click to expand...
Click to collapse
Have you reflashed 4.4.2 stock and had a fresh start? Cause there aren't any/many other reports of this. You may just need a fresh install.
My x has none of those issues anyway on 4.4.2.
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
And have you tried another Bluetooth device. It could be the problem too. Just not compatible with the x.
KidJoe said:
first off, I'm on vacation with my family, typing this on my stupid iPad whose autocorrect is driving me batty so if my details seem sparse, sorry, I have typed this info with more details before, search.
if you are talking about custom, 3rd party rooms, maybe... As it depends on what parts they flash, and what their base is.
But if you are talking about moto roms, then NO. Do not, unless you don't mind turning your X into a brick or paper weight.
Again stop thinking about htc s-off and what you were able to do as it doesn't apply to moto. Coming from an Incredible and Thunderbolt with s-off, I know how it's hard to forget. And trying to compare the two will cause many questions,
Due to changes in the bootloader and gpt.bin included with 4.4.2 on the X, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2. If you have an unlocked boot loader you won't need to downgrade to root.
I've read, (not going to dig up the link right now cause I'm on iPad) of some who had 4.4.2 but successfully mfastboot flashed system.img only, and if they went into app drawer -> setting -> security -> they were kicked back out to settings. This is due to system parts relying on the other components. I'm not sure what other problems were found day to day.
Additionally there were/are many reports asking for help because their device won't boot. The common thread.... They had 4.4.2 and downgraded or tried to downgrade.
I'm not going to go into every possible scenario, what might happen, what causes it, what might be safe, etc. the general consensus is once you have 4.4.2 on your X do not try to downgrade!
Click to expand...
Click to collapse
OK thanks for the explanation.
Sent from my XT1056 using Tapatalk

[Q] Can I update to any rom on any bootloader?

I am currently running rooted 4.4 with an unlocked bootloader. Can I flash any Ghost rom or do I need to update the bootloader?
Thank You
I'm not sure, but it would be nice to have the answer to this question.
Does it matter what bootloader that I am on for custom roms on the Moto X? I know that it has mattered on other devices.
Thank You for the help
No, don't flash roms from other carriers. First of all we have different models, for example I am using a model XT1058. But verizon models are XT1060. The hardware for the radios is different. Only flash your official rom, or a custom rom. I don't recommend flashing ones from other carriers because it can cause problems or worse a bricked cell phone.
Sent from my XT1058 using Tapatalk
AGISCI said:
No, don't flash roms from other carriers. First of all we have different models, for example I am using a model XT1058. But verizon models are XT1060. The hardware for the radios is different. Only flash your official rom, or a custom rom. I don't recommend flashing ones from other carriers because it can cause problems or worse a bricked cell phone.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
But what I am wondering is if I am on currently on 4.4 does it matter if I flash a 4.4.4 rom with my current 4.4 bootloader?
That is fine. But after you do so you can never go back to 4.4.
Sent from my XT1058 using Tapatalk
AGISCI said:
That is fine. But after you do so you can never go back to 4.4.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
I do know that once you upgrade the bootloader THAT IS IT, No going back buddy. I just know with my TF700 there are newer build numbers that can't be flashed with an older bootloader. Since you can't go back after updating the bootloader, I wasn't certain if the Moto X and issues with certain rom builds on certain bootloaders. Basically wondering if all the builds play well with my current 4.4 bootloader.
I only am attempting to prevent starting a thread that says that I bricked my phone because I didn't research enough
DanRo80 said:
I do know that once you upgrade the bootloader THAT IS IT, No going back buddy.
Click to expand...
Click to collapse
Well you can't downgrade the bootloader or partition table, but I am able to bounce back and forth b/t 4.4.2 nandroid and 4.4.4 and another poster was able to do it b/t 4.4.3 and 4.4.4. We have nandroids of the earlier systems, though. Not sure if that makes a difference or not.
I am even able to go from 4.4.4 to 4.4.2 nandroid, return to stock and take the 4.4.4 OTA.
Well, I'm on 4.4
There is no going back to 4.4 after updating. Basically do I need to be on at least 4.4.2?
DanRo80 said:
Basically do I need to be on at least 4.4.2?
Click to expand...
Click to collapse
To do what?
Wansanta said:
To do what?
Click to expand...
Click to collapse
In order to flash 4.4.4 Roms and not have things go badly.
DanRo80 said:
In order to flash 4.4.4 Roms and not have things go badly.
Click to expand...
Click to collapse
IIRC, @Q9Nap tried staying on a lower bootloader and partition table version and only flashing the system, boot and modems to upgrade but eventually he had to upgrade his bootloader b/c the newer systems didn't work right with the older bootloader/partition table.
Is there some reason why you want to keep the older bootloader if you are unlocked?
Wansanta said:
IIRC, @Q9Nap tried staying on a lower bootloader and partition table version and only flashing the system, boot and modems to upgrade but eventually he had to upgrade his bootloader b/c the newer systems didn't work right with the older bootloader/partition table.
Is there some reason why you want to keep the older bootloader if you are unlocked?
Click to expand...
Click to collapse
That was exactly what I was wondering would happen. I was only wondering if it would be a waste of time updating it.
Thank You for the help

Verizon rom

Just wondering which version Verizon phones are running right now? Like Verizon LMY47Z? I tried the beta preview 3 and don't like it and would like to switch back to stock but I can't get any OTAs with a updated bootloader....
Thank you
Sent from my Nexus 6 using Tapatalk
thawte said:
Just wondering which version Verizon phones are running right now? Like Verizon LMY47Z? I tried the beta preview 3 and don't like it and would like to switch back to stock but I can't get any OTAs with a updated bootloader....
Thank you
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The latest build for Nexus 6s on Verizon are LMY48I.
Sent from my Nexus 6 using Tapatalk
Latest is LMY48I. Has the partial Stagefright fix. LMY47Z is also Verizon without the fix.
Thank you very much for the info. I am going to restore back to that then and see if I have better luck with battery power.
Sent from my Nexus 6 using Tapatalk
It looks like the boot loader from LMY48I flashed over the top of the beta 3 boot loader woohoo! Next question, if I root the phone/ install TWRP, will I still be notified about OTAs and then I can just reapply rooting and the custom recovery?
thawte said:
It looks like the boot loader from LMY48I flashed over the top of the beta 3 boot loader woohoo! Next question, if I root the phone/ install TWRP, will I still be notified about OTAs and then I can just reapply rooting and the custom recovery?
Click to expand...
Click to collapse
If you root and install TWRP will be notified of OTA but won't be able to flash it till return to full stock again. Can't have anything modified.
Ah gotcha. Thank you for the info
thawte said:
Ah gotcha. Thank you for the info
Click to expand...
Click to collapse
If gonna be modified just forget about OTAs. If have to flash back to stock just flash the updated factory image and be done with it. Save a lot of time and headaches. And don't relock bootloader.
I do like being modified and having some of the features and whatnot... I just got pretty mad earlier because my phone was awake and killing battery the whole time i was at work. I went to go use it and it was completely dead by the end of work

Moto X 2014 (XT1097 Canada) Wont Boot

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 ?

XT1095 Not getting past "Warning, Bootloader unlocked" screen

I was currently running 6.0 update when I flashed twrp 2.8.7.1. This was successful and was able to boot into recovery but when I was rebooting through twrp it asked me to install superuser since I was not rooted so I said yes. After the phone rebooted I was stuck at "warning bootloader unlocked". In an attempt to fix this I tried going back to stock so I flashed stock recovery and image from 5.1 with the same results. So not sure if I put myself in a worse spot or not by trying to flash back to 5.1 or not. I can still get into fastboot but not sure what else to try at this point. Any help would be great at this point.
You need specific kernel to flash superSU.
Suggestion : flash stock 5.1
wywerny said:
You need specific kernel to flash superSU.
Suggestion : flash stock 5.1
Click to expand...
Click to collapse
This would be with the factory images I get from Motorola right?
cjsill9473 said:
This would be with the factory images I get from Motorola right?
Click to expand...
Click to collapse
No, it's a modified kernel, not official. You will find them in the development forum here.
Sent from my XT1095 using Tapatalk
AGISCI said:
No, it's a modified kernel, not official. You will find them in the development forum here.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Alright think I gotcha. Still new to some of this but I see your post regarding stock roms 5.1 link listed below. I should be able to flash through TWRP and be go to go?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
EDIT: Nevermind it is charging now

Categories

Resources