[Q] TM-805 doesn't boot - Galaxy Tab S Q&A, Help & Troubleshooting

Hello, I've a big problem. I bought tab some days ago and I instantly hated a TouchWiz stock apps so I decided to delete them. Tab continued works fine before yesterday when I switched him to extra battery saver mod. Screen switched to black-white mod then tab rebooted and since this time it boot looped. I tried to flash it with two different stock firmware but problem didn't solved. I don't know what to do pls help me
I don't remember what I deleted but I sure what I deleted stock TouchWiz launcher. Device normally boots in Odin mode but don't boot in recovery (home+volume up+power).

After 30 minutes of efforts I did it, I booted tab in recovery and reseted him. Never give up guys

Related

Samsung Tab 3 7.0 - Stuck on Boot screen

Hello there.
Few month ago , I tried to root my Samsung Tab 3 7.0 . Everything whent fine and when I tried to restart my tablet , it stuck on the boot screen, I mean it have that annoying ''Samsung'' over and over again. I tried the Power buttom + volume down , also I tried with the volume up. Doesn't work. It shows me the ''Samsung'' boot screen over and over again. The only thing which it works is the ''Odin Mode'' but there is a problem too. It stucks on ''Downloading...Please don't turn off''.
I don't know what to do. If there is a solution to put a new ROM , it will help me alot. Since I can't install that custom thing on my tablet. So yeah , please help me with this.
Same thing happen to me as well. Samsung flashing again and again. I restarted device two times and i was able to be in custom recovery mode. I restored my old backup image. and its working fine now.

my tab pro 8.4 has been soft bricked, can anyone help me?

I'll start from the beginining.. Okay so since i bought my tab (3 months ago) i had a battery problem, but it wasnt a bad battery problem. Once it got to 95% battery it stopped charging. Anyway, about a week after that i was unhappy with the performace of touchwiz on my tab so i decided to root it and install the cyanogenmod 12 nightlies. I was happy with cm for a while but eventually i got bored of all the bugs and instabilities so i decided to switch to a touchwiz rom.. This touchwiz rom was a vast improvement from the stock touchwiz so i decided to keep it. However i still wanted to improve the performace so i researched online for apk's/zip's that could improve my tabs performace. I came across crossbreeder and people said it was really good so i decided to install crossbreeder through TWRP. Once installed i rebooted my device and i instantly found many more battery problems. For example my battery would go from 50% to 20% in 5 mins/my battery would run out and i would reboot it and it would have had 40% etc. I downloaded some battery calibrating apps and calibrated my tab. After all that, that battery wasnt so bad. It was still dodgy but no where near as bad as it was straight after installing crossbreeder. Anyway, this was about 1 month ago. Since then, no new problems had occured with the battery until last night. Last night, my battery ent don to 1% then turned off like it should. I put my tab on charge and rebooted however when it rebooted nothing would work. My touchscreen didnt work, my home button didnt work, none of the keys next to the home button didnt work. So i thought that this was no problem and i could just boot into TWRP, factory reset and install the backup that i made. When i tried this, i booted into TWRP successfully however i couldnt press any of the TWRP buttons, again, i thought that this could be solved by flashing the stock firmware through odin. I put my tab into download mode and connected it to my pc, then flashed the stock rom. Once finished it showed a 'pass' and i thought everything was sorted.. When my tab booted up, it again, didnt let me press anything and none of the buttons would work. This is when i panicked. I then went into the stock recovery to factory reset my tab to see if that would work however, when i went into stock recovery, i couldnt go up or down using the volume keys.. So my volume keys didnt work either. I next put my tab in download mode and connected it to my pc. I opened odin and checked the 'Nand erase all' box thinking this would fully reset my whole tab. I then researched the 'nand erase all' function to find that everyone said that it breakes your device and puts it in bootloop etc. After reading this i instantly disconnected the usb from my computer to my tab. I tried rebooting my tab to see if it still booted and it didnt.. (i waited 20 mins). I then ran odin with 'clear efs' box ticked on. Again it didnt boot. I went into stock recovery again to see if the volume keys would work.. they didnt.. Infact when i opened stock recovery it had 3 errors showing (which it didnt last time i opened stock recovery). They all started with 'failed to mount /data'. Now i am here.. Sorry it was such a long read, i thought it would be better if i explained in detail. Thanks to anyone that replies/helps me.
NAND Erase All shouldn't destroy your device. What you need to do is boot into recovery, and choose the Factory Reset/Wipe Data option. From there, reboot and you should be good! Otherwise if it doesn't boot, just flash in Odin again, reboot to recovery, and then Factory Reset/Wipe Data again. We'll get you back up and running in no time
The reason why you are getting those errors is because your data partition is NOT formatted (because NAND Erase All wipes out your partition details, so it looks unformatted), so the recovery and your kernel are not finding your data partition. Your device will be unable to boot without. Factory Reset will reformat your data partition and get everything into place. Let me know how it goes!

Tab stuck in endless com.android.keygaurd // setting has stopped loop

I had to factory reset my tab a few days ago since it was in a endless reboot loop (the samsung tab 3 logo would flash on for a few seconds then off then on) until it looped its self to death. I did a factory reboot and now I at least got past the reboot loop from hell but now all it does is keep popping up com.android.keygaurd // setting has stopped with a white or black background. I wiped the chache and rebooted again. Same thing. I let it die then charged to 100%. Same thing. This thing is about to take trip to a gun range or find a home under the tire of my car if I cant get it fixed.
Also this is pure stock. No custom ROM, nothing. Its a samsung from sprint that I bought from someone well over a year ago and have not had issues until about a week ago.
Try deleting the cache partition in recovery. If that doesn't work use odin to reflash your stock os with pit file that wipes and re partitions to stock and let me know

Samsung Galaxy Tab S stuck in bootloop after flashing official ROM and factory reset.

After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800

Samsung S4 mini GT-I9192 Help with Cyanogen Mod 14 Booting Loop

So 3 days ago I updated my stock kitkat rom to CM 13, but I realised that marshmallow cant write on my sd so i tried a couple of fixes flashed on my device, namely the latest sd fix (2.9b) and so far so good except it didnt solved my problem, so I tried flashing the 1.9b version of the fix through recovery mode, after I finished flashing the TWRP apk asked me if I wanted to install the su apk, I didnt, so I clicked the reboot option instead except it didnt rebooted my phone so I held the power button until it turned off, next thing i know I tried turning my phone on and It gets stuck on the blue mascot booting animation for as long as I let it sit.
I already tried flashing a new CM (14) and factory resetting all to no avail, basically Im blind as to what i must do now. ANY help is welcome.
You cloud try to flash the newest twrp: https://twrp.me/samsung/samsunggalaxys4minidsdd.html
And the official lineage 14.1: https://download.lineageos.org/serranodsdd
@thorium231 I love you man, the problem was with CM after all.

Categories

Resources