Formatted Device - T-Mobile Samsung Galaxy S6 Edge

So somehow I deleted everything on my device except for TWRP. I have a refurbished sapphire black 64gb Tmobile s6 edge. Is there a way I could restore it back to normal?

Commanderdrag said:
So somehow I deleted everything on my device except for TWRP. I have a refurbished sapphire black 64gb Tmobile s6 edge. Is there a way I could restore it back to normal?
Click to expand...
Click to collapse
What do you mean by "normal"?
Do you restore all the files that were deleted?
No, unless you made a back folder on another storage area, like a usb-otg flash drive or copied to your pc, those file are gone!
Have you deleted everything including the OS? Meaning your phone will not boot up?
If so, then you will need to download either the full odin tar file to Flash the stock rom using odin with your pc or download, transfer to your phone and flash a custom rom.
That's basically it.
Unfortunately unless you backed up your personal files from your phone that are lost forever.
It sounds like maybe you recently got the phone and hopefully didn't have much on it so take this as a lesson and definitely be careful when checking things in TWRP.
Good luck and sorry to hear that.
There isn't much as far as development in the Tmo S6 Edge forum, but you can check the Tmo S6 Flat forum or check the International Flat S6 forums.
My OZOP Rom is actually build from official Tmo S6 Edge firmware and would suit your devices compatibility perfectly.
Also pretty much any Flat rom will work on your device, just make sure you go slow and read all the instruction and steps posted my the OP.
We write these steps for you, we know how to install our work so again, the instructions are written for users benefit and we take no enjoyment in writing this stuff, especially if you don't read it and post problems!
Major no no! But happens all the time! Very annoying!

stangdriver44 said:
What do you mean by "normal"?
Do you restore all the files that were deleted?
No, unless you made a back folder on another storage area, like a usb-otg flash drive or copied to your pc, those file are gone!
Have you deleted everything including the OS? Meaning your phone will not boot up?
If so, then you will need to download either the full odin tar file to Flash the stock rom using odin with your pc or download, transfer to your phone and flash a custom rom.
That's basically it.
Unfortunately unless you backed up your personal files from your phone that are lost forever.
It sounds like maybe you recently got the phone and hopefully didn't have much on it so take this as a lesson and definitely be careful when checking things in TWRP.
Good luck and sorry to hear that.
There isn't much as far as development in the Tmo S6 Edge forum, but you can check the Tmo S6 Flat forum or check the International Flat S6 forums.
My OZOP Rom is actually build from official Tmo S6 Edge firmware and would suit your devices compatibility perfectly.
Also pretty much any Flat rom will work on your device, just make sure you go slow and read all the instruction and steps posted my the OP.
We write these steps for you, we know how to install our work so again, the instructions are written for users benefit and we take no enjoyment in writing this stuff, especially if you don't read it and post problems!
Major no no! But happens all the time! Very annoying!
Click to expand...
Click to collapse
I have backups of the original files on my device so I'm not worried about that, I have been trying odin and TWRP flashing and neither have worked, to clarify the phone would show the s6 edge logo go black and repeat until eventually going to TWRP. after I had booted it to TWRP once when I press power off in TWRP it would show the log go black and then go into TWRP. in TWRP I able to boot it into a download mode it only showed the ""Downloading . . ." and "Do not turn off target" and an error in the top left saying "SW. REV. CHECK FAIL. DEVICE: 4. BINARY: 1" From this screen I plugged it into my computer and tried to flash a stock rom and odin would give me the error
"<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
Once this failed I was able to turn off the phone by holding volume down + home + power. it then showed the charging image even after unplugged until I held volume up + home + power for it to boot into download mode, this time saying
"ODIN MODE
PRODUCT NAME: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
RP SWREV: B:4 K:3 S:3" in the top left corner
after trying to flash the same rom with odin I got the same error in odin as the one before and another line on the phone saying "SW REV: CHECK FAILED DEVICE: 4. BINARY: 1"

UPDATE: I reinstalled the firmware using ODIN, and found the problem I was getting in download mode was due to the firmware being wrong/not compatible. the firmware that did work is found here: http://www.sammobile.com/firmwares/confirm/89343/G925TUVS4EPH2_G925TTMB4EPH2_TMB/ (posting for anyone who has this problem in the future.)
thanks to stangdriver44 for the push in the right direction.

Related

[Q] noob who thinks he has .PIT trouble

Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
re: pit file
WetbehindEars said:
Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Click to expand...
Click to collapse
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Misterjunky said:
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Click to expand...
Click to collapse
Sorry, I should have mentioned all of that...
As far as I know, I cannot enter into any type of recovery... the only thing that's working right now is download mode, no other button combinations work (volume up+home+on gives me the "Firmware upgrade encountered an issue" story, same with volume up+volume down+power). So I have no way of doing a wipe, unless there's something else I can do. Is there a way I can wipe the phone remotely, from my computer?
A couple other specifics that I should have mentioned in OP:
This phone is only five days old and has not be rooted or modded at all up until yesterday.
I've never put an SD card into the phone (though I have one handy, if there's something I need to do that requires one).
elesbb said:
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Atmazzz said:
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Click to expand...
Click to collapse
Thanks, I haven't tried a different usb port... I'll try that when I get home. The USB cable I'm using is the brand new Samsung cable that came with the phone, I don't think it's the problem but I'll give it a try anyway.
Thanks!
Edit:
After some more digging, I think I might have NAND rw corruption issues (since I can boot into download mode but not into any kind of recovery/bootloader mode). I get this notion from reading http://forum.xda-developers.com/showthread.php?t=1457458, which isn't for the GS4 but I figure it's probably a good diagnostic tool for both. In the thread, Phistachio says that reflashing the kernel (and if that fails, the bootloader) will fix the problem. Will this fix the problem for the GS4 as well?
At this point, I will try a different USB port and/or cable and if that fails, I'll try reflashing the kernel.
Does that sound good?
WetbehindEars said:
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Click to expand...
Click to collapse
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
re: cable, usb port, drivers
WetbehindEars said:
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
Click to expand...
Click to collapse
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Misterjunky said:
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Click to expand...
Click to collapse
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
WetbehindEars said:
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
Click to expand...
Click to collapse
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
elesbb said:
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
Click to expand...
Click to collapse
Yeah, the USB was probably already busy powering the fan and didn't want any of my Odin nonsense.
Thanks again for all the help!

[Q] Kernel Is Not seandroid Enforcing

It maybe a noob question, and I maybe in the wrong section, but here it goes
I own a T-Mobile Galaxy s4 (m919)
Whenever I tried to install any rom by using CWM or twrp,
I always get
Kernel Is not seandroid Enforcing........ etc.
and then it restarts and takes me to the recovery again
Whatever rom I try to install, I end up at this.
Currently I am on 4.4.2 M919UVUFNK2 rooted with CWM
Please help me, I am really crazy about the 5.0 roms :crying::crying::crying:
Unfortunately I just got myself in the same boat as you, I tried to ODIN the phone back to stock per this guide; http://forum.xda-developers.com/showthread.php?t=2258628
This has been unsuccessful, the phone keeps booting looping these messages.
Update CWM or TWRP to latest version. Try formatting system partition from "advanced wipe" and reboot back into recovery to try flashing.
As for Odin restore. Don't try flashing an image that contains a bootloader older than what is on the device.
If (full) MDL has been flashed MDB will fail...and so on. Try the 4.3 or 4.4 restore image instead.
noticed it was the MDL restore guide being followed. So if it is failing try 4.4.2 or 4.4.4 odin image
The message is normal. For the reboots, update recoveries to latest version
Finallyy!!!
Thanks a lot everyone, I didn't know that updating recovery will fix the issue. I thought that whatever version of recovery it is, it is gonna work.
I was about to sell this phone, but you guys saved it
Thanks again
gurnted said:
As for Odin restore. Don't try flashing an image that contains a bootloader older than what is on the device.
If (full) MDL has been flashed MDB will fail...and so on. Try the 4.3 or 4.4 restore image instead.
noticed it was the MDL restore guide being followed. So if it is failing try 4.4.2 or 4.4.4 odin image
Click to expand...
Click to collapse
What does MDB stand for?
Additionally, although a 4.3/4.4.X rom is recommended; is there anyway to have Odin successfully flash from Android 4.4.2 (M919UVUFNB4) to Android 4.2.2 (M919UVUAMDL)? Perhaps by flashing the bootloader first?
XDAUserWork said:
What does MDB stand for?
Additionally, although a 4.3/4.4.X rom is recommended; is there anyway to have Odin successfully flash from Android 4.4.2 (M919UVUFNB4) to Android 4.2.2 (M919UVUAMDL)? Perhaps by flashing the bootloader first?
Click to expand...
Click to collapse
No. You can flash an MDL rom, but not firmware
serio22 said:
No. You can flash an MDL rom, but not firmware
Click to expand...
Click to collapse
The baseband M919UVUAMDL is only a rom? Why is it not considered a firmware? Moreover, what is the difference between a rom and a firmware?
trying to untangle the mess I seem to have made
I have the same problem as the OP and have been trying to flash back to stock. Problem is that I spend the time to download these huge files only to have them end up as a ".7z" file - which is not recognized by Odin.
I finally found one that (within the zip file) had an ".md5" file. In the process of 'unzipping' this file as we speak. *keeping my fingers crossed*
I remember reading somewhere that this had something to do with the Samsung Knox program and "tripping the knox counter" or something like that. I found forums that also said programs like Triangleaway don't work with Knox-infused devices. Is this true. . . ?
I am starting to feel like I should have paid the $40 bucks to have one of those prefab 1-click ("guaranteed") programs do this for me.
So the first scary thing was when I set the PDA in Odin (v3.07) to the .md5 file, it apparently had to do a check of its own:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..​...I say "scary" because it took a while and I was not prepared for it (I thought the program had locked-up). Then again I guess anything takes a while with a 2+GB file. :silly:
So I got the phone into download mode and clicked Start, then saw the following:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl2.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> sbl3.mbn
<ID:0/010> rpm.mbn
<ID:0/010> aboot.mbn
<ID:0/010> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)​Based on that (and the big red "FAIL!" in the top left corner), I had the sneaking suspicion that the program was not quite as successful as I had hoped, so I unplugged the phone (the process had not been gong on for very long).
As soon as I unplugged the phone, I got that error saying there was some sort of problem with the firmware download and that I should use Kies to restore my phone. I thought "YAY! Let's let Samsung clean up my mess!!" But oh no... Kies wouldn't have anything to do with my (now) modified phone and said it was (now) not compatible.
So I tried the Odin thing again (still in process) and noticed what I thought was a graphical error of some sort under the "Do not turn off target !!!" message. I do believe that this is actually the initial tippy tip of a progress meter that is just moving at about the speed of congealed phlegm (again, as everything takes a long time with a 2+gb file).
So that is where I am for now. I figure I'll give this thing 30-40 min and see if this tippy-tip would-be progress meter becomes something a bit more profound. The problems that I have (above the obvious) at this point are:
Odin has marked this as a "FAIL!"
Odin's message box lists this as "All threads completed. (succeed 0 / failed 1)
Odin appears to not be doing anything at the moment and is waiting for my next move
The progress meter (wannabe) is not progressing
There is some microprint in the top left corner of my phone screen that reads:
(red text)ODIN MODE
(white text) PRODUCT NAME: SGH-919
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CS8-CONFIG-LS8: 0X30 (not sure about the 8s - it is very hard-to-read)
(grey text)WRITE PROTECTION: Enable
eMMC BURST MODE: enable (not sure about the "eMMC", again hard-to-read; also interesting to see the lower-case e's here)
(red text)START [224 1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1​
My hopes are not high, but I will keep the faith for now to see if that progress meter grows up and makes something of itself in this world of ours. I am not sure if it is just my innately blind sense of optimism, however it seems that the tippy-tip has become a little larger in the time that it has taken to type this posting.
Then again, my marker may have just shifted. I guess we will just have to wait and see.
It is just barely 7am now and I think I need a beer already.
---------- Post added at 07:32 AM ---------- Previous post was at 07:23 AM ----------
As I am reading my posts I am getting the nasty feeling that this has seemed to turn into a thread hijacking... I will move this onto a new post and post the link here if you would like to respond.
My apologies to the OP.
---------- Post added at 08:24 AM ---------- Previous post was at 07:32 AM ----------
I created a much more detailed (and long-winded) discussion here. Please post any comments/replies there.
Again, apologies to the OP.

[Q] Need Help Unbricking AT&T I747

Unlike the other threads I've read here so far, I wasn't upgrading or downgrading anything on my phone. Last night, I was playing Scrabble (lol) and the phone blacked out and now won't power on. I've tried booting to Download mode and can't even do that. The battery was running low at the time, but that's normal for late at night. I believe I had about 9% battery.
The symptoms of my phone are now:
When I have the battery installed, plugging in the charger doesn't seem to do anything (no charging light).
When I remove the battery, plugging in the charger lights the LED as red for 90 seconds.
Plugging the phone into my computer via USB (without battery), the phone connects (as a device for which I do not have drivers) for 90 seconds (same duration as the red light) and then disconnects.
If I hold the power button in for 12-13 seconds (without battery with charger connected), the red light will go out. As soon as I release the power button, the red light comes back on and the 90-second timer restarts. If I have the phone connected to my computer while trying this, the phone disconnects when the red light goes out and reconnects to the computer (as the same device from above) when I release the power button.
Overnight, I left the phone (with battery) plugged in hoping to fully charge the battery and that would somehow miraculously bring my phone back to life this morning -- it did not. Unknown if the battery is fully charged now or not.
Any suggestions on what I might try next?
See if this helps:
http://forum.xda-developers.com/showthread.php?t=2549068
Lithium ion batteries are at their least stable when they're low on charge like you indicated yours was. How old is your battery? Does it have any bulges you can see or feel? If you put in on a table and flick it on the corner does it spin around? The spin test is by no means conclusive that a battery won't function, but it is indicative of some damage. My original Samsung battery spins like a top, but it still holds a charge and makes an ok backup in a pinch. If you know someone else with a working S3 try their battery in your phone. Otherwise, if there is a Batteries Plus or somewhere like that convenient, pop in and try a replacement. Most replacement batteries I've bought for phones or cameras usually come partially charged so you can probably test it right in store; the guys in the stores might know a thing or two as well as a lot of battery shops have started replacing phone screens and batteries that aren't as readily removable like that other variety of smartphone.
The debrick threads suggested above are a good idea too, but like you pointed out, those are usually for people who tried to downgrade our wonderful secure bootloaders.
If none of that pans out, a repair shop might be able to jtag it back to life.
Good luck.
Update
I was reading this unbrick thread and downloaded this debrick img for I747U. I applied the debrick img to a 32GB microSD card and I got the phone to at least do something. What I see is:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
WRITE 159488 SECTORS..
[COLOR="Red"]FLASH WRITE FAILURE
ODIN MODE[/COLOR]
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE[/COLOR]
[COLOR="Red"]Warranty Bit: 1[/COLOR]
[COLOR="Silver"]BOOTLOADER RP SWREV: 2[/COLOR]
I can now see the phone in ODIN when I connect with USB.
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.
Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.
audit13 said:
Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.
Click to expand...
Click to collapse
I'm hoping to reflash the stock rooted MJB so I don't lose everything that I had on the phone.
Hossy923 said:
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.
Click to expand...
Click to collapse
When I try and flash with the file above with ODIN v3.07, I get:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
At the same time, I get two additional lines on the screen of the phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)
ODIN : flash read failure[/COLOR]
Looking inside the .tar.md5, I do see a PIT file in there.
---
If I flash with ODIN v1.85, I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)[/COLOR]
Flashing via Odin is almost guaranteed to require a full wipe to boot.
audit13 said:
Flashing via Odin is almost guaranteed to require a full wipe to boot.
Click to expand...
Click to collapse
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?
Hossy923 said:
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?
Click to expand...
Click to collapse
Re-partition is unchecked?
I get the same error in Odin3 with Re-Partition checked and unchecked.
You used a debrick image for the i747u? Did you try an i747 de-brick image?
I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.
Hossy923 said:
I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.
Click to expand...
Click to collapse
I've come to believe now that my internal SD card has died. All attempts I've made to flash, whether with ODIN or Miracle Thunder have failed. I get a bunch of errors on the screen talking about errors reading or writing firmware/flash. I even tried doing a nand erase with ODIN and that failed. Unless someone has a better idea, I believe the device has hardware damage.

Samsng Tab 3 7.0 probably hard bricked

My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
untamed1 said:
My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
Click to expand...
Click to collapse
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
bierma32 said:
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
Click to expand...
Click to collapse
Thank you for your response.
First if with search function you mean by using google, I have done a lot of of that, but so far with no luck.
I am pretty good with this stuff but not good enough. I would like to find someone who has either a lot of knowledge or has resolved a situation like mine and is willing to help.
The link you suggested is probably good, but does not totally relate to my situation. They had a working device they were simply trying to root. I instead don't have a working device and not even access to recovery mode. I don't even know right now what files and folders are on my device.
Thank you for the pit file though; now I have to find out whether repartitioning with it would be good, or whether it would push me down deeper in the hole.
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
bierma32 said:
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
Click to expand...
Click to collapse
Bierma32,
first of all thank you for spending the time to assist me it is very much appreciated. I followed your procedure and unfortunately it went nowhere fast. This is the report from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210RUEU0COB1_T210RXAR0COB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what happened earlier with the only difference being the "Set PIT file" command.
Any idea?
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Rom's for Samsung Tab 3 7.0 SM-T210R
Doom1337 said:
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Click to expand...
Click to collapse
For non stock ROM's:
http://forum.xda-developers.com/galaxy-tab-3/development-7
For Stock ROM's:
http://www.sammobile.com/firmwares/
For stock there are faster download sources also, do some google searching. By the way my issue has nothing to do with rooting.
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
I had found another PIT file as well, that looked very promising but did not work. I will try these two. Thanks.
:fingers-crossed:
Continuation
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
untamed1 said:
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
Click to expand...
Click to collapse
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
No battery picture
vinay said:
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
untamed1 said:
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
Click to expand...
Click to collapse
you just hard bricked your device.
but download mode is working so still a hope.(untill power end)
which version of odin are you using.?
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
untamed1 said:
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
Click to expand...
Click to collapse
When this happen.
What was you doing.
Like
Your tab was running you turned off and it won't turn on. Or you flashed a rom/kernel and it won't turn on.
Sent from my D2212 using XDA Free mobile app
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
untamed1 said:
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
Click to expand...
Click to collapse
First of all update your odin to 3.09 or higher if there is. And try flashing again.
(btw is that rom was made for your variant)
Sent from my Xperia E3 using XDA Free mobile app
same issue
i also have an unresponsive sm-t210r that has the OP's issues of a broken looking download screen, no boot and no recovery
pit file problems in odin and timeouts and now not postitive if my device made it to the 4.4.2 locked bootloader. looking to get it back to stock.
will help with files, time etc.
-ty
SOLVED
got my tab(SM-T210R) back up and running,,
been at it a few hours a day all this week,
kies firmware upgrade and initializaton somewhat didnt work. it installed it but always booted a black screen and backlight no sound. no vibiration,
so i am back to help the OP' and all others with this specific issue of dirty flashing directly to 4.4.2 from a rooted custom recovery tab3 that now have a messed up black screen problem but can still sneek into download mode thats looking all messed up> with the fallowing message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
and then get PIT file errors and setup connection hangs.
please be shure you dont still have your custom recovery. you just have to hold home and vol+ ten seconds longer then usual after releasing the power button when the backlight appears. i thot i didnt have mine. until after i did this. now im just not shur if i held the buttons long enough then.
(if you need to get your current binary to offical please use odin's firmware and initialization process.. it will go thru and your binary will be changed to official but you will still have the black screen boot even though kies installed everything. proceed to next)
to get your brick back to being a useful loaf
this is what you need.
factory usb cable
odin 3.07
LT02.pit file from a 4.4.2 firmware (not 100%on that) ask me for the one i extracted if all eles fails
and T210.TWRP.2.8.0.0.tar.md5
start with opening odin
set your pit file and load the twrp recovery_
you want repartition checked for this (loading pit file should automatically fill the check box)
also autoreboot and f.reset time , checkboxes are checked
get your bricked device into download mode and connect
confirm odin sees the device and flash
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.2.8.0.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
at this point within 15 seconds after the reboot i got a splash screen and it booted up into 4.4.2 checked the status, device status of custom.
restarts and power offs are safe at this point. just take 5 seconds longer than normal.
so now we have an operating tablet with recovery and a messed up but working download mode.
checked download mode screen STILL CORRUPTED with the same weird message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
i checked for twrp to operate it did. just took longer to boot it
PLEASE DO NOT AT THIS POINT wipe everything. it only got me back to the black screen with no booting.
and not being able to odin the .md5 package stock firmwares
it put me back an hour to get back to where these instructions end.
if this happends to you run keis firmware and intialize, to get the stock package back in and return to the corrupted download mode to see binary samsung offical.. then continue my odin instructions.
FALLOW UP:
had some time to experiment. i got back to %100 official system/binary and normal download mode with the green android guy being back.
i had updated to the latest TWRP and rooted.
i then unrooted with the super su app
then with the new kies program called SMARTSWITCH i again did the firmware and initialize and it went through and booted. without a hitch.
try it then go ahead and check for stock recovery and android man in download mode
-your welcome
b.t.w it seems in all the mess im still HW-rev 0x5 and it never installed the knox warraty bit..., blessing in disguise?
if this works for people somebody wanna make a sticky and add it to a 4.4.2 unbricking guide?
be aware that this is what worked for me. if you feel a different recovery or pit file may work go ahead. this is my results and wont be held accountable for what happens to you.
> DISCLAIMER> TRY AT YOUR OWN RISK< I AM NOT RESPONSIBLE
kal swift said:
got my tab(SM-T210R) back up and running,,
been at it a few hours a day all this week,
kies firmware upgrade and initializaton somewhat didnt work. it installed it but always booted a black screen and backlight no sound. no vibiration,
so i am back to help the OP' and all others with this specific issue of dirty flashing directly to 4.4.2 from a rooted custom recovery tab3 that now have a messed up black screen problem but can still sneek into download mode thats looking all messed up> with the fallowing message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
and then get PIT file errors and setup connection hangs.
please be shure you dont still have your custom recovery. you just have to hold home and vol+ ten seconds longer then usual after releasing the power button when the backlight appears. i thot i didnt have mine. until after i did this. now im just not shur if i held the buttons long enough then.
(if you need to get your current binary to offical please use odin's firmware and initialization process.. it will go thru and your binary will be changed to official but you will still have the black screen boot even though kies installed everything. proceed to next)
to get your brick back to being a useful loaf
this is what you need.
factory usb cable
odin 3.07
LT02.pit file from a 4.4.2 firmware (not 100%on that) ask me for the one i extracted if all eles fails
and T210.TWRP.2.8.0.0.tar.md5
start with opening odin
set your pit file and load the twrp recovery_
you want repartition checked for this (loading pit file should automatically fill the check box)
also autoreboot and f.reset time , checkboxes are checked
get your bricked device into download mode and connect
confirm odin sees the device and flash
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.2.8.0.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
at this point within 15 seconds after the reboot i got a splash screen and it booted up into 4.4.2 checked the status, device status of custom.
restarts and power offs are safe at this point. just take 5 seconds longer than normal.
so now we have an operating tablet with recovery and a messed up but working download mode.
checked download mode screen STILL CORRUPTED with the same weird message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
i checked for twrp to operate it did. just took longer to boot it
PLEASE DO NOT AT THIS POINT wipe everything. it only got me back to the black screen with no booting.
and not being able to odin the .md5 package stock firmwares
it put me back an hour to get back to where these instructions end.
if this happends to you run keis firmware and intialize, to get the stock package back in and return to the corrupted download mode to see binary samsung offical.. then continue my odin instructions.
FALLOW UP:
had some time to experiment. i got back to %100 official system/binary and normal download mode with the green android guy being back.
i had updated to the latest TWRP and rooted.
i then unrooted with the super su app
then with the new kies program called SMARTSWITCH i again did the firmware and initialize and it went through and booted. without a hitch.
try it then go ahead and check for stock recovery and android man in download mode
-your welcome
b.t.w it seems in all the mess im still HW-rev 0x5 and it never installed the knox warraty bit..., blessing in disguise?
if this works for people somebody wanna make a sticky and add it to a 4.4.2 unbricking guide?
be aware that this is what worked for me. if you feel a different recovery or pit file may work go ahead. this is my results and wont be held accountable for what happens to you.
> DISCLAIMER> TRY AT YOUR OWN RISK< I AM NOT RESPONSIBLE
Click to expand...
Click to collapse
I still cant get it working, i keep getting stuck with it saying it doesnt have a pit file even when i try to load it

I need an expert, my phone may be trashed

This is my first time posting here and I am at a complete loss.
My sister gave me her ATT SM-N910A Note 4. It had started this awful rebooting process. She thought that I would be able to fix it, so I gave it a try. It will still not go past optimizing apps. This is only sometimes. It just reboots, reboots, and reboots. She was running on Marshmallow when this happened. The battery has been replaced.
I took it to the ATT store today and they did not seem like they were very interested in helping me. They kind of blew me off. They told me that since I could not get to recovery booting there was nothing that they could do. So, I proved to them that I could, indeed, get to recovery mode by holding all of the buttons down and putting the battery in. He looked at it for a second, pressed a button and he was done with it. He told me that my system files are deleted. That I need to find someone to help me recover them or I could do it myself. SD updating is disabled. I have to do this from Odin.
So, I think I need Odin files.
Please help!
rabeccalynn92 said:
This is my first time posting here and I am at a complete loss.
My sister gave me her ATT SM-N910A Note 4. It had started this awful rebooting process. She thought that I would be able to fix it, so I gave it a try. It will still not go past optimizing apps. This is only sometimes. It just reboots, reboots, and reboots. She was running on Marshmallow when this happened. The battery has been replaced.
I took it to the ATT store today and they did not seem like they were very interested in helping me. They kind of blew me off. They told me that since I could not get to recovery booting there was nothing that they could do. So, I proved to them that I could, indeed, get to recovery mode by holding all of the buttons down and putting the battery in. He looked at it for a second, pressed a button and he was done with it. He told me that my system files are deleted. That I need to find someone to help me recover them or I could do it myself. SD updating is disabled. I have to do this from Odin.
So, I think I need Odin files.
Please help!
Click to expand...
Click to collapse
You need to flash stock firmware through Odin.
Follow these steps exactly and hopefully you will recover your device.
Things you will require.
1, windows pc
2, download samsung usb drivers or Samsung kies and install it on your windows pc.
3,download odin tool for pc.
4,download stock firmware for your device.
5,your device battery charged minimum 50%.
6,usb 2.0 cable.
7, winzip/winrar installed on pc to extract the firmware file.
How to flash.
1,extract the firmware file you will get a huge file around 4gb.
2,open odin tool and choose AP Tab And upload firmware file that you extracted (ODIN WILL HANG WHEN YOU UPLOAD THE FILE SO DONT WORRY JUST WAIT 4 TO 5 MINUTES UNTIL FILE WILL UPLOAD )
3,put your phone to download mode by pressing (volume down+home+power button all together) hit volume up when you see warning logo)
4,connect phone to pc via usb cable .
5,HIT START IN ODIN TOOL .
6,once odin shows PASS remove usb cable and battery from phone and insert battery again.
7,boot into recovery mode by pressing(volume up+home+power button )
8,navigate via volume keys to "wipe cache" and hit power button and wipe cache.
8,navigate to "wipe data factory reset" and press power button to factory reset.
9,now reboot and wait 10 to 15 minutes and you will boot into system successfully.
11,Let the phone rest for few minutes then complete setup.
Hope this will help.
Samsung usb drivers link
https://m.en.softonic.com/app/samsung-usb-driver-for-mobile-phones
Odin for windows pc.
http://odindownload.com/download/Odin3_v3.10.6.zip
N910A FIRMWARE LATEST.
https://www.androidfilehost.com/?fid=24651430732238073
Just to be sure, what will happen when it reboots? Will it have recovery booting in the top of the screen? Then reboot by itself? Do you mind if I come back here after I get my daughter from school and get everything downloaded for if something goes wrong?
I will be home in about 35 minutes tops.
Trex888 said:
You need to flash stock firmware through Odin.
Follow these steps exactly and hopefully you will recover your device.
It went to the Samsung Galaxy Note 4 Screen and stayed there for a minute. Now it is off. Is this correct?
Click to expand...
Click to collapse
I am still rebooting. What else can I try?
rabeccalynn92 said:
I am still rebooting. What else can I try?
Click to expand...
Click to collapse
I had stupid problem with my s5 long time ago. It was sticky power button. I turn off my phone, use drop of alcohol and drop on power button. Then press couple times and let dry for 1 hour or use hair dryer to do it faster. Then turn on. Works perfect after all of this. Not saying tjis is your problem and this will help in 100% but wort to try. Good luck.
Sent from my SAMSUNG-SM-G935A using XDA Premium HD app
So, Odin will recognize my phone, but not my computer. My computer says that the device is not working properly. What is really going on here?
It is not even going to optimizing apps any longer. It used to always at least go to the ATT logo.
Now, it is vibrating non stop while it is off.
rabeccalynn92 said:
Trex888 said:
You need to flash stock firmware through Odin.
Follow these steps exactly and hopefully you will recover your device.
It went to the Samsung Galaxy Note 4 Screen and stayed there for a minute. Now it is off. Is this correct?
Click to expand...
Click to collapse
Remove battery and insert again Do factory reset and wipe cache from recovery as i mentioned earlier.then reboot and wait 15 minutes.
If odin not recognise your device try restsrt pc and connect again.
Click to expand...
Click to collapse
Here is a little information from my phone:
ODIN MODE: (HIGH SPEED)
Product Name: SM-N910A
Current Binary: Samsung Official (This used to be custom when my sister was using it on Straight Talk)
System Status: Official
Reactivation Lock: On
Know Warranty Void: 0x0
QualComm Secureboot: Enable (CSB)
AP SWREV: S1 T2 A1 A2 P1
SECURE DOWNLAOD: ENABLE
UOC (?)
I can not get back into Recovery Mode
rabeccalynn92 said:
Here is a little information from my phone:
ODIN MODE: (HIGH SPEED)
Product Name: SM-N910A
Current Binary: Samsung Official (This used to be custom when my sister was using it on Straight Talk)
System Status: Official
Reactivation Lock: On
Know Warranty Void: 0x0
QualComm Secureboot: Enable (CSB)
AP SWREV: S1 T2 A1 A2 P1
SECURE DOWNLAOD: ENABLE
UOC (?)
Click to expand...
Click to collapse
Your reactivation lock is on so you cannot flash anything through odin.
Reactivation lock must be turned off to flash.
Only You can turn off from settings/security/reactivation lock and turn it off.
I suggest you take your device to repair center they will take care of it .you cannot flash or do anything because it requires someone who is expert in adb commands to turn off reactivation lock while your device cannot boot.
If your device boot up you can turn off reactivation lock then try odin method that i mentioned earlier.
No way! That is not what I wanted to hear. There is absolutely nothing that I can do for this phone?
Where do I find a repair center?
It said installing system update and got half way through and cut off.
rabeccalynn92 said:
It said installing system update and got half way through and cut off.
Click to expand...
Click to collapse
Keep trying to boot into recovery and do factory reset then reboot.
Trex888 said:
Keep trying to boot into recovery and do factory reset then reboot.
Click to expand...
Click to collapse
I am going to keep trying. When it does get there (see how I said when and not if, confident) I will come back here. There has to be a way inside of this phone!
The recovery mode looks a little different now. When I got it from my sister, I tried a hard reset. It was red and blue then. Now it is white and yellow and has the option of system/mount(?) I am no expert, but I do believe changes are being made here. I am staying hopeful. I really want to use this phone!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N910AUCU2EPH5_CL8932341_QB10663742_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> userdata.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This was what I got after flashing. So, I thought all was good.
rabeccalynn92 said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N910AUCU2EPH5_CL8932341_QB10663742_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> userdata.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This was what I got after flashing. So, I thought all was good.
Click to expand...
Click to collapse
Looks Everything went well but you have to do factory reset from recovery straight after flashing then reboot and wait 15 to 20 minutes on first boot it will take long time.
Okay..
I feel like it is doing something different.
I was able to get into recovery after leaving the battery out while I took my dog to the vet. I got home and it went into recovery. My droid bot fell out dead with his triangle. I pressed the power button and it bought up the menu. I cleared cache and wiped data/factory reset. It turned off talking about verifying some kind of hash tree.. It passed.
Now I am stuck on the Samsung Galaxy Note 4 screen. Is this the screen I need to leave it on for first boot?
rabeccalynn92 said:
Okay..
I feel like it is doing something different.
I was able to get into recovery after leaving the battery out while I took my dog to the vet. I got home and it went into recovery. My droid bot fell out dead with his triangle. I pressed the power button and it bought up the menu. I cleared cache and wiped data/factory reset. It turned off talking about verifying some kind of hash tree.. It passed.
Now I am stuck on the Samsung Galaxy Note 4 screen. Is this the screen I need to leave it on for first boot?
Click to expand...
Click to collapse
Yes you have to leave atleast 20 minutes for first boot.

Categories

Resources