HELP!! SM-T810 Not Booting - Galaxy Tab S2 Q&A, Help & Troubleshooting

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/

Related

Flashed Germany 4.3 Stuck on Samsung Screen

Hello Guys i flashed the Germany Version of 4.3 lte last night and in doing so i have Temporarily killed my Phone.
I have tried all the Recoveries processes via Kies and Odin and i am having no luck.
I think the reason why it won't flash is because the Germany 4.3 is a Newer Version than the Stock 4.1.2.
When i'm in Odin i get sboot.bin Fail when trying to Flash the Latest Stock rom. I am able to Flash the Germany 4.3 again and that flashes but then the Phone Stays on the Samsung Flash Screen.
Could someone please Help? I have been on with this for Hours now. I think what i need is a 4.3 Version of any rom in Odin .tar format so i can at least get the phone to boot up and then maybe i can get CWM Recovery on there and flash a Stock rom that way.
Thanks in Advance
You have to remove sboot.bin and tz.bin when downgrading. Be careful, downgrading will give you Knox warranty void 0x1!
Sent from my GT-I9305 using xda app-developers app
.NetRolller 3D said:
You have to remove sboot.bin and tz.bin when downgrading. Be careful, downgrading will give you Knox warranty void 0x1!
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
I have already seen that Message in Tiny Writing. What does that mean if i get that and how do you remove sboot.bin and TZ.bin
Do i remove them from the Stock 4.1.2 or the Germany 4.3?
My head is well and truely done in. I was up till 5am trying to fix it and then when i woke i went straight back to it and i still havn't got it working.
Thanks for your help in advance.
marti4578 said:
I have already seen that Message in Tiny Writing. What does that mean if i get that and how do you remove sboot.bin and TZ.bin
Do i remove them from the Stock 4.1.2 or the Germany 4.3?
My head is well and truely done in. I was up till 5am trying to fix it and then when i woke i went straight back to it and i still havn't got it working.
Thanks for your help in advance.
Click to expand...
Click to collapse
I am in the same boat if u found a solution help me also
Currently i flashed philz recovery upon which i have flashed tgp 11.30 but have no imei baseband.
marti4578 said:
I have already seen that Message in Tiny Writing. What does that mean if i get that.
= warranty void and no way so far to remove the count .
Click to expand...
Click to collapse
AMoizK said:
I am in the same boat if u found a solution help me also
Currently i flashed philz recovery upon which i have flashed tgp 11.30 but have no imei baseband.
Click to expand...
Click to collapse
Have you got any efs backup made by yourself? Or have you ever used boeffla kernel or any other that backups efs partition?
Hbohd said:
Have you got any efs backup made by yourself? Or have you ever used boeffla kernel or any other that backups efs partition?
Click to expand...
Click to collapse
Hello I don't have any EFS Backups done by Myself and i have never used Boeffla Kernel or any other Backup. I am so at my Witts end it unreal.
I have tried to do Kies recovery and i am back at the Firmware Upgrade Encountered an Issue. Please select recovery mode in Kies and Try again.
I have no idea which way to go or what to do. I know it will be fixed but i have little Faith at the Moment.
Thanks for your help in advance.
marti4578 said:
Hello I don't have any EFS Backups done by Myself and i have never used Boeffla Kernel or any other Backup. I am so at my Witts end it unreal.
I have tried to do Kies recovery and i am back at the Firmware Upgrade Encountered an Issue. Please select recovery mode in Kies and Try again.
I have no idea which way to go or what to do. I know it will be fixed but i have little Faith at the Moment.
Thanks for your help in advance.
Click to expand...
Click to collapse
THE kies frimware intilition doesnt work as you have 4.3 bootloader and knox blocks older boot loader
dont worry when 4.3 becomes available in your area it wont have to downgrade and ultimately this method will work but still things are looking pretty bad dor the intermediatory days.
PS is ther anyway to restore baseband imei without any backup
AMoizK said:
THE kies frimware intilition doesnt work as you have 4.3 bootloader and knox blocks older boot loader
dont worry when 4.3 becomes available in your area it wont have to downgrade and ultimately this method will work but still things are looking pretty bad dor the intermediatory days.
PS is ther anyway to restore baseband imei without any backup
Click to expand...
Click to collapse
What if i download the Germany Version again and try flashing. I thought it would of worked? I am now in this situation surely the Country it comes from wouldn't make a difference? Could someone take the Germany 4.3 and make it a Working Version .tar file to flash with Odin3?
marti4578 said:
What if i download the Germany Version again and try flashing. I thought it would of worked? I am now in this situation surely the Country it comes from wouldn't make a difference? Could someone take the Germany 4.3 and make it a Working Version .tar file to flash with Odin3?
Click to expand...
Click to collapse
I ment through kies.
Hello Guys i have Fantastic News!!
I have no idea what i did different, However i have reflashed the German 4.3 on my GT-I9305 and this time to my Total Surprise it worked!!
I wish i could say what i did and it worked but i have absolutely no idea what was done differently.
Thanks all for your Help.
I will say i installed the drivers manually and just on the off chance i flashed it again with the file i downloaded last Night. I also flashed a recover trying to get it to load a recover so i could flash a zip file.
marti4578 said:
Hello Guys i have Fantastic News!!
I have no idea what i did different, However i have reflashed the German 4.3 on my GT-I9305 and this time to my Total Surprise it worked!!
I wish i could say what i did and it worked but i have absolutely no idea what was done differently.
Thanks all for your Help.
I will say i installed the drivers manually and just on the off chance i flashed it again with the file i downloaded last Night. I also flashed a recover trying to get it to load a recover so i could flash a zip file.
Click to expand...
Click to collapse
Which file can u specify pls and also which recovery also is wifi and data working
AMoizK said:
Which file can u specify pls and also which recovery also is wifi and data working
Click to expand...
Click to collapse
which file????:crying:
AMoizK said:
which file????:crying:
Click to expand...
Click to collapse
Please read the rules .
JJEgan said:
Please read the rules .
Click to expand...
Click to collapse
Can u point me to the rules
AMoizK said:
Can u point me to the rules
Click to expand...
Click to collapse
http://forum.xda-developers.com/announcement.php?f=256
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer. (Also refer to Rule 16)
Finally
I am so feeling sucessful right now although i didnt got 4.3 but i was sucessful in getting my imei and baseband and network back.:good:
Sorry for the late response but when you get stuck on the Samsung boot screen all you have to do is boot into Recovery and do a Factory Reset and Wipe Cache.
Another thing to remember is to flash the modem for your country otherwise you might accidently disable some frequencies and enable other useless ones.
xkwizt said:
Sorry for the late response but when you get stuck on the Samsung boot screen all you have to do is boot into Recovery and do a Factory Reset and Wipe Cache.
Another thing to remember is to flash the modem for your country otherwise you might accidently disable some frequencies and enable other useless ones.
Click to expand...
Click to collapse
Doesn't work I will syill be stuck at boot screen
AMoizK said:
Doesn't work I will syill be stuck at boot screen
Click to expand...
Click to collapse
Which 4.3 update did you flash? I used the DBT German one.
Did you flash the right modem too? It worked for me and i was using a i9305T. All i did was flash the latest modem (from the brand of phone i have which is Telstra) and did a wipe data and wipe cache.

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL
Yo.
Basically been using this phone for ages, having random freezing issues for a while, so I decided to /****it and re-stock everything because it is likely that I have been an idiot with kernels/messing around with stuff once.
This freezing has persisted through stable, unstable, nightly CM 10.2/10.3/11 ROM's as well as pure stock and unrooted, so I figured it was something deeper down - the kernel, and I got a stock kernel for i9305 (attached). Everything basically went to ****, the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
No biggie, I'll just ODIN it up (3.0.7) and flash the stock firmware, except now (this did not happen before the kernel flash) it simply fails with "sboot.bin FAIL", which people claim to be a PIT error (Kies not open btw, no KiesTrayAgent either, it's on the PC though), so I grab a i9305 stock PIT that I try and flash with the stock firmware, except now it gets stuck at "Get PIT for mapping" and never moves onwards from there.
So I'm essentially stuck with a problem that can probably be fixed by a stock firmware ODIN flash, and a problem that prevents me from fixing the PIT stuff to get the stock firmware through.
I have tried ODIN-flashing CWM recovery as well as stock recovery (also attached), but I'm still stuck on the logo regardless.
Any help here? Kinda lost ATM.
EDIT: Can't link/attach the .rar with the files. :S
Just re-install your back up
Raistlin1158 said:
Just re-install your back up
Click to expand...
Click to collapse
Retarded answer.
@OP
We need more data... first, which kernel did you flash ? If you can't attach it, link to it.
Second, what stock rom did you try to flash ?
Third, are you knoxed?
Hey guys.
Cheers for the answers, I just figured it out though actually. The sboot.bin error was caused by some bootloader-stuff-thingy I could hardly explain if I got a book on it. I got ahold of another stock ROM which flashed fine, I cleaned up and all that (NAND erase all did the job), back to CM11 as TouchWiz didn't fix my problems.
To answer your questions (others might have the problem and find this thread):
http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265 <- kernel
I tried to flash an "XXBMD1" stock ROM from SamMobile, it had worked previously.
I am Knoxed and have "tripeed the fuse" (trying to fix the crashing issues I went back to stock ROM, then it prompted for the 4.3 TouchWiz update which brings KNOX), so I'm without warranty (ODIN returns "KNOX Warranty Void: 1), but I guess I can consider this a learning experience as everything turned out good enough in the end.
There you go:
Based on JellyBean 4.1.2_XXBMD1 <--- You can't flash 4.1.2 because of the knox bootloader.
Had you tried a stick 4.3 you might have been sucessfull
daedric said:
Retarded answer.
Click to expand...
Click to collapse
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
soft bricks aren't fixed by restoring nandroids.
Update odin and change usb cable and port.
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
chongc1996 said:
soft bricks aren't fixed by restoring nandroids.
Click to expand...
Click to collapse
A nandroid wouldn't do any harm as soon as he got a recovery working
Raistlin1158 said:
Update odin and change usb cable and port.
Click to expand...
Click to collapse
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
daedric said:
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
A nandroid wouldn't do any harm as soon as he got a recovery working
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
Click to expand...
Click to collapse
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
.... the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
Click to expand...
Click to collapse
chongc1996 said:
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
Click to expand...
Click to collapse
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
daedric said:
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
Click to expand...
Click to collapse
ok sir, you are right, calm down, I'm out of here.
Cheers for the helpful as well as not-so-helpful responses, all back up and running now.

need firmware for SM-T817A

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'

Help! Not sure what to do, but my Galaxy Tab isn't working properly.

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!

Stuck at Bootlogo after taking OTA!

I have a brand new N950F software version- {N950FXXS3CRF1}
After upgrading To {N950FXXU3CRF4}
Phone won’t pass the boot screen it’s just stuck on Logo! Getting dm-verity error
Even though the system is 100% stock!
I wiped the phone still same/! Even reflash with odin package{
N950FXXU3CRF4} still same/! The phone only boot after flashing back to the old version {N950FXXS3CRF1}
And again if i take the OTA it will stuck on bootlogo again?
What is actually wrong with this phone!
Confused/! Any help will be a lot appreciated/!
Thx/!
Did you use Odin 3.13?
Older versions could cause problems
Of course!
j_hansen said:
Did you use Odin 3.13?
Older versions could cause problems
Click to expand...
Click to collapse
Yes I tried with latest odin/!
But even the OTA will kill the phone/!
After taking official OTA/! phone stuck at bootlogo/!
I don’t know why but I’m getting dm-verity error after ota installation completed/! Even though the system is 100% stock!
Sooo much confused
Sorry I'm no expert but is there by any chance an sd card in the phone, those seem to cause all sorts of weird unexplained errors as well if corrupted
No!
j_hansen said:
Sorry I'm no expert but is there by any chance an sd card in the phone, those seem to cause all sorts of weird unexplained errors as well if corrupted
Click to expand...
Click to collapse
There is no sdcard/!
Did you try and download one off web and try instead of ota. Says dm-verity failed seems like bad download or mismatched firmware.
Yes/!
Amos420en said:
Did you try and download one off web and try instead of ota. Says dm-verity failed seems like bad download or mismatched firmware.
Click to expand...
Click to collapse
Yes i flash same package with odin and same result/!
The update failed. you need to reinstall using odin.
No matter/!
me2151 said:
The update failed. you need to reinstall using odin.
Click to expand...
Click to collapse
I completely flash the entire package with odin:!
But after flash complete phone will stuck at bootlogo!
Phone will only boot after downgrading to (RF1)
and i take the same OTA again it’s throwing dm-verity error
If its brand new, take it back where you bought and get it replaced..
Need Advice!
wase4711 said:
If its brand new, take it back where you bought and get it replaced..
Click to expand...
Click to collapse
July security patch is out
With build number-N950FOLN4CRG1 should i flash it with odin?
M just asking bcz if it stuck at bootlogo after flashing this package i will not be able to downgrade bcz of the updated bootloader-/!
What’s your advice?
pixel989 said:
July security patch is out
With build number-N950FOLN4CRG1 should i flash it with odin?
M just asking bcz if it stuck at bootlogo after flashing this package i will not be able to downgrade bcz of the updated bootloader-/!
What’s your advice?
Click to expand...
Click to collapse
I'd be wary of flashing N4. Are you using USB 3.0 I've read it can bork things up. Or try another version of oden. Otherwise I'd do as wase said and take bace to store see if they can help or replace.
pixel989 said:
July security patch is out
With build number-N950FOLN4CRG1 should i flash it with odin?
M just asking bcz if it stuck at bootlogo after flashing this package i will not be able to downgrade bcz of the updated bootloader-/!
What’s your advice?
Click to expand...
Click to collapse
Stop flashing stuff; you obviously dont know what you are doing
If its a brand new phone like you say it is, return it where you bought it and get a new one
And dont just flash things to your 1000 dollar device unless you are 100% sure of what you are doing..
wase4711 said:
Stop flashing stuff; you obviously dont know what you are doing
If its a brand new phone like you say it is, return it where you bought it and get a new one
And dont just flash things to your 1000 dollar device unless you are 100% sure of what you are doing..
Click to expand...
Click to collapse
Thanks for your advice!
I am 100% sure! What i am doing! That's why i didn't flash it yet! I m just asking for advice!
That's why i m out of there where i bought it!
Thanks!
if you actually were 100% SURE of what you are doing, you wouldn't have to keep asking the same question over and over
wase4711 said:
if you actually were 100% SURE of what you are doing, you wouldn't have to keep asking the same question over and over
Click to expand...
Click to collapse
M 100% sure about flashing stuff! Not about this problem!, that's why i m here asking for your help!

Categories

Resources