Related
Does new phone come with JB? If so should I stay with it and not to accept OTA?
It seems that Kitkat update introduced several issues (problem with email syncing, bluetooth incompatibility wit some cars, etc). Is there anything else? I am fine with not having the latest and greatest.
Also: is it possible to downgrade Moto X DE (GSM) back to JB? I am not 100% sure from reading this forum.
The kit Kat update had issues but nothing on the scale of the Samsung galaxy family's 4.3 update. I haven't noticed any issue on mine nor any on customers. Totally worth upgrading it.
Sent from my Lumia 928
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
texanman said:
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
Click to expand...
Click to collapse
Did you have this issue while on JB?
Dont know as mine came with 4.4 which did not have this weird issue. It may be something I installed so a wipe may be in order.
Go to KK, no question
tapped out via XT1053 DE
The only issue I had was Google maps not showing my direct location with high accuracy on. It was hard for me to distinguish if I needed to go right or left then it has a hard time rerouting. Which pissed my wife off lol.
MOTO X Slapped
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps.
Sent from my XT1053 using HoFo mobile app.
---------- Post added at 07:45 AM ---------- Previous post was at 07:36 AM ----------
@rbiter said:
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps. Blink is in web view. Also means invert lost.
Sent from my XT1053 using HoFo mobile app.
Click to expand...
Click to collapse
Sent from my XT1053 using HoFo mobile app.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Mine arrived with 4.2.2 installed, (2 weeks ago) and it took two updates to get to 4.4, 1'st 4.2.2 then 4.4. No regrets on the update for me, but then again I let the updates fly when I turned on the phone.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Teksu said:
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Click to expand...
Click to collapse
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
dray_jr said:
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
Click to expand...
Click to collapse
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
JoeSchmoe007 said:
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
Click to expand...
Click to collapse
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Moto X DE - mine coming soon as well - some questions
dray_jr said:
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Click to expand...
Click to collapse
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition. Why go back to 4.4.2 if it ships with a later release?
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
dmm108 said:
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition.
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
Click to expand...
Click to collapse
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
edthesped said:
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
Click to expand...
Click to collapse
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
dmm108 said:
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
Click to expand...
Click to collapse
No idea, but freezing moto apps killed the battery. I haven't figured out what the culprit is yet as I'll be travelling this week and I don't want to jack up the phone while I'm on the road. I suspect another system app was spending effort looking for a missing app. Had I not ran my phone stock for a week I may have assumed that was just the phone as the high battery use was about the same as what I typically got on my S3. However, once I started freezing apps battery life went way down. Battery is good again after defrosting all Moto stuff that I assumed to be garbage. Once I get off the road I'll start freezing apps one at a time to see if I can isolate the culprit.
My thought is if you run it stock for a week you'll have a pretty good feel as to how the phone performs so you'll know whether your tweaks are helping or hurting you.
edthesped said:
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
Click to expand...
Click to collapse
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
edthesped said:
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
Click to expand...
Click to collapse
Yes, I am getting the Verizon DE. (VZW, 1st post).
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
mikestrong19 said:
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
Click to expand...
Click to collapse
Do NOT upgrade until you've read another 24 hours on this board!!!!! I think you should take a second look at your status and see if you misread 4.4.2 as 4.2.2
If I may ask, why not update?
mikestrong19 said:
If I may ask, why not update?
Click to expand...
Click to collapse
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
doitinthedirt said:
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
Click to expand...
Click to collapse
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
mikestrong19 said:
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
Click to expand...
Click to collapse
Wow, what a waste. You could have just flashed the entire STOCK SBF as per the Return to Stock thread, and avoided costing Moto money, and hence raising the prices for everybody... :/
This would have repaired any filesystem corruption/damage, which is the only conceivable thing that might have caused your issue.
Your new one will probably have 4.4.2....which means no write protection disabling.
D'oh!
---------- Post added at 07:17 PM ---------- Previous post was at 07:17 PM ----------
You could have had FULL root on 4.2.2.
We have a Moto X from Verizon. We built it with the Moto Maker and got it in December.
At that time, we immediately did whatever secret handshake to get root (something about downgrading). It's been humming along fine for the longest time. At one point, it appears, we took the OTA update and now root is gone. This has been the case for a while, and it hasn't been an issue. Now, the phone is trying to take the Android 4.4.4 upgrade, and the device keeps rebooting and displaying this error:
"Partition (recovery) security version downgraded"
Click to expand...
Click to collapse
We've done some research, and believe I have a path to recover. We don't care about root or custom recovery any longer, we just want a working Moto X.
Question: since I'm on 4.4.2 currently (build KXA20.16-1.25.2), I'm assuming I can use the 4.4.2 FKZ to return to stock?
Here's the thread I used to help me make this determination: http://forum.xda-developers.com/moto-x/general/bricked-attempting-4-4-to-4-4-2-ota-look-t2660441
Can someone validate that I'm going down the right path? Thanks in advance for all replies!
fonixmunkee said:
We have a Moto X from Verizon. We built it with the Moto Maker and got it in December.
At that time, we immediately did whatever secret handshake to get root (something about downgrading). It's been humming along fine for the longest time. At one point, it appears, we took the OTA update and now root is gone. This has been the case for a while, and it hasn't been an issue. Now, the phone is trying to take the Android 4.4.4 upgrade, and the device keeps rebooting and displaying this error:
We've done some research, and believe I have a path to recover. We don't care about root or custom recovery any longer, we just want a working Moto X.
Question: since I'm on 4.4.2 currently (build KXA20.16-1.25.2), I'm assuming I can use the 4.4.2 FKZ to return to stock?
Here's the thread I used to help me make this determination: http://forum.xda-developers.com/moto-x/general/bricked-attempting-4-4-to-4-4-2-ota-look-t2660441
Can someone validate that I'm going down the right path? Thanks in advance for all replies!
Click to expand...
Click to collapse
Use the FXZ that has been posted for your model: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
It is the only safe way to upgrade now that you are receiving the error, which normally indicates that you attempted to downgrade.
If you use one of @SamuriHL 's tools, you can KEEP your data, just like you would if you used took the OTA.
samwathegreat said:
Use the FXZ that has been posted for your model: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
It is the only safe way to upgrade now that you are receiving the error, which normally indicates that you attempted to downgrade.
If you use one of @SamuriHL 's tools, you can KEEP your data, just like you would if you used took the OTA.
Click to expand...
Click to collapse
Thanks for the reply, samwathegreat. After conducting a bit more research, I saw your name pop up a few times assisting people with a similar error.
So if I may ask a follow-on question, should I use the FXZ for 4.4.2, or can I do the 4.4.4 one? I'm currently on 4.4.2, receiving said error, while attempting to upgrade to 4.4.4.
fonixmunkee said:
Thanks for the reply, samwathegreat. After conducting a bit more research, I saw your name pop up a few times assisting people with a similar error.
So if I may ask a follow-on question, should I use the FXZ for 4.4.2, or can I do the 4.4.4 one? I'm currently on 4.4.2, receiving said error, while attempting to upgrade to 4.4.4.
Click to expand...
Click to collapse
You should definitely use the 4.4.4 FXZ from the link I provided you. If you do this, you will be on 4.4.4 running smoothly in no time at all...
Thank you, @samwathegreat! You had the fix:
1. Download the 4.4.4 FXZ from here, even though we were on 4.4.2: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
2. Follow the steps to use RSD flasher from @SamuriHL. Follow them to the T: http://www.droidrzr.com/index.php/topic/48904-rsd-flasher-beta-windows-only/
Our Moto X is now running 4.4.4 stock. Thanks to @samwathegreat & @SamuriHL!
So I didn't read any guides and was following an old YouTube video on how to go back to stock and OTA. Unfortunately the link was for an older version of the Moto X Toolkit and it took me back to 4.2.2 and I accepted the OTA. gg.
I have tried flashing 4.4.4, 4.4.2, 4.2.2 again from fastboot and in the end the result is the same: a flashing dead android popping up every few seconds that says error. After reading the Q/A I think this is a hard brick but has there been any updates on ways to fix this?
I can't USB mount to put in a custom rom either and it won't let me sideload since the USB mounting isn't working. I can flash custom recoveries but that's about it.
Thanks.
Not researching first on any device is a mistake for sure... Especially the X. You've done the procedure that guarantees bricking a Moto X unfortunately.
This thread may be your only hope now...
http://forum.xda-developers.com/showthread.php?t=2629057
Good luck!
I looked into this method but couldn't get it to work since it wasn't recognizing the phone when I plugged it in. I did manage to unbrick it somehow by flashing a 4.2.2 version again using the toolkit (post camera I believe). I managed to boot up again in 4.2.2 but not really sure how to upgrade to 4.4.4 at this point without bricking again.
Is it safe to RSDlite to 4.4.4 using the right carrier?
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
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..