Related
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
How does this affect our device when it gets the lollipop update?
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Since I am running dynamic Kat on stock slot right now, I should be safe from updates for now right?
Waiting to see what happens with all this. I did back up my stock rom to an SD card, so I can restore and unroot etc... to get an update if I choose to later.
muniz_ri said:
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Click to expand...
Click to collapse
was looking for a post like this. well maybe we might get 5.1 in the next few weeks or sooner so i am sure you will give it a try and a good look and hopefully you will have success in attaining root and a good SS. seems like u da man for this...:good::good:
as for 5.1 or a custom rom...well whose to say what that will bring...
will be waiting to see what happens. will check back here when it comes out. i watch for it everyday and as usual, thank you for all your great work!
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily, just because (if) the S5 gets 5.0 does not mean the ability to root will be lost just go check out the Verizon S5 forums you'll see they have a method for rooting with 5.0 that in theory should work for us as well. again it is recomended to remain on a 4.4.x rom until this has been fully evaluated.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
My suggestion would be not to take any updates until the root capabilities have been evaluated.
As always, research goes a long way towards alleviating fears and stopping panic attacks before they happen. be patient there are great devs here give them time to work
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
the att gs5 doesn't seem like it's getting any updates..
wmunn said:
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
Click to expand...
Click to collapse
How are you liking it? I'm seriously thinking about doing the same thing.
I have a coworker that just got the Lollipop update for his Note 3 so that means it will be coming to the S5 very soon!
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
silentscreamz said:
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
Click to expand...
Click to collapse
I used that method as well. Sure, it worked for me, but I came from Dynamic Kat, a well debloated stock rom. Due to this, after installing the update using this method, the built-in apps restore function could not complete due to having all of the useless bloatware back, taking up the extra space I was free to use in Dynamic Kat. Even removing the apps that are safe to remove via Titanium Backup doesn't help because the space is reserved for them. I've also already moved every app that it will allow to move to SD card. I've removed unneeded apps. I've gone through my internal storage to remove any unneeded files.
I've removed most of the apps listed here
This doesn't give me the Bluetooth tether that I used to us for my Gear 1(Running Null Rom). I'd look for an app to cover this but... I can't install anything because I've got no space to do so... I hope a good debloat method comes along soon. I still have root, so I'm hopeful.
Yea, bloatware is ridiculous for this phone. Have you tried the Alliance rom, that is what I run and it's not to bad for bloatware but I have only managed to get 5.6 running. Going to try version 8 today sometime. If you like to customize that is an awesome rom.
Hi folks, new to the S5 forums on here as I just upgraded from my trusty S3 on AT&T. I'm still on the stock 4.4.2 firmware, NG3 build, and I'm wondering if I should just root from here using TowelRoot method or take the 4.4.4 OTA and root from there.
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
SoCalHTCFuze said:
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
Click to expand...
Click to collapse
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
MetalHead66 said:
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
Click to expand...
Click to collapse
You gotta downgrade theres a post on here just type it in the search bar. Pretty easy process
Yes. Follow the 4.4.2 how to root thread, it says that bit still works.
OK thanks a bunch. Getting ready to do that now.
---------- Post added at 03:27 AM ---------- Previous post was at 02:53 AM ----------
Well that was quite easy and I'm a happy camper now! Just had to flash nd3 kernel with odin in order for TR to work then flash my ng3 kernel. So nice to be able to use TiBu. Helium wouldnt install all my apps. Now I can start freezing and uninstalling all the bloatware!
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Rachel Ambler said:
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Click to expand...
Click to collapse
The main reason that some users bricked their phone is that they wiped the OS and had a locked bootloader which leaves no possibility ro recover the phone
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Unless something is special about the N6 that I'm not aware of, the OS you update FROM only matters if you're sideloading an OTA file. Flashing factory images, you could be coming from a custom ROM(I just took my old N4 from CM12.1 to stock 4.4 on Sunday).
The current build for VZW is 5.1 LMY47E. I think they are updating to 5.1.1 now(LMY47Z, which seems to be universal now except for maybe T-Mo). I flashed mine from E to Z on Saturday because I bought mine unlocked but it had the VZW build, and I'm on an AT&T MVNO.
gee2012 said:
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
If you root, you'll.never get an OTA anyway, sonit doesn't matter which rom you flash aa you can flash any other rom.over it
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Rachel Ambler said:
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
Click to expand...
Click to collapse
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
danarama said:
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Click to expand...
Click to collapse
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Rachel Ambler said:
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Click to expand...
Click to collapse
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile adds a kernel fix to allow their wifi calling to work. And that's it...
gee2012 said:
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
Click to expand...
Click to collapse
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
danarama said:
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile addsna kernel fix to allow their wifi calling to work. And that's it...
Click to expand...
Click to collapse
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
gee2012 said:
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Click to expand...
Click to collapse
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
danarama said:
"Well all Nexus 6 used to get the same updates but tmob and red, ..."
Click to expand...
Click to collapse
Great info, very useful.
Rachel Ambler said:
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Click to expand...
Click to collapse
There were no carrier specific ROMs when Nexus 6 came out. Using any rom on any Nexus and they will all act the same, except you wont get improved volte or wifi calling on those carriers. Their changes will not prove detrimental on other carriers
danarama said:
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
Click to expand...
Click to collapse
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Rachel Ambler said:
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
Click to expand...
Click to collapse
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on xda that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Rachel Ambler said:
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Click to expand...
Click to collapse
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
danarama said:
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on sea that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Click to expand...
Click to collapse
I'm sorry if that sudden flash of the light coming on in my head just blinded you, but that's what happens when things start to make sense!
OK, so, this all being the case, and that the OTA's are incremental, then in order to go 5.1 with the build from http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 then I WOULD need 5.0.1? Would that work though if I'm on a generic build since, if it's expecting to patch existing VZW files, wouldn't it fail because they're not there? Failing that I'd need to find a flashable 5.1 for VZW (if one even exists)?
endlessryan said:
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
Click to expand...
Click to collapse
But it wouldn't have the VoLTE improvements, etc, right? Besides, right now I'd like to stay as stock as possible as it's not just my phone I'm working on, both myself and my wife got one at the same time and I know she will most definitely NOT want anything other than stock.
Another interesting development! You can flash the firmware from the U model of the S7 Edge to the AT&T model. Do not know if this is possible for the T-Mobile, Verizon, etc. models. It should be. If anyone tries it and finds out, let me know and I’ll update the post accordingly.
Edit: Root is possible using previously posted method for 935A. Working on a method that doesn't require the engboot file for the U firmware but no promises yet.
The major advantage here to some will be that there is less bloatware. There is zero carrier bloat. None. Nada. Zip. The Samsung bloat is still there, however you can uninstall (yes, uninstall, not disable) most of it. There are 4 it seems that remain and can’t be uninstalled. These are Samsung Pay, Galaxy Apps. Clock, and Calendar (S Planner).
The menus are different. I think the menus are an improvement to be honest. Everything is there aside from the AT&T specific stuff (since this is the U firmware, it's not carrier specific). If you rely on AT&T specific items/bloat, they are not present here.
Frequently asked things I have tested:
Hotspot – Working fine here.
Samsung Pay – Bit the bullet and tested because I knew it would be asked, even though I don’t care to use Samsung Pay. My device was rooted previously. I flashed this and am no longer rooted. Samsung pay works fine. Tested it at the store this morning. IF YOU HAVE A DIFFERENT EXPERIENCE PLEASE UPDATE ME, AS THIS SEEMS TO BE THE MOST ASKED QUESTION.
Update - I have now heard from 7 other users besides myself confirming that Samsung Pay works in store and haven't heard a single report of it failing so far. I'm now confident to call this working across the board, however do keep in mind there's always a risk.
Everything else seems to work as normal. User experiences are different. You may use things that I don’t, so you may find something that’s broken. If you do, please let me know and I’ll update this post for everyone. Please note the firmware also installs Instagram and Whatsapp by default in addition to Facebook, and they are both removable. Facebook however, much like on the AT&T version, is not. You can still turn it off though.
How to install:
Put your phone in download mode.
I personally had success with this version of Odin: http://www.mediafire.com/download/2t2sjqxtogbkafk/odin_3.12.3.rar
However another user couldn’t get it to work and used this version: http://d-h.st/gsDA
Flash the 4 files in this zip to your phone using Odin. All 4 of them: https://www.mediafire.com/?fm3oxddajta1k07
Put the BL in the BL slot, AP in it's slot, and so on. Flash all 4 at once through Odin.
When using the second version of Odin, I encountered an issue where the phone would crash during setup just after the wifi screen. If you have any problems with either, please report back and let me know. Either way, this seems safe to try on the AT&T version of the S7 Edge. I am able to go back to the stock AT&T firmware I’ve uploaded in my other thread just fine. So if this doesn’t work for you, it’s possible to go back. I have went back and forth 4 times now, and met with success going to and from the stock AT&T firmware to this one each time. However as always, try at your own risk.
Again, since many people are asking about carrier specific features - This is the SM-935U firmware. U meaning unlocked. It's not carrier specific. Anything AT&T does to modify the firmware WILL NOT BE PRESENT.. Use this solely if you want a more pure Android experience. No carrier bloat, being able to remove almost all Samsung bloat completely without having to root to do so, and getting updates before carrier specific models. If you rely on AT&T specific modifications to the S7 Edge, this is not for you unless/until someone finds a way to add them (which then defeats the purpose of the U firmware, meaning you might as well stick to the stock firmware).
FAQ
1. Does Samsung Pay work? – Yes. As long as you don’t root the 935U firmware (which is possible using the method currently available for the 935A) Samsung Pay works fine.
2. Does it have Enhanced LTE? – No. Enhanced LTE is a carrier specific feature. This is the U (unlocked) firmware. Anything unique to any carrier is absent. Period. Confirmed by testing against an actual SM-G935U.
3. Does it work with any other carrier than AT&T? – I have had people reporting success with T-Mobile and Verizon versions of the 935. I do not have one, so going from what they say – it works, but attempt at your own risk or search for their posts and ask them personally.
4. How does it perform compared to the 935A firmware? – It benchmarks noticeably higher. It also has a measurable advantage in terms of battery life. It performs better stock than the 935A rooted and tweaked, and when the U firmware is rooted and tweaked, it performs even better still. It’s all around superior to carrier specific firmwares.
5. Can you uninstall the Samsung bloat? – All but 3 apps. Yes, uninstall, not disable, and no, you don’t need to root the U firmware to do it.
6. Can I still revert back to my stock firmware? – Yes. If you have the stock firmware, it’s easy to flash back to it. It won’t trip knox or break Samsung Pay.
7. Will you be modifying it to have the AT&T features? – Likely not. That would entirely defeat the purpose of going to the U firmware. If you want the carrier bloat and features, you’re ahead to just stick to the carrier firmware.
8. Does this work for the regular S7 or the S7 Active? – I have no idea. I don’t own either phone, and cannot test it. I’m going to assume not. If you are brave and test it, do let us all know.
9. Do you have access to the S7 flat or S7 Active U firmwares? – No.
10. It shows the security patch from May. Is it out of date? – As of 7-7-2016 I have an actual 935U as well as my 935A with the U firmware. Neither has an update currently, so it seems the May security patch is the latest out for the U model so far. If I get an update on my actual 935U, I will let you know if it shows on the 935A with the U firmware or not.
And for those wondering about all the U files floating around...
gtg465x said:
For what it's worth, I downloaded three versions: the one from the first post, one labeled an ATT version posted by someone else in the thread, and an XXA one from SamMobile that was a different size zip file, and all three zips contained the exact same firmware, as verified by md5 check, but the SamMobile version was missing the CP and CSC files and was compressed differently.
Here are the md5s of the various firmware files:
AP_G935UUEU2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT.tar.md5
md5: 0d736fd16ea372e21019a5640b54d965
BL_G935UUEU2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT.tar.md5
md5: bd4d93a5387abcac2ba8737a95989fa3
CP_G935UUEU2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT.tar.md5
md5: abf5821c3edeed42b752329b301ab01e
CSC_OYM_G935UOYM2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT.tar.md5
md5: 7aa4025b7a02dfee0d0470cd3ddc98d2
Click to expand...
Click to collapse
Here are a few screenshots. I hadn’t installed all my stuff yet, however I had uninstalled several of the Samsung bloat apps already.
great write-up
Dumb question but this will only work on the edge and not flat AT&T variant, correct?
Sent from my SAMSUNG-SM-G930A using Tapatalk
brianray14 said:
Dumb question but this will only work on the edge and not flat AT&T variant, correct?
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
I have no idea to be honest. I only have the AT&T Edge. But I will update the post if anyone tries it!
I can't wait to try this... i am gonna install the stock 935a firmware you posted first to see which one i am gonna like better my bets on the 935u though that mobile data toggle icon alone is swinging my vote
Cool, thanks! Would love to have this option for flat S7 as I only have interest in debloating at this stage
Sent from my SAMSUNG-SM-G930A using Tapatalk
malcomp87 said:
I can't wait to try this... i am gonna install the stock 935a firmware you posted first to see which one i am gonna like better my bets on the 935u though that mobile data toggle icon alone is swinging my vote
Click to expand...
Click to collapse
935U is also showing better geekbench scores and so far the battery drains less. (nothing disabled, testing it just as it comes aside from uninstalling the Samsung bloat that's uninstallable. Nothing disabled, greenify not installed.)
brianray14 said:
Cool, thanks! Would love to have this option for flat S7 as I only have interest in debloating at this stage
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
I'd love for it to work too! And on the Active! So if anyone tries it and confirms or denies that it works for sure I will let you all know!
i ended up using the modded odin(2nd one). mainly because i had it already loaded up because i ended up having a faulty cord when trying your odin version. so im sure your version odin wouldve worked also if i had my good cord at the time.
Tried 5x keeps failing
Venom0642 said:
Tried 5x keeps failing
Click to expand...
Click to collapse
Hmm that shows that the hash file failed verification it seems, but also verified it before that. Weird. Have you tried re-downloading it? Or if you like, I'll post the program that allows you to download the firmware straight from the source. However it downloads extra files and I'll have to tell you which to use. Let me know.
Venom0642 said:
Tried 5x keeps failing
Click to expand...
Click to collapse
Did you try the other version of Odin I linked out of curiosity? Some reported failures with the first while it works for others of us.
Symphony0fLife said:
Hmm that shows that the hash file failed verification it seems, but also verified it before that. Weird. Have you tried re-downloading it? Or if you like, I'll post the program that allows you to download the firmware straight from the source. However it downloads extra files and I'll have to tell you which to use. Let me know.
Click to expand...
Click to collapse
I tried tool where i download it myself and it fail 3x then i download it yours and still failed, so not sure why is doing this.
Running On Samsung Galaxy S7 Edge G935A Wicked Dark Carnage Edition Theme
Can't wait to see if anyone can get this on the T-Mobile variant...
Venom0642 said:
I tried tool where i download it myself and it fail 3x then i download it yours and still failed, so not sure why is doing this.
Running On Samsung Galaxy S7 Edge G935A Wicked Dark Carnage Edition Theme
Click to expand...
Click to collapse
That is strange! have you previously rooted the device? Just wondering. So far everyone I've confirmed this with was previously rooted, maybe that's part of it?
cybrwulf said:
Can't wait to see if anyone can get this on the T-Mobile variant...
Click to expand...
Click to collapse
The file is actually for T-Mobile believe it or not! However since I don't have a T-Mobile device myself I was hesitant to state it works. But I am sure someone will try it at some point!
Symphony0fLife said:
That is strange! have you previously rooted the device? Just wondering. So far everyone I've confirmed this with was previously rooted, maybe that's part of it?
Click to expand...
Click to collapse
never rooted but worked with second option odin, its booting now!
Venom0642 said:
never rooted but worked with second option odin, its booting now!
Click to expand...
Click to collapse
Good to know! That's the reason I posted both odin files. I and others had success with the first, and others still failed there and the second worked. Enjoy!
Honestly this sounds too good to be true. Remove the carrier bloat, potentially get better speed and better batter and have zero downsides. I definitely didn't want to root, because I want to use Samsung Pay, but if I can remove all the AT&T and Samsung stuff I don't use and still use Samsung Pay, that's a win win win.
Hi
I used 3.12 odin at the beginning, it complains sha-256 is not valid. Then I search internet and xda has a new fixed 3.12 version in the root package which could by pass this check. If you have not rooted, I guess you have to use the one in the root package.
By the way, samsung pay works if you jave not rooted
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
roveer said:
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
Click to expand...
Click to collapse
hi
yes it's not possible to downgrade your rom or your bootloader because of the locked bootloader that prevents any try to modify the device...
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
roveer said:
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
Click to expand...
Click to collapse
Locked bootloaders are often the case for phones provided by carriers. While a phone purchased directly from the manufacturer is usually able to have its bootloader unlocked, carrier phones are locked by the carrier themselves, preventing any tampering by the end user. A custom ROM is any modified version of Android not developed by the company that made your phone. Think of it like a third party system. To get these custom ROMs onto your phone you must "flash" (simply, install) the ROM from your computer to your phone. However, a locked bootloader prevents this. While in some cases there are ways to get around carrier locked bootloaders, it is generally futile. If you purchased the S6 Active in hopes of tinkering around with custom ROMs, I'm afraid you have picked the wrong phone. The S6 Active, as of currently, is permanently locked to Samsung's and AT&T's "stock ROM"
EDIT: as for going back to Lollipop, the reason this is generally not possible is due to the fact that the Marshmallow update also updated critical parts related to the bootloader. It is impossible to roll back these changes once they have been made as they are strictly one way.
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
roveer said:
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
Click to expand...
Click to collapse
If the software you are referring to is something provided by blackberry, perhaps they need to patch their software for compatibility with Android Marshmallow. While not all software is broken by a major Android update, there are definitely some that are. Of course enterprise level software is entirely foreign to me (I'm only 17), so getting a second opinion on this issue would definitely be a good idea.
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
roveer said:
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
Click to expand...
Click to collapse
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
FevenKitsune said:
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
Click to expand...
Click to collapse
So I wiped the cache partition and factory reset within the bootloader and tried my app again. It continued to fail. I even found the MM image in the S6 Active MM thread and sideloaded it. It was only 400+ megs though. Still the app doesn't work so I'm starting to doubt that my problems are related to my particular S6 but its always a possibility. I'm trying to get Blackberry to dig up their own S6A and test on their own. They've been testing with a S6 for the past 2 days (on my BES server) and haven't seen the same problems, so it's either my device or a problem with the S6A (which as has been pointed out does use a different firmware version than the S6), but until I can get another S6 Active device to test I won't know.
Roveer
Any way to root 6.0.1 G920AUCS5DPJ1 yet? Did some research but could not find a way to root for this particular build. Any update?
I've been searching for an easier method to root my phone and I'm shocked at how few options there are to root my s6. I've always been able to come across more than enough information to root all the previous galaxy phones but for some reason there doesn't seem to be an easy method (like ping-pong root or something automated) I'd appreciate if anyone has any feedback on rooting the new build after the November security patch the build number is G925AUCS5DPK1
Hidd3nD3Ath said:
I've been searching for an easier method to root my phone and I'm shocked at how few options there are to root my s6. I've always been able to come across more than enough information to root all the previous galaxy phones but for some reason there doesn't seem to be an easy method (like ping-pong root or something automated) I'd appreciate if anyone has any feedback on rooting the new build after the November security patch the build number is G925AUCS5DPK1
Click to expand...
Click to collapse
Feedback is, there is no root for the new builds.
Sent from my SAMSUNG-SM-G920A using Tapatalk
And is there any way to go back to old builds flashing with ODIN an old stock firmware?
I confirm: once you get the phone on a newer version, you can't downgrade it. I tried to go from 6.0.1 to 5.1.1 flashing with ODIN. The ODIN process went well, but after the phone took the older load, it got stuck in the ANDROID screen
To get it back to life i had to flash again its original stock version at 6..0.1
So the question is if there will be any developement on S6 ATT 6.0.1 to get it rooted or TWRP. RIght now it seems we are stuck. No root, No custom rom I will keep my S4 that performs like a charm with root and custom roms!
ronniler said:
I confirm: once you get the phone on a newer version, you can't downgrade it. I tried to go from 6.0.1 to 5.1.1 flashing with ODIN. The ODIN process went well, but after the phone took the older load, it got stuck in the ANDROID screen
To get it back to life i had to flash again its original stock version at 6..0.1
So the question is if there will be any developement on S6 ATT 6.0.1 to get it rooted or TWRP. RIght now it seems we are stuck. No root, No custom rom I will keep my S4 that performs like a charm with root and custom roms!
Click to expand...
Click to collapse
Development has been essentially dead on the ATT version for many months.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Thanks @dandrumheller for the reply
I am debating myself to try something even i know is highly possible i break the phone. I really need a rooted phone and this s6 is a replacement for my s6 given to me by ATT. If i can't get it rooted, it will sit there forever. So probably i will take the risk to try to root/load anything experimental
:S