[WARNING] HARD Bricking After Upgrading/Downgrading Then Taking OTA - X 2014 General

EDITED - an XT1095 owner on the 60.16 bootloader from a 5.1 soak bricked when he downgraded to 4.4.4 then took the 5.0 OTA. Several Brazilian XT1097 owners have done the same on the 60.14 or 60.16 bootloader.
THERE IS NO REASON TO DOWNGRADE TO 4.4.4 AFTER TAKING THE 5.1 SOAK IF THE 5.0 STOCK IMAGES ARE AVAILABLE FOR YOUR DEVICE!!!! Just flash the 5.0 stock images instead (system, kernel, modems, baseband, recovery - but not bootloader (motoboot) or partition table (gpt)).
Quite a few posters on the Q&A forum have hard bricked by taking the 5.1 soak, then downgrading to 4.4.4 then taking the 5.0 OTA. And unfortunately, the files that are necessary to restore their bootloaders are not available.
Obviously, taking an OTA after downgrading is dangerous. I would only flash the firmware myself or use Motorola Device Manager to upgrade if you have downgraded in the past.
Update - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I would not take the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.

I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?

The bricks are caused when doing OTA after a downgrade. Not when flashing.
Sent from my XT1095

eqjunkie829 said:
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
Click to expand...
Click to collapse
It happens when they downgrade to 4.4.4 then take the 5.0 OTA as stated in the OP.

AGISCI said:
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Click to expand...
Click to collapse
Right, so I would never take an OTA after downgrading - I would only flash the firmware or use MDM (which is the same as flashing but has checks in it).

,,,

wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
I've gone back and forth a few times on my 1095 and the one thing I notice is my software status always says official.
Click to expand...
Click to collapse
I responded in the other thread.
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
Click to expand...
Click to collapse
The issue is with taking the 5.1 soak, downgrading to 4.4.4 then taking the 5.0 OTA. The OTAs are supposed to fail if your system and recovery are not stock. I am sure the issue is taking the 5.0 update with the 5.1 bootloader and partition table - the OTA updater script does not adequately protect you from a hard brick when you have a higher version BL and PT than the system/recovery version you are running.
You simply cannot downgrade the bootloader despite what some people are saying here - it doesn't happen. Neither fastboot nor mfastboot will downgrade your bootloader. If people were on 5.0 system and then went back to 4.4.4 system and they are still on the 4.4.4 bootloader, then it is because they never successfully flashed the 5.0 bootloader. If they had successfully flashed the 5.0 bootloader, their bootloader would not flash back to the 4.4.4 bootloader using either fastboot or mfastboot.
What is going on with the OTAs that I have seen is that once you upgrade to 5.1 via the soak OTA, you flash back to 4.4.4, which will flash your system/kernel/ramdisk/modems/baseband/recovery back to 4.4.4 but not your bootloader or partition table. Then when they take the 5.0 OTA, which is a patch, the OTA updater script is trying to patch the 5.1 bootloader and partition table as if they were the 4.4.4. This should never happen - it is totally a Motorola mistake. The 5.0 updater script should detect that the person is on a different version bootloader and partition table than 4.4.4 and it should fail rather than hard brick the phone. But it doesn't.
It is infuriating that these people are hard bricking due to Motorola's bad coding and they are being denied warranty service due to having rooted. Root has nothing to do with it - the OTA updater scripts should be coded to fail if the person is on the wrong bootloader and partition table.
wolfu11 said:
The one thing I notice is my software status always says official.
Click to expand...
Click to collapse
Your qe however will show you have rooted in the past if you have ever rooted before.

[,,,

wolfu11 said:
Okay but when I've down graded before and after I sign into kitkat I get a message in the status bar saying to downgrade the firmware I click okay and it reboots. What is that downgrading?
Click to expand...
Click to collapse
Not the bootloader and partition table. I explained that in my other thread.

,,,

wolfu11 said:
That doesn't answer the question, which was what does it downgrade? Anyone know ?
Click to expand...
Click to collapse
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.

JulesJam said:
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
Click to expand...
Click to collapse
Actually you didn't nor did anyone else, I'll just downgrade again and see what that Motorola firmware thing is all about.
No big deal since my phone doesn't seem to brick anyway.

wolfu11 said:
Actually you didn't nor did anyone else,
Click to expand...
Click to collapse
Yeah I did, but I am not repeating it b/c I am tired of spoonfeeding people who don't know basic things yet want to argue with me. You can read the thread or don't. No sweat off of my back either way.
wolfu11 said:
No big deal since my phone doesn't seem to brick anyway.
Click to expand...
Click to collapse
Because you aren't downgrading your BL or PT, lol!
Anyhow, please stop cluttering this thread. I suggest you read and learn what you are flashing then you will know. And please don't encourage other people to do dangerous things with their device when you don't even know what it is that you did with yours.

,,,

wolfu11 said:
Was just curious if you actually downgraded yourself
Click to expand...
Click to collapse
Why would I do something stupid?
wolfu11 said:
or was going by hearsay.
Click to expand...
Click to collapse
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
wolfu11 said:
I won't clutter your thread any longer
Peace
Click to expand...
Click to collapse
Thanks.

JulesJam said:
Why would I do something stupid?
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
Thanks.
Click to expand...
Click to collapse
That clears up a lot .
Thanks

FYI - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I am not taking the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.

Heads up peeps - the XT1095 5.1 soak OTA updater script does not have adequate checks in it to prevent a hard brick if you have downgraded and then attempt to upgrade again.
http://forum.xda-developers.com/showpost.php?p=60941697&postcount=132
So this is just like the Brazilian XT1097 5.0 OTA.

Please read the edit to the OP!!!

This happened to me and I'm so frocking pissed I didn't see this thread beforehand!! Does anyone know if a JTAG service could fix this or how Mich Motorola would charge to repair?

Related

5.0.1 has begun to roll out to the Moto G 2014

Well it looks like 5.0.1 has started to roll out to the Moto G 1st and 2nd generation. I hope it fixes the freezing problem I have on my xt1064 running 5.0
Post here if you receive and/or install 5.0.1, and let us know how it works out for you. Such as improvements, bugs, problems with installation, etc. Please include what model you have.
http://www.androidauthority.com/android-5-0-1-lollipop-moto-g-575758/
Indian soak test user received it yesterday
I think we can all safely assume that now, 5 weeks after starting, the "soak test" is now long over and done with. After all, Motorola stated that Lollipop would be out on the Moto G *before* the end of 2014... and guess what? Only 12 days of that left. Unless they're into cutting it fine, this IS the final release, folks.
gnubash said:
I think we can all safely assume that now, 5 weeks after starting, the "soak test" is now long over and done with. After all, Motorola stated that Lollipop would be out on the Moto G *before* the end of 2014... and guess what? Only 12 days of that left. Unless they're into cutting it fine, this IS the final release, folks.
Click to expand...
Click to collapse
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Derfderk said:
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Click to expand...
Click to collapse
What does that matter, when it's all Lollipop, after all? Would you prefer they release 5.0 and not a more updated, polished release version instead? They'll release on time, believe me.
Yep just got it, lets see what it shall bring!
Sent from my SM-P600 using XDA Premium HD app
One vital piece of information that people seem to be overlooking, once THEY get Lollipop on THEIR device, is this:
Mention your country please
Have successfully upgraded to 5.01 on ma XT1033 BRAZ FRAMEWORK Soak LP N now waiting for XT1068.. Its awesome n more smoother now..
sent From My XT1033{LP} using TapatalK
gnubash said:
One vital piece of information that people seem to be overlooking, once THEY get Lollipop on THEIR device, is this:
Mention your country please
Click to expand...
Click to collapse
It would also be nice if people would also make note of the baseband version associated with each release. There already been enough tears from fools flashing baseband firmware willy-nilly.
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25 which I assume is 5.0.1. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
pastorbob62 said:
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25 which I assume is 5.0.1. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Click to expand...
Click to collapse
Correct
Android The Greek said:
Correct
Click to expand...
Click to collapse
To which question?
Are European buyers still being ignored? XT1068: no MFN, no update of any kind here. If I am interpreting Motorola forum correctly, they haven't released anything in the EU, not even a soak test.
Derfderk said:
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Click to expand...
Click to collapse
Correct, 5.0.2 has been released for Nexus 7 today.
And PLEASE, PLEASE before updating go here and try to capture the ota.
kzakhar said:
Are European buyers still being ignored? XT1068: no MFN, no update of any kind here. If I am interpreting Motorola forum correctly, they haven't released anything in the EU, not even a soak test.
Click to expand...
Click to collapse
I think Motorola secretly hate us because we can unlock our devices and still make a warranty claim if the hardware fails.
rufflove said:
I think Motorola secretly hate us because we can unlock our devices and still make a warranty claim if the hardware fails.
Click to expand...
Click to collapse
You could be right.
I got this phone happy in the knowledge I'll always be running (nearly) the latest clean version of Android, instead I have a phone with a memory management issue running at least a month behind other continents.
Tongue in cheek aside, I do have some suspicions.
It stands to reason that the people most likely to join the MFN are those who like to tinker and who are eager to receive updates. These people are also the most like to unlock the bootloader. If something goes awry during an OTA roll-out test and the user cannot resolve the issue, support from Motorola can be requested, potentially resulting in a warranty claim, unless the device has been unlocked and was purchased outside of the EU... It therefore seems logical that Motorola would not do soak tests in the EU, where possible: It reduces the blowback in the unlikely event that there is a serious bug in the update.
rufflove said:
Tongue in cheek aside, I do have some suspicions.
It stands to reason that the people most likely to join the MFN are those who like to tinker and who are eager to receive updates. These people are also the most like to unlock the bootloader. If something goes awry during an OTA roll-out test and the user cannot resolve the issue, support from Motorola can be requested, potentially resulting in a warranty claim, unless the device has been unlocked and was purchased outside of the EU... It therefore seems logical that Motorola would not do soak tests in the EU, where possible: It reduces the blowback in the unlikely event that there is a serious bug in the update.
Click to expand...
Click to collapse
That sounds like the most plausible reason they may have, if they have one. To be honest, I've got better things to think about than when a frivolous software update arrives for a non-cricital device, but your thoughts certainly are rational ones
Well I was part of the xt1069 Brazilian soak test and I have to say it's a bad joke. A lot of users didn't get the update, there was almost no support or even feedback from Motorola in the forum. And to finish it off, they had an issue with their forum software that got all comments deleted. I don't think EU users are missing much

[Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop

If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for Verizon Samsung Galaxy Note 4 (N910V):
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP​
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Hibby- said:
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
Click to expand...
Click to collapse
droidx2.3.3 said:
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
I believe your looking for "SDM"
rhilway said:
I believe your looking for "SDM"
Click to expand...
Click to collapse
You are correct.
Manually updating
hsbadr said:
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
Click to expand...
Click to collapse
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Nameless crowd face said:
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Click to expand...
Click to collapse
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
hsbadr said:
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
Click to expand...
Click to collapse
Thank you again man
samhainww said:
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
Click to expand...
Click to collapse
I did last night, just use Odin to flash the NJ5 firmware, when it tries to boot the first time it will bootloop. Pull the battery, replace the battery and boot to recovery (vol up+home+power) then wipe data. The phone will boot to the setup wizard for KK.
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Click to expand...
Click to collapse
Nameless crowd face said:
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+1
Another example, some Note 3 users fall into the trap of 4.4.4 OTA update & with no option to downgrade, they lost root, custom TW ROMs, and almost everything. Now, they're waiting with Note 4 users for a root method to rejoin the party while Note 3 on 4.4.2 can be rooted using TowelRoot.
Which tool?
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
All of the debloat tools that I find require root, which are you using?
There's a script that someone wrote to disable Ota and debloat. It doesn't need root. Sacher around on here for it
So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?
As of now it makes no difference.
Stupid question, but how do you turn off automatic OTA on lollipop?

how to root 5.0 boe1?

So my old phone had to get warranty replaced and I got sent a refurbished phone already with boe1. Is it rootable? I can't downgrade to kitkat and use that method cause Odin fails. Read too many threads with bad info so I'm just making one here if it's possible what's the tutorial.
For now OE1 is unrootable and can't be downgraded. Once the full tar is released it might be possible to root, but possibly not.
Take it back to them and say you dont like this version, its worth a try
Well I already quoted myself and this post once already so why not do it again? lol
Dudash said:
I'm starting to wonder if Verizon pulled the OE1 update..
Source
Notice the date of the official software update PDFs:
OD5: benefits-galaxy-s5-6-10-15.pdf
OE1: benefits-galaxy-s5-6-29-15.pdf
OD5: benefits-galaxy-s5-7-7-15.pdf
For some reason, they are saying the newest software available is OD5 again. This would explain why the OE1 .tar hasn't surfaced yet.
This doesn't really help people that already updated using the OE1 OTA because they're locked on it now. I'd recommend that those people call verizon and complain because they may send you another phone.
Click to expand...
Click to collapse
So MuminMohamed's idea may not be a bad one.
Is the OE1 stilll Un rootable? - NEVERMIND.. found the answer to my DUMB ASS question.

Updating to lollipop

I have the G900A (Unlocked) but I'm on the T-Mobile Network and I'd like to update from 4.4.4 to lollipop
From what I understand AT&T and T-Mobile have both shipped the lollipop updates but I can't seem to find a way to update my phone.
Going through settings->About->Software Updates tells me there are no updates.
How can I go about updating?
Thanks.
You can look on sammobile for the latest firmwares, but as far as i know the latest for G900A is 4.4.2
In the att s5 section there's threads with the files for it, I think you get the official update and do it through the stock recovery, I've never done it myself so I can't help, sorry :s
Sent from my SAMSUNG-SM-G900A using Tapatalk
ozymandius95 said:
I have the G900A (Unlocked) but I'm on the T-Mobile Network and I'd like to update from 4.4.4 to lollipop
From what I understand AT&T and T-Mobile have both shipped the lollipop updates but I can't seem to find a way to update my phone.
Going through settings->About->Software Updates tells me there are no updates.
How can I go about updating?
Thanks.
Click to expand...
Click to collapse
You could try this
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
But bear in mind, once you are on LP, you can not downgrade to KK again afaik
So things like root might be an issue (Haven't had enough coffee yet to remember 100%) do some reading up first
*Detection* said:
You could try this
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
But bear in mind, once you are on LP, you can not downgrade to KK again afaik
So things like root might be an issue (Haven't had enough coffee yet to remember 100%) do some reading up first
Click to expand...
Click to collapse
Yikes.
I've never cared for rooting before, but I like to keep current on the latest firmware.
So if I understand this correctly I'll be stuck at LP when I get there, even after marshmallow rolls out, yes?
ozymandius95 said:
Yikes.
I've never cared for rooting before, but I like to keep current on the latest firmware.
So if I understand this correctly I'll be stuck at LP when I get there, even after marshmallow rolls out, yes?
Click to expand...
Click to collapse
No, you can upgrade firmwares, so MM will be fine, but from what I remember with that model, and a few other S5s, you can not downgrade due to the bootloader being locked once you update to Lollipop
If you read the whole thread (Link top right) of that link I posted - you'll see me trying to help another G900A member with the same problem

Fastboot ROM?

Can someone post the links for the latest fastboot ROMs for potter? I've been looking for them for two days and I couldn't find them. It'd be nice if someone could post full fastboot ROMs of all variants or if there's already a thread in here, kindly let me know. I'm looking for the fastboot ROM for Indian variant and yes I have looked a free threads here.
psychopac said:
Can someone post the links for the latest fastboot ROMs for potter? I've been looking for them for two days and I couldn't find them. It'd be nice if someone could post full fastboot ROMs of all variants or if there's already a thread in here, kindly let me know. I'm looking for the fastboot ROM for Indian variant and yes I have looked a free threads here.
Click to expand...
Click to collapse
We don't have it... All Moto firmware is leaked, they don't just give it away, and we might get it a few weeks after the OTA comes out, months, or sometimes never, we don't know.
If/when we get it, I'm sure it I'll be posted here and at http://firmware.center
acejavelin said:
We don't have it... All Moto firmware is leaked, they don't just give it away, and we might get it a few weeks after the OTA comes out, months, or sometimes never, we don't know.
If/when we get it, I'm sure it I'll be posted here and at http://firmware.center
Click to expand...
Click to collapse
So if I update to the latest version and something goes wrong and I flash the older build, will everything be fine? I heard that downgrading causes problems in Motos. Is that true?
psychopac said:
So if I update to the latest version and something goes wrong and I flash the older build, will everything be fine? I heard that downgrading causes problems in Motos. Is that true?
Click to expand...
Click to collapse
I am not going to lie, it is true in some cases... we know that you cannot downgrade the bootloader, no matter what you do, so sometimes if you downgrade everything else but gpt.bin and bootloader.img (two things that can't be downgraded, partition table and bootloader), it has been known to cause bricking in some devices if you take an OTA later, and sometimes it doesn't.
For example, the Moto X Style/Pure Edition you could upgrade and downgrade on a whim between Lollipop and Marshmallow with not problem, take OTA's or whatever and it was fine... Then along came Nougat... if you downgraded from Nougat to Marshmallow, then took the Nougat OTA again it was instant hard brick (completely unrecoverable). My point is we don't know until someone tries it... :/
acejavelin said:
I am not going to lie, it is true in some cases... we know that you cannot downgrade the bootloader, no matter what you do, so sometimes if you downgrade everything else but gpt.bin and bootloader.img (two things that can't be downgraded, partition table and bootloader), it has been known to cause bricking in some devices if you take an OTA later, and sometimes it doesn't.
For example, the Moto X Style/Pure Edition you could upgrade and downgrade on a whim between Lollipop and Marshmallow with not problem, take OTA's or whatever and it was fine... Then along came Nougat... if you downgraded from Nougat to Marshmallow, then took the Nougat OTA again it was instant hard brick (completely unrecoverable). My point is we don't know until someone tries it... :/
Click to expand...
Click to collapse
That's a bummer. Anyways I hope that no one bricks their phone

Categories

Resources