Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
vvsarana said:
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
Click to expand...
Click to collapse
Well i hve the same problem like you.. idk wht should i do with this condition.. bootloop.. always restart until logo.. :crying:
Please anyone help to solve our problem..
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
ashyx said:
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
Click to expand...
Click to collapse
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
vvsarana said:
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
Click to expand...
Click to collapse
Did you ever resolved this issue? Curious if you have a solution.
Related
This is a very simplistic method and it probably wont work, on phones that have started flashing and then were disconnected or turned off. But you might as well try ( i am not entirely familiar with the phones firmware, but on a computer the boot block is the last thing that gets flashed -this can be used for recovery)...
So the story goes i was using Odin and it got stuck setting up a connection to my phone to flash.
After a while i built up the courage to unplug it (as i know that interrupting firmware updates is normally the best way to brick an electrical device). I unplugged it and not to my surprise got an exclamation mark between a usb cable and a computer.
Oh great!My phone is bricked.So i left it for a while and tried again nothing, i tried different key combinations again nothing.
It occurred to me that odin had never actually flashed anything (as far as the log was concerned) and that perhaps the rom on the phone was still good but it was stuck in a failed download mode.
So i took the battery out left it for a minute or two and put it back in.
I pressed the key combination to get into download mode (down volume+home+power)
Back in download mode and odin works this time, great!
Hi guys, first of all this is my first post here and won't be my last.
I am an Apple/iPhone long time user and want to tryout Android, just because I think it's time for a change , without knowing if I could get used to the new OS and wanting to spend as less as possible on this "endeavor" I bought a second hand Galaxy Note 2 GT-N7100 from a friend, the phone worked perfectly when I bought it, it had Android 4.1.2 on it and I wanted to update it to 4.4.2, did some research on the net about this (learned about the locked bootloader - this wasn't an issue for me coming from the iPhone) and updated the phone using Kies - and this is were the fun begins.
The update failed, and the phone was softbricked but could still go into download and recovery mode, after reading a few hours on the internet, I used Odin to flash a 4.3 stock rom for the n7100 which I downloaded from samsung-updates, the software got installed on the phone but it was very laggy (with the phone opened but locked, when I pressed the power button it took about 7-8 seconds for the display to light-up, the animations were very sluggish and phone was unusable).
I installed another ROM, using Odin, this time a 4.4.2, with the same results (every time I reset to factory setting and wipe cache from recovery - this didn't help).
I then installed clockwork recovery and rooted the phone then installed cyanogenmod 10.1 which worked almost ok but if i locked the phone after a few seconds the phone would restart, wipe cache/restore factory settings didn't help, i installed it again hoping it would be just an issue with the installation but had the same result, phone would restart.
I've followed all tutorials I could find related to this phone and this issue, installed several patches, reinstalled several stock roms, installed Criskelo rom, all with the same result, the phone is very very very slow and freezez after a while or it restarts after i lock the phone.
So, let me just give u some history on the phone, enumerate the symptoms and where I am right now:
History:
The phone was bought from Vodafone Romania, was never rooted and was never updated (before me ) and still has 3 months warranty.
Symptoms:
- Phone is very slow, unusable
- Freezes after the display is locked
- it is not recognized in windows, when I connect it i can hear the windows connect chime but the phone storage is not mounted, in device manager the phone is recognised as "cdc communication interface" which is not installed - i have the samsung drivers installed, and i have tried on other PC's with the same result, I also tried with several data cables - same thing - the phone works ok when in recovery/download mode
- sometimes when the phone is connected to the PC and the screen goes dark a gray battery appears with a "wait circle" and the phone freezes
- in recovery the phone displays 14 bynaries downloaded and also knox warranty void 1
- most of the roms freez in the language selection screen - i boot-up the phone (after i do a restore factory settings) the installing application dialog appears and then the language selection screen appears, then after 5-6 seconds the phone freezes - the freeze is not triggered by something I do it's triggered by time, after 5-6 seconds no matter what I do with the phone the phone freezes, if it makes any difference, exactly before the phone freezes the display brightness goes to the maximum setting.
Where I am right now
- I installed another stock rom, 4.4.2, it worked acceptable for a few minutes (it got passed the initial setup with no issues) then i left it on the desk, the display went dark and the battery thing happened again and the phone froze, i restarted the phone in recovery, did a factory reset, when the phone started it froze on the language selection screen.
I am at this for about a week now and I have no more ideas and no more patience, and run out of threads and tutorials to read, I am 1 step away of using the phone as a paperweight so please help, any idea would be appreciated, even if it's to enlighten me about what happened and telling me that the phone is bricked.
I am willing to try anything even if it is risky and can totally brick the phone, this is not my main phone and it's purpose is to help me understand android, and help me not make the same mistakes next time.
But, if it's possible I would like to fix the phone because even though it's pretty old it's still an ok phone.
Sorry wrong forum. You need N7100, not the n7000. Good luck.
Problem started when my device ran out of battery. Now, plugging it using the original charger gets the device to a cycle of showing the battery icon (gray with electricity symbol) for two seconds and then disappearing; no loading battery animation nor percentages.
Plugging it to my laptop seems to charge it slowly, about 1% per 5-10 minutes. With this slow charging I was able to load enough juice to try to boot the device. This however only led me to a bootloop (up to the "Samsung Galaxy Tab S2" screen) until it dies again.
Worried and desperate I browsed through articles. Without reading as much as I did for when I was flashing my Xperias (this is my first Samsung that I tried to flash/mess with), I went on and did these procedures:
1. Downloaded Odin
2. Downloaded and flashed cf auto root (http://forum.xda-developers.com/tab-s2/development/root-cf-autoroot-tab-s2-sm-t3187202)
3. Downloaded and flashed twrp (http://forum.xda-developers.com/tab-s2/development/root-cf-autoroot-tab-s2-sm-t3187202)
These now added the following to my problems: a tripped knox counter, and a "recovery not seandroid enforcing" error at boot screen. Device still doing bootloops and is not charging using the original charger.
I went on and thought that maybe reinstalling the stock rom would solve everything. However this failed.
Would appreciate your assistance on this.
I think it's pretty obvious your charger is at fault here if it charges via USB.
Use a different charger.
ashyx said:
I think it's pretty obvious your charger is at fault here if it charges via USB.
Use a different charger.
Click to expand...
Click to collapse
I tried other/new chargers yet now it does not even tell me if it's charging or not. However it's plugged, it gets into a bootloop.
Flashing stock rom did not solve the issue. cant get into recovery either. I can only go to download mode.
Been stuck on this for 4 days now.
Please tell me if there are other methods I can try.
You have the same issue as someone else. They ended up sending to Samsung for repair.
If flashing stock firmware and factory reset can't fix it then it could be a hardware failure.
ashyx said:
You have the same issue as someone else. They ended up sending to Samsung for repair.
If flashing stock firmware and factory reset can't fix it then it could be a hardware failure.
Click to expand...
Click to collapse
I actually got the tab going.
It seems that I was doing fine all along except that the tablet has almost no battery and all rebooting after flashing does not complete.
What I did was I charged the device while it's on download mode for more than two hours then reflashed stock rom. When it rebooted, it booted into two consecutive samsung screens (like normal) then the teal screen with android icon labelled "erasing". Then it proceeded to booting as if it was factory-reset.
However, the wifi is not working now. It is in eternal "turning on" mode.
If my current stock rom is T710ZSU2AOJ2_T710OZS2AOJ2_HOME.tar.md5, is there any other rom I can try?
Thank you
I bought this on swappa and it was previously rooted. The guy restored it to DOK2, non-rooted before he sold he told me. I got it and it worked fine. I turned it off, wanted to go to download mode for ODIN, and nothing. The screen won't turn on, no LED lights up with charger plugged in or anything. I left the battery out for about 30 minutes, and held the power button to get rid of any residual power.
Finally I try one last time and it turns on, but get some weird message and goes straight to the download screen.. Screenshots attached
This first
Hooked to ODIN (both 3.09 and also tried 3.10.6) and it shows that it's added succesfully. As soon I tried flashing something, it said PIT partition not available..
Downloaded the complete firmware to hopefully reset it, and again, same error. Phones shows this
What can I do?? I hope theres some master flash I can do to bypass ODIN and reset the phone.. If I remember correctly, my last S4 was able to be flashed in a different mode to factory image. Anything like this? Hopefully or it be 350 down the drain..
Tried again and on the phone shows another error this time under UDC start " mmx_read fail"
I have an update, hope it helps.. After sitting for X amount of time, I can boot the phone up normally and everything works as intended. However as soon I turn it off, it won't turn back on for X amount of time again. However long it takes for it to completely discharge. Holding down the power button without the battery inside doesn't seem to make a difference.
I tried doing a factory reset, however since that shuts the phone down, it again won't come back on until I wait...
And I cannot flash anything in ODIN, no new firmware or anything since it has the PIT error described above. I DO have another note 4, same specs, company that is rooted. Any way to take the PIT partition of that one and copy it to ODIN to try and fix the broken one?
When you say you flashed the full firmware with Odin did that include the pit file. It's not generally needed unless the partition is messed up. Here is the link to the pit file posted by eduardog131
https://www.androidfilehost.com/?fid=24369303960684492
I have not used this file myself, sorry I could not be more help
As i installed update and clicked reboot to apply it, now my system do not boot. Phone always stuck on white NOKIA logo boot screen forever. I tried few times to restart it via VOL-UP + POWER, but it always have same result - never boots. Please give me advice how to deal with it
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
ravkhar said:
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
Click to expand...
Click to collapse
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
gornex said:
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
Click to expand...
Click to collapse
Ach yes, sorry. First it stucked in logo Nokia and rebooting again... VolumeUp+Power does not work normally on Nokia.
It helped procedure found here:
https://forum.xda-developers.com/showpost.php?p=74406267&postcount=34
Then I was able to make factory reset and mobile booted, but worked with various faults.
Did you unlock your bootloader , flashed TWRP and then changed the slot? Slot A to B or vice versa?
If so, then the solution is
How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo appear any more >>
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
Edit: I sucked the juice (mAh electric-capasity) out of the battery quicker with help of OTG-cable and an external USB-powerd fan.
Use almost any external max 5volt USB-powered devices available at home, even charging another phone unless the second phone doesn't reverse-charge, this Nokia can be used as a power-bank.