Hanging and restarting - Galaxy Tab S Q&A, Help & Troubleshooting

My brother purchased Samsung Galaxy Tab S (SM-CTC705) from Dubai and it is still in warranty for upto Feb 2017. I lived in India and he gave it to me. During playing online multiplayer game, the tab suddenly get hanged and does not get switch off. So I did soft reset by using Power + Volume Down button, then it restarted. Since then it is hanging a lot and get restart time to time. I tried almost all possible method and they are:
1. Power off for 20 sec.
2. Power + Volume volume.
3. Clear cache
4. Factory reset.
5. Reset via recovery mode.
6. Update to lollypop OS.
None of the above method worked for me.
There is another unique problem I have that when going into recovery mode (Home+Volume Up + Power), the option for recovery does not show but using volume bottom I can reset cache and format it. This unique problem I am facing. During formatting, I am getting one more error while wiping all data using recovery mode:
formatting /sbfs...
E: unknown volume for path [/sbfs]
E: unknown volume "/sbfs"
Data wipe complete.
As I am in India so I visit Samsung service center to repair it but they refuse to take it and told that they won't support the device purchased from foreign country. Now I have only one option is to send device back to Dubai to my brother. I am no idea what to do now. I am if you guys can help me to solve this problem.
Thanks

There is no option called recovery. Recovery is what the mode is called when you boot using POWER + VOL UP + HOME.
The sbfs error is normal and can be ignored.
Your issue is usually related to a loose battery connector.

ashyx said:
There is no option called recovery. Recovery is what the mode is called when you boot using POWER + VOL UP + HOME.
The sbfs error is normal and can be ignored.
Your issue is usually related to a loose battery connector.
Click to expand...
Click to collapse
Thanks for the reply. I still don't have any solution. I don't have any idea about loose battery connector. I am planning to send to Dubai for repair.
Thanks again.

Related

Help Please!!!! Unique soft brick scenario!!

So I have searched and searched for a solution to this problem, all over xda, google, and other forum's, but have not found any situation that is like this one and thus no solution as of yet.
Specifics:
Sgh-T999
Was running 4.3 JB
Power button has been removed.
No root, custom rom, or recovery. All stock.
Ok so I've been trying to fix my friends s3 but to no avail. First off, he had to remove his power button a while back because of issues with it sticking and bootlooping. Now, to power on his phone he just plugs it in while holding the volume down and home buttons. Where he enters the download screen and just cancels, which then restarts the phone. Problem solved.
Latley his phone had been running real slow so I suggested he back everything up and do a factory reset to bring it back up to speed. So yesterday he did a soft reset through the settings menu after backing it up. After everything was finished his phone will now only power up to the fourth boot screen, the flashing blue samsung logo, and then gets stuck there, the logo continuing to flash all yge while. He left it that way all day long. I'd say atleast 10 hours. Nothing ever changed. Took out the battery, sim, and ext sd, let it sit for a while restarted it through download mode again but nothing changed.
Once he gave it to me I tried booting into recovery mode but it hasn't been possible without the power button. I tried holding the volume up and home keys while plugging in but it just keeps vibrating every few secs with nothing on the screem, which i'm assuming it just keeps rebooting. Even if I could get into recovery mode, I wouldn't be able to select any of the options without the power button.
I tried re installing the firmware through kies as well as emergency firmware recovery, to no avail. Same problem.
Also used odin to flash the stock firmware but no luck.
I'm going to try and flash a custom recovery and/or custom rom and root the device but that will be my last resort.
He wants to take it to the tmobile store before I do anything that could risk it any further. Which they will likely tell him Its dead or to leave it with them for a few weeks and charge him an arm and a leg. If they can't do anything, then I will flash a custom rom first and go from there.
Are there any safer methods, before I start flashing, that anyone can think of?
Will a custom recovery even possibly work without the power button?
I wonder if it could be something to do with the bootloader?
It doesn't seem hard bricked since I am still able to get into odin mode but I just dont know where to go from here. Also, I'm not sure if ADB is on since he just did a factory reset. It was on before he reset but after resetting would the ADB go back to default?
Also when plugging into computer MTP driver will not install and kies just continues to show that its connecting.
Any help would be greatly appreciated. I just joined the community and have learned a great deal about alot over a short period of time thanks to yall!
Thanks!!!!!
I don't think it's possible to work with without a power button. You can use a touch recovery to work around not having a power button, but the problem will be booting to it. Does it not boot into recovery when pressing the volume down button?
No pressing home and down byttons while plugging in puts it to the download caution screen. Then from there pressing volume down button restarts the phone like normal. Pressing up just enters download mode. I'm wondering now though if I press the up and home keys when it restarts if it'll boot In recovery like that. Since the restart would basically be like pushing the power button to start it right? That's why it boots into download mode when plugged in and down and home buttons pressed maybe? I'll try and see what happens.
My mistake, I actually meant volume up ?
No volume up and home while plugging in just keep vibrating every few seconds with nothing on the screen like its in a boot loop and when I let go the charging screen comes up. And no problem your wrong comment gave me an idea.
And the method I just thought of worked! Pushing up and home buttons as soon as system restarts from download caution page will put you into recovery mode! This is the what i'm getting at the bottom:
E: failed to mount /data (Invalid argument)
Can't mount '/data'(invalid argument)
E: failed to mount /data (invalid argument)
E:Cant mount /data/log/recovery_log.txt
Can someone explain what the failed to mount message means at the bottom?
Now that i'm in I can't do anything but I guess next step would be to flash a custom touch recovery. Maybe Philz?
Is there anything I can do to address the failed to mount issue without flashing a touch recovery?
I think I've seen those errors before, but can't remember what fixed them. Try doing a search on this forum and see if you can find something. Flashing a custom recovery and rom may help, but can't say for sure. Not what your friend wants though
so of course t-mobile couldn't do anything. I flashed philz touch recovery. wiped cache and user data/factory reset. During factory reset it will not format anything but the cache. Keeps saying
Formatting /data....
Error mounting /data!
Skipping format...
Formatting / cache...
Formatting / sd-ext...
E: unknown volume for path [/sd-ext]
Formatting /sdcard/ .android_secure...
Error mounting /sdcard/ .android_secure!
Skipping format...
Formatting /storage/sdcard1/.android_secure....
Data wipe complete.
Dalvik cache will not wipe either.
From their I located the PIT file for this device and re-partitioned with odin. Same problem.
Also tried cleaning to install new ROM which again would format everything except for /data and /scdard/. android_secure
Then flashed the stock 4.3 T999UVUENC2 ROM. No luck.
Now I'm right back to where I was before. Reflashed Philz touch recovery and here we are yet again.
I found this thread http://forum.xda-developers.com/showthread.php?p=30386564#post30386564 [HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick), which looks like what I need but I can't find VRALEC/VRALF boot chain files for my device. I really need help so anyone reading this please reply if you know anything pertaining to this situation. I'm running out of ideas. Please any help would be greatly appreciated.
He's giving me permission to do whatever it takes to get his phone back up and running. Also I don't thing flashing a custom ROM is likely to work in this situation.

Nexus 5X dead -- need help -- wont boot

Nexus 5X - was working fine all this while till about yesterday evening.. then suddenly when i causally checked, it was in powered off state.
Normal press of the power button did not work. No response. Pressed Power button for 10 seconds -- google logo appeared...... and that's about it -- it powered off again when OS/Android started to load. (no android boot animation).
Tried to boot to fastboot -> was successfull. Phone stays alive in fastboot mode.
Tried to boot into recovery (I had TWRP). Again, shows google logo and then when TWRP screen shows up - phone shuts down.
Dont think its a power button issue - since in fastboot/bootloader mode, the power button and rest of the buttons work as expected & the phone does not reboot.
Battery is fully charged using official charger.
Further, in fastboot mode, i am able to access/push .img files - so that way, i could push full factory image (with no errors, including userdata) & relock the boot-loader & also install the factory recovery.
I can now get into factory recovery -- but nothing much.
One thing i noted was, while in factory recovery, if i try "Apply update from SDCard" option, it says its unable to mount /sdcard (error).
The phone was purchased directly from google & is under warranty.
Have had nexus 4, nexus 5 without any issues in the past.
This nexus 5x --- has been replaced once in the past due to yellow screen issues ...
Any help/fixes will be appreciated...
arjunprabhu said:
Nexus 5X - was working fine all this while till about yesterday evening.. then suddenly when i causally checked, it was in powered off state.
Normal press of the power button did not work. No response. Pressed Power button for 10 seconds -- google logo appeared...... and that's about it -- it powered off again when OS/Android started to load. (no android boot animation).
Tried to boot to fastboot -> was successfull. Phone stays alive in fastboot mode.
Tried to boot into recovery (I had TWRP). Again, shows google logo and then when TWRP screen shows up - phone shuts down.
Dont think its a power button issue - since in fastboot/bootloader mode, the power button and rest of the buttons work as expected & the phone does not reboot.
Battery is fully charged using official charger.
Further, in fastboot mode, i am able to access/push .img files - so that way, i could push full factory image (with no errors, including userdata) & relock the boot-loader & also install the factory recovery.
I can now get into factory recovery -- but nothing much.
One thing i noted was, while in factory recovery, if i try "Apply update from SDCard" option, it says its unable to mount /sdcard (error).
The phone was purchased directly from google & is under warranty.
Have had nexus 4, nexus 5 without any issues in the past.
This nexus 5x --- has been replaced once in the past due to yellow screen issues ...
Any help/fixes will be appreciated...
Click to expand...
Click to collapse
if you press hold power + volume up you go into download mode. there is a thread with all official MM and N roms, so you should be able to install one and hopefully fix your problem. ofc do a clean install
if that does not work, then you might have more luck with lg flash tool to do a factory reset
if nothing works then imo its hardware problem, but since i am not as good at such stuff as most here i refrain to say so
Giorgos Chatziioannou said:
if you press hold power + volume up you go into download mode. there is a thread with all official MM and N roms, so you should be able to install one and hopefully fix your problem. ofc do a clean install
Click to expand...
Click to collapse
can you please point me to the forum links on how to flash using download mode? -- Nevermind : got the links. will try.

How can I boot to download mode in my note2 no OS Installed, no power button [HELP!!]

This morning I was experiencing an issue called "MTP host has stopped" while playing a heavy duty game in my Galaxy Note 2. I thought doing a reset would fix the issue. So I reset my phone then it rebooted in TWRP recovery mode. I then did a clean wipe selecting all the boxes as in data, system, delvik, cache, Sd etc. and rebooted my phone. The phone rebooted fine but it now stuck in Samsung logo screen as I have wiped out my OS.
The worst part is, My power button is already broken. Which means I can't enter into recovery mode by pressing Vol up + Home + Power.
I read other forum topics on whether there's any solution on how I can still enter to download mode. All I found is that I either need a working power button or I need to create or purchase a USB Jig that will help me force my phone into Download mode.
But I would like to avoid using USB jig. Is there a way?? Please Help!! :crying:
leota said:
This morning I was experiencing an issue called "MTP host has stopped" while playing a heavy duty game in my Galaxy Note 2. I thought doing a reset would fix the issue. So I reset my phone then it rebooted in TWRP recovery mode. I then did a clean wipe selecting all the boxes as in data, system, delvik, cache, Sd etc. and rebooted my phone. The phone rebooted fine but it now stuck in Samsung logo screen as I have wiped out my OS.
The worst part is, My power button is already broken. Which means I can't enter into recovery mode by pressing Vol up + Home + Power.
I read other forum topics on whether there's any solution on how I can still enter to download mode. All I found is that I either need a working power button or I need to create or purchase a USB Jig that will help me force my phone into Download mode.
But I would like to avoid using USB jig. Is there a way?? Please Help!! :crying:
Click to expand...
Click to collapse
i see 3 ways one try plug a hedset with volium button and try 2 use adb in pc 3 repair button

S20 ultra cannot enter download / bootloader mode

Hi folks
Anyone seen this issue before (see pic) ?
When I try to enter download / bootloader mode I get stuck on red text 'entering fastboot mode... ".
Odin cannot detect the phone connected to PC
The only way out is to press and hold power and volume down for 5 seconds to reboot normally
Tried factory reset and also tried clear data & clear cache partitions in recovery mode.
FYI I'm on O2 UK branded July 2020 stock firmware
With this steps the problem will be solved:
Power Off
Insert cable on pc
Press Vol Up + Vol Down
Insert cable on phone without releasing the buttons
But I agree, the 'old' method does not work anymore, I am getting the same message as the OP.
M1LL3R said:
With this steps the problem will be solved:
Power Off
Insert cable on pc
Press Vol Up + Vol Down
Insert cable on phone without releasing the buttons
Click to expand...
Click to collapse
Amazing worked first time ! Thanks
Is this a very recent change by Samsung? I ran various Google searches but could not find any relevant article on the web or on xda forums

F41 stuck at boot loop and unable to get to recovery mode

The randomly went into boot loop. I followed this guide suggested by @blackhawk in this thread https://forum.xda-developers.com/t/mystery-stuck-at-boot-screen.4518803/, still no use.
I tried the following things:
1. Connected the device with pc and pressed the volume up and power button to get to recovery mode(no response ).
2. Performed soft reset by pressing volume down and power button(still went back to boot screen).
3. pressed tried to get to recovery mode by pressing power button and volume down after the screen went blank pressed volume up and power button to try get to recovery mode(went back to boot screen).
PS:
The device was working fine until it went into this button in a bizarre fashion.
The device has only play store approved apps.
No attempts were made to unlock bootloader or flash custom rom.
Battery is known to be good right? No rear cover bulging? If any doubt, replace it. A fair amount of power is needed to boot.
Otherwise...
Try to get it to go into safe mode, if that fails...
Factory reset from recovery menu. If that works the data user partition was corrupted likely by a 3rd party app or malware.
If that fails reflashing the rom is the only thing left to try. If that fails it's a hardware failure.
blackhawk said:
Try to get it to go into safe mode, if that fails...
Factory reset from recovery menu. If that works the data user partition was corrupted likely by a 3rd party app or malware.
If that fails reflashing the rom is the only thing left to try. If that fails it's a hardware failure.
Click to expand...
Click to collapse
First of all thanks for the response it really means a lot
The response to the points mentioned:
1. The device looks healthy with no rear cover bulging.
2. I am unable to get to the recovery mode at all, any combination of button I press gets me back to the boot screen.
3. my laptop is not recognizing the device so i am not sure how to go about reflashing the rom.
cheekyrascal said:
First of all thanks for the response it really means a lot
The response to the points mentioned:
1. The device looks healthy with no rear cover bulging.
2. I am unable to get to the recovery mode at all, any combination of button I press gets me back to the boot screen.
3. my laptop is not recognizing the device so i am not sure how to go about reflashing the rom.
Click to expand...
Click to collapse
You're welcome. Sorry to hear of all the trouble you're having.
If you can't access recovery mode ie boot menu you have big problems. Try to do it again plugged into the PC; the newer ones need this to access recovery mode on the Android I think.
Make sure the button sequence and timing are correct. Sometimes I goof it twice in a row
Try removing SD and sim cards. Does charging show on the display? Make sure it's at 70% or more.
Otherwise could it be a failure on one of the buttons? A cable may loose? I don't think a C port failure would cause this but not sure if that's always true. Unless dropped or water damaged mobos rarely fail but this is a possibility.
Maybe someone here has a better plan...

Categories

Resources