[Galaxy Tab 2 General] billysam:
Common Issues faced

If you have read about my explanation of android's partitions in the OP(Original Post above), you would know where exactly to look for the problems. Moving on,

For other Geeks

Please remind me if I missed few things, you see I have put up this Guide mostly of the files I have in my system partition,I might have missed few that were stored in data or cache partition

1. Tab is Stuck on Charging Screen. Tab is not turning On, battery completely depleted/Not charging, Nothing is Working​

Possibilities

* if the tab doesn't feels warm even after charging for a whole day,

F1. Battery dead,

F2. Circuit/Motherboard blown,

F3. Bad Charger/charging point

F4. No electricity

if it's getting warm and still not turning on

F5. Hardware buttons not working

F6. Motherboard needs replacement.

F7. Flashed a bootloader/kernel(along with a Rom/firmware), or something not meant for your device, which is the hard brick in this category please refer to case number 5. (process on post 2)

F8. Some Custom Roms have bugs that won't Charge, stay stuck on the battery icon, unless you remove the plug and turn on. always read before flashing a Rom, if there are no info, better ask the developer before you go flashing or post your Question in related thread where they would get noticed.

2. Stuck On Samsung Logo Screen.​

This could be from various reasons generally not so serious ones mostly recoverable issues of which, some are

Flashed a incompatible Custom Rom zip or any other flashable zip containing files not meant for the exact device.

Flashed a kernel/ bootloader incompatible with the Rom, wrong kernel modules, messed up system lib files, (lucky enough to still not be in hard bricked section.)

Formatted system partition and there is no OS installed. (one of the silliest mistakes I have done)

Some other that I maybe forgetting just like I completely forgot about the above

Possible Solutions

Go to the stock recovery and wipe data/factory reset (this will make your precious data that you stored vanish, except data stored on SDcard) (explained further in post 3)

Get a working stable compatible kernel/Rom or flash stock firmware. (explained in post 2 and 3)

Download from a different source cause chances are the file got corrupted or infected while downloading or transferring. (post 3)

Find the file that is stopping the device from booting up, starting from the kernel, to the system files. duh?

Go to the custom recovery way.

Go to the download way

3. Stuck in a Boot Loop.​

Boot Loops are crazy and they will make you mad, they can hit you anytime for even little of tasks, Root or not root, either you are testing a new app, modifying/copying/editing/deleting/overwriting files in the system or data that don't even look so dangerous, just flashing some mod, GAPPS, or just updates rolled out by devs(nothing against them) this will surely hit you, no matter how focused and diligently you work. boot loops will make you do hula hoops.

Boot Loop is generally solved by

Hello? whatever you did that I mentioned above, just roll it back.

if you can't figure it out, well then

Remember the CORA order Quoted above in the first post? Read on

Safe Mode?

Go to recovery and clear cache then reboot.

Clear data/factory reset from stock recovery(data stored will be lost) (root users can skip this and directly go to 7)

No, Recovery?, You sure pressed the button nicely?

Flash a custom recovery image(recovery.tar) from Odin

Repeat from 1-3

Backup/Restore from Nandroid backup

Don't sit for the next exams without memorizing your lesson.

Cleared cache/dalvik cache?

Flash a Compatible Custom kernel

Find the stock replacement of the file/app you messed up from a firmware or a custom Rom, put it in a flashable zip and flash it (advance users)

Clear/data factory reset either from custom recovery. (*loses data)

Flash the Custom Rom, first dirty flash then clean flash.

Flash a Stock firmware from Odin. (loses data)

4. Stuck On Firmware Upgrade Encountered an Issue.​

Well this problems hits non-root users and root users too? why? because we wanted an update.

it was trying to upgrade and something got in between to make it stop

Battery/Power/Electricity - for non root users, the most common culprit would be the battery, seriously guys, please keep the battery in mind always. it's a very common mistake that cost many of users. For ODIN users, please see you have a uninterrupted supply of power to your device and you are using latest version along with Hi speed USB ports.

kies!!! I hate that thing and majority of others will support me here. I got rid of it the day I installed that thing on my PC.

interruption from the user side while the device was taking an upgrade. removed battery? fell down on the floor? no?

hardware issue, unlikely, rare I would say, in case the device did came out with a weak emmc card.

Bad/wrong firmware downloaded files.

In case you had a custom recovery and its still working, check the custom recovery way

I Know 1st didn't helped you,

Refer to the Download Mode way and get a custom recovery

Don't forget to clear cache, you do know that's where the device keeps the downloaded/image firmware file, and that's where it is installing/extracting from. the dream partition, no wonder you got errors. you got a nightmare now

try the download mode way

probably it's best that you either forget about the mobile, or give it to a service center for a J-TAG and get it repaired.

I knew you would look here, there is indeed a last ray of hope, explained at the last thing to do in download mode way

5. Bricked.​

There are 3 types of Bricks, Soft Hard and The Brick, That's it.

Soft brick

well you are safe and sound, you can even recover from custom recovery mode.

Hard brick

skynet has fallen, just like it infected the droid Arnold Schwarzenegger of the terminator version 3.0, the codes were injected into his heart making the brain dis balance and resulting in partial heart seizure and a coma, but he still had the cache and data part intact along with recovery, so it went there, restored a nandroid backup and went online again. BAM!! so easy. but why? I mean ours droid having reached version 6.0 can't recover from the same way? Where only hope here is a CPR or getting J-TAGGED? not to mention, which should be done by expert surgeons who would charge exorbitant . So, don't waste time with a jig or any other miracle to happen and please don't go on the droid with a shocking therapy. I am more of a practical guy and prefer professionalism. :P

The Brick

err, that's the solid one, put that on your heart, and forget about this droid and shell out money for a new one. ::o that's what the company wants to tell you here and that's the reason it doesn't want to put the nandroid on the stock recovery cause they want the blame on you and not them. shhh, keep it hidden, don't say I told you their secret