Database Develop

[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] Lollipop to KitKat

I just got my new Moto X 2014 2 days ago. It came with KitKat installed on it. I remember that on the Moto X 2013 that downgrading caused a lot of bricks. Is this the case with the new 2014 Moto X? Also, has anybody downgraded, then taken the OTA again and it still works?
During the downgrade process would I need to flash all the parts? Or do I need to skip some?

Have you read this thread? http://forum.xda-developers.com/moto-x-2014/help/lollipop-to-kit-kat-t2986044

Yes I have but it didn't answer all my questions. For example if upgrading via ota will cause a brick? If it's necessary to flash all files or if they all can even be flashed.
Sent from my XT1095 using Tapatalk

AGISCI said:
Yes I have but it didn't answer all my questions. For example if upgrading via ota will cause a brick? If it's necessary to flash all files or if they all can even be flashed.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I downgraded to kitkat and took the OTA to lollipop with no issues. When downgrading, you don't really have to skip any commands. If you try to flash an old bootloader (as was the case when I downgraded to kitkat after getting the newer bootloader from the OTA, well, I think it was a newer bootloader anyways), it will just fail to flash. No harm done, at least not on my XT1095). You can skip flashing the bootloader altogether, which is what I did the first time I downgraded to kitkat, and I had no issues.

Thank you, I took the plunge and installed lollipop. I was worried about downgrading since I was not sure if everything would work or not. So far so good.
Sent from my XT1095 using Tapatalk

I would like to know if the process is the same downgrading back to kitkat from lollipo 5.1???

Software Status: Modified - Can it be changed back to Software Status: Official?

The phone is a XT1095; Pure Edition
So I unrooted the phone and flash the stock 5.0 image from Motorola.
In the bootloader, it's still showing that the software was modified even though the phone has been unrooted.
I've wiped cache and did a factory reset and still no change.
Any ideas? I'm sending the phone back for RMA and don't want Motorola rejecting my RMA because of the software status.

phamine said:
So I unrooted the phone and flash the stock 5.0 image from Motorola.
In the bootloader, it's still showing that the software was modified even though the phone has been unrooted.
I've wiped cache and did a factory reset and still no change.
Any ideas? I'm sending the phone back for RMA and don't want Motorola rejecting my RMA because of the software status.
Click to expand...
Click to collapse
What model do you have? XT10??
Sent from my XT1095 using Tapatalk

phamine said:
So I unrooted the phone and flash the stock 5.0 image from Motorola.
In the bootloader, it's still showing that the software was modified even though the phone has been unrooted.
I've wiped cache and did a factory reset and still no change.
Any ideas? I'm sending the phone back for RMA and don't want Motorola rejecting my RMA because of the software status.
Click to expand...
Click to collapse
You need to reflash firmware.

I'm using a x1095.
I reflashed the stock firmware that is posted on Motorola's webpage.

phamine said:
I'm using a x1095.
I related the stock firmware that is posted on Motorola's webpage.
Click to expand...
Click to collapse
Don't worry then. The XT1095 does not lose it's warranty because it is unlocked nd modified, it is the "pure edition".
Sent from my XT1095 using Tapatalk

This problem have one solution.
1. Restore STOCK firmware with ADB o RSDLITE
2. Install one update with MOTOROLA OTA
only then are transform "modified" to "official"

Sindrome123 said:
This problem have one solution.
1. Restore STOCK firmware with ADB o RSDLITE
2. Install one update with MOTOROLA OTA
only then are transform "modified" to "official"
Click to expand...
Click to collapse
Yep, I noticed the same thing. I wonder why flashing stock 5.0 from Motorola doesn't set the status to official.

I don't now. But this is the only mode for change the status modified to oficial.

AGISCI said:
Don't worry then. The XT1095 does not lose it's warranty because it is unlocked nd modified, it is the "pure edition".
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I thought if it was only the bootloader was unlock that would qualify? So with a Pure Edition Software Modified would qualify as well?
Sindrome123 said:
This problem have one solution.
1. Restore STOCK firmware with ADB o RSDLITE
2. Install one update with MOTOROLA OTA
only then are transform "modified" to "official"
Click to expand...
Click to collapse
So fastboot method wouldn't work for #1?
I'll try to find an OTA that would work with the stock 5.0 image.
Moto X(2nd Gen) Pure Edition:
L-5.0-LXE22.46-11 TMO
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Right now if I check for an update on the phone or use Motorola Device Manager, it doesn't pick up any updates.

Modified does not matter on the XT1095. The whole point in unlocking the bootloader is to modify it... So yes being modified ia covered.
Sent from my XT1095 using Tapatalk

bricked?

ok, what happened:
I were on 4.4.4 stock kitkat rom with root. i wanted to update to 5.0 lollipop and i used the moto x 2014 multitool package. i pressed 6 for sideloading 5.0 update.zip every operation turned out successful. and i pressed reboot device when it was done. but my phone wouldn't turn on. i have tried turning it on into bootloader, but then the green light lights up and the two IR led's on the right side light up. i would really appreciate some help!

ulriks9 said:
ok, what happened:
I were on 4.4.4 stock kitkat rom with root. i wanted to update to 5.0 lollipop and i used the moto x 2014 multitool package. i pressed 6 for sideloading 5.0 update.zip every operation turned out successful. and i pressed reboot device when it was done. but my phone wouldn't turn on. i have tried turning it on into bootloader, but then the green light lights up and the two IR led's on the right side light up. i would really appreciate some help!
Click to expand...
Click to collapse
Does your computer detect the phone?
Have you ever downgraded your phone?
Sent from my XT1095 using Tapatalk

AGISCI said:
Does your computer detect the phone?
Have you ever downgraded your phone?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thankyou for answering.
my computer detects it as QHSUSB_BULK. And yes, i downgraded it from 5.1 to 4.4.4 by flashing stock firmware.

You will have to send it to motorola for repair, there is no way for you to fix it yourself.
The problem is you downgraded your phone, after a downgrade you cannot take an OTA ever or it will brick.
Sent from my XT1095 using Tapatalk

AGISCI said:
You will have to send it to motorola for repair, there is no way for you to fix it yourself.
The problem is you downgraded your phone, after a downgrade you cannot take an OTA ever or it will brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
no, sorry. i was on a cm12.1 rom and then i flashed stock firmware. and then i tried to update

You have hardbricked your Moto X 2014...

ulriks9 said:
no, sorry. i was on a cm12.1 rom and then i flashed stock firmware. and then i tried to update
Click to expand...
Click to collapse
Did your phone have stock 5.0 or 5.1 before you installed CM? If so, then yes you did downgrade when you went to 4.4.4 which is why it is now bricked. That message that says QHSUSB_BULK means you are bricked, you will have to send it to motorola.
Sent from my XT1095 using Tapatalk

AGISCI said:
Did your phone have stock 5.0 or 5.1 before you installed CM? If so, then yes you did downgrade when you went to 4.4.4 which is why it is now bricked. That message that says QHSUSB_BULK means you are bricked, you will have to send it to motorola.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
how much will they charge me?

AGISCI said:
Did your phone have stock 5.0 or 5.1 before you installed CM? If so, then yes you did downgrade when you went to 4.4.4 which is why it is now bricked. That message that says QHSUSB_BULK means you are bricked, you will have to send it to motorola.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
and will this work?
https://www.youtube.com/watch?v=FdrdWqaXUBE

Nope. That tutorial won't work.
To unbrick the Moto X 2014 we need the blankflash files, but Motorola didn't release it yet.
If you send it to repair they will replace the MB.

Quetzalcoalt_Lp said:
Nope. That tutorial won't work.
To unbrick the Moto X 2014 we need the blankflash files, but Motorola didn't release it yet.
If you send it to repair they will replace the MB.
Click to expand...
Click to collapse
so is there no way at all to fix it?

Not, at least until Motorola release the files we need.
You can post in motorolaforums and ask for the files in this thread https://forums.motorola.com/posts/b6cb5537f5

Quetzalcoalt_Lp said:
Not, at least until Motorola release the files we need.
You can post in motorolaforums and ask for the files in this thread https://forums.motorola.com/posts/b6cb5537f5
Click to expand...
Click to collapse
one of the guys mentioned that the files were downloadable for the pure edition, is that true?

ulriks9 said:
one of the guys mentioned that the files were downloadable for the pure edition, is that true?
Click to expand...
Click to collapse
No it is not true, those files are not for our phone, they won't work. Until they are leaked, the only thing that can be done is send it to them to fix it.
Sent from my XT1095 using Tapatalk

But can I use a jig?
Sent from my GT-N5110 using XDA Free mobile app

ulriks9 said:
But can I use a jig?
Sent from my GT-N5110 using XDA Free mobile app
Click to expand...
Click to collapse
i also have the same question, anyone has tried using a jig?

jig is for samsung phones to get into downloader mode. We have fastboot, not the same system. So no it will not work.
We have the tools we need, the problem is we don't have the signed files from motorola that are needed to flash. So until those files are leaked, you have no choice but to send it to motorola for the repair.
Sent from my XT1095 using Tapatalk

AGISCI said:
jig is for samsung phones to get into downloader mode. We have fastboot, not the same system. So no it will not work.
We have the tools we need, the problem is we don't have the signed files from motorola that are needed to flash. So until those files are leaked, you have no choice but to send it to motorola for the repair.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
will this work?
http://www.usoftsmartphone.com/t300062.html

No that won't work. That page has an error those files are for the first gen moto x. We have tried what that page says and it does not work with our second gen phones.
Sent from my XT1095 using Tapatalk

Have you got this figured out? Same thing happened to me,and though under EU law these asshats have to fix the phone, they refused to do so after I sent it in for warranty repair. Now Ive got a 300 euros moto paperweight.
Jtag work? Can anyone recommend a phone repair service?

Unable to upgrade to 6.0-marshmallow

Hi,
I'm trying to upgrade my Moto X 2014 to Marshmallow. The OTA upgrade appeared last week, but fails without any error message.
When the devices was new, I unlocked the boot and rooted it. The first upgrade (5.0) installed without any problem, but I chose not to root it anymore.
Upgrade to 5.1 failed. It worked after I reflashed the recovery.img(following idea from Q18 in http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769). The same happened with the Stagefright update some time later. Now, the Marshmallow upgrade is available, but reflashing recovery.img is no longer working. It simply fails without any meaningful message. Could someone help me?
Tks,
Roberto
Device:
Moto X 2014, Brazilian retail version, version 23.16.2.victara_retbr.retbr.en.BR.retbr, version number LPE23.32-14.2

rgreiner said:
Hi,
I'm trying to upgrade my Moto X 2014 to Marshmallow. The OTA upgrade appeared last week, but fails without any error message.
When the devices was new, I unlocked the boot and rooted it. The first upgrade (5.0) installed without any problem, but I chose not to root it anymore.
Upgrade to 5.1 failed. It worked after I reflashed the recovery.img(following idea from Q18 in http://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769). The same happened with the Stagefright update some time later. Now, the Marshmallow upgrade is available, but reflashing recovery.img is no longer working. It simply fails without any meaningful message. Could someone help me?
Tks,
Roberto
Device:
Moto X 2014, Brazilian retail version, version 23.16.2.victara_retbr.retbr.en.BR.retbr, version number LPE23.32-14.2
Click to expand...
Click to collapse
Flash the stock 5.1 firmware to get completely back to stock, then try again.
Sent from my XT1095 using Tapatalk

AGISCI said:
Flash the stock 5.1 firmware to get completely back to stock, then try again.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Isn't there a way to avoid it? I would like to avoid fully resetting the phone.
Tks,
Roberto

rgreiner said:
Isn't there a way to avoid it? I would like to avoid fully resetting the phone.
Tks,
Roberto
Click to expand...
Click to collapse
No there is no other way. An OTA fails if you are not 100% stock. So that means no root, no xposed, no custom kernels, no modifications to anything that is in system. If even one thing is modified it WILL fail. So the solution is to go back to 100% stock by flashing the full firmware.
Sent from my XT1095 using Tapatalk

AGISCI said:
No there is no other way. An OTA fails if you are not 100% stock. So that means no root, no xposed, no custom kernels, no modifications to anything that is in system. If even one thing is modified it WILL fail. So the solution is to go back to 100% stock by flashing the full firmware.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
That's strange. When I upgraded to 5.1 and 5.1/stagefright, I had exactly the same setup: Boot unlocked, no root. It upgraded fine after just reflashing 'recovery.img'. Actually, when I upgraded from 4.4 to 5.0, the phone was rooted, and yet it upgraded perfectly.
Roberto

rgreiner said:
That's strange. When I upgraded to 5.1 and 5.1/stagefright, I had exactly the same setup: Boot unlocked, no root. It upgraded fine after just reflashing 'recovery.img'. Actually, when I upgraded from 4.4 to 5.0, the phone was rooted, and yet it upgraded perfectly.
Roberto
Click to expand...
Click to collapse
Again as I stated, something is modified. In the OTA it checks for modifications, if it finds something modified it fails and exits without upgrading it. So if you want to take the upgrade you need to flash back to stock.
This forum is filled with posts and topics of people having to unroot to get the OTAs to work. So why it worked for you, no idea, since you are the only person I have ever seen who has stated that it worked while rooted. According to every other post on this forum, OTA fails when rooted...
Sent from my XT1095 using Tapatalk

AGISCI said:
Again as I stated, something is modified. In the OTA it checks for modifications, if it finds something modified it fails and exits without upgrading it. So if you want to take the upgrade you need to flash back to stock.
This forum is filled with posts and topics of people having to unroot to get the OTAs to work. So why it worked for you, no idea, since you are the only person I have ever seen who has stated that it worked while rooted. According to every other post on this forum, OTA fails when rooted...
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok. But still, why fully-reflashing? As I said, my phone is NOT rooted since 4.4. It's only boot unlocked, and both 5.0 and 5.1 where installed and no modifications made after that.

rgreiner said:
Ok. But still, why fully-reflashing? As I said, my phone is NOT rooted since 4.4. It's only boot unlocked, and both 5.0 and 5.1 where installed and no modifications made after that.
Click to expand...
Click to collapse
Look, somewhere in your phone there IS something that is NOT stock. What it is, we don't know. The ONLY way for you to take an OTA is to be 100% stock, if not it will fail. So the only solution is to get your phone to 100% stock to take the OTA, which means flash the full firmware. If you don't want to flash the full firmware then you will stay on 5.1.
Sent from my XT1095 using Tapatalk

AGISCI said:
Look, somewhere in your phone there IS something that is NOT stock. What it is, we don't know. The ONLY way for you to take an OTA is to be 100% stock, if not it will fail. So the only solution is to get your phone to 100% stock to take the OTA, which means flash the full firmware. If you don't want to flash the full firmware then you will stay on 5.1.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok,
if that's the only route left, I will try it.
Tks,
Roberto

rgreiner said:
Ok,
if that's the only route left, I will try it.
Tks,
Roberto
Click to expand...
Click to collapse
Ok. After backing-up everything I needed, I flashed the stock 5.1 image. Reinstalled all apps (actually, everything reinstalled automatically), restored backups, and then tried the upgrade. Both stagefright and marshmallow upgrades worked fine, and 6.0 is running fine.
Tks.