We revive the braking Samsung Galaxy TAB 2 WiFi

I bring to your attention my recipe for revitalizing an old, braking tablet and bringing its software up to date.

This year I did an audit and sold my old and idle devices and components. I must say that I hate to watch videos and read from the phone, because there is no complete immersion - working and not very calls, incoming mail, messages from messengers annoy me quite a lot. Time passed, and I studied the offers of shops and selected the price / iron ratio, but did not stop at anything.

It was the turn of cleaning the garage, where I found the Samsung Galaxy Tab 2 7.0 "P3110 (without a SIM card slot). For fun, I turned it on, it blinked the screen and booted up Android 4.1.

It’s great, I thought, a reliable piece of hardware, if for a couple of years in an unheated room it started up and booted up. Perhaps I will take it under my book. Actually, this way I got the opportunity to re-read the contents of the page several times, while the text scrolls to the next, and step by step to watch my favorite TV shows.

So, the tablet configuration:

OS Android 4.1
Dimensions 194x122x11 mm
Weight 344 g
Capacitive sensor, multi-touch
Display 7 inch
Wi-Fi Wi-Fi 802.11n, WiFi Direct, DLNA
Bluetooth Bluetooth 3.0 HS
GPS with support for A-GPS
GLONASS has a
CPU TI OMAP4430 ( ARM32bit)
Frequency 1000 MHz
Cores 2
GPU PowerVR SGX540
Memory 8 GB
RAM 1 GB

Firstly, with the latest firmware, a bunch of services flew in, namely “update”, “debugging” and “from the manufacturer”, which cannot be disconnected, but if you stop them, the performance will increase significantly.

Secondly, the outdated version when I tried to put 50% of the software from the Play Market informed me that "perhaps the software is not optimized for your version of the OS."

Having studied the search results, and having stumbled upon the mention of the custom firmware Lineage-OS, it was decided to mock the device, since there is still no practical benefit.

The firmware process is described in a myriad of manuals, but still the search for the path took time, I publish my recipe.
UPD: The official website of lineage-os
From here we take custom firmware , an alternative bootloaderTWRP , USB cable, Samsung USB drivers (for downloading TWRP firmware), latest version ODIN software , Open Gapps - Play Market for the selected Android version, 8GB microSD card, Windows 10 desktop PC

Preparation:

1. deploy Odin from the archive ( does not require installation) on the disk, install the Samsung USB driver.

2.1. Download TWRP. As it turned out, ODIN sews from a special tar or tar.md5 format. And on the TWRP website there is an img file with a fresh loader. Android from the 7th version changed the format of the boot image, the loader 2.8 does not accept this format. Therefore, clause 2.2

2.2. Download the tar file format utilitywhich will accept ODIN. Rename the downloaded TWRP file to "recovery.img" and drop it into the "parts" directory of the utility. We launch the BAT file and in a couple of seconds we take the twrp-3.1-p3110.tar file from the “packaged” directory, after answering the question what we are doing (point 1 - the tar file) and the “Y” button.

3. Download Gapps, in my case the processor type is ARM, OS 7.1, piko Gapps (the minimum set for the Play Market to function)

Process:

4. Pour on MicroSD OS, Gapps. We insert into the tablet.

5. On the off tablet, press and hold the power button and volume down button. We get into the bootloader firmware menu and click “Confirm” - the sound increase button - screen drivers do not load in bootloader firmware mode.

6. We connect the tablet and the computer with a cable, a certain Com port (in my case COM6) should appear in ODIN. Select the “AP” item and specify the TWRP firmware file (twrp-3.1-p3110.tar) in it. We do a tablet reboot as ODIN completes the firmware.

7. Hold the power button and add sound until the screen goes blank and the tablet model appears again. Next, the TWRP bootloader window opens.

There are three things to do: make a backup of the current firmware for rollback, clear the boot, cashe and data section, fill in the OS and Gapps.

8. We backup partitions, check System, Cache, Data, Boot (Internal Storage can also be specified if you previously saved important data from there - this is the internal memory of the tablet). Swipe to perform backup, wait.



9. Gently erase (Wipe) using the Advanced Wipe section - checkboxes opposite System, Cache, Data and swipe.

10. We proceed to install the OS: Install, select the lineage-os archive, the add archive gapps button. to fulfill.

11. Upon completion, select Reboot. At this stage, I do not recommend experimenting with the bootloader's offer to install Super SU - my OS did not take off, click Do Not Install.

From errors:
There is not enough RAM to install the OS and Gapps - we select a smaller Gapps archive.
The OS boots up (the logo looks like a very sad smile) and nothing happens - remove the microSD and try to boot again
There is no Play Market in the OS - the wrong version of Gapps
I still do not have landscape mode for the desktop, although applications run in landscape mode. I’m looking for a solution, maybe it will be in the comments.



Thanks for attention!!!

PS: I apologize for the quality of the photo, it did not work out better.

UPD2: Gapps can not be installed, there will be no Google services, Play Market. I am very lazy to keep track of the updates of the applications I use, I set. I noticed that without Gapps the tablet is much faster. In case I would use this device as a multimedia device in a car or a TV set-top box, I probably would not install Gapps.
Or organize parental control over applications for children - completely manual installation of applications approved by dad (and mom).

UPD3: The native LinegateOS lancer called Trebushet started to fly out, speed lags appeared again and the screen crumbled into small squares (noise). Installed Nova Launcher, 2 days the flight is normal. The device works at the level of modern similar devices for 2-6 thousand rubles. I noticed that apparently there is a hardware problem - when there is an active use of the WiFi module, there is a slowdown in the response to tapas on the screen. Either the battery voltage drops below critical, or the WiFi module itself is already "breathing in the air." However, in 99% of use with the device, all applications respond perfectly