Related
Hey,
Recently I tried to root my Tab S2 and I don't know where I screwed up.
I need help resetting my device back to stock, I cannot flash the stock roms/images. :crying:
It keeps failing, there is also a 'Kernal is not SEAndroid Enforcing' text in red on the boot screen and it stays stuck.
When I flash a stock rom, it says "SW Rev Check Fail Device : 2 Binary: 1"
If you need more information. just comment.
Hopefully you can help!
Well first of all you need to stop panicking and explain what state the device is in and what you did that caused the issue.
Also screenshots say a thousand words.
So, I tried rooting my device using this, http://forum.xda-developers.com/tab-s2/development/root-cf-autoroot-tab-s2-sm-t3187202
and it put my device into a boot loop. Then I think I flashed it with the http://forum.xda-developers.com/tab-s2/development/kernel-permissive-lollipop-5-1-1-kernel-t3205831 but I can't remember.
Now since it has ran out of battery it looks like this:
blob:https%3A//drive.google.com/5dd4cf24-c9b9-4a91-b27a-e2d280356b9c
and I can only enter 'Download Mode' and it no longer boots past this screen. After I did those 2 things I tried to look for some fixes like using the Stock Roms for it, and Samsung Kies but it didn't work.
You need to fix the Google link, not working.
Which device do you have is it running 5.1.1?
Did you flash the correct permissive kernel first then cf_autoroot?
It's running 5.0.2 and it's the SM-T810.
I think that may have been the problem flashing the 5.1.1 kernel by mistake. Is there a way to fix it. I don't think I can get it repaired as the warranty is probably voided.
SaiyanShivvy said:
It's running 5.0.2 and it's the SM-T810.
I think that may have been the problem flashing the 5.1.1 kernel by mistake. Is there a way to fix it. I don't think I can get it repaired as the warranty is probably voided.
Click to expand...
Click to collapse
Sorry can't post the link as I'm A new member so it won't let me until I make 10 posts
SaiyanShivvy said:
It's running 5.0.2 and it's the SM-T810.
I think that may have been the problem flashing the 5.1.1 kernel by mistake. Is there a way to fix it. I don't think I can get it repaired as the warranty is probably voided.
Click to expand...
Click to collapse
Here is this link, it might help did not read thru out the whole way through, just try to relax there is a way to fix it, if in the end if you cannot fix it just warranty it and play dumb it's worked for me more than once. http://forum.xda-developers.com/showthread.php?p=64137334
dislplin01 said:
Here is this link, it might help did not read thru out the whole way through, just try to relax there is a way to fix it, if in the end if you cannot fix it just warranty it and play dumb it's worked for me more than once. http://forum.xda-developers.com/showthread.php?p=64137334
Click to expand...
Click to collapse
Thanks for the help, I'll let you know of it works ! ???
At the end of the day this is completely fixable. All you need do is simply download the stock firmware for your device and region from SamMobile and flash with odin.
Don't wipe anything just flash.
ashyx said:
At the end of the day this is completely fixable. All you need do is simply download the stock firmware for your device and region from SamMobile and flash with odin.
Don't wipe anything just flash.
Click to expand...
Click to collapse
Yeah, Thanks, I will see if I can, if I can't then I will send it for repairs.
SaiyanShivvy said:
Yeah, Thanks, I will see if I can, if I can't then I will send it for repairs.
Click to expand...
Click to collapse
I promise you, you don't need to send it for repair.
You have several options to fix this.
The reason you get that error in Odin is simply because you are flashing the wrong firmware for your device.
Tell me the region you bought this device and I'll point you to the correct firmware.
ashyx said:
I promise you, you don't need to send it for repair.
You have several options to fix this.
The reason you get that error in Odin is simply because you are flashing the wrong firmware for your device.
Tell me the region you bought this device and I'll point you to the correct firmware.
Click to expand...
Click to collapse
I live in New Zealand, so the region would be Oceania I guess?
SaiyanShivvy said:
I live in New Zealand, so the region would be Oceania I guess?
Click to expand...
Click to collapse
Actually I think your region comes under Australia region XSA.
http://www.sammobile.com/firmwares/database/SM-T810/XSA/
So, today I was trying to recover some lost files after resetting my tablet, only for the app to stop working and caused my tablet to go in an endless boot. I get to the Samsung Title, but get red words on top saying something about recovering seandroid enforcing. I'm not sure what t do other than odin back stock, but I am not sure what firmware it is that I need as I haven't rooted my tablet or done anything that would require it.
Any help would be great, thank you!
You would only get that warning if you somehow flashed a custom recovery.
Just download the firmware for your region and flash with odin.
ashyx said:
You would only get that warning if you somehow flashed a custom recovery.
Just download the firmware for your region and flash with odin.
Click to expand...
Click to collapse
Thank you for the reply. The only thing is, I can't seem to find the one for my region. I checked on Sam Mobile, but don't see anything for the U.S.
zxandrewxz said:
Thank you for the reply. The only thing is, I can't seem to find the one for my region. I checked on Sam Mobile, but don't see anything for the U.S.
Click to expand...
Click to collapse
XAR cellular south
ashyx said:
XAR cellular south
Click to expand...
Click to collapse
'
Ah, thank you. BY chnce, would you know of anywhere else to get the firmware? I'm getting an ETA of 7 hours for donwload lol
Have a look here! http://samsung-updates.ru/
Finally got it, thanks guys!
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave
Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1
dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave
I Downloaded The Fw From Sammobile, Yes Its Was Very Slow, Thats Why I Re-upped It Untouched To Androidfilehost, Much Faster To Dl For Others.
Only For Snapdragon Variants, Its The Universal Firmware, Its Free Of Carrier Bloat But Has Some Samsung Useless Apps.
Not For Exynos Variants Like The Sm-g935f, Etc.
MORE ABOUT UNIVERSAL FW READ THIS
The Zip Has The Att Extension But All Universal Snapdragon Fw Are The Same Afaik, It Does Not Install Anything Specific For Att,
Im On Telus/koodo Using The Sm-g935a Without Issues, Shows Lte Signal When On Data Mode.
Idk If Auto Updates Work, Although Update Options Are Available From The System Menu
Instructions:
Dl Zip, Extract Zip, Put Phone In Dl/odin Mode. Run Odin As Admin, And Load Each Cp, Ap, Bl And Csc(Dont Use The Home Csc As I Read Its Fracks Things Up), Just Use "Csc_oym" File In Odin
Fyi. I Used Princes Odin But Failed, Used Untouched Odin And It Flashed Successfully. Was On Nougat 7.0 Sim Unlocked SM-G935A At&t Branded Stock Fw. I Included Both For Your Pleasure.
Afaik It Will Wipe Your Phone, Do A Backup As Needed
make a backup by using adb, search for this method, and a twrp nandroid
always make a backup, and never just one, and save them somewhere safe in multiple locations and clouds, hard drives die all the time
Disclaimer, Im Not Responsible For What You Do To Your Phones
G935UUES4CRG3_G935UOYM4CRG3_ATT.zip - 2.9GB
Odin3_v3.13.1.zip
Odin3+v3.12+(PrinceComsy).zip - not working with this fw
does wifi calling work this way or no bc its the unlocked version primarily?
Hi , can you confirm if this has no issue? im planning to flash my rom into oreo as well. thanks for sharing this.
Misslys9 said:
does wifi calling work this way or no bc its the unlocked version primarily?
Click to expand...
Click to collapse
rhayann77 said:
Hi , can you confirm if this has no issue? im planning to flash my rom into oreo as well. thanks for sharing this.
Click to expand...
Click to collapse
most answers to questions are linked in the op
MORE ABOUT UNIVERSAL FW READ THIS
vincom said:
answers, if any, are linked in the op
MORE ABOUT UNIVERSAL FW READ THIS
Click to expand...
Click to collapse
Hi Vincom, yes i have already read the article. the main reason im flashing the rom is because of the hidden DATA icon in the toggle screen. and also i want my phone to have the OREO update as well. this is my first samsung phone. i have experience in flashing ROMs in my xiaomi redmi 1s phone. so im a bit skeptical if i can do this on my own. this odin process is very new to me. so what is the worst thing that can happen it i brick my phone? can i do a hard reset and will it default to the stock AT&T ROM if ever?
rhayann77 said:
Hi Vincom, yes i have already read the article. the main reason im flashing the rom is because of the hidden DATA icon in the toggle screen. and also i want my phone to have the OREO update as well. this is my first samsung phone. i have experience in flashing ROMs in my xiaomi redmi 1s phone. so im a bit skeptical if i can do this on my own. this odin process is very new to me. so what is the worst thing that can happen it i brick my phone? can i do a hard reset and will it default to the stock AT&T ROM if ever?
Click to expand...
Click to collapse
odin is as easy as it gets, its made for samsung phones.
safe is to do nothing if ur happy as is.
NEVER EVER USE THE "PIT" OPTION UNLESS DIRECTIONS SAY SO IN XDA FORUM ONLY
read/watch vids on using odin
make a backup by using adb, search for this method, and a twrp nandroid
always make a backup, and never just one, and save them somewhere safe in multiple locations and clouds, hard drives die all the time
vincom said:
odin is as easy as it gets, its made for samsung phones.
safe is to do nothing if ur happy as is.
read/watch vids on using odin
make a backup by using adb, search for this method, and a twrp nandroid
always make a backup, and never just one, and save them somewhere safe in multiple locations and clouds, hard drives die all the time
Click to expand...
Click to collapse
Thanks again, ill watch some youtube videos first and if i feel confident enough then i will go thru with this. will keep you posted.
---------- Post added at 09:58 AM ---------- Previous post was at 09:36 AM ----------
rhayann77 said:
Thanks again, ill watch some youtube videos first and if i feel confident enough then i will go thru with this. will keep you posted.
Click to expand...
Click to collapse
Vincom, by the way this Oreo update has nothing to do with my CSC right? i just check its G935AATT4BQK2. my device model is SM-935A
rhayann77 said:
Vincom, by the way this Oreo update has nothing to do with my CSC right? i just check its G935AATT4BQK2. my device model is SM-935A
Click to expand...
Click to collapse
yes and no, csc controls what bloatware and which settings are setup by default dependant on carrier and country, hence why this is a universal fw and not dependant on original csc files.
if u truly have the att s7edge g935a, which is what i had, then yes.
vincom said:
yes and no, csc controls what bloatware and which settings are setup by default dependant on carrier and country, hence why this is a universal fw and not dependant on original csc files.
if u truly have the att s7edge g935a, which is what i had, then yes.
Click to expand...
Click to collapse
Thanks for the clarification. the download path keeps on failing on me for some reason. i already downloaded 1.8G or maybe its my internet speed perhaps?
rhayann77 said:
Thanks for the clarification. the download path keeps on failing on me for some reason. i already downloaded 1.8G or maybe its my internet speed perhaps?
Click to expand...
Click to collapse
could be android file host is having issues today
or u can try ur luck with sammobile.com which is where i initially got the file
edit. ya, i just tried, issues on their end
vincom said:
could be android file host is having issues today
or u can try ur luck with sammobile.com which is where i initially got the file
edit. ya, i just tried, issues on their end
Click to expand...
Click to collapse
i finally finished downloading the zip file earlier. i will flash it later after i go home from work. and one other thing i need to make sure. with this Oreo rom, the DATA connection icon will be available in the toggle screen right?
@vincom, this Oreo rom has already the DATA icon to be toggled on/off right? this is one of the reason i want to flash the att rom as well.
vincom said:
most answers to questions are linked in the op
MORE ABOUT UNIVERSAL FW READ THIS
Click to expand...
Click to collapse
I did read all of it but your description was vague on the att part so I didnt know if you modified it which it sounds like its just the 935u firmware and Im not a newb n00b
@vincom, initially got an error sha256 when i started to flash it. and my phone started to boot loop after i use a different odin, the prince odin. but after some searching. i fount out i just need to use the newer patch version of odin - Odin3 v3.13.1_3B_PatcheD and now im running Oreo on my s7 edge. hopefully this can help others too.
rhayann77 said:
@vincom, initially got an error sha256 when i started to flash it. and my phone started to boot loop after i use a different odin, the prince odin. but after some searching. i fount out i just need to use the newer patch version of odin - Odin3 v3.13.1_3B_PatcheD and now im running Oreo on my s7 edge. hopefully this can help others too.
Click to expand...
Click to collapse
did u try the one i have in the op, Odin3_v3.13.1.zip
vincom said:
did u try the one i have in the op, Odin3_v3.13.1.zip
Click to expand...
Click to collapse
yup i tried that one the first time. thats when it gave me the error message sha256. then i tried the prince odin that gave me the error mmc something.
The author claims performance and battery improvements but has anyone that switched over really noticed that big of a improvement?
I mean i already disabled all the carrier bloat with adhell isn't that basically the same as installing this rom? Does the universal maybe have a different kernal/different system level tweaks?
Bro , what will happen if my unlocked at&t s7edge installing this ? Is there sim will be locked again or not ? Thanks in advance and sorry for my bad english...
Rifuki18 said:
Bro , what will happen if my unlocked at&t s7edge installing this ? Is there sim will be locked again or not ? Thanks in advance and sorry for my bad english...
Click to expand...
Click to collapse
will not change your current sim lock status, no fw exists that would change it
Thanks
Thanks a lot, this firmware works for me with the 3b patched odin on the first try.
Hello everybody,
I bought new Note 8 to replace my Galaxy S8.Im very happy with the purchase but lack of updates worries meIm stuck with N950FXXU3CRB9 March security update and can't get any further updates at all. Can I do anything to get it sorted without flashing firmware?I can live without Volte and Samsung Pay but I would def like to receive security and other system updates.
Any help much appreciated
Tom
lord_belial78 said:
Hello everybody,
I bought new Note 8 to replace my Galaxy S8.Im very happy with the purchase but lack of updates worries meIm stuck with N950FXXU3CRB9 March security update and can't get any further updates at all. Can I do anything to get it sorted without flashing firmware?I can live without Volte and Samsung Pay but I would def like to receive security and other system updates.
Any help much appreciated
Tom
Click to expand...
Click to collapse
Try a factory reset. This worked for me a while back.
Make sure to back-up data.
I'm going to do it now and I'll post how did I get on.Thanks
Unfortunately it didn't help still no OTA updates...
Go to Samsung Science put in model..build number will tell you if there is an update.
NOTE9...THE BEAST
butchieboy said:
Go to Samsung Science put in model..build number will tell you if there is an update.
NOTE9...THE BEAST
Click to expand...
Click to collapse
I've tried that but my model is not on the list.(N950F)
butchieboy said:
Go to Samsung Science put in model..build number will tell you if there is an update.
NOTE9...THE BEAST
Click to expand...
Click to collapse
lord_belial78 said:
I've tried that but my model is not on the list.(N950F)
Click to expand...
Click to collapse
Samsung Science is only for the US version of the phone's. I wish they had a site like that for the international versions. But you can go to sammobile.com and check if your phone has any upgrades available. I doubt for the N950F that it doesn't have a newer software update, but on my phone the last update I got was in May which is the latest for my model unfortunately.
I have checked this and it looks like there are 3 updates available but I can't get them for some reason.I get a message that my phone is up to date all the time.
Sorry didn't realize you had International..my bad.
NOTE9...THE BEAST
Download the latest full ROM and flash with ODIN.
Just make sure you get the right ROM...
ultramag69 said:
Download the latest full ROM and flash with ODIN.
Just make sure you get the right ROM...
Click to expand...
Click to collapse
Is there any risk I'll turn my phone into a brick?
There is always some risk, as with all things in life, (interrupted process, corrupted files,
wrong files, etc) but the problems commonly arise when flashing unofficial roms
winol said:
There is always some risk, as with all things in life, (interrupted process, corrupted files,
wrong files, etc) but the problems commonly arise when flashing unofficial roms
Click to expand...
Click to collapse
I'm going to do my homework first as I have no clue how to pick the right rom nevermind flashing my phone.
Thanks a lot for help
I would recommend taking your device to a Samsung Service Center and let them take a look at it.
iceepyon said:
I would recommend taking your device to a Samsung Service Center and let them take a look at it.
Click to expand...
Click to collapse
Not necessary, he can just flash latest rom for the device through Odin.
sefrcoko said:
Not necessary, he can just flash latest rom for the device through Odin.
Click to expand...
Click to collapse
How can I be sure that I picked the right rom?And my csc is Malaysian but I have UK/Ireland firmware XEU/XEU/XME.Maybe that's a reason I can't get any updates?Can somebody advise?
Thanks a lot
Tom
lord_belial78 said:
How can I be sure that I picked the right rom?And my csc is Malaysian but I have UK/Ireland firmware XEU/XEU/XME.Maybe that's a reason I can't get any updates?Can somebody advise?
Thanks a lot
Tom
Click to expand...
Click to collapse
OS Updates are released in batches. Different countries will get them at different times. You should get it soon.
iceepyon said:
OS Updates are released in batches. Different countries will get them at different times. You should get it soon.
Click to expand...
Click to collapse
No he won't...If he is still stuck on the March update (see post 1) then he is not getting updates at all. It's not a question of staggered releases for different countries, it's likely because his CSC doesn't match.
lord_belial78 said:
How can I be sure that I picked the right rom?And my csc is Malaysian but I have UK/Ireland firmware XEU/XEU/XME.Maybe that's a reason I can't get any updates?Can somebody advise?
Thanks a lot
Tom
Click to expand...
Click to collapse
You can search updato.com or sammobile for the proper firmware for your device and flash it with the latest Odin. If, for example, you have an N960F, then search for that and then download the most recent specific country firmware that matches your original csc (XME). This will install the latest firmware and should also allow future updates. Suggest reading around a bit before you flash for the first time to be sure you're comfortable with the process. Better to be sure
sefrcoko said:
No he won't...If he is still stuck on the March update (see post 1) then he is not getting updates at all. It's not a question of staggered releases for different countries, it's likely because his CSC doesn't match.
You can search updato.com or sammobile for the proper firmware for your device and flash it with the latest Odin. If, for example, you have an N960F, then search for that and then download the most recent specific country firmware that matches your original csc (XME). This will install the latest firmware and should also allow future updates. Suggest reading around a bit before you flash for the first time to be sure you're comfortable with the process. Better to be sure
Click to expand...
Click to collapse
Many thanks for this.Im in the UK and would like to have the UK firmware.Can I flash my phone with the UK firmware or I have to use Malaysian one.I bought this phone online brand new unlocked but it is Asian version with Exynos.There was a sticker on the box saying about using the phone for 5mins to remove regional lock.This was done by the seller as I can use any sim.I just can't get any updates at all even using smart switch.
Many thanks again
T
lord_belial78 said:
Many thanks for this.Im in the UK and would like to have the UK firmware.Can I flash my phone with the UK firmware or I have to use Malaysian one.I bought this phone online brand new unlocked but it is Asian version with Exynos.There was a sticker on the box saying about using the phone for 5mins to remove regional lock.This was done by the seller as I can use any sim.I just can't get any updates at all even using smart switch.
Many thanks again
T
Click to expand...
Click to collapse
The 5 minute call for regional locks in a one time thing. You shouldn't have to worry about that ever again, regardless of what firmware you flash.
Now you can install the latest UK firmware, but not sure if OTA updates will work that way. If not, you can just repeat this process whenever new firmware is released.
Otherwise, flashing original firmware for your device (Malaysia) should fix OTAs if that's what you want