Related
Hey guys, I just bought a Galaxy S 3 SCL21 here in Japan from AU KDDI. It is the 4G LTE, 2GB RAM variant.
So far I have not been able to find a rooting method for this phone. It is currently running ICS 4.0.4 build number IMM76D.SCL21KDALJD.
Any help is appreciated.
I think that's not i9305!
Sent from my GT-I9305
olifq said:
Hey guys, I just bought a Galaxy S 3 SCL21 here in Japan from AU KDDI. It is the 4G LTE, 2GB RAM variant.
So far I have not been able to find a rooting method for this phone. It is currently running ICS 4.0.4 build number IMM76D.SCL21KDALJD.
Any help is appreciated.
Click to expand...
Click to collapse
Hey, important information. Don't try to use manual intended for docomo phone. I tried it and now my phone is bricked :silly:
If you explore some method, please send me a mail ....
Spaam said:
Hey, important information. Don't try to use manual intended for docomo phone. I tried it and now my phone is bricked :silly:
If you explore some method, please send me a mail ....
Click to expand...
Click to collapse
No I'm not going to try that. I will let you know if find something.
that is not the I9305 so i can not reccomend anything in this forum . The I9305 forum deals with GT I9305, I9305N & I9305T model numbers
SCL21
olifq said:
Hey guys, I just bought a Galaxy S 3 SCL21 here in Japan from AU KDDI. It is the 4G LTE, 2GB RAM variant.
So far I have not been able to find a rooting method for this phone. It is currently running ICS 4.0.4 build number IMM76D.SCL21KDALJD.
Any help is appreciated.
Click to expand...
Click to collapse
Hello,
I'm with you in the "SCL21, I need help" department. Some info for you though, the international versions are in fact, very different. and the docomo version is too. DON'T use the docomo root method, it will brick your phone.
you can, however use the TeamEpic CWM recovery method. or the Mskip's Toolkit method. I've used both, and it flashes just fine. The problem I run into, is when I try to boot into recovery...the phone doesn't load. It gets stuck with an upside down SGS III logo. It will load into the normal android though. good luck. and if I come across a good method, I'll let you know. you're not alone.
bopatriot said:
Hello,
I'm with you in the "SCL21, I need help" department. Some info for you though, the international versions are in fact, very different. and the docomo version is too. DON'T use the docomo root method, it will brick your phone.
you can, however use the TeamEpic CWM recovery method. or the Mskip's Toolkit method. I've used both, and it flashes just fine. The problem I run into, is when I try to boot into recovery...the phone doesn't load. It gets stuck with an upside down SGS III logo. It will load into the normal android though. good luck. and if I come across a good method, I'll let you know. you're not alone.
Click to expand...
Click to collapse
So your phone is bricked or no ? I am asking because I changed the booting from original to the CWM recovery 2 months ago. Now I cant start up the android. I dont know how to fix it....
no brick
Spaam said:
So your phone is bricked or no ? I am asking because I changed the booting from original to the CWM recovery 2 months ago. Now I cant start up the android. I dont know how to fix it....
Click to expand...
Click to collapse
Hey bro. No my phone isnt bricked at all. what method did you use to flash? And what version of CWM did you use? Which .tar file?
bopatriot said:
Hey bro. No my phone isnt bricked at all. what method did you use to flash? And what version of CWM did you use? Which .tar file?
Click to expand...
Click to collapse
I used the docomo method before notifacations about not working on AU version
oh noos...
Spaam said:
I used the docomo method before notifacations about not working on AU version
Click to expand...
Click to collapse
So its def bricked? What are your indications? Does it do anything? It may be save able.
bopatriot said:
So its def bricked? What are your indications? Does it do anything? It may be save able.
Click to expand...
Click to collapse
yes, bricked...almost 2 months Same issue as your phone - reversal srcreen and logo Docomo when system booting. After voice nothink ...
Standard? What's that?
Yup, I'm there, too. If there's anybody out there with the Japanese AU version that hasn't already made this mistake, it would be great if they could pull the stock recovery from it with Odin... maybe if we had that, we could revive ours. I can still get to download mode, so there's still hope, right?
ryoga_otaku said:
Yup, I'm there, too. If there's anybody out there with the Japanese AU version that hasn't already made this mistake, it would be great if they could pull the stock recovery from it with Odin... maybe if we had that, we could revive ours. I can still get to download mode, so there's still hope, right?
Click to expand...
Click to collapse
You might try the following links to restore your phone. I am looking at getting the same phone this month or next, so very curious if anyone succeeds in restoring.
http://forum.xda-developers.com/showpost.php?p=33953446&postcount=1
http://forum.xda-developers.com/showpost.php?p=23188887&postcount=1
The second link requires an unmodified phone, so you might have to ask around your network and see if anyone can help. Good luck!
---------- Post added at 11:23 AM ---------- Previous post was at 11:18 AM ----------
If you happen to be able to restore your phone and wanna give it another crack. Maybe try the CWM all variants tar and see if it gets you any further. Unfortunately I can't post outside links yet, so you'll have to google for it!
Make sure to follow the directions! ;-D
If you guys are wanting to try other cwm root methods, I would choose one of the Qualcomm S4 root methods, namely either the Verizon, Us Cellular or Sprint as those would be the closest to this model. I would certainly doublecheck the partition table first though.
Oh, and if/when you guys do get root, would any of you mind pulling your radio partition? I'm curious about something with it.
Edit: Scratch that. I'm heading over to Samfirmware.com for the files, if you need to ODIN to stock, head over there and you can pull the files to restore your device.
SCL21 Conflicting reports :/
Hi everyone,
I just got the SCL21 about two weeks ago. I think it's really strange that even on the Japanese forums, there is very little info on rooting this model. From everything I've found, some Japanese sites also both say it's OKAY to root using the Docomo SC-06D recovery and Superuser zip while others say that it's NOT safe to use that same method and it will result in a bricked phone. Really odd, conflicting messages!
I know that some people successfully rooted by flashing the SC-06D custom recovery and then Superuser zip. But, it it also seems like many have ended up with a bricked phone while using this "Docomo method". I tried Bin4ry’s Root and Restore v30 but no luck installing Superuser after the ADB push from the Windows command prompt completed.
I just found the Team Epic CWM recovery method but according to Bopatriot, it flashes fine and then won't boot into recovery. Anyone have any ideas why this model phone is so difficult to root successfully?
Thanks guys!
Any Luck?
I was able to find a post somewhere about the stock rom for it that works with the SCL21 phone but, it was still 4.0.4(epic fail). Anyone have any luck finding 4.1+?
Repeat this is I9305 forum no information on other phones .
Try sammobile.com
4.1.2 was officially released for this phone just this week. Grab it OTA or from SamMobile and flash it.
If you need to root, the SC-06D method works fine.
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
4.1.2 was officially released for this phone just this week. Grab it OTA or from SamMobile and flash it.
If you need to root, the SC-06D method works fine.
Spaam said:
Hey, important information. Don't try to use manual intended for docomo phone. I tried it and now my phone is bricked :silly:
If you explore some method, please send me a mail ....
Click to expand...
Click to collapse
i have the same phoen and now is bricked did you unbricked it?
bboydude said:
i have the same phoen and now is bricked did you unbricked it?
Click to expand...
Click to collapse
What were the steps you used?
My phone keeps failing to update. I keep getting "Failed to update firmware due to network or server problem.Try software update via settings > Software Update > Update or try using PC Kies later". I read all the solutions and ended up just resetting my phone to factory settings and I am still getting the same message. I am don't know what to do at this point. Any ideas?
tarsierspectra said:
I read all the solutions...
Click to expand...
Click to collapse
I do not really believe this. Install a JB stock release for your region with PC Odin. Or install PhilZ kernel and then try one of the available Custom Roms.
If I believe you: so you read all solutions before and I d not need to give you the links to the sticky tutorials related to this.
Good luck.
ThaiDai said:
I do not really believe this. Install a JB stock release for your region with PC Odin. Or install PhilZ kernel and then try one of the available Custom Roms.
If I believe you: so you read all solutions before and I d not need to give you the links to the sticky tutorials related to this.
Good luck.
Click to expand...
Click to collapse
OK, I am sorry, I guess I didn't see all the solutions yet. Yes, I need links. I don't know how to install JB stock release. I don't know what PC Odin means. I basically read that I must have rooted my device and now I can't install updates and that if I wipe the device it will be able to install firmware update. I am puzzled why factory reset doesn't fix the problem but please point me to the links where I can learn how to install JB stock release and whatever PC Odin thing I need. Thank you
Sorry, but no links. You are a member since Nov 2011. You should know about the simple way of searching for sticky threads in a forum already. If you are too lazy to do this, then you should stop thinking about manual updates and custom roms, kernels etc.
But you could continue asking for spoon-feeding. There might be other members here that aren't tired of this way of being a part of XDA and they will post the links for you.
ThaiDai said:
Sorry, but no links. You are a member since Nov 2011. You should know about the simple way of searching for sticky threads in a forum already. If you are too lazy to do this, then you should stop thinking about manual updates and custom roms, kernels etc.
But you could continue asking for spoon-feeding. There might be other members here that aren't tired of this way of being a part of XDA and they will post the links for you.
Click to expand...
Click to collapse
I am sorry I don't understand what a custom rom is and I don't want any. I don't want to do any manual updates. I just want update my phone as my phone keeps.telling me there is a firmware update. I searched for the error message and came back empty handed. The suggestions I found said to reset the phone but it didn't help me. You talked.about some things that I have never heard of so I asked for clarification. Is it wrong to ask? Yes I have been a member zince 2011 when I got my phone. I asked some questions back then and nothing since. It does not mean I am an expert in find out about some roms. I.just wanto have the the latest update.released by Samsung on my Samsung phone.
To putnit in a simple way. Why not just bring your phone to a customer service center and let them update for you?
Since you are not sure what those terms means and your phone seems to be in stock version. Samsung will update for you.
Sent from my GT-N7000
devll said:
To putnit in a simple way. Why not just bring your phone to a customer service center and let them update for you?
Since you are not sure what those terms means and your phone seems to be in stock version. Samsung will update for you.
Sent from my GT-N7000
Click to expand...
Click to collapse
There is no Samsung Customer Center in Massachusetts. What do I do in this case?
Call up Samsung and ask them?
Sent from my GT-N7000
devll said:
Call up Samsung and ask them?
Sent from my GT-N7000
Click to expand...
Click to collapse
So I called them and they don't have a center in the area that I can go to and even if they did he wasn't sure if they could update my international phone.
Does anyone know what the problem is?
tarsierspectra said:
So I called them and they don't have a center in the area that I can go to and even if they did he wasn't sure if they could update my international phone.
Does anyone know what the problem is?
Click to expand...
Click to collapse
See original android dev section, the 3rd sticky thread particularly, read it thoroughly!!!!
..
tarsierspectra said:
So I called them and they don't have a center in the area that I can go to and even if they did he wasn't sure if they could update my international phone.
Does anyone know what the problem is?
Click to expand...
Click to collapse
did you a brand new phone or was it used.
Did you change stuff? root it debloat it?
Anything else? A little history is nice
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
did you a brand new phone or was it used.
Did you change stuff? root it debloat it?
Anything else? A little history is nice
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Brand new phone. I have not done anything to it. Was using it as is. Always got updates with no problem until a few days ago. I just want to get an official update that Samsung released.
tarsierspectra said:
Brand new phone. I have not done anything to it. Was using it as is. Always got updates with no problem until a few days ago. I just want to get an official update that Samsung released.
Click to expand...
Click to collapse
first, try Kies.
if that fails try again.
Then we check efs
try dial *#06# and check if imei is the one you expect, it should not be 00049.
Then dial *#272*yourimeihere# and check if csc is selected. That should be the one of your phone. Maybe something went wrong with previous updates there. If you select the original your phone came with then a factory reset wil occur. be carefull, phones have bricked that way.
Now another ingredient for succesful updating is pcode, this can be found via a another code. forgot which one. Getting that back is to much work, unless you have efs backup of working condition. Which nobody has usually.
I would recommend going back via dr ketans pc odin way to latest rom for the csc found in previoius steps and in a clean way. Or earliest and update back up. Before you do that backup efs Search how.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
first, try Kies.
if that fails try again.
Then we check efs
try dial *#06# and check if imei is the one you expect, it should not be 00049.
Then dial *#272*yourimeihere# and check if csc is selected. That should be the one of your phone. Maybe something went wrong with previous updates there. If you select the original your phone came with then a factory reset wil occur. be carefull, phones have bricked that way.
Now another ingredient for succesful updating is pcode, this can be found via a another code. forgot which one. Getting that back is to much work, unless you have efs backup of working condition. Which nobody has usually.
I would recommend going back via dr ketans pc odin way to latest rom for the csc found in previoius steps and in a clean way. Or earliest and update back up. Before you do that backup efs Search how.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I already tried Kies and before I reset the phone to factory settings it gave me an error message in Korean. Then I reset the phpne and now Kies says that I am on the latest firmware, but I am not.
IMEI is not 00049
The right CSC is selected.
The previous updates ran just fine.
Iam having the same exact problem! "Failed to update firmeware due to network or server error. Please try again later or try using kies" My phone is not rooted. What could be the problem? Earlier updates were just fine! Please help, I want to update it to jellybean 4.3 !
Sent from my GT-N7100 using xda app-developers app
lohrii said:
...Please help, I want to update it to jellybean 4.3 !
Click to expand...
Click to collapse
The latest official update from Samsung is 4.1.2!
Is that same iemi as that thai dia joker as he puts it a developer iemi so instead of insulting this guy why dont you just help him especialy that ti di character now of subject when i was a little boy oh so many years ago i tried ti di on clothes thought it was so boring seems things are still the same
Sent from my GT-N7000
ThaiDai said:
The latest official update from Samsung is 4.1.2!
Click to expand...
Click to collapse
He has a note 2. It has official 4.3.
Why don't you try a factory reset by Settings>backup&reset>factory data reset! maybe this solved the issue, and try to be on a fast and secured data connection!, 3G will work! try this if it doesn't work then more solutions by my side!
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
Oh god are you on the US version (SGH-I537)? If you're on the international version (I9295) ignore this post but otherwise, you need to read and take in my short rant. Trust me I wish this weren't the case, but it is, and it's important:
The Galaxy S4 Active i537 has a locked bootloader. There is no way around this, no ifs ands or buts. You simply cannot flash custom ROMs or recoveries. That's it, end of story as far as CM, CWM, AOSP and such things are concerned. That being said there is a sort of recovery called SafeStrap which you can use to make nandroid backups, flash mods and STOCK-BASED roms, but it's not a true custom recovery in the sense that we had been used to, because of this locked bootloader nightmare.
OK so I think you're gonna want to check out this thread. It's all about how to install any firmware from download mode, I think you're gonna have to go with NE3 or NH3.
Let me reiterate. NO CUSTOM ROMS. NO CWM. No Paranoid, no cyanogenmod, no AOSP, no crossing go before going directly to jail. Sorry for the stupid joke but seriously, you have got to keep your phone on stock-based roms (of which there are unfortunately few).
Firmware download links
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
What phone do you have (i537 or i9295) and what version of firmware were you on?
Devo7v said:
What phone do you have (i537 or i9295) and what version of firmware were you on?
Click to expand...
Click to collapse
i537 and second to last, I537UCUCNE3
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Web browser login, edit, advanced.
Add "solved" to title?
same problem with my i537, need help
timmytron said:
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Click to expand...
Click to collapse
Need help, having the same problem
baddhabbitz88 said:
Need help, having the same problem
Click to expand...
Click to collapse
Have you used ODIN before?
i537 Stuck in download mode
timmytron said:
Have you used ODIN before?
Click to expand...
Click to collapse
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Did you get my PM?
timmytron said:
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
Click to expand...
Click to collapse
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
Well AT&T decided to completely lock us out on this particular version on this particular phone. At least we have *ROOT*.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Devo7v said:
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Click to expand...
Click to collapse
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
timmytron said:
Did you get my PM?
Click to expand...
Click to collapse
yeah I got it thanks but it didn't work still digging
baddhabbitz88 said:
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
yeah I got it thanks but it didn't work still digging
Click to expand...
Click to collapse
Always check the stickies.
http://forum.xda-developers.com/showthread.php?t=2892445
please can anyone help?
I cant find this anywhere.
I did the 5.1.1 update so not sure if I need the original or the updated one?
I think this is the one I had T817AUCU1AOH2
thank you
so with 44 views and no answers , I'm assuming there's no firmware for at&t?
those bastards!
so can't prove I bought it to send it in for warranty repair......
now willing to try anything! any devs have a new hack they need tested?
rredlin said:
so can't prove I bought it to send it in for warranty repair......
now willing to try anything! any devs have a new hack they need tested?
Click to expand...
Click to collapse
Thank @envirocy for this. SM-T817OH1 firmware.
https://drive.google.com/file/d/0B1DaPxlq4YoQUXQ0NG5xVUpKUm8/view?usp=sharing
ashyx said:
Thank @envirocy for this. SM-T817OH1 firmware.
https://drive.google.com/file/d/0B1DaPxlq4YoQUXQ0NG5xVUpKUm8/view?usp=sharing
Click to expand...
Click to collapse
so extracted the zip and put ap in Odin and it worked. but I have no cell signal no lte or anything. it shows att but nadda. did I do some wrong? should I have put all 4 files in the spots in odin?
also I found there is now an oem unlock. does that mean I can unlock this bootloader or get perm root? or twrp?
thanks
You need to flash all of them in the appropriate slots, but you probably can get away with just the modem. That should get your signal back.
Enable OEM unlock before rooting with Kingroot again.
You can't install twrp or supersu as you still have a locked bootloader.
ashyx said:
You need to flash all of them in the appropriate slots, but you probably can get away with just the modem. That should get your signal back.
Enable OEM unlock before rooting with Kingroot again.
You can't install twrp or supersu as you still have a locked bootloader.
Click to expand...
Click to collapse
Thanks my friend, you really do help, not only me but a lot of ppl!
I just did all 4 anyways....
Tried king root 4.8.0 and it put a different kind of warring on screen (blue screen over entire tab that read unauthorized software install, go to an at&t store now, or something) that also tripped Knox to = 1 (yes I had oem unlocked).
So at this point I will try anything.......Goin to try king root 4.8.2!
Thanks
rredlin said:
Thanks my friend, you really do help, not only me but a lot of ppl!
I just did all 4 anyways....
Tried king root 4.8.0 and it put a different kind of warring on screen (blue screen over entire tab that read unauthorized software install, go to an at&t store now, or something) that also tripped Knox to = 1 (yes I had oem unlocked).
So at this point I will try anything.......Goin to try king root 4.8.2!
Thanks
Click to expand...
Click to collapse
well. I give up! for now......locked again. same as last time
rredlin said:
so with 44 views and no answers , I'm assuming there's no firmware for at&t?
those bastards!
Click to expand...
Click to collapse
ikr im stuck over here
which one is the modem
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
ashyx said:
You need to flash all of them in the appropriate slots, but you probably can get away with just the modem. That should get your signal back.
Enable OEM unlock before rooting with Kingroot again.
You can't install twrp or supersu as you still have a locked bootloader.
Click to expand...
Click to collapse
which one is the modem
Man this worked great for me
Sent from my LGLS991 using XDA Free mobile app
Updating to Marshmallow FAILS... dm-verity verification failed... need to check drk
ashyx said:
Thank @envirocy for this. SM-T817OH1 firmware.
https://drive.google.com/file/d/0B1DaPxlq4YoQUXQ0NG5xVUpKUm8/view?usp=sharing
Click to expand...
Click to collapse
I sent my tablet to Samsung Repair a few weeks ago (they replaced the battery and LCD due to overheating /freezing up), and just got it back today in the mail. It had Android Marshmallow 6.0 on it when I sent it to them, when I got it back today it has Lollipop 5.1. I tried to update through system update, and when it restarted to flash the update, it failed.
So I tried to reset it back to stock in the Backup/Reset option in settings and when it restarted to reset to Factory, I got this message :
"dm-verity verification failed...
need to check drk"
So I flashed this stock ROM you provided here, hoping a clean slate would fix the problem, and it flashed perfectly in ODIN. Then I tried to update to Marshmallow again, and after it downloaded and restarted to update it said "FAILED"
I have no idea how to update now.
How in the world does Samsung repair then send back a tablet that can't update!
Can you please help in any way?
I really don't want to send my tablet back for a third time and wait 2-3 more weeks, especially after the Samsung Note 7 recall, probably take months to get back. My wife is still waiting for her Note 5 screen to be replaced and they have had her phone almost a month now.
xdaDemiGod said:
I sent my tablet to Samsung Repair a few weeks ago (they replaced the battery and LCD due to overheating /freezing up), and just got it back today in the mail. It had Android Marshmallow 6.0 on it when I sent it to them, when I got it back today it has Lollipop 5.1. I tried to update through system update, and when it restarted to flash the update, it failed.
So I tried to reset it back to stock in the Backup/Reset option in settings and when it restarted to reset to Factory, I got this message :
"dm-verity verification failed...
need to check drk"
So I flashed this stock ROM you provided here, hoping a clean slate would fix the problem, and it flashed perfectly in ODIN. Then I tried to update to Marshmallow again, and after it downloaded and restarted to update it said "FAILED"
I have no idea how to update now.
How in the world does Samsung repair then send back a tablet that can't update!
Can you please help in any way?
I really don't want to send my tablet back for a third time and wait 2-3 more weeks, especially after the Samsung Note 7 recall, probably take months to get back. My wife is still waiting for her Note 5 screen to be replaced and they have had her phone almost a month now.
Click to expand...
Click to collapse
Try Device Recovery with Kies. That's how I upgraded to Marshmallow.
hello,
sorry for upping this offtopic.. but i have sm-t817a at&t carrier tablet, and how can i change official firmware to custom. i can't find any information about this in web... please help me
Same problem kinda
serik1986 said:
hello,
sorry for upping this offtopic.. but i have sm-t817a at&t carrier tablet, and how can i change official firmware to custom. i can't find any information about this in web... please help me
Click to expand...
Click to collapse
Hello, I own samsung galaxy tab s2 SM-T817A baseband version
T817AUCU1AOH2
The problem is that it is stuck on lollipop and i think i need to insert att sim to get update but the problem is that i live in Pakistan i have tried many times to update it but nothing works for me.i have galaxy tab a t550 as well and it runs nougat.i need to get the 7.0 firmware for my tab s2 so i can flash it i cannot find the firmware anywhere else please help me to upgrade my tab s2 to nougat
AT&T Galaxy Tab S2 SM T-817A Nougat firmware T817AUCU2CQE3 here:
http://combinefile.com/home/browse/category/id/9448/T817AUCU2CQE3
colins said:
AT&T Galaxy Tab S2 SM T-817A Nougat firmware T817AUCU2CQE3 here:
http://combinefile.com/home/browse/category/id/9448/T817AUCU2CQE3
Click to expand...
Click to collapse
thx,i update my s2,it's free download.
This worked for me as well; was able to go straight from 5.1.1 (OH2) to 7.0 (QE2) via the link above and Odin 3.12.7. Didn't need to flash any intermediate versions.
houtaobbs said:
thx,i update my s2,it's free download.
Click to expand...
Click to collapse
Please upload to gdrive, link not work.
Thanks.
Alexander Kalinin said:
Please upload to gdrive, link not work.
Thanks.
Click to expand...
Click to collapse
Try this
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=28744
It's the same firmware as Colins'
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!