Related
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
ericizzy1 said:
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
Click to expand...
Click to collapse
Yes and No
No you can not flash the complete 4.2.2 PCU package it will fail because you can't downgrade the bootloader
Yes because you can flash everything but the bootloader and it will take but if you accidentally take a OTA. you will brick your device.
but if you are able to unlock your bootloader then why would you want to downgrade. with a unlocked bootloader you will be able to root 4.4.2 with no issues
because when I was on 4.4, I had some battery consumption and heating issues also bluetooth was not perfect, I just wanted to make sure I have a way back To 4.2.2
also, not being able to downgrade the bootloader, in which way does this affect me going back to four point 4.2.2?
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
dray_jr said:
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Yup that is correct
Sent from my XT1056 using XDA Premium 4 mobile app
ericizzy1 said:
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Click to expand...
Click to collapse
No. Once you start mixing bootloader versions with system file versions (i.e. 4.4.2 bootloader with 4.2.2 system files), RSD Lite won't work. You will have to use a command line and mfastboot.exe to manually flash each partition.
And I actually tried to run 4.2.2 (post camera update) system files with a 4.4.2 bootloader and it would not boot; however, 4.4 system files do work with a 4.4.2 bootloader.
This has actually been discussed at great length and detail in this forum and A LOT of people were bricking their phones playing around with bootloader versions, just like you are talking about doing. At one point there was a sticky dedicated to it, but its since disappeared from the board for some reason.
To put it simply, please don't start mixing bootloader versions with system files. If you like 4.2.2, don't upgrade to 4.4.2. If you are on 4.4, then you can still downgrade to 4.2.2 (post camera update version). Do that and stay there. But if you upgrade to 4.4.2, don't fool around with it and start trying to downgrade. There is no point, and you will likely end up bricking your phone.
It's your phone, so do what you want, but you have been warned (by someone with personal experience by the way). If you do brick it, please don't start another "OMG! HELP ME!! I BRICKED MY PHONE!!" thread. There's plenty of those already floating around here. :good:
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
I was on verizon galaxy nexus for over two years. I wanted better radio performance, so i got a moto x. Nexus bootloader was unlocked and I was a bit of a crackflasher.
I have unlocked bootloader on moto x and installed twrp and supersu.
I did all this before taking firmware update, so I can see how it runs on 4.2.2. I ran it awhile and wanted to try kk out. I downloaded the ota update and went to have it autoflash, but instead, it rebooted into twrp.
so, I have downloaded rsdlite (i used to have a droid x, so i am familiar) and will get the 4.4.2 firmware downloaded too.
Q: can i flash aosp 4.4.2 roms with my x in it's 4.2.2 state or do i need the 4.4.2 update first?
Q: are there standalone radio (baseband) files around I can download and flash in recovery?
Thx!
RSDLite when you have an unlocked bootloader?
Grab the 4.4.2 sbf, extract the individual imgs, then flash with fastboot.
You will find the moto x is no nexus I'm afraid. Not a flashaholics phone for sure. There's just a few ROMs....not a lot of mods, and whatever you do, once on 4.4.2....never downgrade. It can cost you your phone. Dev edition or not.
Just a heads up!!
BTW....not knocking it....I still recommend it to everyone I know!!! Except the couple rooting and tinkering types....then I recommend the N5 hands down.
update : upgraded to kk firmware with rsdlite. bootloader still unlocked. I am on Eclipse now and enjoying it.
Sent from my XT1060 using Tapatalk
kochoid said:
update : upgraded to kk firmware with rsdlite. bootloader still unlocked. I am on Eclipse now and enjoying it.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I moved from a galaxy nexus last fall to the X. I definitely flashed constantly... now with an unlocked bootloader (MotoMaker!) I don't have the need. Xposed is all you really need to get features you want, unless you just like to tinker.
Hi, I already have te brazilian 5.1 OTA installed on my xt1097 but in my country they released 5.1 few days ago. I wonder if I could have my country softwt but the only roblem is that I have to downgrade to 4.4.4 and the directly install the OTA to 5.1 because they jumped directly to 5.1 in Argentina.
I want to know if there is any risk of hardbrick if do this in the proper mode (I have the bootloader unlocked and I know how to downgrade but beacause it is to 4.4.4 I have the doubt o fwhat could happen if I do it).
I thin that this could be very usefull to other users that are in the same situation that me.
Thanks in advance!
Yea there is a risk of bricking. The downgrade to 4.4.4 then taking OTA's has caused many brazilian moto x to brick.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yea there is a risk of bricking. The downgrade to 4.4.4 then taking OTA's has caused many brazilian moto x to brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Even if the ota update is to 5.1 directrly?
I´m asking becasue i have understood that the problem was due to the vertsion of the bootloader.
maxibat92 said:
Even if the ota update is to 5.1 directrly?
I´m asking becasue i have understood that the problem was due to the vertsion of the bootloader.
Click to expand...
Click to collapse
The issue is due to the boot loader version. The OTA updater script sometimes fails to check for the boot loader status and flashes/bricks anyway. There is no guarantee if you downgrade to 4.4.4 and take 5.1 OTA that you will brick, but there is no guarantee that you will not either. Just take it through MDM and be safe. MDM will do the proper checks.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Just yesterday I had made a downgrade from 5.1 to 4.4.4 PE because WIFI issues.
with no brick at all.
bunglemx said:
Just yesterday I had made a downgrade from 5.1 to 4.4.4 PE because WIFI issues.
with no brick at all.
Click to expand...
Click to collapse
But my point is if there would be any risk of brick when i update via ota directly to 5.1.
bunglemx said:
Just yesterday I had made a downgrade from 5.1 to 4.4.4 PE because WIFI issues.
with no brick at all.
Click to expand...
Click to collapse
The brick is not when you downgrade. The brick happens when you downgrade then take an OTA. Don't take an OTA or you risk bricking it.
Sent from my XT1095 using Tapatalk
Oh sorry my mistake. Yes, most probably is its gonna semibrick if you take the ota
xKroniK13x said:
The issue is due to the boot loader version. The OTA updater script sometimes fails to check for the boot loader status and flashes/bricks anyway. There is no guarantee if you downgrade to 4.4.4 and take 5.1 OTA that you will brick, but there is no guarantee that you will not either. Just take it through MDM and be safe. MDM will do the proper checks.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
You are saying that if I do the downgrade succesfully and then I upgrade to 5.1 by MDM y will have 5.1 with no brick risk ?
maxibat92 said:
You are saying that if I do the downgrade succesfully and then I upgrade to 5.1 by MDM y will have 5.1 with no brick risk ?
Click to expand...
Click to collapse
Correct. Because MDM doesn't upgrade the phone like an OTA. MDM flashes the complete images.
Sent from my XT1095 using Tapatalk
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.