Related
Hello! This is my going to be my first post, so please bear with me.
I own a Samsung Galaxy S4 Active (SGH-I537) from AT&T. I've owned the device for about 6 months now and love it. Recently, I encountered a problem with connecting to GApps/Google services and adding a Google Account.
I rooted my S4 Active with this method from geohot I found here: http://forum.xda-developers.com/showthread.php?t=2347793
After tooling around with it for a day, I had trouble getting on the Play Store. My screen displayed "No Connection; Retry). After trying various solutions I removed my Google Account from the device.
When I couldn't log back in to my Google Account, I disabled 2-step verification and tried application-specific passwords. No avail.
I performed many factory reset, both from the Settings page and by a hard reset. I've wiped all the user data, so I have no apps or anything.
I keep getting this error message, see attachment below.
TD;LR #1 : I rooted my GS4a and I can't use my Google Account. Period.
My guess is that I need to restore the stock firmware onto my Galaxy S4 Active. I haven't been able to find a safe method of doing this yet. I think that this will "restore" my device as if I was doing this to an iOS device (I'm a convert from the Apple ecosystem )
Does anyone know how to flash the stock TouchWiz firmware onto the Galaxy S4 Active. I'm open to alternative solutions too, such as Cyanogenmod or stock Android 4.4.
TD;LR #2 : I need to flash stock firmware or something on my GS4a!
I appreciate all the help I can get. For now, I'm sitting with the Amazon Appstore and Google Chrome for Facebook, Gmail, Twitter, etc.
-Z3RODay
The method used for rooting shouldn't cause any problems with your phone since it only touches a couple files. I doubt that rooting your phone caused GApps to stop working, I'm guessing that either a root file got deleted or another app is incompatible and causing problems.
You're asking how to return your phone to stock and you're correct in that it will "restore" your device, but in doing so it will completely wipe your device and you will lose everything. It will essentially return your phone to the state of when you first pulled it out of the box. This question has been asked and answered a few times and you could probably find the answer by searching, but I'll post the answer here too. For the i537 below are the only known ways to get stock firmware back on your phone:
Devo7v said:
You can Odin back to a pre-release version and have a fully functioning phone, but you will no longer receive official OTA updates (read more about this option here), or
You can take it to the Samsung Experience Shop at your local Best Buy and have them restore your phone to official stock MF3 (read more about this option here).
Other than that I don't really know what else you can do.
Click to expand...
Click to collapse
Devo7v said:
The method used for rooting shouldn't cause any problems with your phone since it only touches a couple files. I doubt that rooting your phone caused GApps to stop working, I'm guessing that either a root file got deleted or another app is incompatible and causing problems.
You're asking how to return your phone to stock and you're correct in that it will "restore" your device, but in doing so it will completely wipe your device and you will lose everything. It will essentially return your phone to the state of when you first pulled it out of the box. This question has been asked and answered a few times and you could probably find the answer by searching, but I'll post the answer here too. For the i537 below are the only known ways to get stock firmware back on your phone:
Click to expand...
Click to collapse
Thank you so much! I'm going to take my phone to Best Buy tonight. I backed up everything on my SD card which is still intact (Thank God!).
I have tested and can now confirm that the latest kingroot apk successfully roots the at&t tab s 10.5 LTE (T807A) on 5.0.2.
Does NOT trip Knox
I will supply a direct download link to this apk
https://drive.google.com/file/d/0B44uRRTMeBhMdDVHZmxFV2VmOEE/view?usp=docslist_api
You know that this version is already posted in a couple of other threads?
http://forum.xda-developers.com/showthread.php?t=3158198
http://forum.xda-developers.com/showthread.php?t=3129484
Unless it's a different build, in which case wouldn't it be better to post it in one of the existing threads rather than create another thread?
ashyx said:
You know that this version is already posted in a couple of other threads?
http://forum.xda-developers.com/showthread.php?t=3158198
http://forum.xda-developers.com/showthread.php?t=3129484
Unless it's a different build, in which case wouldn't it be better to post it in one of the existing threads rather than create another thread?
Click to expand...
Click to collapse
You are correct. It has been posted multiple times in multiple threads. But not a single on of them confirms this Tab S model and software version. So as I have spent the past two weeks searching aimlessly through threads, creating one which is specific for this model for the FIRST time seemed a little more sensible and helpful. And given that the search tool doesn't find any positive confirmation on a working root for that model, it makes this thread that much more sensible
jzd5032 said:
I have tested and can now confirm that the latest kingroot apk successfully roots the at&t tab s 10.5 LTE (T807A) on 5.0.2.
Does NOT trip Knox
I will supply a direct download link to this apk
https://drive.google.com/file/d/0B44uRRTMeBhMdDVHZmxFV2VmOEE/view?usp=docslist_api
Click to expand...
Click to collapse
I can confirm as well. I personally had to use the desktop app but I've gone through several reboots, removed Kingroot with JRummy's ROM Toolbox and have had no problems (other than not being able to find a stock ROM for the t807a).
Not for 707A
It is falsely posted elsewhere that this works on 707A. I tried it this morning and can say it does not. It quits at about 20%. Kingroot downloaed from the link quits at 20% on AT&T 707A.
mpanwar said:
It is falsely posted elsewhere that this works on 707A. I tried it this morning and can say it does not. It quits at about 20%. Kingroot downloaed from the link quits at 20% on AT&T 707A.
Click to expand...
Click to collapse
It's not false, for some it works, for some it doesn't. Did you let it continue after reboot?
No. It does not reboot it just quits at about 25% with Root Failed .... submit ...
Perhaps it works for you but I do not intend to help others possibly brick their units with experiments.
Unless a tool is consistently rooting safely I suggest we stay away.
It does not work on my AT&T Samsung Galaxy Tab S 8.4 LTE with Lollipop. Tried again after your post to see about re-boot. No re-boot. Kingroot just quits.
mpanwar said:
No. It does not reboot it just quits at about 25% with Root Failed .... submit ...
Perhaps it works for you but I do not intend to help others possibly brick their units with experiments.
Unless a tool is consistently rooting safely I suggest we stay away.
It does not work on my AT&T Samsung Galaxy Tab S 8.4 LTE with Lollipop. Tried again after your post to see about re-boot. No re-boot. Kingroot just quits.
Click to expand...
Click to collapse
You're being a little dramatic, no one has bricked their device whether successful or not. Neither Samsung or any other manufacturer.
Some people have made many many attempts before success. Also new versions are being released all the time with previous unsuccessful devices gaining root.
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.
Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?
Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it
my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.
I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...
So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.
ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse
What was the solution that found? I'm going through the same problem.
I have been looking for 3 days now for the US firmware for the SM-T550NZASXAR (might be the same as SM-T550NZAAXAR) and I can't find it. Sam mobile has the files for many countries but fails to show the US version. Am I missing something?
The digitizer keeps losing the touch sensing ability but I'm pretty sure it's a software problem as it comes back after maybe 15 minutes then it stops again after about 20 minutes of use. I want to try and re-install the OS with Oden and see if it clears whatever is going on. I'm hoping it's just bad cache or something.
The Canadian version is usually the same but double check just in case
Sent from my SM-T350 using XDA Free mobile app
Same Issue. I been also looking for US firmware for my SM-T350 Samsung Galaxy Tab A. I see it available for all other countries but not for USA. For all people that live in the US like me. We need to all nag Samsung & complain cause obviously they only support it for all other countries & not US. It pisses me off & it's so unfair. I need the firmware for part of the procedure to fix my rooted tab that's in bootloop
Upset with T-350 firmware situation
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
weaselleaf said:
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
Click to expand...
Click to collapse
http://www.thegalaxytabforum.com/index.php?/topic/33026-recovery-twrp-2871-tab-a/
Twrp tested on sm-t350
weaselleaf said:
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
Click to expand...
Click to collapse
twrp for SM-T350 is file name twrp-28.71-t350.tar
I can't link or i would link you it. Just google search that file name and there is one from android file host
Flash with Odin 3.10.7
Tested and works perfect
Seth50 gets all the credit just confirming it works
WOW! i have been messing with this for hours and cant believe that the samsung smart switch offered such an easy solution.
i made the mistake of flashing a rooted firmware file before unlocking the bootloader and soft bricked it. the smartswitch asks for the model# (SM-T350) and the serial number (no, im not putting mine here), tells you to enter odin mode and then it does all of the dirty work for you... amazing!
one thing to keep in mind is that the install for smart switch will not work on newer machines unless you install legacy software that you can find here https://www.microsoft.com/en-us/download/confirmation.aspx?id=5582
qixiixiq said:
WOW! i have been messing with this for hours and cant believe that the samsung smart switch offered such an easy solution.
i made the mistake of flashing a rooted firmware file before unlocking the bootloader and soft bricked it. the smartswitch asks for the model# (SM-T350) and the serial number (no, im not putting mine here), tells you to enter odin mode and then it does all of the dirty work for you... amazing!
one thing to keep in mind is that the install for smart switch will not work on newer machines unless you install legacy software that you can find here https://www.microsoft.com/en-us/download/confirmation.aspx?id=5582
Click to expand...
Click to collapse
I realize this is an old thread, but looking for help. Purchased a Wifi-only Galaxy Tab A, and looking for the stock 6.0.1 ROM. The Smart Switch software doesn't downgrade it anymore. They've since updated the software to remove that capability, but even older versions still reapply Nougat. Sammobile.com doesn't seem to have it. Has anyone had success finding the stock MM US ROM for this tablet? If you're asking why, adb restore doesn't work on Nougat and I'm trying to restore backups without root. I have a second SM-T350 fresh out of the box, and restore is working. So, want to downgrade to official MM to restore, then maybe upgrade again if I feel like it....
Edit: Embarrassingly, it's in this same forum.... Download it now...I'll see myself out....
https://forum.xda-developers.com/ga...m-stock-builds-sm-t350-ghost-project-t3529439
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