I have a SM-T827V which has been working great, up until last night. At that time I pulled it out and opened the magnetic cover which normally wakes the screen. This time, nothing. I thought maybe the unit had turned off for some reason or hadn't been properly connected to the charger so the battery had died, so I held the power button to turn it on. The tablet vibrated and the "Samsung Galaxy Tab S3 powered by Android" screen appeared and sat for what seemed like at least a minute or two. At that point the device went black, vibrated again, and the same screen appeared. It kept doing this in a cycle, endlessly.
After a little online searching it seems that this is not a completely unusual problem with the Tab S3 and the recommended solution is to reflash the firmware. So I downloaded Odin 3.14.4 and the most recent Android 9 firmware from Sammobile.com, installed the Samsung USB drivers and put the device into Odin mode. Following provided instructions I ran Odin, selected the firmware files in the appropriate places (I used HOME_CSC rather than just plain CSC as I was hoping to retain my settings and apps) clicked Start and Odin went to work. It ran through some text output and ended with "<OSM> All threads completed. (succeed 1 / failed 0)" and the tablet rebooted. It vibrated and came up with a black screen with "Recovery booting...." in blue lettering at the top. Progress! Except now it just boot loops to that screen instead of the Samsung logo one.
I tried re-flashing with CSC instead of HOME_CSC. Same results. Tried booting with the SIM and SD cards removed. Same results. Tried re-flashing with the SIM and SD card removed. Same results. So, am I SOL or is there something else I can try?
Thanks in advance!
Anyone? This tablet is just over two years old and I'm not really in a position to replace it so I'd really like to get it working.
davel23 said:
Anyone? This tablet is just over two years old and I'm not really in a position to replace it so I'd really like to get it working.
Click to expand...
Click to collapse
Didn't see it earlier.
Another thing to try is flashing with older Odin version as somewhere I read that 3.13 is recommended for Android 8 and 9 while 3.14 is for Q.
Flashing several times one after another is worth a try as well.
Related
Hi, got a galaxy s2 i19210 and using cm-10-20120926-UNOFFICIAL-i9210t
Was having a few random restarts and found that if I tweaked the voltages it would put an end to this. I found I had to use DreamKernel-GTI9210T-v1.7.1CM10-20121010073231-CWM to do this, so I downloaded it and tried to install via the rom manager.
Phone restarted to install, now when it turns on it says the usual 'galaxy s2 i9210' etc, then it usually goes to the blue cyanogen symbol spinning. Unfortunately, it no longer reaches this and the screen stays black. The lights turn on, but screen stays off.
Can't seem to get into download or reset mode with the key combination and sometimes instead of turning off the phone restarts which makes trying the key combinations a bit harder.
Have tried removing and replacing the battery but that didn't help either.
HOWEVER!
My computer recognises the phone although I can't access the hdd because the phone is locked
Odin recognises the phone
So, what options do I have to get my phone working again?
I've looked at a few threads and googled a bit but haven't found anything substantial
To clarify it's a Galaxy S2 i9210T 4G Australian Telstra phone
So I finally got into odin mode and cleared the dalvik cache and did a factory reset. Installed latest i9210 firmware via download mode and odin and everything is working again. Unfortunately I lost all my data but i'd prefer that than a brick. Still doesn't explain what happened in the first place though, did I use the wrong kernel or go about the install the wrong way? I'd like to go back to cm10 but fix the random resets.
You're more likely to get an answer here. Almost everyone here has an I9100/I9100T.
MistahBungle said:
You're more likely to get an answer here. Almost everyone here has an I9100/I9100T.
Click to expand...
Click to collapse
Thanks bud!
Hello! So.. I have a problem and i sincerely don't know what to do. 3 days ago, after a day of use (everything went ok for a while) i came home, i grabbed the charger and pluged it into my phone so it can..charge(nothing out of ordinary). After like 1 hour, i took my phone, unpluged it from the charger and pressed the on/off button to open my phone, check my gmail,facebook, the usual..buuuuuut it won't open..
For the first couple of minutes i thought it was just a bug and tried to restart it(take the battery out, wait 1 minute, put it back in, press "the button" and so on) but still it would not start. RESEARCH TIME!
After this, i went online from my laptop and started looking for explanations regarding why is my phone (i am trying to avoid the word but..) maybe "bricked"..
Here is a video i found online that explains what my phone is behaving like: "*SOLVED* SAMSUNG GALAXY S2 wont turn on, in description"
(i can't post links )
IMPORTANT
- My S2 has the official software ( JB 4.1.2)
- Never rooted my phone
- Never tryed to change anything to the software
- Did a couple of factory resets in the last 1 and a half year just to refresh it(so it is not such an old phone)
- It is not under warranty
Ok.. after 1 day of research i tryed the following methods:
-went into recovery mode and did a factory reset to it, erased the cache, rebooted it etc..still nothing
-when i saw it was not working, i went further into the download mode. Odin on my computer, official firmware downloaded(4.1.2) ready to go..
After i waited for a couple of minutes so Odin would do it's magic, the little window( In odin, the one with factoryfs, cache,hidden etc.) reached the "Reset" status, the blue bar on my phone dissapread and it started to reboot.. but here everything got out of control.. my phone started to reboot like this: samsung logo on for a few seconds, and then the green android with the blue things spinning appeared on the screen but just for one second, and then, it was gone...and the phone started to repeat itself.. i mean the logo and the green android again and again, without any improovment and way to stop it.. so i pulled the battery out and started thinking for other solutions..
OK, after i saw this, i tried again with the 4.1.2 one, and then with the 4.0.4 one(i thought maybe an older soft would help me) but still it wouldn't go through all the way( ok honnestly i think this one was the one that wasn't stuck rlly on the green android screen but on the samsung startup screen with the S sign on)..
the end..
Sorry for the long story but i really don't know what to do with my phone
I am willing to listen to any solution you guys can offer..thanks :good:
Keep flashing different firmwares and take a look at this guide
forum.xda-developers.com/galaxy-s2/help/guide-26-12-flash-stock-firmware-rom-t2365701
http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
I have a Samsung Galaxy S2 SCH-R760.
What happened: Tried to update phone from standard IceCreamSandwich to Jelly Bean via Samsung provided SimpleUpgradeTool. Very new to flashing phones, forgot to check model number, first attempt failed. Eventually got the right one (difficult to do with my model apparently), and the mobile network wouldn't work. Was told to reset APN, could not find it anywhere in the system.
Got fed up and decided to revert back to original OS, which failed. Waited overnight (it was late) with the phone off. Found the right file (just going to go back to Jelly Bean), however whenever I attempted to get into recovery mode it told me there was not enough power and to charge the phone. Phone was plugged in, this happened a couple of times. Now after the phone has been plugged in for well over 3 hours I cannot get the phone to power on or anything, it absolutely will not respond. Attempted to use Kies, will not recognize my phone model and is waiting for the phone to be connected anyway. When plugged in (trying/using various different cords) I have a little faint blue light flashing in the top left corner of the phone (not the phone screen).
The phone has been in excellent condition up until this point, and I have little reason to believe that my battery just suddenly went 100% bad after showing no signs of decay in recent weeks. Any suggestions?
How did you try to revert? But kind of sounds like it might be hard bricked. If you can't get get into Download mode by Vol Down and Power and it isn't charging not even sure if this would work: http://forum.xda-developers.com/galaxy-s2/general/ref-usb-jig-faq-frequently-questions-t1402286
But unless you try another battery or something like that jig, and it does not power up to any screen, then your only hope would be a JTAG service. I recommend these guys:
http://mobiletechvideos.mybigcommerce.com/
es0tericcha0s said:
How did you try to revert?
Click to expand...
Click to collapse
Just tried to use the samsung quicktool program and just install the old OS back onto the phone.
Aquaserge said:
Just tried to use the samsung quicktool program and just install the old OS back onto the phone.
Click to expand...
Click to collapse
I'm not familiar with the QuickTool. Why not use Odin? It's the preferred method for most popular Samsung phones.
Hello All!
My first post here, even though I have long been a lurker. I hope I'm posting in the right place. If not, apologies, and Mods - please redirect me, and I shall re-post in the correct place.
Phone: SAMSUNG GALAXY S3 GT-I9300 International version
Last known installed/running OS: Official SAMSUNG JB ROM (Unsure WHICH version) after having run on CM 4.4 for a couple of weeks.
PROBLEM:
a few months after going back to stock, Phone suddenly developed issues of random reboots. These would happen at any point in time, with no predictability whatsoever. One fine day, it rebooted, and wouldn't get past the Samsung splash screen. Pulling the battery and trying to restart phone resulted in the same stuck at Samsung logo issue.
Left the phone alone for a couple of months after this as I had a spare, but finally decided to try and revive the S3.
Phone does not charge when connected to charger. At least, it shows no visible signs of it. It DOES, however, try booting itself when plugged in, but gets stuck on the first screen of ODIN Download mode, instead of the Samsung logo splash screen as it used to earlier. Also note that this screen it gets stuck on is a pixellated screen, not the clear normally seen screen when entering ODIN mode.
The Vol UP, Home and power button combo brings me to this very same screen, there is no recovery menu to be seen, as would be normally. The Vol DOWN, Home and power button combo brings me to the regular clear ODIN mode as usual.
The headings at this screen read:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
I have read through most posts regarding similar issues on XDA as well as other forums, and tried flashing stock firmwares (single AND multiple part ones) through ODIN, with no success. The error i always get is as in the attached screen captures.
I've tried ALL versions of ODIN, and many PIT files. All were failures.
So, is this a dead for all purposes phone, or do I still have hope since ODIN mode is still available?
I don't think USB debugging was checked before bricking, because ADB toolkits just keep waiting for phone to be detected.
All drivers are up to date and installed correctly. Kies is not installed.
Any help is welcome.
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
I have a Device here which seems to have the same or at least a similar problem, however, i got it for free from someone else to experiment with, so there is no urgent need to repeir it.
I tried flashing a pit and erasing nand, but when i start to do it, odin just gets stuck at "erasing", if i try to flash a full firmware it just hangs at "getting pit for mapping" so i assume the nand is gone for good... however, i have one more dead s3 arround that seems to have a burned cpu, probably i manage to solder over the nand or the cpu
rp158 said:
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
Click to expand...
Click to collapse
ODIN stays at "Setup Connection" without any progress. I've left it overnight a few times, just to ensure I was giving it enough time.
When the cable is pulled, it reads "there is no pit partition"
@Mohanms04: I suppose, it's hardbricked
rp158 said:
@Mohanms04: I suppose, it's hardbricked
Click to expand...
Click to collapse
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Mohanms04 said:
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Click to expand...
Click to collapse
Try this recovery firmware, if not the jtag is required.
http://forum.xda-developers.com/showpost.php?p=30087735
Hello XDA community,
I have a G965F that is permanently stuck on the first boot screen (Samsung Galaxy S9+ secured by Knox powered by Android) and it will not progress past this point. I have left it on for hours, and it just stays on that screen. Recovery mode does not work; if I try the button combination for it, it just stays on the same screen as mentioned before. However, I am able to get it into download mode. From here, I have tried flashing every firmware I possibly could, of course with the correct region and version, but nothing works, and the situation stays the same as mentioned before. Odin usually finishes up with no problems and reboots the phone, in which case the bootloop happens once again. On the rare occasion that Odin does fail, it will not boot even to the first splash screen but rather to the blue screen with the triangle, telling me to connect it to SmartSwitch and go from there. I have attempted this also, but SmartSwitch only gives some errors, and it fails.
The phone was on the stock firmware for a few years and even updated through Odin when OTA didn't work. It is a UK-unlocked Exynos device. About 2 years ago, I decided to switch to lineageOS using Neuroticals ROM, and that worked flawlessly, OTA updates and everything, 0 problems. I even went back to stock at some point and reinstalled Lineage shortly after because of how much it improved the device. About 9 months since I last did any type of flashing, the phone randomly froze while I was using it (I think the bottom half of the screen went black) and was totally unresponsive until I forced shut it down. This is where the aforementioned problem began.
I thought letting the battery run out would help, but it hasn't. One thing I have noticed is that it either charges very slowly or doesn't at all; it will only stay on for a maximum of a minute after it is unplugged. I left it for a few months, hoping to discharge it completely, but the problem persists.
Apologies for the lengthy post; I've used this site for about a decade for mods on various devices and it has solved all of my problems, but this is the first one that has really stumped me. For the past few months I've spent tens of hours searching various forums and webpages but can find very little about my specific problem. Thank you for any help in advance.
I will include pictures of the codes that download mode shows, and hopefully someone has some answers.
PS. For some reason current binary says "Custom (0x8)" after successfully flashing the stock firmware many times with Odin, but when Odin does fail it will show "Samsung Official". This I cant make heads or tails of.