yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
So...

Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.

Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.

Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.

Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.

So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.

Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.
[Galaxy Tab S Q&A, Help & Troubleshooting] Lightn1ng:
Ok this will take a few tries but here is my method of dealing with this situation

1) Flash stock using Odin

2)

AS SOON AS

the screen goes blank, start holding Power+Volume Up+Home

3) When recovery boots, release the buttons

4) Use the volume buttons to select "Wipe data/factory reset"

5) Press power to confirm

6) Reboot

If that doesn't work, you may either:

1) (more likely) Installing a ROM will fix the problem

2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
Thanks, I'll try these steps tonight when I get home, and report back!
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).

Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.

It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.

I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?

All right. Thanks for your response!
[Galaxy Tab S Q&A, Help & Troubleshooting] ashyx:
Try this as a test.

First make a full backup of every partition with twrp including the EFS <<IMPORTANT!

Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.

Reboot the device and try and enable wifi.
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).

Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.

I'm running out of ideas.
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
The Latest...

All right...

I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...

Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?

It booted into the RR lockscreen.

Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).

Afraid to try and connect WiFi, afraid that it'll just bootloop.

Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.

So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.

Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.

Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, [MENTION=6553354]Lightn1ng[/MENTION] and [MENTION=4899305]ashyx[/MENTION].
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
All right, because I can't leave well enough alone....

I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.

Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...

I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...
[Galaxy Tab S Q&A, Help & Troubleshooting] Lightn1ng:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
It's the WiFi-only model - SM-T800.

It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.

I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.

AGH - I was so close!
[Galaxy Tab S Q&A, Help & Troubleshooting] Lightn1ng:
I'm running out of ideas!

Maybe somebody else with a T800 could backup their entire EMMC using

dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin

And you take the file on your tablet and do

dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0

And restore YOUR efs folder using TWRP.

THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!

---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------

@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?
[Galaxy Tab S Q&A, Help & Troubleshooting] ashyx:
I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.

If twrp cannot backup the system partition then there is an issue with the partition.

Try backup again and post the recovery log, it may contain some relative information.
[Galaxy Tab S Q&A, Help & Troubleshooting] DrinkSlinger:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
[Galaxy Tab S Q&A, Help & Troubleshooting] DJ Palmis:
Exactly the same issue on my LTE version.

Samsung support just asked me 230€ for a new motherboard.

I refused to repair. I think it is related to nand memory..
[Galaxy Tab S Q&A, Help & Troubleshooting] ashyx:
Why not just update to Marshmallow? Absolutely no issues for me.
[Galaxy Tab S Q&A, Help & Troubleshooting] srfairhurst:
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.
[Galaxy Tab S Q&A, Help & Troubleshooting] gimmeluck2:
Hello,

and the rest of story??

i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,

but, cant odin flash official md5 file, it stucks on logo.
[Galaxy Tab S Q&A, Help & Troubleshooting] daina:
The one thing I never tried (and always meant to) was re-flashing the .PIT file. Someday, I'll drag this thing back out of storage, and try that. Until then.... :confused:
[Galaxy Tab S Q&A, Help & Troubleshooting] DJ Palmis:
I can't understand where I can find a PIT file

Inviato dal mio SM-T820 utilizzando Tapatalk
[Galaxy Tab S Q&A, Help & Troubleshooting] DrinkSlinger:
Okay, my old Tab S has been sitting for a couple years now. I finally decided to look around again and found this:

https://youtu.be/BvdPPSsJ31M

Check my connection and sure enough it’s no where near what I would call a solid connection. I just got done doing this little fix and the tab has been going strong for a couple hours now. Hope this helps.

---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------

Check my last post at the end of this thread. It worked for me and cost nothing. Happy tableting man.
[Galaxy Tab S Q&A, Help & Troubleshooting] DJ Palmis:
I came back to my hometown for holidays, so I tried to follow your suggestion on my old tablet.

I thought you were right: it could be a brownout reset but it didn't work.

I did my best, maybe it is not a good job.. but I didn't see any issue with my connector.

I think it is something related to flash memory.. or maybe battery itself.

Unfortunately no fix!

Inviato dal mio SM-T820 utilizzando Tapatalk
[Galaxy Tab Q&A, Help & Troubleshooting] nastypup:
My tab A won't play MP4 files. I placed the same files on my granddaughter 's tab A last week and they worked perfectly. How can this be fixed?
[Motorola Droid RAZR] physicsmaster131:
Hello All.

Apologies if I am missing something obvious, but I am experiencing an issue with my US VZW XT912. Over a year ago, the phone bricked itself seemingly out of nowhere, only booting up into the "Encryption Failed" state. I went ahead and put it into AP fastboot and grabbed a copy of Matt's droid razr utility. I installed the motorola drivers and fired up the utility, then tried to flash the factory JB image to it WITH data wipe (option 1 on the utility). The process started, but right after "sending 'mbm' (512 KB)... OKAY [ 0.092s]" I got the message in the title of this post: "writing 'mbm'... FAILED (remote: )".

No matter how many different USB cables I tried, or how many different USB ports I used on several different computers and Operating Systems, I always got the same result; "writing 'mbm'... FAILED (remote: )".

I've gone as far as using ADB by hand and going through the flash instructions from an XML file step by step, but that fails in the same spot as well. RSDlite also failed.

My suspicions here are either A) The partition table is messed up somehow (which I unfortunately do not know how to fix) or B) The flash memory is actually just bad on the phone, which would obviously suck.

Now, most of my troubleshooting took place a year or so ago, so I've included a screenshot of Matt's utility that I just ran this morning. imgur<dot>com / QHsJbtO (sorry about the link; new user)

Any input is most appreciated.

Regards,

Steve P
[Motorola Droid RAZR] sd_shadow:
do you know which version the utility is?

what RSD Lite version?

Firmware version?

what is on AP Fastboot screen?
[Motorola Droid RAZR] physicsmaster131:
Couldn't find a version number in the batch file of Matt's utility, but the created date on the file is August 26, 2014.

RSDLite 6.1.4

Was running stock JB when it bricked but I believe the phone shipped with ICS. I never loaded any custom ROMS, though.

"

AP Fastboot Flash Mode (S)

0A.77

eMMC Info: Size 16G

To return to normal mode - first press power key to power down

Device is LOCKED. Status Code: 0

Battery OK

OK to Program

Transfer Mode:

USB Connected

"

Some (relatively poor) pictures of the AP screen: imgur<dot>com / a / mEFxz
[Motorola Droid RAZR] physicsmaster131:
This is probably a dead thread, but I've been troubleshooting this issue on/off for over a year and still haven't managed to make any headway. Any other thoughts?
[Motorola Droid RAZR] sd_shadow:
What's the bootloader saying?
[Motorola Droid RAZR] physicsmaster131:
Everything looks pretty normal on the bootloader. Trying to attach images but I keep getting an error so I'll type it out:

AP Fastboot Flash Mode (S)

0A.77

eMMC Info: Size 16G

To Return to normal mode - first press power key to power down

Device is LOCKED. Status Code: 0

Battery OK

OK to Program

Transfer Mode:

USB Connected
[Motorola Droid RAZR] physicsmaster131:
Some additional info:

When I try to boot normally I always get the "encryption failed" screen, and the reset button doesn't do anything.

When I try to boot into recovery, the android logo comes up, but I am never able to make it into the actual recovery menu.
[Xperia Z5 Premium Android Development] zacharias.maladroit:
one
[Xperia Z5 Premium Android Development] zacharias.maladroit:
two
[Xperia Z5 Premium Android Development] zacharias.maladroit:
three
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Previous ("legacy") threads,

by moonbutt74:

CM13 Z5P E6853 Beta -- Updated NegaSpork

[Rootable Kernel/ TWRP 3 - E6833/E6853/E6883 Marshsmellow ] [32.1.A.1.163] AU]
[Xperia Z5 Premium Android Development] dominicstg2:
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
there is very little battery drain compared to Sony Stock ROMs,

It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better ;)

Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,

until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm

[MENTION=5139398]dominicstg2[/MENTION] Weren't you one of those RR (Resurrection Remix) lovers ?
[Xperia Z5 Premium Android Development] dominicstg2:
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Was that when I uploaded the first build of RR ?

Cause I hope that this time you have more luck with it and it works:

http://xdaforums.com/showpost.php?p=67538514&postcount=45

Is the taken picture now fine with Camera Next Mod and CM13 ?

Both RR and CM13 now should be pretty close, please give RR another try :)

Thanks
[Xperia Z5 Premium Android Development] dominicstg2:
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now :) also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
It's related to the device string that is in the zip-file of the ROM,

if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.

That mismatch can be made in error (something went wrong during creation, typo, etc.)

or on purpose - in that case it's not so wise to flash the wrong ROM ;)
[Xperia Z5 Premium Android Development] dominicstg2:
Oh has other people had this problem?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
yeah, not sure if on Z5 compact,

but certainly on Z5 Premium and Z5
[Xperia Z5 Premium Android Development] Tani_bc:
waitting for 6883 ^_^

Thanks Dev.
[Xperia Z5 Premium Android Development] Humbersp:
I join the testing!
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Changelog

Kernel Source:

https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm

ROM Source:

mostly

https://github.com/SonyAosp/

https://github.com/Sony-Kitakami/

https://github.com/sonyxperiadev/

Kernel

Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip

ROM

6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56

Thanks
[Xperia Z5 Premium Android Development] Tani_bc:
Hi Dev ^_^

about version cm13 for Z5P E6883, When will be released ?
[Xperia Z5 Premium Android Development] guhvanoh:
Don't ask for ETAs on XDA. It is rude.
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Work in progress,

please take a look at the CM13 thread for the Z5, will ya ?

there are several factors that influence access and working for

microSD, sim cards (both), fingerprint scanner and others
[Xperia Z5 Premium Android Development] Nibleheim:
Okay, after having this installed for a few weeks I figured I'd chime in what I've found/liked/disliked.

After having Stock Root/Xposed, RomAur, and Ressurection Remix - This one seems to be the one I like most... It just lets me do what I want to do and it seems the least buggy...

The ADB Wi-Fi thing always seems to turn on every reboot, not sure if its intended but I find it somewhat annoying...

Brave Exvius seems to be a horrid game for this Rom as if I play it a lot it will bog down the phone and force me to reboot

Rebooting seems to hang about 20% of the time forcing me to hard shutdown. (Power+Vol^)

Bluetooth seems to have no problems despite "needing testing" for me and I have a SmartWatch 3 that used to lose connection with my phone all the time on Stock/no root. Same with my Ford SYNC.

Speakerphone doesn't seem to work on calls??? It hears my voice fine but does not play loudly enough for me to use it reliably.

The Camera app that comes is garbage. CameraNext Seems to crash every other open and takes so long to Focus and low light just doesn't work. If I end up uninstalling - this will be why.

A few things I would like to see...

I know they took away Google Search with the Home Button Hold and Search in MM, I'd love that to come back... I miss it a lot.

We have a 4k phone that's capable of destroying batteries, a 2k and 4k Toggle somewhere easy to access would be pretty sweet - and I think I'm not alone in that. I know it would take a mountain of work to make it look flawless with just the app drawer, but I think if you gave people a switch they could play with it and I know multiple people would be willing to work with what they're given.

I cry wen I see I can only fit 4 apps per row on a page, maybe give a choice here?

I think bug wise its pretty clean except for the camera. I really appreciate all of your work, and if I could test anything/help you with anything let me know. I'm not savy when it comes to "pulling logs" but I'm great with direction.
[Xperia Z5 Premium Android Development] claesr:
hey, have you tried any bluetooth headset and done any phone calls? i tried it but in the res remix rom and it didnt work but music through bluetooth worked for me