SM-T800 Soft-bricked, Odin stuck initialization. Stuck Samsung logo bootloop. - Galaxy Tab S Q&A, Help & Troubleshooting

What I have is a SM-T800 Wifi Samsung Galaxy Tab S 10.5. Below what odin mode states:
Product Name: SM-T800
Current Binary: Samsung Official
System status: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: A1
On to the problem: Device stuck at "Samsung Galaxy Tab S" (bootloop). It also will not boot into recovery. It will, however, boot into download mode. Therefore, I booted it into download mode, hooked it up to Odin 3.09, downloaded the latest stock firmware from sammobile, and attempted to flash via Odin. Latest Samsung drivers (1.5.55.0) are installed, and Odin definitely recognizes the device. However Odin always stuck at initialization. I have research and it sounded like the "Half SDS" symptoms in that thread (You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.).
I have been researching this problem for a while now (2 days and one very late night) and I have read all sorts of threads ( http://forum.xda-developers.com/galaxy-tab-s/help/to-event-soft-brick-disaster-t2838473/post54618555#post54618555 , http://forum.xda-developers.com/galaxy-tab-s/help/how-to-unbrick-tablet-model-t800-t2863246 , http://forum.xda-developers.com/galaxy-tab-s/help/mannage-to-soft-brick-t3025447 , http://theunlockr.com/2014/08/09/how-to-unroot-the-samsung-galaxy-tab-s-10-5-wifi/ , http://forum.xda-developers.com/galaxy-tab-s/help/wiped-accident-t2832346 , http://forum.xda-developers.com/galaxy-tab-s/help/stuck-sudden-bootloop-t3067280/) from forums in every corner of the Internet, but I'm still completely stuck. Any help is greatly appreciated.
What I have done so far and the results:
1. Kies 3 = Input Model & SN then selected firmware update and initialisation. Download then when come to software update and initialization, the progress stuck at 0% for forever.
2. Smart switch = same result as Kies 3.
3. ADB_fastboot = It would not list samsung device.
4. TWRP (twrp-2.8.7.0-chagallwifi.img.tar) = odin stuck initialization
5. Odin 1.85, 3.04, 3.07, 3.09, 3.10.6 (T800XXU1BOJ1_T800XAR1BOJ1_HOME.tar) -> stuck initialization. I also downloaded PIT from ( http://forum.xda-developers.com/galaxy-tab-s/help/t800-pit-file-t2818817) and try repartition but still got same result. Also Kies is not running the background during my Odin attempts.
For the record, I don't know any details about the exact version of Android the tablet ran before it failed (I bought this tablet online used). I also used OEM cable then swapped with 4 other cables and switch between window 8.1 and 7 pc. Switched USB ports (Used USB 3.0 and 2.0 ports).
Does stock SM-T800 Tablet has locked bootloader? Do I have to try bootchain? I'm at the end of my wits. Short of an actual eMMC failure, I can't see any reason why this tablet would be permanently hard bricked or why ODIN refuses to cooperate. Can anyone suggest anything?
Finally I have submitted a repair ticket with Samsung but my device is 1yr 4 months old so no warranty. However I check the warranty for my tablet (via http://imeidata.net/warranty/samsung) and it say its has Factory Warranty Coverage until October 31, 2016. What does that mean and would that cover anything with regard to my problem?
P.S. Sorry for long post.

Never has KIES on my PC, only the samsuns and usb driver installed. (only my way) Also for my HTC devices i ever only install the drivers, because of there are complications with ADB, flashing, etc. if you have the HTC Device Manager on your PC. Perhaps for samsung is the same. But I don't know.
I have also used Odin3_v3.10.6. for flashing recovery, but I and many other user here use TWRP 2.8.7.2 from @ashyx .
For command line search for Heimdall. A tool made for Linux user but works also on Win.

First things first. You need to post a screen shot of odin when it fails so we can assess the situation.

@ashyx, thanks for you help.

ashyx said:
First things first. You need to post a screen shot of odin when it fails so we can assess the situation.
Click to expand...
Click to collapse
Thank you for responding.
Newbie to this forum. I don't see attachment icon on desktop version . When I select insert image, it ask for URL and I can't add outside link? I have try it on old tablet and firefox and chrome. Is it because I need to have 10 posts before I can add picture?
I'll research more how to add picture.
Anyways here the Odin log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T800XXU1BOJ1_T800XAR1BOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004>
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

OK, which version of odin are you using and which slot have you placed the firmware file in?

ashyx said:
OK, which version of odin are you using and which slot have you placed the firmware file in?
Click to expand...
Click to collapse
I have used alot of odin version (v1.85, 3.04, 3.07, 3.09, latest 3.10.6). I put the md5 file in the AP/PDA slot. I downloaded the T800XXU1BOJ1_T800XAR1BOJ1_HOME.tar.md5 from sammobile.com with XAR (which I confirmed with Kies 3).

I have the exact same problem with T700 and I'm running out of ideas!
Any luck??

Sorry mate, in my instance there was nothing left that could be done on my end. I finally send it to samsung repair service last week and they repaired for me (under warranty luckily). Apperantly it was hardware failure, they replaced the whole PBA. I suggest talking with samsung tech at best buy or something to see if you can do the same. If you don't have warranty you might need to pay for the repair. Again sorry to be bearer of bad news cause I was in same boat as well. Good luck.

Ditto the symptoms on an 18 month old SMT800.

Same thing for me on my SM-T805.
Odin 3.10.7 says the following:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
there it's stuck forever.
I've tried twrp_3.0.2-1_sm_t805.tar as well as CF-Auto-Root-chagalllte-chagallltexx-smt805.tar.md5 (Odin -> AP).
I've tried different USB cables and PCs on top of that.
Latest Samsung drivers are installed (1.5.51.0).
Somewhere I read that it helps to unplug the battery beforehand. Did anyone try that yet?
I'm kind of hesitant to disassemble my tablet, but may try it soon as last resort. My warranty is already void/expired anyway.
Cheers
Michael

Phear666 said:
Same thing for me on my SM-T805.
Odin 3.10.7 says the following:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
there it's stuck forever.
I've tried twrp_3.0.2-1_sm_t805.tar as well as CF-Auto-Root-chagalllte-chagallltexx-smt805.tar.md5 (Odin -> AP).
I've tried different USB cables and PCs on top of that.
Latest Samsung drivers are installed (1.5.51.0).
Somewhere I read that it helps to unplug the battery beforehand. Did anyone try that yet?
I'm kind of hesitant to disassemble my tablet, but may try it soon as last resort. My warranty is already void/expired anyway.
Cheers
Michael
Click to expand...
Click to collapse
Put it in download mode.

ashyx said:
Put it in download mode.
Click to expand...
Click to collapse
the device was in download mode (Vol Down+Home+Power, on warning screen Vol Up)... That's why I even tried to rule out connection issues by trying different USB cables, USB ports and different PCs.

Related

[Q] Phone stuck after flashing stock rooted

OK--1st post EVER in a forum, so I feel like I'm gonna get layed into,
but here goes:
Just got Epic Touch two days ago and felt I needed root so I downloaded
and used the EL29 Odin one-click method of flashing the stock rooted ROM.
This was yesterday. No problems. Took 15 minutes. I installed some apps,
then I installed ROM Manager And tried to use it to install CW, but I'm not sure if that was successful, as I tried to do a couple of NAND backups from within the GUI
of ROM Manager and failed both times, going to the stock android recovery screen.
I think I pulled the battery both times.
Then I installed Widget Locker, was playing around with that for a bit, took
a photo and tried to attach it to a text response, then the phone locked while
I was sending that. Pulled battery, wont get past Samsung startup screen.
Looked around a bit, decided to try and reflash using the one-click method.
I get:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.bin
every time. BTW, I cannot access anything with VolUP+power buttons.
I've tried different combos of that, always Samsung boot screen hang.
I can get into Odin, and Odin sees my device. but never has the device indicated
that anything is happening. No progress bar.
Also, I have tried the two USB cables that i have in all the ports of my computer,
but I do not have another handy.
So I poked around and found this:
http://forum.xda-developers.com/showthread.php?t=1492771
which suggested I individually flash ROM, kernel, and modem.
none of that has worked, either.
Flashing the modem does get a green progress bar(in Odin, not on the device),
but then it hangs at--
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
flashing kernel yields:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_KERNEL_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
...and a hang.
So....... haven't foud anything else adressing this. Lotta stuff out there about
careless ICS/CWM brickers, but I didn't do anything fancy, did I?
Just stock rooted, 5 hours of use and blammo.
Thanks for the assistance.
Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?
Edit: If you need them, the samsung drivers are here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Please remove kies prior to installing them. In any case, you should probably uninstall what you have now and install the driver suite if it's still not working, then reboot the pc and try again. Sometimes the drivers aren't working correctly and require a reinstall.
I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure.
Sent from my SPH-D710 using XDA
I think what Rocket meant to say is not use Rom Manager any more.
Sent from my SPH-D710 using XDA
RE:
>> Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?<<<<
I have BOTH installed...but Kies I only installed midway (i.e. this morning)
through troubleshooting. nonetheless i will uninstall/reboot/reinstall/reboot
with these guys. Which is better?
And YES, EVERY time i've tried something with either EL29 oneclick or 1.85 regular Odin, I have always started Odin first, and then plugged the phone in.
If I plug the phone in before putting it in download mode, it just displays an empty battery charging icon, and cannot be turned off except by removing battery.
RE:
>>>>I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure. <<<<<<<<<<
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Thanks for the replies.
iguai said:
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Click to expand...
Click to collapse
It sounds like you're ok but Kies needs to go, it conflicts with the regular drivers and causes issues using odin. Goood luck and let us know how it goes.
make sure the samsung drivers are on you PC/Laptop. make sure your computer sees your phone. I have read that sometimes trying different USB ports and cables can be helpful as well when using Odin. hope this helps.
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
iguai said:
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
Click to expand...
Click to collapse
You're likely bricked. Sorry. Rom Manager has been bad for almost all Samsung phones.
Sent from my SPH-D710 using XDA
Allow your phone to charge for SEVERAL hours.
Follow this guide to the letter: http://forum.xda-developers.com/showthread.php?t=1274337
Flash this rom which has root: http://forum.xda-developers.com/showthread.php?t=1703406
If you follow this correctly and your phone does not boot. You are bricked.
Sounds like somehow you reversed the modem or rom and flashed them between the phone and pda (which I hope you didn't because you are bricked if you did... but its good in away because you can take it back and say look what I woke to...).
Let us know if it works...
Edit- and if it does boot, don't ever try to install cwm with rom manager on this phone.
No dice. I am, however, going to give it one more try on a friends computer this evening. That's my last throw though, I think, unless I get some fresh inspiration.
I'll report back tomorrow.
OK---I gave it everything, and no dice.
This phone was bricked.
I believe using ROMManager to try and install CWM f'd some things,
and perhaps when I was trying to do individual flashes
in Odin I flashed a modem in PDA.
Thanks for all responses.
Tried everything and nothing
So I wasn't trying anything crazy with my phone, left it charging, and went to check the time and it was off, tried turning it on and nothing.
I was running CM10 Beta 2... so I went into recovery mode, tried to run do wipe factory reset, wipe dalvik, wipe cache, flash the CM10 again, and it was getting stuck.
Mounted usb on pc and tried to save some files to flash the full tar through odin, in the middle of that copy it failed, so I tried to odin the tar anyway and it was getting stucked.
Tried flashing modem separately - stuck on Wait 2 mintues...
Tried flashing kernel separately - stuck on NAND Write Start!!
Tried flashing rom - stuck
Tried flashing pit file - stuck
Tried one click - stuck
The thing is that I can't just say to samsung service that I didn't do anything to the phone, because when you try to boot in recovery it shows CWM 6..., but only one line, it doesn't really load cwm.
So even if I use a usb jig to reset odin counter, they'll notice I had done some stuff to the phone, even when I wasn't really doing anything when it crashed.
Any new way to fix the phone? I don't have insurance or anything, so I might be pretty much screwed
Anything else I could do? Thank you very much!

[Q] Soft bricked? Need to restore back to stock

Hey yall,
Neighbor's kid handed me his Sprint galaxy s3 today and asked if I could fix it. It's not working at all right now. I'd like to think I know a thing or two about technology but I know jack about Android...I use the other brand of phones. Anyway, lots of searches led me here to ask for help.
Far as I can tell it's a Spring LPH-710 Samsung Galaxy S3. When I turn it on it has the firmware upgrade encountered an issue screen and it doesn't do anything else. I can't get VOLUP+HOME+POWER to work (recovery mode I think) but download mode works with VOLDOWN+HOME+POWER.
I went and downloaded the Kies program from samsung but it fails to load the software. here's the error message; CAN'T POST LINKS! arrrgggg. It says "Failed to upgrade firmware due to an unexpected error. Do you want to run firmware emergency recovery now?" It then says I should enter some recovery code from another PC which I don't have.
It also has some small red text on the phone screen after I saw the Kies error message. It says SW REV CHECK FAIL : Fused 2 > Binary 1. That makes no sense to me but it's red and Kies error out so I'm going to assume that's not good.
I don't have a recovery key to use and the kid tells me he never backed it up to a computer before. I've read Odin is the preferred method to use for stock recovery but I don't know what files to download and use. Apparently, people are pretty unhappy with Kies...kinda like iTunes I guess. Why can't the Kies software wipe and reload the phone? Am I doing something wrong?
The device malfunctioned or had an error when he tried doing an update / flash. And if Kies is malfunctioning you can try PC Odin.
Download Sammy drivers of device, download the stock .tar image of the sprint s3 ( L710VPUDND8 ), download Odin v3.07
- At PC. Open Odin in admin mode. Click PDA and select the .tar image file and let that load and leave everything else alone in the program.
- On device press vol dn + home + power to get into download mode, press vol up to continue.
- Plug in device and let driver installation be completed. If a box in Odin ( on PC ) doesn't show a COM:##, replug device or try different ports and cables.
- Once you have that all set up click start and leave it to flash. It takes roughly 15 minutes to flash the whole thing or lesser.
If all else fails tell him to bring it in for servicing.
Posted via XDA Mobile
Thanks for the reply Sparks. I downloaded Odin 3.07, uninstall Kies and rebooted the PC. When I loaded the .md5 file, I then plugged in the phone and saw it look for drivers. The phone shows up on COM3. Below is what I see after I press start. Doesn't look good to me! Did I get the right file?
I've read that attepting to alter the operating system will void the warranty. Would this line on the download screen indicate he tried to do that? Current Binary: Custom. He said the contract is up in March so I'd hate for him to get screwed over by this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUDND8_L710SPRDND8_L710VPUDND8_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> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's the right file. Says md5 is valid.
Binary custom and/or warranty bit 1 means he already tried to flash something and it ticked the counters so he's out of luck getting it repaired.
Go download the Galaxy S3 Samsung drivers through the official site and install them, reboot pc and try the method again in a different USB PORT ( Preferebly 2.0 slots ) some ports and different cables can be iffy at times.
Posted via XDA Mobile Free

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

Memory Damaged message, won't reset, recovery mode fails (red triangle,Android down )

Hi, I've searched hi and low for help, but can't find anything that seem to apply to my phone or case. I have a Canadian Mobilicity S3 model SGH-T999V that just bricked itself. Everything is official other than I unlocked it to switch to Wind: Binary Count = 0.
The Story: Last week (Tuesday Sep 22nd 2015) The phone restarted a few times for no apparent reason, then the next day errors about missing files started to pop up to the point that I had to reset the phone to be able to use it. Start fresh all good for a week, then one restart yesterday (Sep 30) and this morning I have a screen that says: "Device Memory Damaged - the data partition has been corrupted.you need to reset your device to factory defaults.this will erase all your date. (reset device button)" I press the button nothing happens, so I take out the battery, leave it while at work, then try again: same thing - I try to reboot into recovery but fail: I get a down android with an open belly cover and a red triangle picture for a bit and the phone reboots back to the damaged memory screen. I can get into the download mode, but Odin doesn't see the phone.
Any advice on how to proceed from here would be greatly appreciated.
I've used Odin before on my Nexus S, but that was many moons ago, it's dead now...
Thanks in advance.
Can you get into download mode? If you can, yet flashing the stock ROM from sammobile.com and flash it using Odin.
Thanks for the reply.
Odin doesn't see the phone and I don't remember exactly how to use it either, but I know it's very model specific, as to files and ROMs to download and install, hence the advise seeking. I guess I'm hoping someone in the know can tell me "follow the instructions for such [more popular] model #, that will work on the 999"...
The T999v is a very popular model in Canada as it was used by Wind and Videotron.
Are you able to boot the phone into download mode? The Samsung drivers are installed? Are you using a Win7 machine?
Yes it boots into Download mode but not into recovery. I have Kies installed along with the drivers, could reinstall that just in case. Running Windows 10 Pro Preview, in the process of upgrading to the final release.
I recommend grabbing the latest firmware from sammobile.com for the phone and flash it in Odin 3.07 with the phone in download mode. I would not bother with Kies.
I've updated my build of Windows 10, that may have been one of my problems, now Odin reacts to the phone but fails:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNH2_T999VYVLFNH2_T999VVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says in red: "Secure Check Fail: aboot
So much for that! guess it's fried at the hardware level.
I'm thinking you are suffering from a hardware failure as stated by the message you mentioned before. It has happened to others and I can't recall anyone having much success in restoring functionality.
If you want to try again though, uninstall kies from your computer as it interferes with Odin. There is also a newer version of Odin, but I doubt that would make much difference on the S3.
If you are unable to get it working again and want a relatively cheap fix, search ebay for a used motherboard or a device that has a broken screen but otherwise works. Then swap out the board.
Sent from my SGH-T999 using Tapatalk
The update is failing because the ROM you are flashing has a bootloader that is older than the version currently installed on the phone as verified by the following stop error in Odin:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
I have a feeling DocHoliday77 is probably right, I've bought a new phone from my provider for 9$ (Alcatel onetouch Pop D3) and posted a wanted ad for broken S3 ... not ready to completely give up on the S3 just yet, but neither do I have high hopes.
Getting rid of Kies
The firmware is the most recent for the SGH-T999V on sammobile.com - I can try without the V maybe
Only T999V firmware will work on the T999V.
If you are selling it and it has a good working display you should be able to get a decent amount for it still. Not sure how much they are going for these days but it's always been the most expensive and in demand part for the device.

Need help with flashing GT-N7105

My Note 2 randomly started to reboot and got stuck in the GT-N7105 screen. I have never rooted or done anything similar (never tried either). I have no idea what is wrong. It had been restarting randomly at about once a day or once every 2 days.
But here is what I tried from various forums and guides:
1. Removed battery and held power button for up to a minute then tried turning on - Didn't help
2. Help Power+Vol up+Home and tried factory reset. Factory reset failed. (nothing could be mounted) (I removed sd card before doing this).
3. I can get the phone to download mode, but flash fails on Odin. (I downloaded latest firmware for GT-N7105 from sammobiles). Haven't tried using PIT file and re-partition option (too scared).
4. I also tried using the Unified Android Toolkit. It was a failure too.
Other info: 1. I do NOT have USB debugging enabled (I feel so bad for not doing it); 2. Odin shows NAND write failed error.
If anyone can help it would really be great. I mostly got help from this post: http://forum.xda-developers.com/showthread.php?t=2154890 But this is for GT-N7100.
What error did you get in Odin? Did you use the original Samsung cable to flash via Odin? Tried other USB cables and all available USB ports?
audit13 said:
What error did you get in Odin? Did you use the original Samsung cable to flash via Odin? Tried other USB cables and all available USB ports?
Click to expand...
Click to collapse
NAND write failed. Yes I used the original samsung cable, its the best one i have. Tried all available USB ports
What is the actual file that did not flash? Maybe post the Odin log?
audit13 said:
What is the actual file that did not flash? Maybe post the Odin log?
Click to expand...
Click to collapse
This is the .md5 file I used: http://www.sammobile.com/firmwares/download/48001/N7105XXUFOB2_N7105OLBFOD1_XSP/
Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The error after sboot.bin file leads me to believe that the ROM may not be made for the phone or the bootloader in the ROM is too old.
The model # is confirmed as being the GT-n7105 in download mode?
audit13 said:
The error after sboot.bin file leads me to believe that the ROM may not be made for the phone or the bootloader in the ROM is too old.
The model # is confirmed as being the GT-n7105 in download mode?
Click to expand...
Click to collapse
Yes, I'm sure the model number is GT-N7105. Here is what the Download mode screen says:
ODIN MODE
Product Name: GT-N7105
Current Binary: Samsung Official
System Status: Official
Knox Warrant Void: 0
RP SWREV: A2
"Android Logo"
Downloading...
Do not turn off target!!
This screen also stays the same when I'm trying to flash. I'm not sure if that's ok or not.
Everything looks fine. Maybe try a different computer or version of Odin?
audit13 said:
Everything looks fine. Maybe try a different computer or version of Odin?
Click to expand...
Click to collapse
This is what has been bugging me, everything looks fine, but nothing seems to work. I've tried every version of Odin, but I used only one PC. If u have any suggestion on why NAND write would fail, do tell me.
Could it be because of USB debugging not being enabled?
Thanx a lot for your help!
I think you'll need to try another PC.
Odin usually fails to write for five main reasons:
1) nand chip is damaged;
2) USB cable is not compatible with Odin and/or phone;
3) USB port (usually USB 3.0/3.1 port) is not compatible with Odin, phone, and/or USB cable;
4) ROM was not made for the phone;
5) ROM's bootloader is older than bootloader on the phone.

Categories

Resources