Samsung Galaxy Tab 2 brick help

[ThomasP34]

A couple of days ago, my samsung galaxy tab 2 7.0. (It was running on either 4.2.1 or 4.2.2. I can't remember exactly. It could've been 4.1.2, for all I remember. I know I had the most recent automatic update, so whatever that was for the tab 2) ended.up soft bricking on me. I've been slacking on finding out what os firmware to download and fixing my tablet and I decided to get to it tonight. I put my tablet on the charger and.charged it fully and tried.turning it on. As usual the welcome screen stopped with the word Samsung flashing blue and black. I held the power button until it.restarted and.it.did.the.same thing. I did it once more and got the same results, so.I gave up and pressed down the power button.with.the volume down button and.was surprised to.see the.screen switch to system recovery mode. It has all the same options. Reboot system now, apply update from adb, apply update from external storage, wipe data/factory reset, wipe cache partition and apply update from.cache partition. It seems the only difference (at least I think it's a difference if I remember correctly) is the red triangle.with.the.explanation point in the middle. What bricked me was downloading an animation drive to start up/switch from app to app in different fancy ways like bounce in or fly in of twist. What should I do right now? I haven't touched it yet. Its.still in recovery mode with red triangle. Too scared to mess with it. Has anybody else ever experienced this? Being in a brick and then all of a sudden being allowed to enter recovery mode... with.a red.triangle...?

 

[ThomasP34]

Nobody?

 

[Dngrsone]

Frankly, I'd go ahead with a factory reset, then move on from there. Once you have a usable machine, then you can look at different firmware.

If I recall correctly, the latest stock ROM is 4.1.2

 

[dave260]

I agree. Factory reset. You will lose everything you have put on the device, so you will have to go to Google Store and manually add the apps. Good luck! (You/ve probably already got it fixed, but I just now noticed your post.)