stuck on boot screen with no recovery mode [SM-t320] - Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble

Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.

bmesta said:
Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.
Click to expand...
Click to collapse
Very strange.
Did you tried another firmware version using odin?

edlabh said:
Very strange.
Did you tried another firmware version using odin?
Click to expand...
Click to collapse
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?

bmesta said:
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?
Click to expand...
Click to collapse
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".

crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device

bmesta said:
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device
Click to expand...
Click to collapse
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?

edlabh said:
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?
Click to expand...
Click to collapse
Im really happy to say that now i got a working tablet. I guess removing the battery did the trick.
'edlabh' thanks for all your help. I was able to charge the battery by plugging it directly to the wall. Please note that i had to take the entire tablet apart and disconnect the batteryfor 15 min before reconnecting it. Thank god im good with teardowns and i dont give up that easy

crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
Hello, I was wondering if you would help with the kernel... Idk how to do it. I have done everything he did and even opened my tablet and took out the battery but it still did not work. :crying:
---------- Post added at 07:01 PM ---------- Previous post was at 06:32 PM ----------
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I already tried flashing TWRP, CWM, CF Autoroot (to be able to install a custom recovery). I opened it and removed the battery for 15 mins. unlike this guy, it didnt work for me. I also tried flashing CM12. The tablet wont turn on without being plugged in and I can only access "Downloading Mode"
Perhaps the kernel is broken, but how do I fix it?
This is Odin's message, after flashing stock firmware.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320XXU1BOC1_T320UVS1BOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
But it still wont boot past the splash screen nor can I access recovery mode.

Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key

otyg said:
Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key
Click to expand...
Click to collapse
Also, another thing is the when I plug it in and press the power button it lights up and shows the battery icon with no charge stuck in a loading icon that is not animated.
I will try your suggestion but I had already try (on Kies) Update and Recovery but it didnt work (perhaps because of the tablet being in Downloading mode?)
UPDATE: Kies 3 wont recognize tablet, even in Downloading mode (which is the only mode I can access).
Thanks!

This thread is very old. But I've the same problem, stuck at samsung logo and only get into download mode. Accessing the twrp recovery mode is not possible. I've not flashed the device and the battery had over 90% percent. I started the device suddenly it turned of and it was not possible to start it again. Has anyone solved this problem?

I didn't thought that the battery was the problem, because one time the devices started and showed about 90%, but it was the battery. The batteries are very bad for this device, this is my third one.

Related

[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

[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

Stuck a Teamwin-logo, cant go into recovery mode

I flashed my Galaxy Tab S 8.4 a while ago with TWRP and installed CM12. Worked fine until a couple of days ago when I turned on the tablet. It got stuck on the Teamwin-logo and I cant do anything what so ever... Cant turn it off, reboot, go into recovery etc no matter what I do. Even if I let the battery die out the **** starts again as soon as I turn it on again. Can this be fixed and if so, how? Thanks a bunch!
Put it into download mode and reflash twrp.
Hold HOME +VOL DOWN +POWER in that order until download mode appears.
ashyx said:
Put it into download mode and reflash twrp.
Hold HOME +VOL DOWN +POWER in that order until download mode appears.
Click to expand...
Click to collapse
Well, that worked but now I´m stuck at "Downloading... Do not turn off the target!" instead. *sigh*
Lunaspice78 said:
Well, that worked but now I´m stuck at "Downloading... Do not turn off the target!" instead. *sigh*
Click to expand...
Click to collapse
Well of course it worked. You have to flash TWRP!
ashyx said:
Well of course it worked. You have to flash TWRP!
Click to expand...
Click to collapse
How am I suppose to flash it when I cant get any further than "Downloading..." ?
Lunaspice78 said:
How am I suppose to flash it when I cant get any further than "Downloading..." ?
Click to expand...
Click to collapse
Because that's how you flash twrp. Am I missing something here? :what:
How did you flash twrp the first time?
Also no need to create new threads on the same issue.
ashyx said:
Because that's how you flash twrp. Am I missing something here? :what:
How did you flash twrp the first time?
Also no need to create new threads on the same issue.
Click to expand...
Click to collapse
I did just like that... going into download mode. But as I said, when I go into download mode I get stuck at "Downloading... Do not turn off target!" I cant get any further. The only thing to do is a reboot -> power + vol up and down which results in being stuck in another TWRP-loop. When ever I try to enter recovery mode by power + home + vol up, either when in the TWRP-boot screen loop or when being stuck in the download mode nothing happens. Oh, and also... I cant turn off my device. I try to empty its batteries and when I plug in the charger it boots up and gets stuck at looping the TWRP-logo.
Sorry for the doublepost.
OK I'm a little confused so please clarify.
You put the tablet in download mode. You plug in the usb cable and you see the added message in Odin?
You then load twrp into the AP slot and press start to begin flashing.
Now are you saying here nothing happens, no flashing at all? What does odin do, can you post a screen shot?
ashyx said:
OK I'm a little confused so please clarify.
You put the tablet in download mode. You plug in the usb cable and you see the added message in Odin?
You then load twrp into the AP slot and press start to begin flashing.
Now are you saying here nothing happens, no flashing at all? What does odin do, can you post a screen shot?
Click to expand...
Click to collapse
No no... I dont even get to the point where I can load TWRP etc. This is what it looks like:
http://img.wonderhowto.com/img/00/3...ndows-so-easy-your-grandma-can-do-it.w654.jpg
Not my picture, just trying to illustrate. It has been like this for several hours now and the only thing I can do from here is reboot the device (POWER + vol up + down) which puts the device back in TWRP-boot loop or I can put it in download mod again (POW + HOME + vol down). If I do that the same screen appears and I´m stuck again. No way to enter recovery mode, boot into to the OS or anything.
Hi,
Same problem.
Tried solution above to re-flash TWRP/CWM via Odin.
File with recovery (.tar) successfuly sent to phone in Dwonload mode from Odin but after reboot still stuck on Teamwin logo.
Any other advice?
P.S. Phone stuck after Factory reset attempt from Settings menu.
Odin log:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Well, you dont have the same problem because you actually have the option to flash which I dont. I´m stuck at the screen showed in the screenshot in the above post.
no... I dont even get to the point where I can load TWRP etc. This is what it looks like:
http://img.wonderhowto.com/img/00/3...ndows-so-easy-your-grandma-can-do-it.w654.jpg
Not my picture, just trying to illustrate. It has been like this for several hours now and the only thing I can do from here is reboot the device (POWER + vol up + down) which puts the device back in TWRP-boot loop or I can put it in download mod again (POW + HOME + vol down). If I do that the same screen appears and I´m stuck again. No way to enter recovery mode, boot into to the OS or anything.
Click to expand...
Click to collapse
I don't understand what you're saying here. That's the screen EVERYBODY sees when installing firmware.
What else are you expecting to see? :what:
Put it in download mode. When you see that screen start up odin, load twrp into the AP slot. Plug in the usb cable, wait for the added message in Odin then hit start.
That's it twrp will then flash.
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
xronofag said:
Hi,
Same problem.
Tried solution above to re-flash TWRP/CWM via Odin.
File with recovery (.tar) successfuly sent to phone in Dwonload mode from Odin but after reboot still stuck on Teamwin logo.
Any other advice?
P.S. Phone stuck after Factory reset attempt from Settings menu.
Odin log:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
According to that nothing flashed, did you flash using the AP slot?
ashyx said:
I don't understand what you're saying here. That's the screen EVERYBODY sees when installing firmware.
What else are you expecting to see? :what:
Put it in download mode. When you see that screen start up odin, load twrp into the AP slot. Plug in the usb cable, wait for the added message in Odin then hit start.
That's it twrp will then flash.
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
According to that nothing flashed, did you flash using the AP slot?
Click to expand...
Click to collapse
I tried in AP first and then in BL. Both results are the same. Nothing changes.
Here is the same for BL slot. What I am doing wrong?
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
xronofag said:
I tried in AP first and then in BL. Both results are the same. Nothing changes.
Here is the same for BL slot. What I am doing wrong?
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Please post me a screenshot shot of odin after the flash and the firmware you are flashing.
Only use AP nothing else.
I´m so sorry ashyx for have taken up your time. I feel like a retard. I figured out what I was doing wrong (and I´m not gonna tell you how stupid that was) and now my device works just fine. Thanks for your help anyway!
ashyx said:
Please post me a screenshot shot of odin after the flash and the firmware you are flashing.
Only use AP nothing else.
Click to expand...
Click to collapse
Forum does not allow me to post images as my account has low rights.
Before flash --- http ://s15.postimg.org/74jen6ukr/screen_odin_1.png
After flash --- http ://s29.postimg.org/4te6j5zg7/screen_odin_2.png
twrp-2.8.6.1-i9300.tar from official download page
Lunaspice78 said:
I´m so sorry ashyx for have taken up your time. I feel like a retard. I figured out what I was doing wrong (and I´m not gonna tell you how stupid that was) and now my device works just fine. Thanks for your help anyway!
Click to expand...
Click to collapse
Come on spill the beans, we all do daft things.
Don't keep me hanging! :sly:
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
xronofag said:
Forum does not allow me to post images as my account has low rights.
Before flash --- http ://s15.postimg.org/74jen6ukr/screen_odin_1.png
After flash --- http ://s29.postimg.org/4te6j5zg7/screen_odin_2.png
twrp-2.8.6.1-i9300.tar from official download page
Click to expand...
Click to collapse
Can I ask why you are trying to flash TWRP for the GALAXY S3 and not TWRP for the TAB S? :what:
Surely you should be flashing this:
http://forum.xda-developers.com/showthread.php?t=3074633
ashyx said:
Come on spill the beans, we all do daft things.
Don't keep me hanging! :sly:
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
Can I ask why you are trying to flash TWRP for the GALAXY S3 and not TWRP for the TAB S? :what:
Surely you should be flashing this:
http://forum.xda-developers.com/showthread.php?t=3074633
Click to expand...
Click to collapse
OMG just noticed the thread in on Tab S2. Well I have the problem with Galaxy S3 GT-i9300.
Any luck that I can still get help in this thread? If not, thanks anyways for the time and consideration. Appreciate it.
xronofag said:
OMG just noticed the thread in on Tab S2. Well I have the problem with Galaxy S3 GT-i9300.
Any luck that I can still get help in this thread? If not, thanks anyways for the time and consideration. Appreciate it.
Click to expand...
Click to collapse
Flash the stock firmware this will clear the command that is stuck in cache causing the issue.
For future reference never try to factory reset from android without original recovery.
ashyx said:
Flash the stock firmware this will clear the command that is stuck in cache causing the issue.
For future reference never try to factory reset from android without original recovery.
Click to expand...
Click to collapse
Thanks. This is still an issue for me.
I only know how to flash from recovery(reboot to recovery choose ROM from internal FLASH etc) but the problem is that I can not enter the recovery mode. I am stuck in this cyclic TeamWin logo. Do you know how to act in such case top proceed wtih stock ROM flashin as advised above?

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