Related
I'm using Moto XT1060 and on 4.4.4. I want to flash custom ROM, is there any ways to do this? Because i saw that must be on 4.2.2 to use safestrap recovery, and downgrade would be brick ? So anyway for me to go on ?
Once you are on 4.4.4 downgrading will result in a brick! The bootloader can NOT be downgraded.
Travisdroidx2 said:
Once you are on 4.4.4 downgrading will result in a brick! The bootloader can NOT be downgraded.
Click to expand...
Click to collapse
Bad news !
Yup, anything after and including 4.4.2 will brick if downgraded. This even goes for my Dev edition
Have you looked into the China middleman? He seems to be becoming somewhat less reliable but you may be able to get an unlock code which would allow you to flash unlocked versions of ROMs rather than being limited to safestrap versions. Either that or wait to see if sunshine gets updated to work on 4.4.4.
To answer your question directly. Do NOT downgrade. While there is SOME conflicting info here, the overwhelming consensus is that downgrading will result in a brick either now or during a future upgrade.
cntryby429 said:
Have you looked into the China middleman? He seems to be becoming somewhat less reliable but you may be able to get an unlock code which would allow you to flash unlocked versions of ROMs rather than being limited to safestrap versions. Either that or wait to see if sunshine gets updated to work on 4.4.4.
To answer your question directly. Do NOT downgrade. While there is SOME conflicting info here, the overwhelming consensus is that downgrading will result in a brick either now or during a future upgrade.
Click to expand...
Click to collapse
Curious what the conflicting information is?
cntryby429 said:
To answer your question directly. Do NOT downgrade. While there is SOME conflicting info here, the overwhelming consensus is that downgrading will result in a brick either now or during a future upgrade.
Click to expand...
Click to collapse
Travisdroidx2 said:
Curious what the conflicting information is?
Click to expand...
Click to collapse
The conflicting information is due to a few things...
1. It usually revolve around not explaining that due to security and other issues, GPT.BIN and MOTOBOOT.IMG can't be downgraded properly. And this causes a wide variety of issues.
2. We've had some who downgrades, doesn't brick then declares it "SAFE" for all... without taking into consideration what happens when future OTA gets installed (which is brick).
3. We've seen some try to be "fancy" and use mfastboot to downgrade everything but GPT.BIN and MOTOBOOT.IMG, the phone reboots and may generally work, so its declared "safe"... but doesn't explain there have been issues (like when on 4.4.2 and flashing down to 4.4 this way, go to Settings -> Security kicks you out)... and also doesn't take into consideration what happens when parts of the phone are miss-matched when a future OTA is taken and gets installed (bricks or on occasion user gets lucky and it just fails to install instead)... and this also poses a challange returning to a 100% consistent state.
4. We've seen those who don't explain that trying to downgrade with RSDLite will likely fail or will immediately brick your phone (which has happened). Or at least convey some kind of warning.
and more..
In most/all of these cases, the person who "tested it" and says "Its safe" fails to explain the risks and fails to state there are MANY threads and Posts of users who HAVE BRICKED while trying to downgrading, or at some point after downgrading, etc.
So, rather than seeing a ton of caveats, conditions, etc you'll just see most of give the "DO NOT DOWNGRADE!!" warnings.
I have read all of those "safe" way to downgrade that eventually leads to a brick. That is why I tell people do not downgrade even though I know it is the gpt.bin and bootloader security that can not be downgraded. I was just curious if that was the conflicting information or if it was me telling him that you will brick if downgrading was the conflicting information.
Travisdroidx2 said:
I have read all of those "safe" way to downgrade that eventually leads to a brick. That is why I tell people do not downgrade even though I know it is the gpt.bin and bootloader security that can not be downgraded. I was just curious if that was the conflicting information or if it was me telling him that you will brick if downgrading was the conflicting information.
Click to expand...
Click to collapse
Sorry if that wasn't clear. By "here" I meant that conflicting info can be found here in the Moto X xda forum, not in your post. Now that these people have recklessly posted stuff trying to say that you can downgrade, I think it's worth acknowledging that the misinformation exists rather than just saying "you can't, period." That way the casual reader doesn't see one of those posts and think he's about to get away with something that other (read, capable & most knowledgeable) folks have said "just can't be done." That's all. No confrontation intended unless you count those yahoos trying to say it's safe.
cntryby429 said:
Sorry if that wasn't clear. By "here" I meant that conflicting info can be found here in the Moto X xda forum, not in your post. Now that these people have recklessly posted stuff trying to say that you can downgrade, I think it's worth acknowledging that the misinformation exists rather than just saying "you can't, period." That way the casual reader doesn't see one of those posts and think he's about to get away with something that other (read, capable & most knowledgeable) folks have said "just can't be done." Today's all. No confrontation intended unless you count those yahoos trying to say it's safe.
Click to expand...
Click to collapse
Thanks for the response! I see your point. It is a good one to point out because we still see people ending up with a brick because they followed what someone told them was safe. Or they just don't read the warnings first.
I'll try to sum this up...
No, you can't downgrade. Unless you have money sitting in your pocket for a new device... Which more times than not is what you'll need to do.
2 new downgrade brick threads today.
Still wanna try? ?
[solved]
Tried to update the phone to 5.1 OTA. I have unlocked bootloader, TWRP, Root, completely stock 4.4.4 TMO other than that. I flashed the stock recovery back, and I understand that the update will break root. Then I downloaded the OTA, and went to install. It began to install in stock recovery, then rebooted after just a few seconds. Got a message that says something like "sorry there was a problem updating your moto x no changes were made" I accidentally closed the window before writing down exactly what it said, but that was basically it. Any ideas?
Now the OTA isn't even available if I check for it in settings, which is a bummer, but I understand that's probably because of it being a soak test... I just want to be ready for it when it does become available again.
Any helps is appreciated!
------
UPDATE: Solved on Reddit. For those who don't know, you can't flash an OTA if you have rooted, even if you haven't done anything with root. I didn't think this was the case, as it hasn't been an issue with different devices previously, but apparently that changed with lollipop.
rickathenrystuff said:
[solved]
Tried to update the phone to 5.1 OTA. I have unlocked bootloader, TWRP, Root, completely stock 4.4.4 TMO other than that. I flashed the stock recovery back, and I understand that the update will break root. Then I downloaded the OTA, and went to install. It began to install in stock recovery, then rebooted after just a few seconds. Got a message that says something like "sorry there was a problem updating your moto x no changes were made" I accidentally closed the window before writing down exactly what it said, but that was basically it. Any ideas?
Now the OTA isn't even available if I check for it in settings, which is a bummer, but I understand that's probably because of it being a soak test... I just want to be ready for it when it does become available again.
Any helps is appreciated!
------
UPDATE: Solved on Reddit. For those who don't know, you can't flash an OTA if you have rooted, even if you haven't done anything with root. I didn't think this was the case, as it hasn't been an issue with different devices previously, but apparently that changed with lollipop.
Click to expand...
Click to collapse
If you were part of the MFN soak test, you do acknowledge and agree to flashing back to 100% stock if you are rooted, when you accept entrance into the test.
Not being 100% stock HAS been an issue in the past. That is why this thread -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and its predecessors existed.
.
I never agreed to anything with this one. The update just showed up on my phone. I wasn't a part of the official soak test... Probably just part of the initial rollout/soak test/whatever-it's-called.
Regarding root being an issue before, that simply hasn't been the case for me previously, at least on different phones. It's always been understood that taking the ota would break root, but not that I had to remove root prior to taking it. Even the post you quoted indicates that... "You should expect to lose root when you take an OTA."
Regardless of what it was before, it's worth noting to future people who run in to this issue, that yes, you have to completely remove root in order to accept the ota.
rickathenrystuff said:
I never agreed to anything with this one. The update just showed up on my phone. I wasn't a part of the official soak test... Probably just part of the initial rollout/soak test/whatever-it's-called.
Click to expand...
Click to collapse
I wasn't aware it was being sent out to anyone but those who were invited by the MFN yet... then again, I haven't been on as often lately and might have missed it.
rickathenrystuff said:
Regarding root being an issue before, that simply hasn't been the case for me previously, at least on different phones. It's always been understood that taking the ota would break root, but not that I had to remove root prior to taking it. Even the post you quoted indicates that... "You should expect to lose root when you take an OTA."
Click to expand...
Click to collapse
{bold added by me} And that is the biggest issue we've seen... comparing what happened on other phones to the 2013 X...
I see it happen all too often.
And yes, those posts do say you should expect to lose root... but they also discuss the pre-flash validations, and that returning to stock is required.
rickathenrystuff said:
Regardless of what it was before, it's worth noting to future people who run in to this issue, that yes, you have to completely remove root in order to accept the ota.
Click to expand...
Click to collapse
Oh, I completely agree.
I have been out of the loop on this phone for a while. I had to get a replacement G4 and it came with ZVB and I recently took the new ZVC OTA. It looks to me that there is no current root method for phones running ZVB and above. Can someone please confirm this for me? Just wanting to make sure I am not missing something.
mikeregister said:
I have been out of the loop on this phone for a while. I had to get a replacement G4 and it came with ZVB and I recently took the new ZVC OTA. It looks to me that there is no current root method for phones running ZVB and above. Can someone please confirm this for me? Just wanting to make sure I am not missing something.
Click to expand...
Click to collapse
Root has been gone for a while with a locked bootloader it's very highly unlikely new software updates will never receive root. At least on older phone models.:crying:
mikeregister said:
I have been out of the loop on this phone for a while. I had to get a replacement G4 and it came with ZVB and I recently took the new ZVC OTA. It looks to me that there is no current root method for phones running ZVB and above. Can someone please confirm this for me? Just wanting to make sure I am not missing something.
Click to expand...
Click to collapse
Zv6 is only firmware rootable.
as of rite now you cannot rollback before zvb any ways. You can brick device. Basicly for now ypur screwed til someone makes a modded sysyem image with tweaks only no root. U aint missed much on g4
I have also just now come back to the G4, and it seems like there is no root method at all, even in mods like my favorite UltraPOP AOSP, the difficult ones where you're pulling the plug on the battery at certain times.
What those mods HAVE done, specifically UltraPOP, is that they are able to unlock or make accessible most things people want root for, but manually, and requiring a software update for each thing. Those may do what you're looking for.
This will be a thread only for people willing to test a root method for the s6 active
I will volunteer.
I am on marshmellow test PE9 and can Odin back to 5.1.1 if needed.
Sent from my SAMSUNG-SM-G890A using XDA-Developers mobile app
I don't suggest you attempt an ODIN from Marshmallow to Lollipop
I attempted to ODIN from Marshmallow to Lollipop due to Battery Drain and poor cell signal after updating. It soft bricked my phone and could not get smart switch to restore or even the Best Buy Samsung Tech to reflash marshmallow. I had to send it to Samsung Service Center as a last ditch effort to unbrick.
Basically I tried to flash 5.1.1 it failed ODIN Flash. Then I thought well I the Engineering Build 0K2 Combination filed worked when I flashed it using 5.1.1, so I thought maybe I can flash it back to this version then reflash to 5.1.1. It didn't work for me and ended up soft bricking the device. Who knows maybe it will let you flash 5.1.1 from Marshmallow.
Bones2374 said:
I will volunteer.
I am on marshmellow test PE9 and can Odin back to 5.1.1 if needed.
Click to expand...
Click to collapse
Cool so what you'll have to do first, it's visit samsungfirmware.com, and download the 5.1.1 rom. Once you do that, visit this site, and download necessary files. Report back when you have finished, I will then tell you what to do next.
Please understand any bricked or damaged devices, will not be my fault, for it is you who wants to test it.
Flash back to android 5.1.1 using Odin, and then flash the G890AUCU3AOK2.tar file, and once done go into recovery on your phone, and on your phone hit fix root.
http://forum.gsmhosting.com/vbb/f453/how-root-g890a-5-0-2-5-1-1-a-2103269/
Ihaveaflashingproblem said:
I attempted to ODIN from Marshmallow to Lollipop due to Battery Drain and poor cell signal after updating. It soft bricked my phone and could not get smart switch to restore or even the Best Buy Samsung Tech to reflash marshmallow. I had to send it to Samsung Service Center as a last ditch effort to unbrick.
Basically I tried to flash 5.1.1 it failed ODIN Flash. Then I thought well I the Engineering Build 0K2 Combination filed worked when I flashed it using 5.1.1, so I thought maybe I can flash it back to this version then reflash to 5.1.1. It didn't work for me and ended up soft bricking the device. Who knows maybe it will let you flash 5.1.1 from Marshmallow.
Click to expand...
Click to collapse
Hmm were you able to enter Odin mode, or recovery?
I attempted to ODIN from Marshmallow to Lollipop due to Battery Drain and poor cell signal after updating. It soft bricked my phone and could not get smart switch to restore or even the Best Buy Samsung Tech to reflash marshmallow. I had to send it to Samsung Service Center as a last ditch effort to unbrick.
Basically I tried to flash 5.1.1 it failed ODIN Flash. Then I thought well I the Engineering Build 0K2 Combination filed worked when I flashed it using 5.1.1, so I thought maybe I can flash it back to this version then reflash to 5.1.1. It didn't work for me and ended up soft bricking the device. Who knows maybe it will let you flash 5.1.1 from Marshmallow.
Click to expand...
Click to collapse
How would the system have any memory of the previous OS, does Odin wipe all data before flashing? If it does how would there be any problems?
Thanks for your time,
Matt
Iglooian said:
I attempted to ODIN from Marshmallow to Lollipop due to Battery Drain and poor cell signal after updating. It soft bricked my phone and could not get smart switch to restore or even the Best Buy Samsung Tech to reflash marshmallow. I had to send it to Samsung Service Center as a last ditch effort to unbrick.
Basically I tried to flash 5.1.1 it failed ODIN Flash. Then I thought well I the Engineering Build 0K2 Combination filed worked when I flashed it using 5.1.1, so I thought maybe I can flash it back to this version then reflash to 5.1.1. It didn't work for me and ended up soft bricking the device. Who knows maybe it will let you flash 5.1.1 from Marshmallow.
How would the system have any memory of the previous OS, does Odin wipe all data before flashing? If it does how would there be any problems?
Thanks for your time,
Matt
Click to expand...
Click to collapse
Well once you flash with Odin, it updates the system partitions. So you have to factory reset after the update.
I was in download mode where you flash Odin files.
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
Let me provide some background. I bought the phone with 5.1.1
AT&T system update automatically pushed marshmallow update. I wanted to roll back due to some noticeable issues with marshmallow. So I attempted to Odin 5.1.1 it failed in Odin with no issues. Then I tired a couple different lollipop files they failed. I then tried the ok2 combination fa50 file and it failed but this time the phone booted to update failed blue screen and would not turn off. I could go to the download mode where you flash Odin files, but it would fail on everything. If there was an Odin flashable marshmallow I'm sure it would work. The phone would not shutoff. It stay on until the battery drained completely. I visited samsung tech at best buy who could not charge it to push the marshmallow update with his smart software. It gave him and x so he told me to send it to samsung they can do more. I forgot to mention smart switch did not work for me despite having two different serial numbers from owning multiple s6 actives. I didn't decide to install the app package disable on my other phone to prevent the marshmallow update. It might have trouble because I use straight talk AT&T and the updates have to do with voLTE which don't work with prepaid I believe.
Ihaveaflashingproblem said:
I was in download mode where you flash Odin files.
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
Let me provide some background. I bought the phone with 5.1.1
AT&T system update automatically pushed marshmallow update. I wanted to roll back due to some noticeable issues with marshmallow. So I attempted to Odin 5.1.1 it failed in Odin with no issues. Then I tired a couple different lollipop files they failed. I then tried the ok2 combination fa50 file and it failed but this time the phone booted to update failed blue screen and would not turn off. I could go to the download mode where you flash Odin files, but it would fail on everything. If there was an Odin flashable marshmallow I'm sure it would work. The phone would not shutoff. It stay on until the battery drained completely. I visited samsung tech at best buy who could not charge it to push the marshmallow update with his smart software. It gave him and x so he told me to send it to samsung they can do more. I forgot to mention smart switch did not work for me despite having two different serial numbers from owning multiple s6 actives. I didn't decide to install the app package disable on my other phone to prevent the marshmallow update. It might have trouble because I use straight talk AT&T and the updates have to do with voLTE which don't work with prepaid I believe.
Click to expand...
Click to collapse
Do you still have the phone? if so I can help you with the problem.
Continuing my previous instructions, after you fix root, and phone restarts, you should see factory binary. It will take quite a while to fully boot. When done, you should have full root permissions. This is where the experimental part comes to play. You won't have any Google or samsung apps, so head over to samsungfirmware.com, and get the 5.0.2 rom. Extract the file, and then rename the tar.md5 file, by removing the.md5 part. Then extract that using 7 zip. Now find the bootloader file, and replace the 5.1.1 bootloader file with this, in the hopes of unlocking the bootbootloader. Post back whether or not this works, then we can mover on top the next steps.
Bones2374 said:
I will volunteer.
I am on marshmellow test PE9 and can Odin back to 5.1.1 if needed.
Click to expand...
Click to collapse
I put on the thread the necessarily steps you need to take as a volunteer, I hope you check them out, and get back to us soon!!!
Tonster, why are you asking people to experiment with their phones? Do you have any reason to believe that following your instructions will lead to a rooted phone? Please post a screen shot proving that you've gotten it to (partially?) work. AoN
anneoneamouse said:
Tonster, why are you asking people to experiment with their phones? Do you have any reason to believe that following your instructions will lead to a rooted phone? Please post a screen shot proving that you've gotten it to (partially?) work. AoN
Click to expand...
Click to collapse
I have tried this method on android 5.1.1, and can confirm that it is a working partial method of root. However I am now running marshmallow, and unfortunately I have no valid screen shots, but if you need proof, watch this YouTube video.
Comment whether this method worked for you or not.
Tonster21 said:
I have tried this method on android 5.1.1, and can confirm that it is a working partial method of root. However I am now running marshmallow, and unfortunately I have no valid screen shots, but if you need proof, watch this YouTube video.
Click to expand...
Click to collapse
this is to unlock carrier only.
izote61 said:
this is to unlock carrier only.
Click to expand...
Click to collapse
I do realize that, but I am looking for possible ways to use this, and root the phone.
Tonster21 said:
I do realize that, but I am looking for possible ways to use this, and root the phone.
Click to expand...
Click to collapse
not possible I have file for 5.0 and 5.11 root.
at this moment there is no root for 6.0.1 and if root become available will be at xda forum
When can be available a root? i upgrado to 6.1.1 and i see that i dont have Polish language
dustmanop said:
When can be available a root? i upgrado to 6.1.1 and i see that i dont have Polish language
Click to expand...
Click to collapse
This is an old thread
That being said, root is being worked on by a handful of people. Since this device is strictly AT&T however (and I'm sure a lot of other reasons too), root for 5.1.1 is still VERY experimental and breaks most of the device functionality from what I've heard. 6.0.1 is going to be an even harder challenge. Root may be possible some time in the future but I wouldn't count on it being easy.
Tonster21 you joined the forum July 29th, 2016..
You are having forum members download files from other websites and have absolutely ZERO credentials nor do have any relevant solutions to any issues regarding the S6 Active.
You might want to validate your actions real quick..
---------- Post added at 03:05 PM ---------- Previous post was at 02:58 PM ----------
FevenKitsune said:
This is an old thread
Click to expand...
Click to collapse
The OP just joined the forum in July this year .. explain what you mean by old?
Useless time wasting of forum members with probable cause for downloading malicious software is what this is..
Hey, I am currently running 6.0.1 as my android version. Just asking but would it be suggested to downgrade the android version? If yes, than too which version?
Why do you want to downgrade?
The Nexus 6 came out with the 5.0, you can't go further back, even with custom roms. Actually I've head somebody trying to build KitKat for the shamu, but I don't know if he succeeded.
Also why would you like to downgrade, anyway?
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Why not upgrading to android 7 instead of downgrading?
php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
Why don't you try upgrading instead? Android 7.0 factory image has just been released.
Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?
php111 said:
Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?
Click to expand...
Click to collapse
If you want to flash the factory image then go here: https://developers.google.com/android/nexus/images#shamu
You will find the factory image for 7.0 there and also the instructions on how to flash it. If you are already on stock 6.0.1, you should bee recieving an OTA update soon. But since you say you have reboots and freezes I would take a backup of what every you need onto your computer and then start of fresh from the link above. That way you won't be haunted by old bugs that might be stuck because of previous versions.
php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
These freezing/slow/crashing issues look very unique to you. Why didn't you try a factory reset, then add your apps back one by one, and look for those that give you trouble. Also are you rooted, do you use xposed or anything that modifies the basic system? Because I'm runnin 6.0.1 myself, and never had the issues you do.
The instructions on the developer page to flash looks too confusing. Well, it jumps right into it when myself I never done it before.
Everybody on this site once knew nothing about Android. Your safest bet is to just wait for the OTA to be offered (or proactively check for it) and accept it. If you're as novice as your posts suggest, I'm guessing that you're running a pure stock device, so you won't run into any problems with the upgrade. And if you do, you know where we are...